Here is my fstab zvmlinx5:/etc # cat fstab /dev/dasda1 / ext2 defaults 1 1 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 zvmlinx5:/etc #
Ralph > -----Original Message----- > From: Adam Thornton [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 11, 2004 1:10 PM > To: [EMAIL PROTECTED] > Subject: Re: Suse install under z/vm > > On Wed, 2004-08-11 at 12:59, Noll, Ralph wrote: > > Right ipling from dasd NOT reader > > > > **** cat of parmfile **** > > zvmlinx5:/boot/zipl # cat parmfile > > dasd=0a0e,0a0f root=/dev/dasda1 > > zvmlinx5:/boot/zipl # > > So this looks fine. Your root filesystem is on 0a0e, and > something else is on 0a0f...does that match up with what's in > /etc/fstab? > > > 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) > > This looks good; this means that the initrd will contain the > ECKD drivers, so you should be able to use eckd as the system > boots, before it has a filesystem yet. > > > 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 # > > This looks fine too. > > ReIPLing under VM still works, and IPLing under LPAR still > fails? If that's the case...I don't see what's wrong. Anyone else? > > 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
