vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| (Read a discussion of this problem a few weeks ago. Didn't solve my boot situation however.) Trouble with my boot after install. Tried Grub and Lilo. Suspect I've done something wrong somewhere. Have a P3-1000. Lots of ordinary hardware that has worked pretty well with many other distros. Downloaded the correct iso I'm pretty sure. Am keen to try Gentoo. Using the genkernel rather than compiling a kernel because it simplifies much of my intro to Gentoo. Tried Google but got into technical extremes. And I suspect there is a simple solution. 1) With Grub, after what looks like it's going to be a successful boot, the message is: VFS: Cannot open root device "hda3" or 00:00 Please append a correct"root=" option Kernel panic :VSF: Unable to mount root fs on 00:00 I followed the install procedure closely, changed /dev/boot to /dev/hda1 etc. Wrote my file for grub using the suggested example as a model. Got the lines where kernel is mentioned correct I think, like this one: kernel (hdo,0)/boot/kernel-2.4.20-gentoo-r5 root=/dev/hda3 Got back in using the cd and tried a few variations. Looked OK. Nice splash screen for Grub. No success. 2) With Lilo the message is, again after a nice start to the boot: USB Mass Storage suppor registered ---- Detected usb-storage hardware kernel panic: Attempted to kill init! Followed the example given in the documentation. Made sure default and label both said "gentoo". Did an /sbin/lilo. Umounted and rebooted. The previous thread suggested I read: http://forums.gentoo.org/viewtopic.php?t=74112 which I did. The problem was solved for that individual by changing the append line to this append="root=/dev/hda3 init=/linuxrc" But it changed nothing for my boot. Hope someone sees something I've missed or recognizes what the problem must be to create these two error messages. Harry |
| |||
| On Fri, 05 Sep 2003 22:17:41 -0400, Harry Ellis wrote: > (Read a discussion of this problem a few weeks ago. Didn't solve my boot > situation however.) > > Trouble with my boot after install. Tried Grub and Lilo. Suspect I've done > something wrong somewhere. Have a P3-1000. Lots of ordinary hardware that > has worked pretty well with many other distros. Downloaded the correct iso > I'm pretty sure. Am keen to try Gentoo. Using the genkernel rather than > compiling a kernel because it simplifies much of my intro to Gentoo. > > Tried Google but got into technical extremes. And I suspect there is a simple > solution. > > 1) With Grub, after what looks like it's going to be a successful boot, the > message is: > > VFS: Cannot open root device "hda3" or 00:00 > Please append a correct"root=" option > Kernel panic :VSF: Unable to mount root fs on 00:00 > > I followed the install procedure closely, changed /dev/boot to /dev/hda1 > etc. Wrote my file for grub using the suggested example as a model. Got > the lines where kernel is mentioned correct I think, like this one: > kernel (hdo,0)/boot/kernel-2.4.20-gentoo-r5 root=/dev/hda3 > > Got back in using the cd and tried a few variations. Looked OK. Nice > splash screen for Grub. No success. > > 2) With Lilo the message is, again after a nice start to the boot: > > USB Mass Storage suppor registered > ---- Detected usb-storage hardware > kernel panic: Attempted to kill init! > > Followed the example given in the documentation. Made sure default and > label both said "gentoo". Did an /sbin/lilo. Umounted and rebooted. > > The previous thread suggested I read: > http://forums.gentoo.org/viewtopic.php?t=74112 > which I did. The problem was solved for that individual by changing the > append line to this > append="root=/dev/hda3 init=/linuxrc" But it changed nothing for my boot. > > Hope someone sees something I've missed or recognizes what the problem > must be to create these two error messages. > > Harry Please post a copy of your /etc/fstab file. |
| |||
| > Please post a copy of your /etc/fstab file. Hope this has a clue for you: /etc/fstab /dev/hda1 /boot ext2 noauto,noatime 1 1 /dev/hda3 / reiserfs noatime 0 0 /dev/hda2 none swap sw 0 0 /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 Harry |
| |||
| Harry Ellis wrote: > >> Please post a copy of your /etc/fstab file. > > Hope this has a clue for you: > > /etc/fstab > > /dev/hda1 /boot ext2 noauto,noatime 1 1 > /dev/hda3 / reiserfs noatime 0 0 change to read /dev/hda3 / reiserfs notail,noatime 0 0 should fix your problem and check to ensure you've built reiserfs support into the kernel. > /dev/hda2 none swap sw 0 0 > /dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0 > > none /proc proc defaults 0 0 > none /dev/shm tmpfs defaults 0 0 > > Harry > -- Registered Linux User # 286635 |
| |||
| On Sat, 06 Sep 2003 20:40:23 +0000, Whyld-Chyld wrote: > change to read /dev/hda3 / reiserfs notail,noatime > 0 0 should fix your > problem Thanks. I did this but the reboot led to the same problem. >and check to ensure you've built reiserfs support into the kernel. When I compiled the kernel I just typed "genkernel" at the prompt as suggested by the installation documents. 1) Is there a way for me to check that reiserfs support is built into the kernel? And 2) If I have to recompile the kernel (iffy territory for me!) is there a way to keep everything the same except to add this one element of reiserfs support? I ask because when the cd boots, it seems to find my hardware quite nicely, and my other experience with recompiling a kernel with a different distro left my OS in a shambles. My errors no doubt, but still.... Maybe that could be some learning for later in my linux career Harry |
| |||
| On Sun, 07 Sep 2003 03:33:46 +0000, Insom wrote: > > I had the same error, seems when you remove the line in lilo that turns on > the ramdrive the problem goes away. > ~Josh Josh, did you remove the entire line, or just change to "hda3"? I changed it as suggested in an article and it didn't fix the problem. Are you suggesting if I remove the entire line (#) it should work? Harry |
| |||
| Are you > suggesting if I remove the entire line (#) it should work? > > Harry I did comment out the line with # and now I have a lilo boot that works and a "functioning" kernel. Still lots to do - network for example. Thanks to the two of you for your concern and help. Time for a beer. Harry |
| |||
| Op Fri, 05 Sep 2003 22:17:41 -0400, schreef Harry Ellis: [snip] > USB Mass Storage suppor registered > ---- Detected usb-storage hardware > kernel panic: Attempted to kill init! I had the same problem using genkernel. When I compiled the kernel myself everything worked out fine. [snip] Kind regards, -- Jo Vermeulen Student Computer Science at the tUL email: jo@lumumba.luc.ac.be www: http://lumumba.luc.ac.be/jo |
| ||||
| On Sun, 07 Sep 2003 23:33:02 +0200, Jo Vermeulen wrote: > > I had the same problem using genkernel. When I compiled the kernel myself > everything worked out fine. Just out of curiosity, did you do the compiling after the install was completed and you had a boot (as I have now) or did you redo the install? Harry |