Right ipling from dasd NOT reader **** cat of parmfile **** zvmlinx5:/boot/zipl # cat parmfile dasd=0a0e,0a0f root=/dev/dasda1 zvmlinx5:/boot/zipl #
What I did ******** and output from that zvmlinx5:/boot/zipl # mkinitrd using "/dev/dasda1" as root device (mounted on "/" as "ext2") Found ECKD dasd, adding dasd eckd discipline! Note: If you want to add ECKD dasd support for later mkinitrd calls where possibly no ECKD dasd is found, add dasd_eckd_mod to INITRD_MODULES in /etc/sysconfig/kernel creating initrd "/boot/initrd" for kernel "/boot/kernel/image" (version 2.4.19-3suse-SMP) (s390) - insmod dasd_mod dasd=$dasd (kernel/drivers/s390/block/dasd_mod.o) - insmod dasd_eckd_mod (kernel/drivers/s390/block/dasd_eckd_mod.o) Run zipl now to update the IPL record! zvmlinx5:/boot/zipl # zipl building bootmap : /boot/zipl/bootmap adding Kernel Image : /boot/kernel/image located at 0x00010000 adding Ramdisk : /boot/initrd located at 0x00800000 adding Parmline : /boot/zipl/parmfile located at 0x00001000 Bootloader for ECKD type devices with z/OS compatible layout installed. Syncing disks.... ...done zvmlinx5:/boot/zipl # Ralph > -----Original Message----- > From: Adam Thornton [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 11, 2004 11:18 AM > To: [EMAIL PROTECTED] > Subject: Re: Suse install under z/vm > > On Wed, 2004-08-11 at 11:02, Noll, Ralph wrote: > > Ok.. Sorry here are the msgs > > > > Vfs mounted root (ext2 filesystem) > > Kmod: failed to exec /sbin/modprobe -s -k block-major-94 errno=2 > > Vfs: cannot open root device dasda1 or 5e:01 Please append > a correct > > "root=" boot partition Kernel panic vfs unable to mount root fs or > > 5e:01 > > Hmmm. My initial guess would be that it's trying to load the > ECKD driver as a module and failing. That probably means > it's not in the ramdisk that you loaded...but if this is the > default SuSE install, it certainly should be. > > When it comes up under VM, you're IPLing from DASD, not from > the reader, right? You might want to bring the system up > under VM and do both a "zipl" and a "mkinitrd" (is this what > the command is under SuSE?) to make sure the boot record and > ramdisk are correct. > > Another thing to check is that you have exactly the same set > of DASD defined under VM and in the LPAR: if there's an extra > disk that Linux can see under VM, that might be the problem. > What does /etc/boot/parmfile (or parmline, don't remember > which) contain? > > Adam > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access > instructions, send email to [EMAIL PROTECTED] with the > message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
