On Friday 27 June 2008 04:47, Aristarc Diez Redorta wrote:
>Hi, we are trying to move our Linux guest from G6 9672 with z/VM 4.3 to our
>z9 with z/VM 5.2
>After we halt our guest, we make a DDR copy of the DASD volumes and restore
>them in the new machine. It seems that all works fine, but in the boot log
>appears this error.
Here's a bit from your attached log:
>Waiting for device /dev/dasdb1 to appear: . ok
>rootfs: major=94 minor=5 devn=24069
>rootfs: /sys/block/dasdb/dasdb1 major=94 minor=5 devn=24069
>EXT3-fs: INFO: recovery required on readonly filesystem.
>EXT3-fs: write access will be enabled during recovery.
>kjournald starting. Commit interval 5 seconds
>EXT3-fs: recovery complete.
>EXT3-fs: mounted filesystem with ordered data mode.
>VFS: Mounted root (ext3 filesystem) readonly.
>Trying to move old root to /initrd ... failed
>Unmounting old root
>Trying to free ramdisk memory ... okay
>Freeing unused kernel memory: 100k freed
> INIT: version 2.85 booting
>System Boot Control: Running /etc/init.d/boot
>Mounting /proc filesystem..done
>Mounting sysfs on /sys..done
>Mounting /dev/pts..done
> Boot logging started on /dev/ttyS0(/dev/console) at Fri Jun 27 12:36:45 2008
>Mounting shared memory FS on /dev/shm..done
>Activating swap-devices in /etc/fstab...
>Adding 14380k swap on /dev/dasda1. Priority:42 extents:1
>^1A..done
>dasd_erp(3990): 0.0.0202: EXAMINE 24: No Record Found detected - fatal error
It looks like the Linux kernel successfully mounted /dev/dasdb1 from device
0202, started up init(1) and made the transition to user-space. It is
running shell scripts, so it was able to read the label and partition table
from your 0202 device.
But then it gets that EXAMINE error, which is what I usually see when
unformatted DASD is activated and the DASD driver tries to read an invalid
label. But a bit further down, we see this:
>end_request: I/O error, dev dasdb, sector 4806552
>Buffer I/O error on device dasdb1, logical block 600816
The device driver is not trying to read the label or partition table, it is
trying to read some file out near the end of the device. I can think of two
possible reasons for this failing: 1) you didn't get the entire filesystem
copied over to the new DASD, or 2) the 0202 device isn't defined to be as big
as it was on your original system. It's probably the latter. Check your
minidisk definition to make sure you got all the cylinders into that DASD
extent.
Disclaimer: I'm a Linux guy, so I'm mostly guessing about the VM part of
things. But I have learned a thing or two about managing DASD extents from
Linux in the past few years. :-)
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software, Inc.
Newton, MA USA
----------------------------------------------------------------------
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
