Hmmmm....seems the last command has 4 DASD units missing (0124-0127)
cat /etc/dasd.conf
0.0.0100          
0.0.0101          
0.0.0102          
0.0.0103          
0.0.0104          
0.0.0105          
0.0.0106          
0.0.0107          
0.0.0108          
0.0.0109          
0.0.010A          
0.0.010B          
0.0.010C          
0.0.010D          
0.0.010E          
0.0.010F          
0.0.0110          
0.0.0111          
0.0.0112          
0.0.0113          
0.0.0114          
0.0.0115          
0.0.0116          
0.0.0117          
0.0.0118          
0.0.0119          
0.0.011A          
0.0.011B          
0.0.011C          
0.0.011D          
0.0.011E          
0.0.011F          
0.0.0120          
0.0.0121          
0.0.0122          
0.0.0123          
Do they need to be added to this file?
Frank Ramaekers | Senior Systems Administrator | CIS Mainframe Services 


-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Neale 
Ferguson
Sent: Sunday, February 26, 2023 11:40 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

You should be able to get the system up to network access by using commands. At 
that point you can use the standard tools to update the configuration files.

- Get into maintenance mode using ^D (not sign D on 3270)
- Provide root password
- cio_ignore -R
- chcchwdev -e 0.0.0124 (repeat for other disks that haven't appeared)
- pvscan (to ensure the volumes you need are there)
- vgscan (see if the VG(s) is/are active, If not use the vgchange -ay <vg>  to 
activate)
- lvscan (to see if the logical volumes are available)
- mount -o remount,rw / (remount root so that it's r/w)
- mount -a to get all the other mountpoints populated
- cat /etc/dasd.conf (tell me what you see)
 
If all that's required to get the root file system up is already present with 
the current rd.dasd= entries in /etc/zipl.conf, then updating /etc/dasd.conf 
may be enough for you to get going again. Given how far you are into the boot 
process I think that *may* be the case.





----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit 
https://urldefense.com/v3/__http://www2.marist.edu/htbin/wlvindex?LINUX-390__;!!GePVz-XrgrDUrw!s3FXKmzYA9KT3K4j1fHLcdIhtzfArs5bTLNzgn8c5sQkQHYqCy6msyrjHsTuROlPtaoK2S-vjZ9vh1Cw$
 

----------------------------------------------------------------------
This message contains information which is privileged and confidential and is 
solely for the use of the intended recipient. If you are not the intended 
recipient, be aware that any review, disclosure, copying, distribution, or use 
of the contents of this message is strictly prohibited. If you have received 
this in error, please destroy it immediately and notify us at 
privacy...@globe.life.


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to