Check the contents of your /mnt/etc/zipl.conf. I believe the parmfile entry in there overrides other things.
Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED] Sent: Friday, September 19, 2003 10:11 AM To: [EMAIL PROTECTED] Subject: Moving dasd - something odd. After moving all my dasd and doing everything I thought was correct, I IPL'ed off of the new IPL device, Device B213 Upon inspection however, I found the following: rockhopper:/mnt/boot # cat /proc/dasd/devices a240(ECKD) at ( 94: 0) is dasda:active at blocksize: 4096, 217980 blocks, 851 MB b217(ECKD) at ( 94: 4) is dasdb:active at blocksize: 4096, 1821060 blocks, 7113 MB b219(ECKD) at ( 94: 8) is dasdc:active at blocksize: 4096, 1821060 blocks, 7113 MB b21a(ECKD) at ( 94: 12) is dasdd:active at blocksize: 4096, 1821060 blocks, 7113 MB b218(ECKD) at ( 94: 16) is dasde:active at blocksize: 4096, 1821060 blocks, 7113 MB a241(ECKD) at ( 94: 20) is dasdf:active at blocksize: 4096, 217980 blocks, 851 MB All indications are that it IPL'ed off of B217, my previous root volume! I went and checked the load address I entered for the IPL, and sure enough, it was B213. I used the relevant parts of the how-to on moving file systems, then mounted things thus: Original dasd Filesystem 1k-blocks Used Available Use% Mounted on /dev/dasdb1 7169608 257064 6548340 4% / /dev/dasdc1 7169608 38252 6767152 1% /var /dev/dasdd1 7169608 4041324 2764080 60% /opt /dev/dasde1 7169608 838428 5966976 13% /usr /dev/dasdf1 858100 13636 800876 2% /tmp New Dasd Filesystem 1k-blocks Used Available Use% Mounted on /dev/dasdg1 7098536 250456 6487484 4% /mnt /dev/dasdl1 858100 9268 805244 2% /mnt/tmp /dev/dasdj1 7098536 37496 6700444 1% /mnt/var /dev/dasdi1 7098536 838416 5899524 13% /mnt/usr /dev/dasdh1 7098536 4039352 2698588 60% /mnt/opt I IPL'ed off of the new 'root' volume after doing a chroot /mnt, editing the parmfile and running zipl Upon re-mounting the disk so I can see everything I can tell that: The parmfile in /boot on B213 (mounted at /mnt) was edited to: rockhopper:/mnt/boot # more parmfile dasd=a23c,b213,b216,b214,b215,a23d root=/dev/dasdb1 noinitrd The parmfile in /mnt/boot/zipl, however does not reflect the change that I would have expected zipl to produce. rockhopper:/mnt/boot/zipl # more parmfile dasd=a240,b217,b219,b21a,b218,a241 root=/dev/dasdb1 noinitrd So in the course of creating this e-mail I did a chroot to /mnt and ran zipl again, from the /boot directory of the disk rockhopper:/boot/zipl # ls -al total 68 drwxr-xr-x 2 root root 4096 Sep 19 09:02 . drwxr-xr-x 4 root root 4096 Feb 27 2003 .. -rwx------ 1 root root 16384 Sep 19 09:02 bootmap -rw-r--r-- 1 root root 512 Dec 19 2001 diag0 -rw-r--r-- 1 root root 920 Dec 19 2001 diag2 -rw-r--r-- 1 root root 24 Dec 19 2001 eckd0 -rw-r--r-- 1 root root 424 Dec 19 2001 eckd1a -rw-r--r-- 1 root root 144 Dec 19 2001 eckd1b -rw-r--r-- 1 root root 1136 Dec 19 2001 eckd2 -rw-r--r-- 1 root root 4096 Dec 19 2001 eckd2dump -rw-r--r-- 1 root root 232 Dec 19 2001 fba0 -rw-r--r-- 1 root root 1192 Dec 19 2001 fba2 -rw-r--r-- 1 root root 61 Sep 19 09:02 parmfile -rw-r--r-- 1 root root 4096 Dec 19 2001 tapedump As can be seen, the /boot/zipl directory shows changes dated today, a few minutes ago for both bootmap and parmfile which is expected. The parmfile contains: rockhopper:/boot/zipl # more parmfile dasd=a240,b217,b219,b21a,b218,a241 root=/dev/dasdb1 noinitrd So what did I miss? Did I edit the wrong parmfile? I always thought it was the parm file in /boot that was user by zipl to create the parmfile in /boot/zipl....
