Carsten, Thanks for the tip, I've tried it out and it has helped me get further with my problem analysis.
FYI - I've fixed the problem with all those I/O error messages on boot from the root dasd basevol (mounted r/o under VM) by making the boot sequence bypass /etc/init.d/boot.rootfsck when it is in the r/o root (basevol/guestvol) configuration. Thks Robert Yeung -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Carsten Otte Sent: Thursday, September 08, 2005 1:22 AM To: [email protected] Subject: Re: Boot i/o errors when running SLES9 with guestvol + R/O basevol Yeung, Robert wrote: > Thank you Carsten for the response, The guestvol/basevol notes > http://linuxvm.org/present/misc/basevol.html (by William Scully > 28Jan2004) advises that changing /etc/zipl.conf in this way is not > possible so I haven't tried it. If I do change it in that way on the > basevol (and zipl) can you suggest an easy way to change it back when > I need to write to the basevol? You can modify the ro attribute on-the-fly: echo 0 >/sys/bus/ccw/drivers/dasd-eckd/<device>/readonly makes the volume r+w echo 1 >(same as above) makes the volume readonly again -- Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- 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
