Please append a correct root= boot option
Kernel panic: VFS: Unable to mount root fs on 5e:01
I have shutdown my linuxrtr... Linux under z/vm acting like a router
Suse linux...
Above is the error I am getting..
Please help
Thanks a bunch
Ralph
--
ralph noll
[EMAIL PROTECTED
Sent: Monday, December 20, 2004 1:59 PM
To: [EMAIL PROTECTED]
Subject: Re: VFS: Unable to mount root fs on 5e:01
I restored my root file system to recover from this error. I restored
everthing except /var, /tmp, /home, and /opt. SuSE told me to run mkinitrd
and then a zipl. I never ran the mkinitrd
cc
[EMAIL PROTECTED]
IST.EDU Subject
Re: VFS: Unable to mount root fs on
5e:01
12/20/2004 02:42
PM
Please
On Dec 20, 2004, at 1:45 PM, Peter E. Abresch Jr. - at Pepco wrote:
Thanks for such a quick reply. I found the RPM databases in
/var/lib/rpm. I
restored these files and used yast to download and install the updates
again. This time I ran the mkinitrd before the zipl and all seems
fine. I
always
Hi Daniel,
As you can probably tell, I'm real fluent with a lot of the Linux commands, so I
really appreciate your help.
I tried that command, and here is what I got:
rpm: only one major mode may be specified
[EMAIL PROTECTED] 04/01/04 09:14AM
It's funny, this is the one I use to clone,
for i in `rpm -qa`; do rpm -V $i; done |grep missing
rpm: only one major mode may be specified
Those are backticks around rpm -qa (on my keyboard, upper left, shared
by ~).
~ Daniel
---
This message is the property
You hit it right on the head. Somehow tar was gone from this instance of Linux. It's
funny, this is the one I use to clone, and I just went to another instance, found it
and copied it back.
Once tar was there, it worked great.
I really appreciate your help
Thanks
Gene
[EMAIL PROTECTED]
It's funny, this is the one I use to clone, and I just went
to another instance, found it and copied it back.
Once tar was there, it worked great.
I really appreciate your help
Glad you are back in business now, though the missing binary IS
disconcerting. You should probably take inventory
-major-94, errno = 2
VFS: Cannot open root device dasda1 or 5e:01
Please append a correct root= boot option
Kernel panic: VFS: Unable to mount root fs on 5e:01
HCPGIR450W CP entered; disabled wait PSW 000A 8022CD08
All the modules appear to be in the right place, and the modules.dep
has
option
Kernel panic: VFS: Unable to mount root fs on 5e:01
HCPGIR450W CP entered; disabled wait PSW 000A 8022CD08
All the modules appear to be in the right place, and the modules.dep
has all the right directories in it. Did anyone else experience this
when they put on Service Pack 3?
Did
Yes, I checked the zipl.conf and then ran zipl.
Does your zipl.conf have a line like ramdisk=/boot/initrd ?
If not, you should probably add it (run mkinitrd if you haven't), and
then run zipl again.
Loading module dasd_mod dasd=$dasd ...
insmod: dasd_mod: no module by that name found
on Subject: SuSE SP3 Kernel panic: VFS:
Unable to mount root fs on 5e:01 ( was Re: Myth
390 Port of the 1K blocksize on e
[EMAIL PROTECTED]
ST.EDU
03/31/2004 08:22
AM
My zipl.conf does have that statement, but I didn't run the mkinitrd.
I just tried, but I get this error:
using /dev/dasda1 as root device (mounted on / as ext2)
Found ECKD dasd, adding dasd
creating initrd /boot/initrd for kernel /boot/kernel/image
(version 2.4.21-83-default) (s390)
dasd_mod: failed to add module /lib/modules/2.4.21-83-
default/kernel/drivers/s3
90/block/dasd_mod.o
initrd too small
Run zipl now to update the IPL record!
how do I make it bigger?
How much
Before the zipl, did you do a mkinitrd? The dasd
drivers are in the initrd module and not in the kernel.
=
Jim Sibley
RHCT, Implementor of Linux on zSeries
Computer are useless.They can only give answers. Pablo Picasso
__
Do you Yahoo!?
Yahoo! Finance Tax
I did as you suggested, but I don't get any additional messages, it's the exact same
thing.
[EMAIL PROTECTED] 03/31/04 12:04PM
creating initrd /boot/initrd for kernel /boot/kernel/image
(version 2.4.21-83-default) (s390)
dasd_mod: failed to add module /lib/modules/2.4.21-83-
At line at 1061 which is:
dd if=/dev/zero of=$tmp_initrd_small bs=1k count=$img_size
2/dev/null
Can you remove the 2/dev/null portion of that, run mkinitrd again
and
see if you get any No space left on device errors?
I did as you suggested, but I don't get any additional messages, it's
the
Well, i tried upping the initial size, I quadrupled it, to no avail. It looks like
that messages is generated around line 837 in the mkinird, before your change.
Here is the results of the bash on mkinitrd:
bash -x mkinitrd
+ kernels_default=vmlinuz vmlinuz.shipped
, 2004 2:33 PM
To: [EMAIL PROTECTED]
Subject: Re: SuSE SP3 Kernel panic: VFS: Unable to mount root fs on 5e: 01 (
was Re: Myth of the 1K blocksize
Well, i tried upping the initial size, I quadrupled it, to no avail. It
looks like that messages is generated around line 837 in the mkinird, before
It looks like that messages is generated around line 837 in the
mkinird,
before your change.
Ugh, my find had wrapped back to the beginning without me realizing.
Okay, on line 844
tar -C $root_dir -cf - $x 2/dev/null | tar -C $tmp_mnt -xpf -
2/dev/null
you're getting a rc 127. It's as if
20 matches
Mail list logo
