Re: Kernel panic: VFS: Unable to mount root fs on 01:00
> As my subject line indicates, I'm getting the diagnostic: > > Kernel panic: VFS: Unable to mount root fs on 01:00 i would say the #1 cause of this is lack of support for the disk controller which the root drive is hooked to compiled into the kernel(it can't be a module). first thing to check is to see if the drive is detected on boot ...if it is we can go from there.. also make sure the filesystem your using is compiled into the kernel. nate
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Make sure that you have compiled the ide and ext2 into the kernel and not just made them loadable mods. Xeno Campanoli wrote: Subject: Kernel panic: VFS: Unable to mount root fs on 01:00 From: Xeno Campanoli <[EMAIL PROTECTED]> Date: Thu, 29 Nov 2001 14:57:45 -0800 To: debian-user@lists.debian.org As my subject line indicates, I'm getting the diagnostic: Kernel panic: VFS: Unable to mount root fs on 01:00when I try to boot up with my home grown kernel. I've tried severalthings with lilo on this, but I'm stumped. rdev indicates the rootpartition is /dev/hda1, which is what I expect, and I seem to have goodlilo entries, as follows:image=/vmlinuzlabel=Linuxread-onlyinitrd=/boot/initrdand in fact with the dist kernel this lilo entry works fine, but withthe one I get with make bzImage I get stuck on boot as stated. Cansomeone point me to a specific doc to read on this problem, or is mymistake obvious?-- http://www.eskimo.com/~xeno[EMAIL PROTECTED]-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
> As my subject line indicates, I'm getting the diagnostic: > > Kernel panic: VFS: Unable to mount root fs on 01:00 > > when I try to boot up with my home grown kernel. I've tried several > things with lilo on this, but I'm stumped. rdev indicates the root > partition is /dev/hda1, which is what I expect, and I seem to have good > lilo entries, as follows: > > image=/vmlinuz > label=Linux > read-only > initrd=/boot/initrd > > and in fact with the dist kernel this lilo entry works fine, but with > the one I get with make bzImage I get stuck on boot as stated. Can > someone point me to a specific doc to read on this problem, or is my > mistake obvious? > -- > http://www.eskimo.com/~xeno > [EMAIL PROTECTED] > The mistake is not obvious to me. Just guessing: (1) Are you sure you need the initrd line? Do you actually have /boot/initrd? This line is not shown in /usr/share/doc/lilo/examples/conf.sample. (2) Have you run lilo after you installed the new kernel and before you rebooted? (3) Does the fs driver for the root device in the new kernel compiled as a module? (4) Could it be that you have not installed the new kernel properly? One way to avoid this is to use Debian kernel-package. -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Shaul Karl wrote: > > > As my subject line indicates, I'm getting the diagnostic: > > > > Kernel panic: VFS: Unable to mount root fs on 01:00 > > > > when I try to boot up with my home grown kernel. I've tried several > > things with lilo on this, but I'm stumped. rdev indicates the root > > partition is /dev/hda1, which is what I expect, and I seem to have good > > lilo entries, as follows: > > > > image=/vmlinuz > > label=Linux > > read-only > > initrd=/boot/initrd Okay, you were right about initrd. I took that out and it works. Thank you. Now however I have another problem with two of my four NIC drivers not showing up in dmesg. I'll start another thread for that one. Sincerely, Xeno > -- > > Shaul Karl > email: shaulka (replace these parenthesis with @) bezeqint, >delete the comma and the white space characters and add .net -- http://www.eskimo.com/~xeno [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
--- Xeno Campanoli <[EMAIL PROTECTED]> wrote: > Shaul Karl wrote: > > > > > As my subject line indicates, I'm getting the > diagnostic: > > > > > > Kernel panic: VFS: Unable to mount root fs > on 01:00 > > > > > > when I try to boot up with my home grown kernel. > I've tried several > > > things with lilo on this, but I'm stumped. rdev > indicates the root > > > partition is /dev/hda1, which is what I expect, > and I seem to have good > > > lilo entries, as follows: > > > > > > image=/vmlinuz > > > label=Linux > > > read-only > > > initrd=/boot/initrd > > Okay, you were right about initrd. I took that > out and it > works. Thank you. > <> Now, I'm really confused. I haven't been able to get any of the 2.4.x debian kernel packages to boot and everything I had read previously in the list archives indicated that the initrd line was necessary for 2.4.x kernels. I never had any problems with 2.0.x or 2.2.x kernels. = - [EMAIL PROTECTED] Hacking is a "Good Thing!" See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
Thus spake Charles Baker: > > --- Xeno Campanoli <[EMAIL PROTECTED]> wrote: > > Shaul Karl wrote: > > > > > > > As my subject line indicates, I'm getting the > > diagnostic: > > > > > > > > Kernel panic: VFS: Unable to mount root fs > > on 01:00 > > > > > > > > when I try to boot up with my home grown kernel. > > I've tried several > > > > things with lilo on this, but I'm stumped. rdev > > indicates the root > > > > partition is /dev/hda1, which is what I expect, > > and I seem to have good > > > > lilo entries, as follows: > > > > > > > > image=/vmlinuz > > > > label=Linux > > > > read-only > > > > initrd=/boot/initrd > > > > Okay, you were right about initrd. I took that > > out and it > > works. Thank you. > > > <> > > Now, I'm really confused. I haven't been able to get > any of the 2.4.x debian kernel packages to boot and > everything I had read previously in the list archives > indicated that the initrd line was necessary for 2.4.x > kernels. I never had any problems with 2.0.x or 2.2.x > kernels. Not _necessary_ but an option. I personally don't use the initrd method with my kernels, as I found the boost in boot time to be negligable and therefor more trouble than it was worth, but I don't use the make-kpkg method, it may be easier. You can use it or not, is what I have found - neither is 'The Right Way'(TM) although the make-kpkg way is 'The Dbian Way'(TM) and I am _not_ advising against, just throwing in my 2ยข. HTH, Steve -- Boucher's Observation: He who blows his own horn always plays the music several octaves higher than originally written. pgpHAnpAO0dDX.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
> > --- Xeno Campanoli <[EMAIL PROTECTED]> wrote: > > Shaul Karl wrote: > > > > > > > As my subject line indicates, I'm getting the > > diagnostic: > > > > > > > > Kernel panic: VFS: Unable to mount root fs > > on 01:00 > > > > > > > > when I try to boot up with my home grown kernel. > > I've tried several > > > > things with lilo on this, but I'm stumped. rdev > > indicates the root > > > > partition is /dev/hda1, which is what I expect, > > and I seem to have good > > > > lilo entries, as follows: > > > > > > > > image=/vmlinuz > > > > label=Linux > > > > read-only > > > > initrd=/boot/initrd > > > > Okay, you were right about initrd. I took that > > out and it > > works. Thank you. > > > <> > > Now, I'm really confused. I haven't been able to get > any of the 2.4.x debian kernel packages to boot and > everything I had read previously in the list archives > indicated that the initrd line was necessary for 2.4.x > kernels. I never had any problems with 2.0.x or 2.2.x > kernels. > I never tried a 2.4.x kernel and I do not know if there is a default configuration for the 2.4.x debian kernel packages. In case there is none, could it be that you are expected to have ram disk support when configuring the 2.4.x debian kernel? And since you were asking, why won't you add more details about what you have done and where does the booting process stop? > > = > - > [EMAIL PROTECTED] > Hacking is a "Good Thing!" > See http://www.tuxedo.org/~esr/faqs/hacker-howto.html > > __ > Do You Yahoo!? > Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. > http://geocities.yahoo.com/ps/info1 -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
--- Shaul Karl <[EMAIL PROTECTED]> wrote: > > > > --- Xeno Campanoli <[EMAIL PROTECTED]> wrote: > > > Shaul Karl wrote: > > > > > > > > > As my subject line indicates, I'm getting > the > > > diagnostic: > > > > > > > > > > Kernel panic: VFS: Unable to mount > root fs > > > on 01:00 > > > > > > > > > > when I try to boot up with my home grown > kernel. > > > I've tried several > > > > > things with lilo on this, but I'm stumped. > rdev > > > indicates the root > > > > > partition is /dev/hda1, which is what I > expect, > > > and I seem to have good > > > > > lilo entries, as follows: > > > > > > > > > > image=/vmlinuz > > > > > label=Linux > > > > > read-only > > > > > initrd=/boot/initrd > > > > > > Okay, you were right about initrd. I took > that > > > out and it > > > works. Thank you. > > > > > <> > > > > Now, I'm really confused. I haven't been able to > get > > any of the 2.4.x debian kernel packages to boot > and > > everything I had read previously in the list > archives > > indicated that the initrd line was necessary for > 2.4.x > > kernels. I never had any problems with 2.0.x or > 2.2.x > > kernels. > > > > > I never tried a 2.4.x kernel and I do not know if > there is a default > configuration for the 2.4.x debian kernel packages. > In case there is > none, could it be that you are expected to have ram > disk support when > configuring the 2.4.x debian kernel? > > And since you were asking, why won't you add more > details about what > you have done and where does the booting process > stop? > I will when I get home this evening. I've been down this road on the list before with no relief. I've been too busy doing some other stuff to go on a "I've got to make this 2.4.x kernel work" type binge, especially since my 2.2.x kernel is working nicely. I did however provide quite a few details on one of my attempts. In fact here is the message in the archives: http://lists.debian.org/debian-user/2001/debian-user-200110/msg00635.html I have since tried with a 2.4.10 and 2.4.12 kernel with the same results, and then I had problems with modules as well on the 2.4.12. But like I said, I will try again tonight and give more details. BTW, these problems were with the stock debian kernel packages. I haven't even tried to compile 2.4.x for myself yet using the traditional methods or the debian way. = - [EMAIL PROTECTED] Hacking is a "Good Thing!" See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
> > > <> > > > > > > Now, I'm really confused. I haven't been able to > > get > > > any of the 2.4.x debian kernel packages to boot > > and > > > everything I had read previously in the list > > archives > > > indicated that the initrd line was necessary for > > 2.4.x > > > kernels. I never had any problems with 2.0.x or > > 2.2.x > > > kernels. > > > > > > > > > I never tried a 2.4.x kernel and I do not know if > > there is a default > > configuration for the 2.4.x debian kernel > packages. > > In case there is > > none, could it be that you are expected to have > ram > > disk support when > > configuring the 2.4.x debian kernel? > > > > And since you were asking, why won't you add more > > details about what > > you have done and where does the booting process > > stop? > > > > I will when I get home this evening. I've been down > this road on the list before with no relief. I've > been > too busy doing some other stuff to go on a "I've got > to make this 2.4.x kernel work" type binge, > especially > since my 2.2.x kernel is working nicely. I did > however > provide quite a few details on one of my attempts. > In > fact here is the message in the archives: > > http://lists.debian.org/debian-user/2001/debian-user-200110/msg00635.html > > I have since tried with a 2.4.10 and 2.4.12 kernel > with the same results, and then I had problems with > modules as well on the 2.4.12. But like I said, I > will > try again tonight and give more details. BTW, these > problems were with the stock debian kernel packages. > I > haven't even tried to compile 2.4.x for myself yet > using the traditional methods or the debian way. Dell Latitude CPi D300XT 128MB Ram PII 300Mhz lilo.conf vga=1 append="apm=on" default=Linux22 # kernel 2.4.12 image=/vmlinuz initrd=/boot/initrd label=LinuxNew read-only # kernel 2.4.10 image=/vmlinuz.old initrd=/boot/initrd-2.4.10-686 label=LinuxOld read-only # kernel 2.2.18pre image=/vmlinuz.2.2 label=Linux22 read-only Well, shoot. I cleaned up my lilo.conf, found a mistake when going over it this time and presto, the 2.4.12 kernel booted and the modules loaded but not pcmcia. Well, I take that back, the pcmcia_core module loaded, but not the module for my pcmcia NIC. In fact, here are the modules loaded by 2.2.18pre21 af_packet xirc2ps_cs serial_cs ds i82365 pcmcia_core serial nfs lockd sunrpc smbfs vfat unix And here are the modules loaded by 2.4.12 pcmcia_core nfs lockd sunrpc smbfs vfat fat rtc unix ide-disk ide-probe-mod ide-mod ext2 I tried to insmod i82365.o from /lib/modules/2.4.12-686/pcmcia and got "i82365.o: unresolved symbol isapnp_find_dev_R7651deff" . I got similar messages when try to load the other missing modules. = - [EMAIL PROTECTED] Hacking is a "Good Thing!" See http://www.tuxedo.org/~esr/faqs/hacker-howto.html __ Do You Yahoo!? Buy the perfect holiday gifts at Yahoo! Shopping. http://shopping.yahoo.com
Re: Kernel panic: VFS: Unable to mount root fs on 01:00
> > Dell Latitude CPi D300XT 128MB Ram PII 300Mhz > > lilo.conf > > vga=1 > append="apm=on" > default=Linux22 > > # kernel 2.4.12 > image=/vmlinuz > initrd=/boot/initrd > label=LinuxNew > read-only > > # kernel 2.4.10 > image=/vmlinuz.old > initrd=/boot/initrd-2.4.10-686 > label=LinuxOld > read-only > > # kernel 2.2.18pre > image=/vmlinuz.2.2 > label=Linux22 > read-only > > > Well, shoot. I cleaned up my lilo.conf, found a > mistake when going over it this time and presto, the > 2.4.12 kernel booted and the modules loaded but not > pcmcia. Well, I take that back, the pcmcia_core module > loaded, but not the module for my pcmcia NIC. > > In fact, here are the modules loaded by 2.2.18pre21 > > af_packet > xirc2ps_cs > serial_cs > ds > i82365 > pcmcia_core > serial > nfs > lockd > sunrpc > smbfs > vfat > unix > > And here are the modules loaded by 2.4.12 > > pcmcia_core > nfs > lockd > sunrpc > smbfs > vfat > fat > rtc > unix > ide-disk > ide-probe-mod > ide-mod > ext2 > > I tried to insmod i82365.o from > /lib/modules/2.4.12-686/pcmcia and got "i82365.o: > unresolved symbol isapnp_find_dev_R7651deff" . I got > similar messages when try to load the other missing > modules. > > = > - > [EMAIL PROTECTED] > Hacking is a "Good Thing!" > See http://www.tuxedo.org/~esr/faqs/hacker-howto.html > No sure but looks like something to do with the fact that 2.4.x has Plug and Play support built in. Is there some module or kernel config option like isapnp or pnp? Maybe you got the isapnp tools which should be removed or configured otherwise for a 2.4.x kernels? Isn't there any reference in the kernel documentation? Perhaps there is a reference in the isapnp package docs? My 2.2.19pre17 has files that looks related: [14:33:07 tmp]$ ls /lib/modules/2.2.19pre17/*pnp* /lib/modules/2.2.19pre17/modules.isapnpmap /lib/modules/2.2.19pre17/modules.pnpbiosmap [14:34:14 tmp]$ Yet I have never touched them and I do not know how they are related. Hopefully someone else on debian-user can fill in the missing parts better then I can. -- Shaul Karl email: shaulka (replace these parenthesis with @) bezeqint, delete the comma and the white space characters and add .net
