08:06
Kernel Panic: VFS: Unable to mount root fs on 08:06
what should I do now?
-gnana
ernel 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
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 /
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
While some googling revealed that I&#
ev/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
oot=/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
>
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." C
; 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
>
>
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 drive
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 file
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
_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
>&g
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
> >
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 i
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
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 ker
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 a
"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
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
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
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 th
e 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
> > Ple
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,
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 mach
Hi,
I tried using a stock debian 2.4 kernel (kernel-image-2.4.17-k7) for the
first time before now I've been compiling vanilla kernels. I get the
following message while booting (after the LVM probing devices message)
cramfs: wrong message
Kernel panic: VFS: Unable to mount root fs on 03:
Hello:
I recently installed Debian 1.3.1 that I purchased from Linux System
Labs. I have had several problems, and cannot seem to find the
answers.
I installed the system by booting from a floppy and installing the
base system from cdrom. (My cdrom is bootable; the cd is bootable,
but for some
fter 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
What do these messages mean, what have I done to myself, and how can I undo it?
I installed the 2.0.34 kernel source pa
Had a power outage, and when I brought my Debian 3 system back up it was
hosed:
---
EXT2-fs: unable to read superblock
Attempt to access beyond device
.
.
.
FAT bread failed
Invalid session number or type of track
.
.
.
Kernel panic: VFS: unable to mount root fs on 03:04
---
How
> 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 modul
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
> 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 roo
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 o
--- 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
> > >
> > >
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: Unabl
>
> --- 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
&g
--- Shaul Karl <[EMAIL PROTECTED]> wrote:
> >
> > --- Xeno Campanoli <[EMAIL PROTECTED]> wrote:
> > > Shaul Karl wrote:
> > > >
> > > > > As my subject line indicates, I'm getting
> the
> > > diagnostic:
> >
> > > <>
> > >
> > > 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 an
>
> 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
>
- 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'
I've tried grub _and_ lilo. Grub just comes up in the interactive menu.
Lilo starts loading the kernel and then the kernel spits out this meesage.
This hapened just after I upgraded to the 2.4 kernel from the kernel
packages for that.
I desperately need to have this machine working by Monday.
Ca
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 hav
> > 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.c
- 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:
&
Hi,
Problem:
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
th
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
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
> 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 pa
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 ne
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 drive
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
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
> How do I interpret 03:04? If I boot off the boot floppy, everything is
It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld
/dev/hda4' to see this).
> fine. Have poked around for answers in the archives, but haven't
> figured it out.
>
> boot drive:
> hda1 - /boot
> hda2 - sw
On Thu, 21 Oct 2004 09:22:40 + (UTC), Alexis Huxley <[EMAIL PROTECTED]> wrote:
> > How do I interpret 03:04? If I boot off the boot floppy, everything is
>
> It's /dev/hda4 (the 3 and 4 are the major and minor numbers; do 'ls -ld
> /dev/hda4' to see this).
>
> > fine. Have poked around for an
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
On Sat, Oct 06, 2001 at 05:42:19PM -0400, Stan Brown wrote:
| I've tried grub _and_ lilo. Grub just comes up in the interactive menu.
| Lilo starts loading the kernel and then the kernel spits out this meesage.
Is this the same machine you just asked about the initrd stuff for?
To boot with an ini
fs not mounted
VFS: Cannot open root device 21:05
Kernel panic: VFS: Unable to mount root fs on 21:05
It looks as if my Harddisk on the UDMA-controller is not found. The startup
sequence with the debian kernel-image-2.2.19-ide looks something like this:
...
loop: registered device at major 7
Unif
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
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 boo
=/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
2.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 th
Ohlemeyer Matthias said:
> * in toplevel kernel-source directory
> export PATCH_THE_KERNEL=YES
> make-kpkg clean
> make-kpkg --revision=custom.1.0 kernel_image
>
> Everything seems to work fine - the kernel gets patched and after
> answering a few questions the compile-process starts
t option
Kernel panic: VFS: Unable to mount root fs on 03:03
Before you start to tweak a lilo.conf file, do make sure you *include*
ATA-ATAPI disk support in the kernel config prior to compiling! :)_
Main menu: ATA/IDE/MFM/RLL support --->
Then: IDE, ATA and ATAPI Block devices ---&g
62 matches
Mail list logo
