Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
On Tue, Apr 20, 2004 at 03:10:58PM +0200, Philippe Dhont (Sea-ro) said > My new kernel is compiled with ext2, ext3 and the others also. > My filesystem is ext3. In the kernel or as modules? They have to be builtin for it boot. > When i reboot my system i can choose to boot the debian2.6.5 but in the > boot process i get this: > > Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0) Did you include support for your ide/scsi controller IN the kernel, too? -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: corporate security Bosnia Syria ICE Verisign SRI Nazi signature.asc Description: Digital signature
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0)
Philippe Dhont (Sea-ro) wrote: Hi, I installed debian SARGE with grub and everything works fine. I downloaded the latest stable kernel, compiled everything and put the boot lines in the grub configuration Menu.lst This was before: Title Debian 2.4.25 Root (hd0,0) Kernel /vmlinuz-2.4.25-1-386 root=/dev/hda3 ro Initrd /initrd.img-2.4.25-1.-386 Savedefault Boot THIS IS NOW: Title Debian 2.4.25 Root (hd0,0) Kernel /vmlinuz-2.4.25-1-386 root=/dev/hda3 ro Initrd /initrd.img-2.4.25-1.-386 Savedefault Boot ***I ADDED THE FOLLOWING*** Title Debian.2.6.5 Root (hd0,0) Kernel /bzImage2.6.5 root=/dev/hda3 ro Savedefault Boot My new kernel is compiled with ext2, ext3 and the others also. My filesystem is ext3. When i reboot my system i can choose to boot the debian2.6.5 but in the boot process i get this: Kernel Panic: VFS: Unable to mount root fs on unknown-block(0,0) How can i fix it so that i can boot with my 2.6.5 ?? Is your kernel really at /bzImage2.6.5 ? Does it have an initrd that you forgot to specify? -Roberto Sanchez signature.asc Description: OpenPGP digital signature
Re: Kernel panic: VFS: Unable to mount root fs (Solved)
On Tuesday 26 August 2003 14:56, Joris Huizer wrote: > --- Alphonse Ogulla <[EMAIL PROTECTED]> wrote: > > Hi all, > > Just compiled kernel 2.4.21 but cannot boot it > > despite creating the initrd > > image and respective links in / to files in /boot. > > The last 5 lines printed on screen before hang-up > > are printed below. > > > > RAMDISK: Couldn't find valid RAM disk image starting > > at 0. > > Freeing initrd memory: 2664k freed > > VFS: Cannot open root device "301" or 03:01 > > Please append a correct "root=" boot option > > Kernel panic: VFS: Unable to mount root fs on 03:01 > > > > Passing root=/dev/hda1 to lilo at boot time did not > > bear fruit. > > Created initrd as follows: > > # mkinitrd -o /boot/initrd.img-2.4.21 > > /lib/modules/2.4.21 > > > > Added the following lines in lilo.conf before > > running lilo. > > . > > image=/vmlinuz-2.4.21 initrd=/initrd.img-2.4.21 > > label=2.4.21 > > root=/dev/hda1 > > read-only > > > > Grateful for any assistance in resolving this > > difficulty. > > > > -- > > Alphonse Ogulla > > Nairobi, Kenya > > Check that: > > - under "File systems", "Second extended fs support" > has "y" > - under "Block devices", "Normal PC floppy disk > support" has "y" > - under "ATA/IDE/MFM/RLL support", "IDE, ATA and > ATAPI Block devices" has "y" >- under submenu "IDE, ATA and ATAPI Block Devices", >"Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy > support" and "Include IDE/ATA-2 DISK support" have "y" > clicked. > > This helped me to solve similar problems - I hope > it'll help you too Yes it did. Coming to think of it, make exited with an error during the final step of kernel compilation - "make modules_install" because of dependancy issues with some *pmcia* and *mtd* modules. Therefore the resulting initrd.img created from /lib/modules/2.4.21 directory must have been lacking in some aspect. Building disk & filesystem drivers directly into the kernel as per above instructions and forgetting about initrd.img did the trick. atlas:~# uname -a Linux atlas 2.4.21 #3 Tue Aug 26 20:01:03 EAT 2003 i686 unknown Thanks and regards -- Alphonse Ogulla Nairobi, Kenya -- 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 Tue, Aug 26, 2003 at 12:40:44PM +0300, Alphonse Ogulla wrote: | Just compiled kernel 2.4.21 but cannot boot it | VFS: Cannot open root device "301" or 03:01 You probably forgot to include the driver for your hard disk when you built the kernel. Follow Joris' suggestion for enabling the driver for the most common type of disks. (BTW, I've done this before. It's a good way to learn to include the driver :-)) -D -- (A)bort, (R)etry, (T)ake down entire network? http://dman13.dyndns.org/~dman/ pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
--- Alphonse Ogulla <[EMAIL PROTECTED]> wrote: > Hi all, > Just compiled kernel 2.4.21 but cannot boot it > despite creating the initrd > image and respective links in / to files in /boot. > The last 5 lines printed on screen before hang-up > are printed below. > > RAMDISK: Couldn't find valid RAM disk image starting > at 0. > Freeing initrd memory: 2664k freed > VFS: Cannot open root device "301" or 03:01 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 03:01 > > Passing root=/dev/hda1 to lilo at boot time did not > bear fruit. > Created initrd as follows: > # mkinitrd -o /boot/initrd.img-2.4.21 > /lib/modules/2.4.21 > > Added the following lines in lilo.conf before > running lilo. > . > image=/vmlinuz-2.4.21 initrd=/initrd.img-2.4.21 > label=2.4.21 > root=/dev/hda1 > read-only > > Grateful for any assistance in resolving this > difficulty. > > -- > Alphonse Ogulla > Nairobi, Kenya > Check that: - under "File systems", "Second extended fs support" has "y" - under "Block devices", "Normal PC floppy disk support" has "y" - under "ATA/IDE/MFM/RLL support", "IDE, ATA and ATAPI Block devices" has "y" - under submenu "IDE, ATA and ATAPI Block Devices", "Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support" and "Include IDE/ATA-2 DISK support" have "y" clicked. This helped me to solve similar problems - I hope it'll help you too Joris __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- 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 Fri, Dec 06, 2002 at 08:26:48AM -0600, Shyamal Prasad wrote: > Paul, > > To be fair, you should point out that this is an opinion that run's > contrary to how Debian's 2.4 kernels are packaged. Yes, I realise this, however, when compiling one's own kernel from the kernel archive (oppose to the debian source) then it's easier to do it my way. People who are new to building kernels should do it the Debian way for simplicity, and newbies should stick to the kernel-image packages until the process makes sense without too much additional assistance. -- .''`. Baloo <[EMAIL PROTECTED]> : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17568/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
In article <20021206045426.GA22017@ursine>, Paul Johnson wrote: > > Wait, are you trying to boot a kernel that doesn't have ext3 compiled > in on a system whose /etc/fstab specifies the / partition as being > ext3? Nope, ext2/ext3 have been included in the vmlinuz-image all along. I'll throw in another question here: from /etc/fstab: /dev/hdc6 / ext2errors=remount-ro 0 1 from dmesg: kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. ... EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,6), internal journal I know I initially created / as an ext2 partition, and I can't recall having converted it to ext3 (though I could be wrong, I've certainly thought about it, I just can't recall having actually done it yet), I also just tried adriot3:~# mount -v -t ext3 -o remount /dev/hdc6 / /dev/hdc6 on / type ext3 (rw) adriot3:~# mount /dev/hdc6 on / type ext2 (rw) So why the mount as EXT3 while booting? Anyway, I've now got 2.4.20, plus the patches I wanted, up and running fine, and hopefully this won't be an issue again. It was probably some silly mistake on my part. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
Just a thought, but do you have ide and/or scsi as modules instead of compiled into the kernel? You will get this message if the kernel can't mount the root partition because it doesn't have the necessary drivers to talk to the disk on which the root partition sits. That is, if / is on an ide disk you need ide compiled into the kernel, not a module. ap -- Andrew J Perrin - http://www.unc.edu/~aperrin Assistant Professor of Sociology, U of North Carolina, Chapel Hill [EMAIL PROTECTED] * andrew_perrin (at) unc.edu On Thu, 5 Dec 2002, Stig Are M. Botterli wrote: > In article <[EMAIL PROTECTED]>, Klaus Imgrund wrote: > > On Thu, 05 Dec 2002 15:16:29 + > >> > > I had kernels bigger than 1 MB - no problem. > > It would help if you remember what things you configured as modules. > > Unfortunately, I don't. > > > If you got i.e a driver for the wrong sound card compiled in the kernel > > it can give you a kernel panic.If it is compiled as module the module > > just doesn't load. > > Perhaps, but I doubt anything like that can cause this particular kernel > panic. > > Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'll make my > changes one by one, so that if I'm hit by this again I will hopefully be > able to pinpoint what introduced it. > > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [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
"Paul" == Paul Johnson <[EMAIL PROTECTED]> writes: Paul> Support for your root device hardware and filesystem should Paul> be part of your kernel for maximum ease and reliability. Paul> Pretty much everything else that can be moduled out should. Paul, To be fair, you should point out that this is an opinion that run's contrary to how Debian's 2.4 kernels are packaged. ~$ uname -r 2.4.18-k7 ~$ /sbin/lsmod | grep ^ext ext2 30848 1 (autoclean) ext3 57248 6 (autoclean) The Debian kernels do provide for "maximum ease and reliability" IMHO :-) Cheers! Shyamal -- 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 Sat, Dec 07, 2002 at 12:38:37AM +1300, Richard Hector wrote: > It is? I thought that was the usual way to do it (with 2.4 kernels, > anyway) ... should I look at recompiling my kernel with my SCSI drivers > built in instead? Or are you specifically referring to filesystem > drivers rather than all drivers necessary to mount the filesystem? Support for your root device hardware and filesystem should be part of your kernel for maximum ease and reliability. Pretty much everything else that can be moduled out should. -- .''`. Baloo <[EMAIL PROTECTED]> : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17420/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
On Fri, 2002-12-06 at 17:54, Paul Johnson wrote: > You can't get away with having your root partition being a > filesystem for which you must load a module to support. Unless you > use initrd, but that's messy and not very failproof. It is? I thought that was the usual way to do it (with 2.4 kernels, anyway) ... should I look at recompiling my kernel with my SCSI drivers built in instead? Or are you specifically referring to filesystem drivers rather than all drivers necessary to mount the filesystem? Richard -- 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 Thu, Dec 05, 2002 at 07:10:42PM +, Stig Are M. Botterli wrote: > > I had kernels bigger than 1 MB - no problem. > > It would help if you remember what things you configured as modules. > > Unfortunately, I don't. Wait, are you trying to boot a kernel that doesn't have ext3 compiled in on a system whose /etc/fstab specifies the / partition as being ext3? You can't get away with having your root partition being a filesystem for which you must load a module to support. Unless you use initrd, but that's messy and not very failproof. -- .''`. Baloo <[EMAIL PROTECTED]> : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17357/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs
In article <[EMAIL PROTECTED]>, Klaus Imgrund wrote: > On Thu, 05 Dec 2002 15:16:29 + >> > I had kernels bigger than 1 MB - no problem. > It would help if you remember what things you configured as modules. Unfortunately, I don't. > If you got i.e a driver for the wrong sound card compiled in the kernel > it can give you a kernel panic.If it is compiled as module the module > just doesn't load. Perhaps, but I doubt anything like that can cause this particular kernel panic. Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'll make my changes one by one, so that if I'm hit by this again I will hopefully be able to pinpoint what introduced it. -- 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 Thu, 05 Dec 2002 15:16:29 + "Stig Are M. Botterli" <[EMAIL PROTECTED]> wrote: > In article <20021205080347.GE7442@ursine>, Paul Johnson wrote: > > > > On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli > > wrote:> Basically, if my /boot/vmlinuz image exceeds a certain size > > (the limit se=> ems be > >> somewhere around 90 bytes), the following occurs on boot: > > > > Whoa! Huge kernel! Module some of that stuff out and it should > > help if there's some hidden size limitation. I have a pretty big > > kernel, the bzImage is 644,225 bytes. > > I did this, and got the kernel down to 719kB. However, the exact same > thing occurs on boot (minus the three last lines, as I included NTFS- > support as a module), so a hidden size limitation is obviously not the > problem. Now I'm really wondering what actually 'solved' it for me > with 2.4.19 and 2.4.20-pre10. My 2.4.20-pre10 (+ RML's preemption > patch) image at 865kB boots, whereas an image approx. 20kB bigger > panicked, and the only thing I can recall changing was turning some > non-essential things into modules. That's why I was certain the > problem was related to the size of the kernel image. > I had kernels bigger than 1 MB - no problem. It would help if you remember what things you configured as modules. If you got i.e a driver for the wrong sound card compiled in the kernel it can give you a kernel panic.If it is compiled as module the module just doesn't load. Have fun, Klaus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article <20021205080347.GE7442@ursine>, Paul Johnson wrote: > > On Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote: >> Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se= >> ems be >> somewhere around 90 bytes), the following occurs on boot: > > Whoa! Huge kernel! Module some of that stuff out and it should > help if there's some hidden size limitation. I have a pretty big > kernel, the bzImage is 644,225 bytes. I did this, and got the kernel down to 719kB. However, the exact same thing occurs on boot (minus the three last lines, as I included NTFS- support as a module), so a hidden size limitation is obviously not the problem. Now I'm really wondering what actually 'solved' it for me with 2.4.19 and 2.4.20-pre10. My 2.4.20-pre10 (+ RML's preemption patch) image at 865kB boots, whereas an image approx. 20kB bigger panicked, and the only thing I can recall changing was turning some non-essential things into modules. That's why I was certain the problem was related to the size of the kernel image. >> hdc6: bad access: block=3D2, count=3D2 >> end_request: I/O error, dev 16:06 (hdc), sector 2 >> EXT3-fs: Unable to read superblock >> hdc6: bad access: block=3D2, count=3D2 >> end_request: I/O error, dev 16:06 (hdc), sector 2 >> EXT2-fs: Unable to read superblock >> hdc6: bad access: block=3D0, count=3D1 >> end_request: I/O error, dev 16:06 (hdc), sector 0 >> NTFS: Reading super block failed >> Kernel panic: VFS: Unable to mount root fs on 16:06 > > Is your drive going bad? Are the filesystems OK? I've seen nothing to indicate that there's anything wrong with neither my drives nor my filesystems. The system operates fine once booted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
Paul Johnson said: > Whoa! Huge kernel! Module some of that stuff out and it should > help if there's some hidden size limitation. I have a pretty big > kernel, the bzImage is 644,225 bytes. sounds like a 2.4.x kernel. I was amazed how huge the 2.4.x kernel got. my biggest 2.2.x kernel I think is about 800kb. I built a similarly configured 2.4.20 kernel a few days ago(first successful 2.4.x run for me), and its 1.1MB! damn. but my system(ibm thinkpad t20) has no trouble booting the 1.1MB bzimage.. nate -- 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 Thu, Dec 05, 2002 at 01:04:34AM +, Stig Are M. Botterli wrote: > Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be > somewhere around 90 bytes), the following occurs on boot: Whoa! Huge kernel! Module some of that stuff out and it should help if there's some hidden size limitation. I have a pretty big kernel, the bzImage is 644,225 bytes. > hdc6: bad access: block=2, count=2 > end_request: I/O error, dev 16:06 (hdc), sector 2 > EXT3-fs: Unable to read superblock > hdc6: bad access: block=2, count=2 > end_request: I/O error, dev 16:06 (hdc), sector 2 > EXT2-fs: Unable to read superblock > hdc6: bad access: block=0, count=1 > end_request: I/O error, dev 16:06 (hdc), sector 0 > NTFS: Reading super block failed > Kernel panic: VFS: Unable to mount root fs on 16:06 Is your drive going bad? Are the filesystems OK? -- .''`. Baloo <[EMAIL PROTECTED]> : :' :proud Debian admin and user `. `'` `- Debian - when you have better things to do than to fix a system msg17120/pgp0.pgp Description: PGP signature
Re: Kernel panic: VFS: Unable to mount root fs on 03:41
Sorry, I've found the problem my fault I was playing with ext3 about the time it came in the kernel and for some reason the filesystem was identified as ext3 but was ext2. Sorry again Nick
Re: kernel panic: vfs: unable to mount root fs install errror 01:00
Thus spake Philip Blundell: > On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote: > > I'm trying to get a server built with 2.2r4 potato cd and keep getting > > the above error. I tried the boot options in f2-f8 and tried mounting > > various root.bins from specifying floppy0 at boot: then got kernel > > panic: no init found try passing init= option to kernel. I looked up > > the errors on the deb user list and found similar questions but no > > answers. > > Have you tried booting from one of the other CDs? Each one has a different > kernel, and they don't all work properly for all users. > > You might also like to try the woody installer instead. Nobody is doing > active development on the potato disks any more. 01:00 is not an ide drive - it should 03:01 or something. I tsounds like you're trying to using an initrd image without having an /initrd. Try a boot kernel that doesn't use initrd. HTH, Steve -- George Washington was first in war, first in peace -- and the first to have his birthday juggled to make a long weekend. -- Ashley Cooper pgp7v4T9e8ElD.pgp Description: PGP signature
Re: kernel panic: vfs: unable to mount root fs install errror 01:00
On Sat, Jan 12, 2002 at 05:56:37PM -0800, justin cunningham wrote: > I'm trying to get a server built with 2.2r4 potato cd and keep getting > the above error. I tried the boot options in f2-f8 and tried mounting > various root.bins from specifying floppy0 at boot: then got kernel > panic: no init found try passing init= option to kernel. I looked up > the errors on the deb user list and found similar questions but no > answers. Have you tried booting from one of the other CDs? Each one has a different kernel, and they don't all work properly for all users. You might also like to try the woody installer instead. Nobody is doing active development on the potato disks any more. p.
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
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
--- 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
> > --- 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
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. = - [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
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
> 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
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 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 21:04
- Original Message - From: "Dave Sherohman" <[EMAIL PROTECTED]> To: "Debian User List" Sent: Monday, October 08, 2001 4:52 PM Subject: Re: Kernel Panic: VFS Unable to mount root fs on 21:04 > On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote: > > I'm trying to set up a new machine this weekend, and i'm in trouble. > > I know you needed a solution by Monday, so this is a bit late, but I > haven't seen anyone else post an explanation of what the error > actually means, so... > > > Now, I have a problem. The machine will no longer boot from the hard disk. > > I get the message from the subject line. I can boot it from the boot > > floppy. > > lilo (or something else) is telling the kernel to mount / from device > 21:04 and the kernel doesn't know how to do that. According to > Documentation/devices.txt in my kernel source tree, major device 21 > is the generic SCSI subsystem and minor device 04 in that system is > the fifth device, so 21:04 would be /dev/sg4 (or /dev/sge). Either > a) you don't have generic SCSI support in your kernel, b) you don't > have five generic SCSI devices, or c) you have to boot off a SCSI > drive (/dev/sd*), not a generic SCSI device (/dev/sg*). Hmm, maybe the kernel has no support for your scsi card/devices, yes. BTW, probably the magic number written to the real-root-dev file is the magic number description for your root device (every device in Linux can be described by such a number combination - for the numbering system see attached file devices.txt, the format in the real-root-dev file is for example for /dev/hdb1: 0x365). Cheers, Stephan <>
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
> > During the install of the 2.4 kernel package. I goot a message about > > needing to add a initrd line to lilo.conf. This is probably the cause of your problem. I had the same problem the first time I installed a 2.4 kernel package with apt-get. Just follow the instructions and edit your lilo.conf file to point to the initrd file and your machine should work again. HTH
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
On Sat, Oct 06, 2001 at 02:17:20PM -0400, Stan Brown wrote: > I'm trying to set up a new machine this weekend, and i'm in trouble. I know you needed a solution by Monday, so this is a bit late, but I haven't seen anyone else post an explanation of what the error actually means, so... > Now, I have a problem. The machine will no longer boot from the hard disk. > I get the message from the subject line. I can boot it from the boot > floppy. lilo (or something else) is telling the kernel to mount / from device 21:04 and the kernel doesn't know how to do that. According to Documentation/devices.txt in my kernel source tree, major device 21 is the generic SCSI subsystem and minor device 04 in that system is the fifth device, so 21:04 would be /dev/sg4 (or /dev/sge). Either a) you don't have generic SCSI support in your kernel, b) you don't have five generic SCSI devices, or c) you have to boot off a SCSI drive (/dev/sd*), not a generic SCSI device (/dev/sg*). Although a) and b) are both possible, I suspect that c) is also true, so your machine will continue to fail to boot until you tell it to use a device of the correct type. > During the install of the 2.4 kernel package. I goot a message about > needing to add a initrd line to lilo.conf. That's really only necessary if you use the stock kernel or roll your own and have certain things built as modules; I know filesystem drivers fall into this category, but can't say what else does. I don't use modules much, so I haven't had to deal with initrd. -- When we reduce our own liberties to stop terrorism, the terrorists have already won. - reverius Innocence is no protection when governments go bad. - Mr. Slippery
Re: Kernel Panic: VFS Unable to mount root fs on 21:04
- Original Message - From: "Stan Brown" <[EMAIL PROTECTED]> To: "Debian User List" Sent: Saturday, October 06, 2001 8:17 PM Subject: Kernel Panic: VFS Unable to mount root fs on 21:04 > I'm trying to set up a new machine this weekend, and i'm in trouble. > > I installed a minimal "stable" over the network. then upgraded to Progeny. > Then I wen to istall the 2.4 kernel packages from > http://people.debian.org/~bunk (thanks for the good work on these BTW). > > Now, I have a problem. The machine will no longer boot from the hard disk. > I get the message from the subject line. I can boot it from the boot > floppy. > > During the install of the 2.4 kernel package. I goot a message about > needing to add a initrd line to lilo.conf. It sufested puting a line in > /etc/kern-img.conf (from memory). I have tried this, and also tried adding > the sugested initrd line to /etc/lilo.conf. But nieht gets me to the point > where I can boot from the hard disk. > > Help Please! Hi! Have you called the command "lilo" once at the command line after changing lilo.conf? Maybe that'll do it. Cheers, Stephan
Re: Kernel Panic!..VFS.....
Hi, Mark! Problems solved, thanks! I found what happened to lead to the problem was - I changed the hard disk from secondary master to primary master, lilo was looking for '/' in /dev/hdc5, rather /dev/hda5. From your tips, I first tried to put 'rescue root=/dev/hda5' at the boot prompt when the rescue disk was loaded. Then typed in the root password to doo the maintenance jobs. But the system did not allow me to edit any files at all. It was still looking for /dev/hdc5 and /dev/hdc6 (swap partition). So, I used the rescue disk and the root disk to mount the '/' fs and edit the /etc/lilo.conf, fstab and mtab where all hdc were changed to hda. And this time, it worked! Thank you very for deciphering the meaning of the numbers in the error message so that I understand what was the problem and find the right direction to fix it. Best regards, Wilson : ) Mark Suter wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Wilson, > > > Yes, thank you for reminding me the missing bits (The machine with broken > > O/S is > > not with me at the moment, I'm sorry that I have not jotted them down > > properly). > > Now, presuming what you said is right and once I've checked out the > > number,x > > in the error message "VFS: Unable to mount root fs on 3:0x". What command > > should I do to fix the problem and get the O/S back to live? > > The basic procedure to fix most boot problems is easy to > describe. The devil is in the details ;) > > 1) Boot the system by manually specifying the root fs. > > 2) Reconfigure your boot method with correct the root fs. > > 3) Reboot to be certain that you have fixed the problem. > > Based on what you wrote about using the rescue disk, I believe > you are able to boot this system manually. Step 2 is should be > editing /etc/lilo.conf and running "/sbin/lilo" - you should > ensure the "boot=" and "root=" lines are correct. > > Yours sincerely, > > - -- Mark John Suter | I know that you believe you understand > [EMAIL PROTECTED] | what you think I said, but I am not sure > GPG key id F2FEBB36 | you realise that what you heard is not > Ph: +61 4 1126 2316 | what I meant. anonymous > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.1 (GNU/Linux) > Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ > > iD8DBQE5RPEF7EsZXfL+uzYRAu6tAJ9ATaJ/k61Brws1TJuo+Y5QmN30+wCghjWx > j/8y6KoAGeAEQI+qeqsN65g= > =jcXd > -END PGP SIGNATURE- > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Kernel Panic!..VFS.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, > Yes, thank you for reminding me the missing bits (The machine with broken O/S > is > not with me at the moment, I'm sorry that I have not jotted them down > properly). > Now, presuming what you said is right and once I've checked out the number,x > in the error message "VFS: Unable to mount root fs on 3:0x". What command > should I do to fix the problem and get the O/S back to live? The basic procedure to fix most boot problems is easy to describe. The devil is in the details ;) 1) Boot the system by manually specifying the root fs. 2) Reconfigure your boot method with correct the root fs. 3) Reboot to be certain that you have fixed the problem. Based on what you wrote about using the rescue disk, I believe you are able to boot this system manually. Step 2 is should be editing /etc/lilo.conf and running "/sbin/lilo" - you should ensure the "boot=" and "root=" lines are correct. Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RPEF7EsZXfL+uzYRAu6tAJ9ATaJ/k61Brws1TJuo+Y5QmN30+wCghjWx j/8y6KoAGeAEQI+qeqsN65g= =jcXd -END PGP SIGNATURE-
Re: Kernel Panic!..VFS.....
Mark, Yes, thank you for reminding me the missing bits (The machine with broken O/S is not with me at the moment, I'm sorry that I have not jotted them down properly). Now, presuming what you said is right and once I've checked out the number,x in the error message "VFS: Unable to mount root fs on 3:0x". What command should I do to fix the problem and get the O/S back to live? Cheers, Wilson Mark Suter wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Wilson, > > > When my machine boots up, Linux is auto-probing the hardware, then it > > stops and pops up an error message "Kernel Panic..VFS" > > > > I tried to use a 'rescue' disk and did the e2fsck, but it said the '/' > > partition was clean. > > I could mount the '/' partition and navigate the directories, but just > > can't boot up? > > What could be wrong? > > It is probable that the filesystem you tested is not the same one > the kernel is trying to mount as the root filesystem. The error > message should include the filesystem that was being tested, as > in the following example. > > VFS: Unable to mount root fs on 3:05 > > These numbers, "3" and "5", are the major and minor device > numbers, that is /dev/hda5, as follows > > $ ls -l /dev/hda? > brw-rw1 root disk 3, 1 Mar 29 15:25 /dev/hda1 > brw-rw1 root disk 3, 2 Mar 29 15:25 /dev/hda2 > brw-rw1 root disk 3, 3 Mar 29 15:25 /dev/hda3 > brw-rw1 root disk 3, 4 Mar 29 15:25 /dev/hda4 > brw-rw1 root disk 3, 5 Mar 29 15:25 /dev/hda5 > brw-rw1 root disk 3, 6 Mar 29 15:25 /dev/hda6 > brw-rw1 root disk 3, 7 Mar 29 15:25 /dev/hda7 > brw-rw1 root disk 3, 8 Mar 29 15:25 /dev/hda8 > brw-rw1 root disk 3, 9 Mar 29 15:25 /dev/hda9 > Yours sincerely, > > - -- Mark John Suter | I know that you believe you understand > [EMAIL PROTECTED] | what you think I said, but I am not sure > GPG key id F2FEBB36 | you realise that what you heard is not > Ph: +61 4 1126 2316 | what I meant. anonymous > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.1 (GNU/Linux) > Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ > > iD8DBQE5RNeb7EsZXfL+uzYRAk4KAJwLxMXjeGaGgGYTHsIrn3wrWhYfkwCfWWik > NRup/oPb3b+hB/TcMj+lkbg= > =OIUv > -END PGP SIGNATURE-
Re: Kernel Panic!..VFS.....
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wilson, > When my machine boots up, Linux is auto-probing the hardware, then it > stops and pops up an error message "Kernel Panic..VFS" > > I tried to use a 'rescue' disk and did the e2fsck, but it said the '/' > partition was clean. > I could mount the '/' partition and navigate the directories, but just > can't boot up? > What could be wrong? It is probable that the filesystem you tested is not the same one the kernel is trying to mount as the root filesystem. The error message should include the filesystem that was being tested, as in the following example. VFS: Unable to mount root fs on 3:05 These numbers, "3" and "5", are the major and minor device numbers, that is /dev/hda5, as follows $ ls -l /dev/hda? brw-rw1 root disk 3, 1 Mar 29 15:25 /dev/hda1 brw-rw1 root disk 3, 2 Mar 29 15:25 /dev/hda2 brw-rw1 root disk 3, 3 Mar 29 15:25 /dev/hda3 brw-rw1 root disk 3, 4 Mar 29 15:25 /dev/hda4 brw-rw1 root disk 3, 5 Mar 29 15:25 /dev/hda5 brw-rw1 root disk 3, 6 Mar 29 15:25 /dev/hda6 brw-rw1 root disk 3, 7 Mar 29 15:25 /dev/hda7 brw-rw1 root disk 3, 8 Mar 29 15:25 /dev/hda8 brw-rw1 root disk 3, 9 Mar 29 15:25 /dev/hda9 Yours sincerely, - -- Mark John Suter | I know that you believe you understand [EMAIL PROTECTED] | what you think I said, but I am not sure GPG key id F2FEBB36 | you realise that what you heard is not Ph: +61 4 1126 2316 | what I meant. anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.1 (GNU/Linux) Comment: Public key available from Keyservers or http://www.uq.edu.au/~suter/ iD8DBQE5RNeb7EsZXfL+uzYRAk4KAJwLxMXjeGaGgGYTHsIrn3wrWhYfkwCfWWik NRup/oPb3b+hB/TcMj+lkbg= =OIUv -END PGP SIGNATURE-
Re: Kernel panic VFS ...
At 01:54 AM 10/22/99 +0200, Jocke wrote: >Hi all, > >I did something stupid today :( >While recompiling my kernel to add scsi support for my cdrw I accidently >forgot some ide stuff and now I can't boot. If you want to change something important like a...*hmmm* a kernel or something ALWAYS make lilo PROMPT you for a kernel! So you can ALWAYS boot the OLD one and TEST the new one. Also make always a custom boot flop when you install Debian (it is an installation option ;-) These two precautions can make your life a whole lot easier. For your problem you can use the standard rescue flop. Mount your HD and repair your mistake... Onno
Re: Kernel panic VFS ...
On 22/10/99 Jocke wrote: I have 2 debian partitions the one that works are on hda2 and the one that messed up is on hda5. I have some old vmlinuz + System.map in /boot Could anyone guide me thru this so I can get my hda5 debian to boot again ? Can I fix it from "this" (hda2) partition or do I have to use a rescue disc or something and recompile or what ? Hoping for some help! do you have lilo configured so you can boot the other partition? if not you should do that after to get this straightened out, and then alway leave your old kernel in place and have a lilo image for it so if the new one fails you can just boot the previous without problem... i will give you example lilo .conf at the end so you can do this. if you have successfully booted to your unbroken root hda2 then you can mount -t ext2 /dev/hda5 /mnt to get access to your messed up root, if you still have the working kernel there then simply edit your /etc/lilo.conf (on hda2) and add image=/mnt/boot/vmlinuz #whatever working kernel name is label=linux.good root=/dev/hda5 read-only make sure that you also have prompt in there and run lilo when you reboot press tab at the lilo boot: prompt and you will see linux.good so type linux.good and you should boot into hda5 with the working kernel you put there. you can use the above convention to dual boot between different linux setups just make sure to mount the appropriate filesystems before updating lilo. my lilo.conf to dual boot debian and redhat with support for one backup kernel (debian side): boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 default=linux image=/vmlinuz label=debian alias=linux read-only root=/dev/hda1 image=/vmlinuz.old label=debian.old read-only root=/dev/hda1 image=/redhat/boot/vmlinuz label=redhat read-only root=/dev/hda2 image=/redhat/boot/vmlinuz.old label=redhat.old read-only root=/dev/hda2 on the redhat side the /redhat part of the paths are deleted and the debian parts (and the map and install lines) have /debian added to them, each time I run lilo I first make sure that either /debian or /redhat is mounted (the root filesystem of the other system) depending on which i am running, I also make sure that the symlinks point to the right kernels one old/previous one current then I can boot into anything i want right from the lilo prompt. note: I always use the debian lilo binary, so if I boot into redhat i use /debian/sbin/lilo to update lilo this is to keep the bootloader consistent. if you build kernels the debian way then the vmlinuz.old symlink should be taken care of for you but check it anyway :) Best Regards, Ethan Benson To obtain my PGP key: http://www.alaska.net/~erbenson/pgp/
Re: kernel panic: VFS: unable to mount root fs
its possible you forgot to include scsi support in your kernel, i have made that mistake and gotten that error many times. nate [mailto:[EMAIL PROTECTED] ]-- Linux System Administrator http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- On Mon, 18 Oct 1999, T.V.Gnanasekaran wrote: > hello, > I am trying to install kernel 2.2.12. I compiled as documented in the > README of the kernel source distribution. I edited lilo.conf and exec > lilo and added. My root dev=/dev/sda3 (extend partition) boot=/dev/sda > But when I tried booting the new kernel, I got > > VFS: Cannot open root device 08:06 > Kernel Panic: VFS: Unable to mount root fs on 08:06 > > what should I do now? > > -gnana > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: kernel panic: VFS: unable to mount root fs
On Mon, Oct 18, 1999 at 05:09:13PM -0700, T.V.Gnanasekaran wrote: > hello, > I am trying to install kernel 2.2.12. I compiled as documented in the > README of the kernel source distribution. I edited lilo.conf and exec > lilo and added. My root dev=/dev/sda3 (extend partition) boot=/dev/sda > But when I tried booting the new kernel, I got > > VFS: Cannot open root device 08:06 > Kernel Panic: VFS: Unable to mount root fs on 08:06 > > what should I do now? Compiled ext2 filesystem as module? Make it permanent. Mirek
Re: "Kernel panic: VFS: Unable to mount root fs..."
I went through "make config" again while reading the "Configure help file for the source (along with making the image and the other processes), and, upon boot, the new kernel got as far as VFS: root fs mounted [...] then it simply stopped. ...anyone have any info that would help here? Does the Debian system need to have kernels made differently from other Linux kernels (e.g., directory differences?)? Art On Fri, Dec 25, 1998 at 11:36:18AM +, Art Lemasters wrote: > I just tried to patch the 2.0.35 kernel with Initio SCSI > adapter drivers. After make config, make dep, make zImage, > make modules, make modules_install and lilo (and copying zImage > to / as vmlinuz), I rebooted the machine. > > It booted partially, then stopped with the error message > "Kernel panic: VFS: Unable to mount root fs on 03:02." Can you > help me get past this one (first time compiling a kernel)? > > And by the way, this box is running frozen. > > Thanks, > > Art > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
On Sat, Sep 19, 1998 at 11:41:24PM +0200, Miquel van Smoorenburg wrote: > In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote: > > VFS: Can't open root device 03:01 > > Kernel Panic: VFS unable to mount root fs on 03:01 > > Sounds like you didn't compile in the driver for your harddisk. You > did compile in (not as module) the IDE driver right? And support > for the ext2 filesystem? Looks like missing IDE support was my problem. I had read only the beginning of the help on the Enhanced IDE support: "... the full-featured IDE driver to control up to four IDE interfaces ..." and had figured that, since I have only two IDE drives, I did not need this "full-featured" driver. If I had read further: "... If you have one or more IDE drives, say Y ..." I could have spared us this thread. Well, problem solved, and thanks for your help. Lesson learned: R(all)TFM. Matt Miller
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
On Sat, Sep 19, 1998 at 03:41:47PM -0500, Mark Panzer wrote: > > What do these messages mean, what have I done to myself, and how can I undo > > it? > > > > Next time also try to use the kpkg utility, all you do is enter the > source directory enter kpkg and it creates a .deb of the kernel (well > almost you'll have to read the doc's or ask me for more info if you want > it). When you do a dpkg -i kernel-XX.deb it does everything for you, > even runs lilo! Thanks. I should have figured Debian had a wrapper around kernel building. Matt Miller.
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote:
> VFS: Can't open root device 03:01
> Kernel Panic: VFS unable to mount root fs on 03:01
Sounds like you didn't compile in the driver for your harddisk. You
did compile in (not as module) the IDE driver right? And support
for the ext2 filesystem?
>make modules
>make modules_install
>cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34
>lilo
You might want to cp System.map /boot/System.map-2.0.34. "ps" uses
this ("l" option) and klogd to decode OOPSes if you get one.
Mike.
--
"Did I ever tell you about the illusion of free will?"
-- Sheriff Lucas Buck, ultimate BOFH.
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
In article <[EMAIL PROTECTED]>, Samuel Landau <[EMAIL PROTECTED]> wrote: >dear mister, that's the orginal doc from de kernel source, not the >Debianized one. >well, with Debian there are some more files that are necessary for the >kernel to work >(e.g. : /boot/SystemMap) That's nonsense. I have never used the Debian style and always installed my own kernels. /boot/System.map is not essential for the boot process either. Remember.. Debian is just Linux .. there's nothing special about the kernel. Mike. -- "Did I ever tell you about the illusion of free will?" -- Sheriff Lucas Buck, ultimate BOFH.
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
> VFS: Can't open root device 03:01 > Kernel Panic: VFS unable to mount root fs on 03:01 strange maybe you compiled the root fs as a module (which is not to be done), but how would you boot?... ah there's the answer: > I installed the 2.0.34 kernel source package. I think I'm following the > instructions in /usr/doc/kernel-source-2.0.34/README. I do: > > make mrproper > make menuconfig > make dep > make clean > make zImage > make modules > make modules_install > cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 > lilo dear mister, that's the orginal doc from de kernel source, not the Debianized one. well, with Debian there are some more files that are necessary for the kernel to work (e.g. : /boot/SystemMap) you have to use the make-kernel package tools, or whatever is its name : # cd /usr/src/linux # make-kpkg clean # make xconfig /* sorry I like it :) */ # make-kpkg -r custom.1.0 binary which buils all you need in /usr/src then # cd /usr/src # dpkg -BRGiE kernel-image 2.0.34_custom.1.0.deb but before : $ man make-kpkg $ cd /usr/doc/kernel-(uh what's its name? look for it!) and rtfd :) you're welcome -- Samuel Landau
Re: Kernel Panic: VFS Unable to mount root fs on 03:01
[EMAIL PROTECTED] wrote: > > My Hamm system is a couple weeks old, and I'm trying to roll my own kernel. > The first few trys seemed to work, (removing PCI support, setting processor > type to 486, etc...), but now, no matter how simple of a kernel I try to > build, the system won't reboot. The kernel loads, then, after about 3/4 of a > screen of normal startup messages, the system halts with: > > VFS: Can't open root device 03:01 > Kernel Panic: VFS unable to mount root fs on 03:01 > You might be making your kernel too simple if you don't include support for the minix fs then it cannot mount the root partiton. Try remaking your kernel and be sure to include ext2 support. > What do these messages mean, what have I done to myself, and how can I undo > it? > Next time also try to use the kpkg utility, all you do is enter the source directory enter kpkg and it creates a .deb of the kernel (well almost you'll have to read the doc's or ask me for more info if you want it). When you do a dpkg -i kernel-XX.deb it does everything for you, even runs lilo! > I installed the 2.0.34 kernel source package. I think I'm following the > instructions in /usr/doc/kernel-source-2.0.34/README. I do: > > make mrproper > make menuconfig > make dep > make clean > make zImage > make modules > make modules_install > cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz-2.0.34 > lilo > > Here is some other potentially relevant info: > > $ less /etc/lilo.conf > boot=/dev/hda1 > root=/dev/hda1 > install=/boot/boot.b > map=/boot/map > vga=normal > delay=20 > image=/vmlinuz > label=Linux > read-only > > $ ls -l /vmlinuz > lrwxrwxrwx 1 root root 19 Sep 7 15:01 /vmlinuz -> > boot/vmlinuz-2.0.34 > > $ ls -l /boot > total 295 > -rw-r--r-- 1 root root 512 Sep 7 15:27 boot.0301 > -rw-r--r-- 1 root root 4536 Nov 21 1997 boot.b > -rw-r--r-- 1 root root 300 Nov 21 1997 chain.b > -rw--- 1 root root 6656 Sep 15 23:12 map > -rw-r--r-- 1 root root 444 Dec 12 1997 mbr.b > -rw-r--r-- 1 root root 308 Nov 21 1997 os2_d.b > -rwxr-xr-x 1 root root 281865 Sep 15 23:12 vmlinuz-2.0.34 > > Thanks, > > Matt Miller > > "Software is never finished, it is only released" > Mike Gancarz, The Unix Philosophy > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
