> Remounting root filesystem in read-write mode That disk might still be attached to the other guest and you did not detach them, so when you ipled your guest the system's disk was mounted read only?
Sam Bass -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael MacIsaac Sent: Tuesday, August 21, 2012 9:02 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: RHEL 6.2 will not IPL Filipe, > I think you best shot for now is to start RHEL in init 1 or > Single user mode, and put SELinux in permissive mode. > If it works, probably RACF is not behaving well with SELinux. Thanks for the quick reply (and welcome to the land of z :)) I did not try run level 1. What I did try was logging off, DETACHing the DASD from SYSTEM, ATTACHing it to another Linux (two actually, both a SLES and a RHEL) and trying to mount the root file system. The other systems were not able to mount /dev/dasd<x>1. Curious - so maybe SE Linux was an effect and not the cause. I do not have time to debug, so I commented out the two DASD, grabbed two more DASD for minidisks 100 and 101 and updated the user directory entry. I reinstalled 6.2 onto the new disks *remembering to first start a root shell and dasdfmt the disks* (that is something I forgot to do the first time and had to do later after the first intall failed). Let me digress and say that this is an issue we've been trying to get fixed for years. It is mentioned on p 119 of the RHEL 6 Cookbook ( http://www.redbooks.ibm.com/abstracts/sg247932.html) with the following words: Important: If the minidisks 100-102 (dasdb-dasdd) have not been formatted for Linux by dasdfmt before this installation, you should see the window shown in Figure 7-5 on page 118. However, there is a known issue in RHEL 6 where this window does not open and you do not have the ability to format the disks through the installer. If you proceed without formatting the disks with dasdfmt, the installation process will fail later. If this is the case, perform the following steps: ... There was a bugzilla opened for this in RHEL 6, but I don't have the number handy. Brad knows about it and almost had it fixed in the Anaconda python code. If you can re-open it at Red Hat, that would be most appreciated. (sorry, don't mean to dump on you so soon :)) I'll follow up with more info on the can't login/SE Linux issue later. I did see two 3390-9s in /proc/dasd/devices listed as both 7042 and 7043 MB. I'm now wondering if forgetting to dasdfmt the first time is the cause of this problem. Again, welcome to system z - it will be good to have a Red Hat rep on the list again. "Mike MacIsaac" <mikemac at-sign us.ibm.com> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
