|
Home > Archive > Red Hat General > January 2004 > Kernel panic: VFS: Unable to mount root fs on 03:03
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Kernel panic: VFS: Unable to mount root fs on 03:03
|
|
|
| Hi there,
My Red Hat Linux 7.2 wasn't properly shutdown.
When I power on it again, I get Kernel panic as below:
Kernel panic: VFS: Unable to mount root fs on 03:03
I have tried to power it on a couple of times. I even have tried to boot
from floppy. I get the same error.
Any idea would be very much appreciated,
Ross
| |
|
| Ross wrote:quote:
>
> My Red Hat Linux 7.2 wasn't properly shutdown.
> When I power on it again, I get Kernel panic as below:
> Kernel panic: VFS: Unable to mount root fs on 03:03
>
> I have tried to power it on a couple of times. I even have tried to boot
> from floppy. I get the same error.
Can you use the first installation CD and boot into rescue mode?
--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.22 SMP i686 (GCC) 3.3.2
Uptime: 28 days, 8:39, 1 user, load average: 0.15, 0.12, 0.12
| |
|
| No, it says "You don't have any Linux partition".
What can I do next? SOS!
It's WinXP/Linux dual-boot on my IBM laptop. The partitions are:
/dev/hda1 -- NTFS for Windows XP Pro.
/dev/hda2 -- IBM recovery hidden partition.
/dev/hda3 -- Linux ext3.
/dev/hda4 -- extended
/dev/hda5 -- swap
/dev/hda6 -- FAT32 for both WinXP and Linux.
Thanks a lot,
Ross
"David" <thunderbolt01@netscape.net> wrote in message
news:nsEpb.98940$HS4.826462@attbi_s01...quote:
> Ross wrote:
>
> Can you use the first installation CD and boot into rescue mode?
>
> --
> Confucius: He who play in root, eventually kill tree.
> Registered with The Linux Counter. http://counter.li.org/
> Slackware 9.1.0 Kernel 2.4.22 SMP i686 (GCC) 3.3.2
> Uptime: 28 days, 8:39, 1 user, load average: 0.15, 0.12, 0.12
| |
| Sybren Stuvel 2004-01-23, 7:09 pm |
| ["Followup-To:" header set to comp.os.linux.]
Ross enlightened us with:quote:
> My Red Hat Linux 7.2 wasn't properly shutdown. When I power on it
> again, I get Kernel panic as below: Kernel panic: VFS: Unable to mount
> root fs on 03:03
Auch... You could try running Knoppix. From there you can try mounting
the partition and/or running fsck on it.
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
| |
|
| Ross wrote:quote:
> No, it says "You don't have any Linux partition".
> What can I do next? SOS!
> It's WinXP/Linux dual-boot on my IBM laptop. The partitions are:
> /dev/hda1 -- NTFS for Windows XP Pro.
> /dev/hda2 -- IBM recovery hidden partition.
> /dev/hda3 -- Linux ext3.
> /dev/hda4 -- extended
> /dev/hda5 -- swap
> /dev/hda6 -- FAT32 for both WinXP and Linux.
I would go with Sybren's idea if you can get a hold of a KNOPPIX
CD. Then see if you can mount the Linux partition and if nothing
else maybe you can at least save your personal files if you end
up doing a re-install.
--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.22 SMP i686 (GCC) 3.3.2
Uptime: 29 days, 2:39, 1 user, load average: 0.40, 0.27, 0.34
| |
|
| I have booted Knoppix and run fsck Later when I tried to boot, I get the
following messages:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 319k freed
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Red Hat nash version 3.2.6 starting
Loading jbd module
Journalled Block Device driver loaded
Loading ext3 module
Mounting /proc filesystem
Creating root device
Mounting root filesystem
ext3: No journal on filesystem on ide0(3,3)
mount: error 22 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
Freeing unused kernel mrmory: 220k freed
Kernel panic: No init found. Try passing init= option to kernel.
This seems an improvement of some sort.
Is there anything else you can suggest to try now?
BTW, I can boot to WinXP without problem.
Thanks a million,
Ross
"Sybren Stuvel" <sybrenUSE@YOURthirdtower.imagination.com> wrote in message
news:slrnbqffk2.5dc.sybrenUSE@sybren.thirdtower.com...quote:
> ["Followup-To:" header set to comp.os.linux.]
> Ross enlightened us with:
>
> Auch... You could try running Knoppix. From there you can try mounting
> the partition and/or running fsck on it.
>
> Sybren
> --
> The problem with the world is stupidity. Not saying there should be a
> capital punishment for stupidity, but why don't we just take the
> safety labels off of everything and let the problem solve itself?
| |
| Sybren Stuvel 2004-01-23, 7:09 pm |
| ["Followup-To:" header set to comp.os.linux.]
Ross enlightened us with:quote:
> I have booted Knoppix and run fsck
Knoppix rules 
quote:
> This seems an improvement of some sort. Is there anything else you
> can suggest to try now?
Can you mount your root filesystem from Knoppix?
quote:
> Thanks a million,
No problem!
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
| |
|
| Ross wrote:quote:
> I have booted Knoppix and run fsck Later when I tried to boot, I get the
> following messages:
quote:
> Mounting root filesystem
> ext3: No journal on filesystem on ide0(3,3)
> mount: error 22 mounting ext3
quote:
> Kernel panic: No init found. Try passing init= option to kernel.
> This seems an improvement of some sort.
> Is there anything else you can suggest to try now?
It seems that it lost the journal on the root filesystem.
Have you tried adding the journal back to it?
man tune2fs
--
Confucius: He who play in root, eventually kill tree.
Registered with The Linux Counter. http://counter.li.org/
Slackware 9.1.0 Kernel 2.4.22 SMP i686 (GCC) 3.3.2
Uptime: 29 days, 23:24, 1 user, load average: 0.08, 0.05, 0.03
| |
| Scott Lurndal 2004-01-23, 7:09 pm |
| "Ross" <Ross@nospam.com> writes:quote:
>I have booted Knoppix and run fsck Later when I tried to boot, I get the
>following messages:
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 319k freed
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Red Hat nash version 3.2.6 starting
> Loading jbd module
> Journalled Block Device driver loaded
> Loading ext3 module
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> ext3: No journal on filesystem on ide0(3,3)
> mount: error 22 mounting ext3
Here's a big clue - error 22 is 'EINVAL'. From the mount(2) man
page:
EINVAL Specialfile had an invalid superblock. Or, a remount was attempted,
while specialfile was not already mounted on dir. Or, an umount was
attempted, while dir was not a mount point.
It would appear that either your superblock is toast, or the filesystem
is damaged in some other respect. Which file system did you fsck?
What was the exact command syntax (including device node path) that you
used?
| |
|
| When I boot back to Knoppix again, and mount /dev/hda3 to /tmp, I can't see
anything except lost+found.
Under lost+found, there are many files like #20, #21, ...
Where are my files? Did the "fsck -y /dev/hda3" command delete all my files?
Ross
"Ross" <Ross@nospam.com> wrote in message news:bob165$1fv$1@news.storm.ca...quote:
> I have booted Knoppix and run fsck Later when I tried to boot, I get the
> following messages:
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 319k freed
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Red Hat nash version 3.2.6 starting
> Loading jbd module
> Journalled Block Device driver loaded
> Loading ext3 module
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> ext3: No journal on filesystem on ide0(3,3)
> mount: error 22 mounting ext3
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> Freeing unused kernel mrmory: 220k freed
> Kernel panic: No init found. Try passing init= option to kernel.
> This seems an improvement of some sort.
> Is there anything else you can suggest to try now?
> BTW, I can boot to WinXP without problem.
> Thanks a million,
> Ross
>
> "Sybren Stuvel" <sybrenUSE@YOURthirdtower.imagination.com> wrote in
messagequote:
> news:slrnbqffk2.5dc.sybrenUSE@sybren.thirdtower.com...
>
>
| |
| Bill Marcum 2004-01-23, 7:09 pm |
| ["Followup-To:" header set to comp.os.linux.]
On Wed, 5 Nov 2003 09:24:03 -0500, Ross
<Ross@nospam.com> wrote:quote:
> I have booted Knoppix and run fsck Later when I tried to boot, I get the
> following messages:
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 319k freed
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Red Hat nash version 3.2.6 starting
> Loading jbd module
> Journalled Block Device driver loaded
> Loading ext3 module
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> ext3: No journal on filesystem on ide0(3,3)
> mount: error 22 mounting ext3
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> Freeing unused kernel mrmory: 220k freed
> Kernel panic: No init found. Try passing init= option to kernel.
> This seems an improvement of some sort.
> Is there anything else you can suggest to try now?
> BTW, I can boot to WinXP without problem.
> Thanks a million,
> Ross
>
Your ext3 filesystem has somehow lost its journal, turning it into an
ext2. Boot the Knoppix disk again and try "tune2fs -j /dev/hda3"
--
You can go anywhere you want if you look serious and carry a clipboard.
|
|
|
|
|