Hi Mark, I updated zipl.conf to add the "ro" to the end of the kernel parameters and that did fix that but it is still performing a "fsck" on the root file system prior to mounting it as R/O. As a result, I still end up with I/O errors on the root file system due to lost page writes. I reviewed the latest "Device Drivers, Features, and Commands - November 2007" but there does not appear to be a kernel parameter to stop it performing a "fsck" during initrd. This only seems to be the case with SLES10. I rebooted a SLES9 z/Linux guest to check what it does during initrd. It does not appear to "fsck" the root file system and mounts it R/O even though I do not specify "ro" in the kernel parameters. Is there a way to tell initrd not to "fsck" the root file system no matter what?
This is from the SLES10 boot log: Waiting for device /dev/dasda1 to appear: ok rootfs: major=94 minor=1 devn=24065 fsck 1.38 (30-Jun-2005) /dev/dasda1: clean, 46695/903168 files, 1171324/1802856 blocks fsck succeeded. Mounting root device read-only. Mounting root /dev/dasda1 end_request: I/O error, dev dasda, sector 192 Buffer I/O error on device dasda1, logical block 0 lost page write due to I/O error on dasda1 Regards, Craig. ---------------------------------------------------------------------- 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
