Does it make a difference whether you work with /mnt/sysimage (which is automatically mounted) instead of creating /mnt/sysimage2? i.e. chroot to /mnt/sysimage instead of manually mounting and chrooting to /mnt/sysimage2, then run mkinitrd/zipl (sorry about the reverse order before, quick fingers) :)
I wonder whether having the filesystems mounted twice could be causing a problem. -Brad On Tue, 2008-04-01 at 14:52 +0100, Ian S. Worthington wrote: > Thanks Peter > > But no better I regret. On restart: > > Scanning logical volumes > Reading all physical volumes. This may take a while... > No volume groups found > Activating logical volumes > Kernel panic - not syncing: Attempted to kill init > > > The recovery console log seems to suggest it should have worked though: > > login as: root > Welcome to the Red Hat Linux install environment 1.1 for zSeries > > Running anaconda, the CentOS 4.5 rescue mode - please wait... > > Your system is mounted under the /mnt/sysimage directory. > When finished please exit from the shell and your system will reboot. > > -/bin/sh-3.00# vgscan > Reading all physical volumes. This may take a while... > Found volume group "VGztpf" using metadata type lvm2 > Found volume group "VolGroup00" using metadata type lvm2 > -/bin/sh-3.00# vgchange -a y > 1 logical volume(s) in volume group "VGztpf" now active > 2 logical volume(s) in volume group "VolGroup00" now active > -/bin/sh-3.00# pvdisplay > --- Physical volume --- > PV Name /dev/dasdd1 > VG Name VGztpf > PV Size 6.88 GB / not usable 3.11 MB > Allocatable yes (but full) > PE Size (KByte) 4096 > Total PE 1760 > Free PE 0 > Allocated PE 1760 > PV UUID 27fl0g-kjxZ-VTij-eVvc-kfSM-MngN-0zrYNF > > --- Physical volume --- > PV Name /dev/dasdb1 > VG Name VolGroup00 > PV Size 2.29 GB / not usable 11.64 MB > Allocatable yes (but full) > PE Size (KByte) 32768 > Total PE 73 > Free PE 0 > Allocated PE 73 > PV UUID CYsk0I-XLWq-Kv9d-WtiJ-FEgu-b2IA-nY3aKi > > --- Physical volume --- > PV Name /dev/dasda2 > VG Name VolGroup00 > PV Size 2.19 GB / not usable 7.66 MB > Allocatable yes (but full) > PE Size (KByte) 32768 > Total PE 70 > Free PE 0 > Allocated PE 70 > PV UUID hVAnW9-UZWp-gCqC-Sphe-I70J-MZSm-GKjOXN > > --- Physical volume --- > PV Name /dev/dasdc1 > VG Name VolGroup00 > PV Size 6.88 GB / not usable 3.11 MB > Allocatable yes (but full) > PE Size (KByte) 32768 > Total PE 220 > Free PE 0 > Allocated PE 220 > PV UUID Os3guQ-6mwh-w2JE-LM3n-3Nwy-QaGp-U6E4cd > > -/bin/sh-3.00# vgdisplay > --- Volume group --- > VG Name VGztpf > System ID > Format lvm2 > Metadata Areas 1 > Metadata Sequence No 2 > VG Access read/write > VG Status resizable > MAX LV 0 > Cur LV 1 > Open LV 0 > Max PV 0 > Cur PV 1 > Act PV 1 > VG Size 6.88 GB > PE Size 4.00 MB > Total PE 1760 > Alloc PE / Size 1760 / 6.88 GB > Free PE / Size 0 / 0 > VG UUID W43y78-W5NB-JGP4-8nGY-Xeh1-0xix-vsgPgI > > --- Volume group --- > VG Name VolGroup00 > System ID > Format lvm2 > Metadata Areas 3 > Metadata Sequence No 5 > VG Access read/write > VG Status resizable > MAX LV 0 > Cur LV 2 > Open LV 2 > Max PV 0 > Cur PV 3 > Act PV 3 > VG Size 11.34 GB > PE Size 32.00 MB > Total PE 363 > Alloc PE / Size 363 / 11.34 GB > Free PE / Size 0 / 0 > VG UUID HR6ncp-igb1-xWEo-m57q-HFfl-UdSk-wNRBjC > > -/bin/sh-3.00# lvdisplay > --- Logical volume --- > LV Name /dev/VGztpf/LVztpf > VG Name VGztpf > LV UUID eENhVR-eSRV-pFi6-GU2K-Gph8-h1es-tI2MyN > LV Write Access read/write > LV Status available > # open 0 > LV Size 6.88 GB > Current LE 1760 > Segments 1 > Allocation inherit > Read ahead sectors 0 > Block device 253:0 > > --- Logical volume --- > LV Name /dev/VolGroup00/LogVol00 > VG Name VolGroup00 > LV UUID 9u3PP2-LwdK-XA58-rQPO-3kLs-K73H-NSIEDj > LV Write Access read/write > LV Status available > # open 1 > LV Size 10.84 GB > Current LE 347 > Segments 4 > Allocation inherit > Read ahead sectors 0 > Block device 253:1 > > --- Logical volume --- > LV Name /dev/VolGroup00/LogVol01 > VG Name VolGroup00 > LV UUID WDKLbG-Ysln-It39-0eaH-cqw9-ISrf-y6Esd9 > LV Write Access read/write > LV Status available > # open 1 > LV Size 512.00 MB > Current LE 16 > Segments 1 > Allocation inherit > Read ahead sectors 0 > Block device 253:2 > > -/bin/sh-3.00# mkdir /mnt/sysimage2 > -/bin/sh-3.00# mount /dev/VolGroup00/LogVol00 /mnt/sysimage2 > -/bin/sh-3.00# mount /dev/dasda1 /mnt/sysimage2/boot > -/bin/sh-3.00# mount /dev/VGztpf/LVztpf /mnt/sysimage2/ztpf > -/bin/sh-3.00# chroot /mnt/sysimage2 /bin/bash > bash-3.00# /sbin/mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r` > Creating initramfs > Looking for deps of module ide-disk > Looking for deps of module ext2 > Looking for deps of module dm-mod > Looking for deps of module dm-mirror dm-mod > Looking for deps of module dm-mod > Looking for deps of module dm-zero dm-mod > Looking for deps of module dm-mod > Looking for deps of module dm-snapshot dm-mod > Looking for deps of module dm-mod > Using modules: ./kernel/drivers/md/dm-mod.ko ./kernel/drivers/md/dm-mirror.ko > ./kernel/drivers/md/dm-zero.ko ./kernel/drivers/md/dm- > > snapshot.ko > /sbin/nash -> /tmp/initrd.qAk813/bin/nash > /sbin/insmod.static -> /tmp/initrd.qAk813/bin/insmod > /sbin/udev.static -> /tmp/initrd.qAk813/sbin/udev > /etc/udev/udev.conf -> /tmp/initrd.qAk813/etc/udev/udev.conf > copy from /lib/modules/2.6.9-55.EL/./kernel/drivers/md/dm-mod.ko(elf64-s390) > to /tmp/initrd.qAk813/lib/dm-mod.ko(elf64-s390) > copy from > /lib/modules/2.6.9-55.EL/./kernel/drivers/md/dm-mirror.ko(elf64-s390) to > /tmp/initrd.qAk813/lib/dm-mirror.ko(elf64-s390) > copy from /lib/modules/2.6.9-55.EL/./kernel/drivers/md/dm-zero.ko(elf64-s390) > to /tmp/initrd.qAk813/lib/dm-zero.ko(elf64-s390) > copy from > /lib/modules/2.6.9-55.EL/./kernel/drivers/md/dm-snapshot.ko(elf64-s390) to > /tmp/initrd.qAk813/lib/dm-snapshot.ko(elf64-s390) > /sbin/lvm.static -> /tmp/initrd.qAk813/bin/lvm > /etc/lvm -> /tmp/initrd.qAk813/etc/lvm > `/etc/lvm/lvm.conf' -> `/tmp/initrd.qAk813/etc/lvm/lvm.conf' > Loading module dm-mod > Loading module dm-mirror > Loading module dm-zero > Loading module dm-snapshot > bash-3.00# /sbin/zipl -V > Using config file '/etc/zipl.conf' > Target device information > Device..........................: 5e:00 > Partition.......................: 5e:01 > DASD device number..............: 0120 > Type............................: disk partition > Disk layout.....................: ECKD/compatible disk layout > Geometry - heads................: 15 > Geometry - sectors..............: 12 > Geometry - cylinders............: 3339 > Geometry - start................: 24 > File system block size..........: 4096 > Physical block size.............: 4096 > Device size in physical blocks..: 25596 > Building bootmap '/boot//bootmap' > Building menu 'rh-automatic-menu' > Adding #1: IPL section 'linux' (default) > kernel image......: /boot/vmlinuz-2.6.9-55.EL at 0x10000 > kernel parmline...: 'root=/dev/VolGroup00/LogVol00' at 0x1000 > initial ramdisk...: /boot/initrd-2.6.9-55.EL.img at 0x800000 > Preparing boot device: 0120. > Preparing boot menu > Interactive prompt......: enabled > Menu timeout............: 15 seconds > Default configuration...: 'linux' > Syncing disks... > Done. > bash-3.00# > > > > > ------ Original Message ------ > Received: Tue, 01 Apr 2008 01:28:43 PM BST > From: Peter 1 Oberparleiter <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: DASD error on zlinux ipl > > > Linux on 390 Port <[email protected]> wrote on 01.04.2008 13:59:27: > > > I should have mentioned that I did try Brad's original suggestion, whose > > > mkinitrd syntax works, but it didn't fix the problem: > > > > Not sure if this has been mentioned, but Brad's original suggestions > > contained this step: > > > > > > 4. Rerun zipl/mkinitrd: > > > > zipl -V; mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r` > > > > which has the order of zipl/mkinitrd reversed. zipl needs to be run > > *after* > > mkinitrd. > > > > > > Regards, > > Peter Oberparleiter > > > > -- > > Peter Oberparleiter > > Linux on System z Development > > IBM Deutschland Entwicklung GmbH > > > > ---------------------------------------------------------------------- > > 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 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 ---------------------------------------------------------------------- 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
