?
Solved

Kernel Panic:VFS: Unable to mount root fs on 03:03

Posted on 1998-02-14
6
Medium Priority
?
577 Views
Last Modified: 2013-12-15
I have a WDC 2.1GB with WIN95(800M) & Linux(1.2G). I reformatted the DOS partition, created/deleted/messed partitions and finally settled for 800MB PRI-DOS for my WIN95. All this while, I was expecting Linux to stay unaffected since I never even touched it (right ?) but now when I'm done with my WIN setup and tried to boot Linux, I get this error message:
Kernel Panic:VFS:Unable to mount root fs on 03:03

I've a Linux swap on hda2 and Linux native (holds /) on hda3.

I tried rescue boot and was able to mount my DOS partion but can't get /dev/hda3 (or hda2 for that matter) to mount on /mnt.
I'm running RH4.2 with 2.0.30 kernel.

Any help highly appreciated.

Thanks
Nishi
0
Comment
Question by:nkapoor
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 

Accepted Solution

by:
spjuver earned 400 total points
ID: 1631347
When you use dos-fdisk it will rename and mess around with partitions and sometimes change system id on old existing partitions...

Boot on your rescue-floppy and do fdisk /dev/hda.
Print the partition table and quit with comman 'q' (DO NOT WRITE anything).

There you may find Linux as hda5 or similiar. The worst is if the system id is changed. Then you have to change it and the DOS-partition will be unbootable...

Although, if you find that the hda-number is changed for linux you must change that

Boot the rescuefloppy with your new hdax as root and then reinstall lilo with the new root.
0
 

Author Comment

by:nkapoor
ID: 1631348
I've tried recue boot but fdisk is not able to open /dev/hda1 (DOS partition). Anyway, fdisk in win95 shows that hda1 is PRI-DOS, hda2 id Non-DOS (swap) and hda3 is Non-DOS(native). So, it does match with the expected configuration and also with the Kernel Panic message "03:03".
Only if I could mount it somehow, I can access it.
(BTW, I've installed LILO on the floppy, so my MBR should be safe :-)
0
 

Expert Comment

by:spjuver
ID: 1631349
You can't get /dev/hdax from fdisk in win 95...

It shows partition number 1,2,3.... this is not corresponding to hda1,hda2,hda3...

It can be hda1,hda4,hda5.

Fdisk under linux is handling haddisk's not partitions...
Try fdisk /dev/hda not /dev/hda1.


0
Will your db performance match your db growth?

In Percona’s white paper “Performance at Scale: Keeping Your Database on Its Toes,” we take a high-level approach to what you need to think about when planning for database scalability.

 

Author Comment

by:nkapoor
ID: 1631350
Tried fdisk /dev/hda. Got "Unable to open /dev/hda" message.
0
 

Author Comment

by:nkapoor
ID: 1631351
Having tried everything I could, I tried to re-install Linux RH4.2 and during install, he is asking me for the partition to install in. That's where I see this:
Device     Boot  Begin  Start  End  Blocks   Id   System
-----------    --------- ---------  --------  ------ ------------ ------- --------------
/tmp/hda1  *       1       1      388  782176+  6  Dos 16-bit>=32M
/tmp/hda2         389    389  1022  1278144  55  Unknown
                                                                            ^^^^^^^^^
I think 'Unknown' is the problem. I aborted the fresh installation and thought you should know it before I erase/recreate Linux.
0
 

Expert Comment

by:spjuver
ID: 1631352
This confusing me...
First you can't reach the /dev/hda with fdisk and then you can get a message of the partitions at boot-time.

How do get this message??
Are you booting from lilo or from  boot-disks?
If you are using boot-disks what are you writing at the 'boot:' promt??

1) Lilo really don't like changing in the partition table. Lilo must always be reinstalled after a new partition table is written.

2) If you write 'boot /dev/hdax' at the boot promt with boot disks you must know exactly which number 'x' have.

If you can't figure out which 'x' you actually have with fdisk then can your have been corrupted. It is not too uncommon that dos-fdisk messes with the system-id of a linux-partition.

The partition can be printed as 'unknown' in dos-fdisk and the actual partition is really is written as UNKNOWN.

So my summary is:

If you really cannot access the harddisk with linux fdisk. You can use dos fdisk to reenter the partition as dos-fat (write down the cylinder entry/end, remove the partition and put it back again as dos). The boot on boot disks and use linux fdisk to change the system id back to linux.
The boot linux on that partition.
It worked for me earlier. This makes the dos-fdisk happier and may fix your problem.

If this not works I have no better medicine than reinstall linux.

I have messed up my partition a lot but never been forced to reinstall (yet...).


0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

rdate is a Linux command and the network time protocol for immediate date and time setup from another machine. The clocks are synchronized by entering rdate with the -s switch (command without switch just checks the time but does not set anything). …
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Suggested Courses
Course of the Month8 days, 21 hours left to enroll

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question