I ran into this problem as well. I went back and re-installed my master image. When I got to the partitioning step, I changed the FSTAB options for dev/dasdx to use "device-name" instead of "device-id". I'm not sure what one selection has over the other but it sure makes cloning a lot easier.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, February 28, 2008 5:49 PM To: IBMVM@LISTSERV.UARK.EDU Subject: error bringing up cloned system Does anyone know what I did wrong here. DDR'd new SLES10 -sp1 system and now receive the following IPL errors.. After the DDR I correctly relabel the pack to reflect its real addr as usual, define the pack to another guest machine and modify the mdisk to match the original. This time it does not work. I took the SLES defaults for installation for storage Device names. If I knew if this info was in a Yast log I could try to find it, if it would help. Waiting for udev to settle... Scanning for LVM volume groups... Reading all physical volumes. This may take a while... Found volume group "system" using metadata type lvm2 Activating LVM volume groups... 1 logical volume(s) in volume group "system" now active ..done Waiting for /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1 . no more events Checking file systems... fsck 1.38 (30-Jun-2005) Checking all file systems. error on stat() /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1: No such f [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 -a /dev/disk/by-id/ccw-IBM.75000000029 error on stat() /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1: No such f fsck.ext3: No such file or directory while trying to open /dev/disk/by-id/ccw-I /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1: /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> fsck.ext3 /dev/disk/by-id/ccw-IBM.75000000029217.2500.2e-part1 failed (status 0 [1A..failedblogd: no message logging because /var file system is not accessible fsck failed for at least one filesystem (not /).
