There will be clues of some kind in the spooled console log, I'm sure. (Hint, hint.)
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Wolfe, Gordon W Sent: Thursday, April 14, 2005 5:24 PM To: LINUX-390@VM.MARIST.EDU Subject: Why read-only filesystem? I just cloned a new SLES9 server in VM from another, working (shut-down) SLES9 server. When I bring it up, however, the boot disk comes up read-only. lnx20019:/# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 3548928 2983088 385560 89% / proc 3548928 2983088 385560 89% /proc lnx20019:/# cat /proc/dasd/devices cat: /proc/dasd/devices: No such file or directory mount /dev/dasda1 / -o rw,remount -t ext3 mount: block device /dev/dasda1 is write-protected, mounting read-only The VM directory shows the disk as MR. There isn't anything in /etc/zipl.conf or /etc/fstab that would indicate this dasd device is read-only. So why is it coming up read-only? ---------------------------------------------------------------------- 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
