Kernel Panic: not syncing: VFS error while booting

Post in this forum for problems at boot time, if there was no problem for burning the disc. For example can't find the CD, or strange errors when you press enter at the very first prompt.
Post Reply
mgbt1623
Posts: 2
Joined: 12 Sep 2007, 20:40

Kernel Panic: not syncing: VFS error while booting

Post by mgbt1623 » 12 Sep 2007, 20:57

Hi,

I am trying to rescue a crashed Windows XP system in my laptop.

After downloading the SystemRescueCD software, I tested the CD on another XP machine - The cd is booting and working correctly.

When the same CD was run on the laptop, it gave the following error during bootup:

(last few lines)

md: Autodetecting RAID arrays
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
crc error
UDF-fs: No partition found (1)
List of all partitions:
0300 39070080 hda driver: ide-disk
0301 39062016 hda1
1600 127700 hdc driver: ide-cdrom
No filesystem could mount root, tried (reiserfs reiser4 ext3 ext2 cramfs squashfs minix msdos vfat iso9660 ntfs romfs fuseblk udf jfs xfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (1,0)
[The system stops here]

The drive has data, I could boot with ntfsboot, a dos for NTFS program and can see the files in 8.3 format in the drive (but do not know how to access them/transfer to another machine)

The system is standard issue Compaq Presario V2000 with CPU: AMD Turion 64) with 768 MB RAM, bootable CDROM etc.

Similar problems encountered (same error message) with latest Knoppix, Gentoo distributions.

Questions:

a. Is there some option I should be using (other than the standard - default) during bootup? (for example to bypass hd detection during the load and then to mount it later?

b. Any other workarounds?

c. Any insight/pointers to the reason for this error? - Could it be due to the fact that the laptop has 64 bit processor (Turion 64)? (the tested machines are all non 64 bit processors.)

TIA

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 12 Sep 2007, 21:09

The interesting info is "crc error". If your CD is good, it means that's an hardware problem, or this hardware cannot read this kind of CD well. Try another disc, but if you say you have the same problem with other distros, I think you have to change your CD drive.

Try booting with the USB key, or with the new "PXE via network" option available on version 0.4.0-beta1 and newer

Try disabling the DMA with "rescuecd ide=nodma". It's not related to the 64bits.

mgbt1623
Posts: 2
Joined: 12 Sep 2007, 20:40

Follow-up - more data while trying network boot

Post by mgbt1623 » 13 Sep 2007, 00:12

Thanks fdupoux for your reply. I appreciate it very much.

I tried setting up the PXE server with the latest 0.4.x beta. Was able to set up the server machines successfully. On booting the laptop via the Lan, here is what I saw:

ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright Intel etc
Using IPI shortcut mode
eth0: link up, 100 Mbps, full-duplex, lpa 0x45E1
Sending DHCP Requests ., OK
IP-Config: Got DHCP answer from 192.168.3.45, my address is 192.168.3.100
IP-Config: Complete:
device=eth0, addr=192.168.3.100, mask=255.255.255.0, gw=192.168.3.254,
host=192.168.3.100, domain=, nis-domain=(none),
bootserver=192.168.3.45, rootserver=192.168.3.45,rootpath=
md: Autodetecting RAID arrays
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
crc error
VFS: Cannot open root device "<NULL>" or unknown-block(8,9)
Please append a correct "root=" boot option; here are the available partitions:
0300 39070080 hda driver: ide-disk
0301 39062016 hda1
1600 127700 hdc driver: ide-cdrom
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,9)
[The system stops here]

The system is able to get the program from the network via DHCP, but still hangs.

I have tried "rescuecd ide=nodma" and "root=ide-cdrom", "root=/dev/hdc" options, similar problem encountered

Any suggestion to try is appreciated.

Is there an option to load the program without trying to access any local hard drives - I could not find the option listed.

Also, I agree with you that "crc error" after RAMdisk setup stands out as a sore thumb and so it looks like it is not able to setup the RAMDISKs or the data is corrupted while setting up the RAMDISK, But isn't the system supposed to do a RAM test and block out bad memory location, if any? I am still not sure what and why I am seeing the "crc error" message at that point. Is there a way to force the system to provide more diagnostics at this point?

I have not been able to get the USB method working - But if it works, could we then set up the root partition in the r/wable USB drive instead of the RAMDISK? Then, on exit, the root partition will still be there and can be investigated.

TIA

Post Reply