repdeck Posted October 29, 2004 Report Share Posted October 29, 2004 I get the following error message each time I try to boot the kernel I compiled. Kernel panic: VFS: Unable to mount root fs on hda1" I compiled the kernel (2.6.3-16) on my computer following instructions I found on a website. How can I fix this problem? Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted October 30, 2004 Report Share Posted October 30, 2004 Ok. Let's troubleshoot this. Can you boot to another kernel? If so, that's great. If you could post the output of the following commands it would be great: ls -l /boot cat /etc/lilo.conf This way we could troubleshoot the issue a bit more. My guess is that it's something easy to fix, but overlooked. We all do it. Quote Link to comment Share on other sites More sharing options...
repdeck Posted October 30, 2004 Author Report Share Posted October 30, 2004 Here are the results: ls -l /boot total 14336 -rw-r--r-- 1 root root 512 Sep 4 13:36 boot.0300 lrwxrwxrwx 1 root root 17 Oct 29 19:58 config -> config-2.6.3-7mdk -rw-r--r-- 1 root root 54087 Mar 17 2004 config-2.6.3-7mdk -rw-r--r-- 1 root root 5032 Feb 19 2004 diag1.img -rw-r--r-- 1 root root 16796 Feb 19 2004 diag2.img drwxr-xr-x 2 root root 4096 Sep 4 13:14 grub/ -rw-r--r-- 1 root root 342684 Sep 20 20:07 initrd-2.6.3-7mdk.img lrwxrwxrwx 1 root root 21 Sep 4 13:36 initrd.img -> initrd-2.6.3-7mdk.img -rw-r--r-- 1 root root 341083 Sep 27 19:26 initrd-win4lin-2.6.3-7mdk.img lrwxrwxrwx 1 root root 29 Sep 27 19:26 initrd-win4lin.img -> initrd-win4lin-2.6.3-7mdk.img lrwxrwxrwx 1 root root 25 Oct 29 19:58 kernel.h -> /boot/kernel.h-2.6.3-7mdk -rw-r--r-- 1 root root 537 Sep 4 17:50 kernel.h-2.6.3-7mdk -rw------- 1 root root 577536 Oct 29 15:06 map lrwxrwxrwx 1 root root 15 Oct 27 07:18 message -> message-graphic -rw-r--r-- 1 root root 442273 Sep 27 19:26 message-graphic -rw-r--r-- 1 root root 116 Sep 4 13:41 message-text lrwxrwxrwx 1 root root 21 Sep 22 16:47 System.map -> System.map-2.6.3-7mdk -rw-r--r-- 1 root root 898908 Mar 17 2004 System.map-2.6.3-7mdk lrwxrwxrwx 1 root root 21 Sep 4 17:49 System.map.pre-win4lin -> System.map-2.6.3-7mdk -rw-r--r-- 1 root root 1009485 Oct 19 12:17 System.map.win4lin -rw-r--r-- 1 root root 743434 Apr 2 2004 System.map.win4lin-2.6.3-7mdk -rw-r--r-- 1 root root 256 Sep 4 13:36 us.klt -rw-r--r-- 1 root root 1440700 Sep 27 20:29 vmkernel lrwxrwxrwx 1 root root 18 Sep 4 13:36 vmlinuz -> vmlinuz-2.6.3-7mdk -rw-r--r-- 1 root root 1440198 Mar 17 2004 vmlinuz-2.6.3-7mdk -rw-r--r-- 1 root root 1440704 Oct 21 21:05 vmwareker -rw-r--r-- 1 root root 1407493 Oct 27 07:14 vmwarekers -rw-r--r-- 1 root root 3042368 Oct 19 12:17 win4lin -rw-r--r-- 1 root root 1428330 Apr 2 2004 win4lin-2.6.3-7mdk cat /etc/lilo.conf # File generated by DrakX/drakboot # WARNING: do not forget to run lilo after modifying this file boot=/dev/hda map=/boot/map default="Mandrake_10.0" keytable=/boot/us.klt prompt nowarn timeout=1000 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz label="Mandrake_10.0" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount acpi=ht splash=silent mem=256M" vga=788 read-only other=/dev/hda2 label="WindowsXp" table=/dev/hda image=/boot/win4lin-2.6.3-7mdk label="Mandrake_10_Win4lin" root=/dev/hda1 initrd=/boot/initrd-win4lin-2.6.3-7mdk.img append="devfs=mount acpi=ht splash=silent mem=256M" vga=788 read-only image=/boot/vmkernel label="Linux_2.6.3-16_Vmware" root=/dev/hda1 append="mem=256M" read-only image=/boot/win4lin label="Win4Lin_Generic_Kernel" root=/dev/hda1 append="mem=256M" read-only image=/boot/vmwareker label="Vmwaresource" root=/dev/hda1 append="mem=256M" read-only image=/boot/vmwarekers label="Vmware_Kernel_Compiled_Oct27" root=/dev/hda1 read-only Quote Link to comment Share on other sites More sharing options...
Guest Franzmaximilian Posted November 8, 2004 Report Share Posted November 8, 2004 It seems to be a well known and much discussed item. I'm facing it as well. Searched with Google and found TONS of info about it. Well, too much information is sometimes worst than no information! Hard to say which is good stuff and what is useless crap. By the way i tried some suggestions I found around on message boards without any success. My version of the same problem is: Kernel Panic: VFS: Unable to mount fs on unknown block(3,3) Now my two questions: Anything specifically Mandrake related with this problem? Which is the best source of info about solving this problem? Thanks you all Franz Energia Nucleare ??? No, Grappa !!! Quote Link to comment Share on other sites More sharing options...
Sherpa Posted November 9, 2004 Report Share Posted November 9, 2004 i had the same problem with kernel 2.6.9 just recently, i fixed it by saving my .config file, then erasing all traces of the kernel then recompileing it using the .config settings file Quote Link to comment Share on other sites More sharing options...
Leo Posted November 15, 2004 Report Share Posted November 15, 2004 I think this may be the same issue as this one and may we ll be solved by compiling in CONFIG_MSDOS_PARTITION from the filesystems menu (I think) Does this help? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.