Re: ClefOS will not come up

2023-02-28 Thread Fred Bader 
I’m not sure if ClefOS includes the s390-tools package, but if so, the chzdev 
command may be an alternative way to handle adding devices to the current or 
persistent configuration.  More information is available at the following URLs:

https://www.ibm.com/docs/en/linux-on-systems?topic=linuxonibm/com.ibm.linux.z.ludd/ludd_c_perscfg.html
https://www.ibm.com/docs/en/linux-on-systems?topic=linuxonz-chzdev
https://github.com/ibm-s390-linux/s390-tools

Regards, Fred
_

   Fred Bader, IBM Z Washington Systems Center (WSC) - IBM Systems
   IBM Corp, 470 Springpark Pl, Suite 950/1000, Herndon, VA 20170-5253
   E-mail: fba...@us.ibm.com, Phone: 720-395-, Tieline: 676-

   IBM Z - "A powerful and secure platform built for business"
https://www.ibm.com/it-infrastructure/z/hardware


From: Linux on 390 Port  on behalf of Frank M. 
Ramaekers 
Date: Tuesday, February 28, 2023 at 7:41 AM
To: LINUX-390@VM.MARIST.EDU 
Subject: [EXTERNAL] Re: ClefOS will not come up
Again, much thanks to Neale for helping me through this.
Apparently, I missed the last of 12 steps needed to add DASD to a zLinux 
system, which was modifying the /etc/dasd.conf.

Thank you!
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: Monday, February 27, 2023 12:30 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

- cp /etc/dasd.conf /etc/dasd.conf.save

- echo "0.0.0124" >>/etc/dasd.conf (and repeat for each address - NOTE the >>) 
OR
- printf "0.0.0124\n0.0.0125\n0.0.0126\n0.0.0127\n" >>/etc/dasd.conf

- cat /etc/dasd.conf (to make sure it looks okay)

If you make a mistake then just copy the saved version back over.



--
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<http://www2.marist.edu/htbin/wlvindex?LINUX-390>

--
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

--
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

Re: ClefOS will not come up

2023-02-28 Thread Frank M. Ramaekers 
Again, much thanks to Neale for helping me through this.
Apparently, I missed the last of 12 steps needed to add DASD to a zLinux 
system, which was modifying the /etc/dasd.conf. 

Thank you!
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: Monday, February 27, 2023 12:30 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

- cp /etc/dasd.conf /etc/dasd.conf.save

- echo "0.0.0124" >>/etc/dasd.conf (and repeat for each address - NOTE the >>) 
OR
- printf "0.0.0124\n0.0.0125\n0.0.0126\n0.0.0127\n" >>/etc/dasd.conf

- cat /etc/dasd.conf (to make sure it looks okay)

If you make a mistake then just copy the saved version back over.



--
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!tOVfmKUazSEyOn_Kx-SMwwr2xpFSvzGbaFFwD_aMWAY74rhTD8hJcCBffQlciAmf8TlUwwu5KHnMsFf8$
 

--
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

Re: ClefOS will not come up

2023-02-27 Thread Steffen Maier 

On 2/27/23 07:30, Neale Ferguson wrote:

- cp /etc/dasd.conf /etc/dasd.conf.save

- echo "0.0.0124" >>/etc/dasd.conf (and repeat for each address - NOTE the >>)
OR
- printf "0.0.0124\n0.0.0125\n0.0.0126\n0.0.0127\n" >>/etc/dasd.conf

- cat /etc/dasd.conf (to make sure it looks okay)


That's good and fixes the persistent device configuration on the root file 
system.
I think you can do that once you dynamically fixed up the active device
configuration on the dracut emergency shell to continue booting successfully.
After all this, a rebuild of the initramfs and the boot record are likely
required to have subsequent boots work correctly out of the box:
https://public.dhe.ibm.com/software/dw/linux390/docu/lgu5dd06.pdf#%5B%7B%22num%22%3A311%2C%22gen%22%3A0%7D%2C%7B%22name%22%3A%22XYZ%22%7D%2C59.8677%2C697.459%2Cnull%5D
(https://www.ibm.com/docs/en/linux-on-systems?topic=bd-rebuild-initrd)

--
Mit freundlichen Gruessen / Kind regards
Steffen Maier

Linux on IBM Z and LinuxONE

https://www.ibm.com/privacy/us/en/
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschaeftsfuehrung: David Faller
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
- cp /etc/dasd.conf /etc/dasd.conf.save

- echo "0.0.0124" >>/etc/dasd.conf (and repeat for each address - NOTE the >>)
OR
- printf "0.0.0124\n0.0.0125\n0.0.0126\n0.0.0127\n" >>/etc/dasd.conf

- cat /etc/dasd.conf (to make sure it looks okay)

If you make a mistake then just copy the saved version back over.



--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Hseems 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   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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
My typo chccwdev (change CCW device)

On 2/27/23, 15:45, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:

chcchwdev -d 0.0.0124 
bash: chcchwdev: command not found



--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
chcchwdev -d 0.0.0124 
bash: chcchwdev: command not found

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   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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
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   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
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
   
   ramdisk=/boot/initramfs-3.10.0-1160.25.1.el7.s390x.img   

Ýlinux-0-rescue-d02295ef486d45f287f9e07e98cc909a¨   

 image=/boot/vmlinuz-0-rescue-d02295ef486d45f287f9e07e98cc909a  

 ramdisk=/boot/initramfs-0-rescue-d02295ef486d45f287f9e07e98cc909a.img  

 parameters="root=/dev/mapper/clefos_mfclef00-root crashkernel=auto 
rd.lvm.lv=clefos_mfclef00/root rd.dasd=0.0.0100 rd.dasd=0.0.0101
 rd.dasd=0.0.0102 rd.dasd=0.0.0103 rd.dasd=0.0.0104 rd.dasd=0.0.0105 
rd.dasd=0.0.0106 rd.dasd=0.0.0107 rd.lvm.lv=clefos_mfclef00/swa
p rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1" 


...something awk and/or sed?

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:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

No, those parameters are (for ClefOS 7) in /etc/zipl.conf. I use the rd.dasd= 
mechanism for devices needed for the root file system. Other dasd may be 
specified in /etc/dasd.conf. 

 Checkout: 
https://urldefense.com/v3/__https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-post-installation-configuration-s390__;!!GePVz-XrgrDUrw!tIoQ6NI21w08dt33hCkClKGUj8bPoUPW8YPnKNYidf50oBZ_hAWbQMUa_tKhOUGKd3nv6VRSWkTNYutY$
 

On 2/27/23, 15:11, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:

Hmmm...don't think I use parameters, I 'IPL 100' rather than from a RDR deck.



--
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!tIoQ6NI21w08dt33hCkClKGUj8bPoUPW8YPnKNYidf50oBZ_hAWbQMUa_tKhOUGKd3nv6VRSWr_-EwDG$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
No, those parameters are (for ClefOS 7) in /etc/zipl.conf. I use the rd.dasd= 
mechanism for devices needed for the root file system. Other dasd may be 
specified in /etc/dasd.conf. 

 Checkout: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-post-installation-configuration-s390

On 2/27/23, 15:11, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:

Hmmm...don't think I use parameters, I 'IPL 100' rather than from a RDR deck.



--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Hmmm...don't think I use parameters, I 'IPL 100' rather than from a RDR deck.

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:00 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

Like parameters to the dasd driver. In any event to get going again just use 
cio_ignore -R to remove the disks from the ignore list and then use chccwdev -e 
to bring them online. Have pvscan look again to see if it can find things. 

On 2/27/23, 14:57, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


Other methods?



--
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!sJsN9uj39t_AuLphRlWRKZy3HO-9W2OhnQwlaSfRgRIGLymnoHCKrZGMU-EqnZG_0EOU5i_0DR_WEd9T$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
Like parameters to the dasd driver. In any event to get going again just use 
cio_ignore -R to remove the disks from the ignore list and then use chccwdev -e 
to bring them online. Have pvscan look again to see if it can find things. 

On 2/27/23, 14:57, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:


Other methods?



--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Other methods?

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 10:52 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

You may have added disks to the LV but you cio_ignore settings are stopping 
them from being seen at IPL. There are a number of ways to avoid this. The 
hammer approach is to add the devices to your boot parameter "rd.dasd=" but 
check the other methods.

On 2/27/23, 14:44, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


Hmmmseems some are missing:


--
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!oZ6aHbWdmrvhDzyppMvAHmXcf357S27MWeFlH0eZRPzkvbExgPWZM4fcoQAByzO5GAC0-9WNWnvlx9t7$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
You may have added disks to the LV but you cio_ignore settings are stopping 
them from being seen at IPL. There are a number of ways to avoid this. The 
hammer approach is to add the devices to your boot parameter "rd.dasd=" but 
check the other methods.

On 2/27/23, 14:44, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:


Hmmmseems some are missing:


--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Odd...the order 0100-0127 should be same order as the dasda-dasdaj

Frank Ramaekers | Senior Systems Administrator | CIS Mainframe Services 


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

External Message – Think Before You Click

Hmmmseems some are missing:
q v dasd  
LNXCLF00 : DASD 0100 3390 VM2F50 R/W  10016 CYL ON DASD  2F50 SUBCHANNEL = 
0005
LNXCLF00 : DASD 0101 3390 VM2F51 R/W  10016 CYL ON DASD  2F51 SUBCHANNEL = 
0006
LNXCLF00 : DASD 0102 3390 VM2F52 R/W  10016 CYL ON DASD  2F52 SUBCHANNEL = 
0007
LNXCLF00 : DASD 0103 3390 VM2F53 R/W  10016 CYL ON DASD  2F53 SUBCHANNEL = 
0008
LNXCLF00 : DASD 0104 3390 VM2F54 R/W  10016 CYL ON DASD  2F54 SUBCHANNEL = 
0009
LNXCLF00 : DASD 0105 3390 VM2F55 R/W  10016 CYL ON DASD  2F55 SUBCHANNEL = 
000A
LNXCLF00 : DASD 0106 3390 VM2F56 R/W  10016 CYL ON DASD  2F56 SUBCHANNEL = 
000B
LNXCLF00 : DASD 0107 3390 VM2F57 R/W  10016 CYL ON DASD  2F57 SUBCHANNEL = 
000C
LNXCLF00 : DASD 0108 3390 VM2F58 R/W  10016 CYL ON DASD  2F58 SUBCHANNEL = 
000D
LNXCLF00 : DASD 0109 3390 VM2F59 R/W  10016 CYL ON DASD  2F59 SUBCHANNEL = 
000E
LNXCLF00 : DASD 010A 3390 VM2F5A R/W  10016 CYL ON DASD  2F5A SUBCHANNEL = 
000F
LNXCLF00 : DASD 010B 3390 VM2F5B R/W  10016 CYL ON DASD  2F5B SUBCHANNEL = 
0010
LNXCLF00 : DASD 010C 3390 VM2F5C R/W  10016 CYL ON DASD  2F5C SUBCHANNEL = 
0011
LNXCLF00 : DASD 010D 3390 VM2F5D R/W  10016 CYL ON DASD  2F5D SUBCHANNEL = 
0012
LNXCLF00 : DASD 010E 3390 VM2F5E R/W  10016 CYL ON DASD  2F5E SUBCHANNEL = 
0013
LNXCLF00 : DASD 010F 3390 VM2F5F R/W  10016 CYL ON DASD  2F5F SUBCHANNEL = 
0014
LNXCLF00 : DASD 0110 3390 VM2F60 R/W  10016 CYL ON DASD  2F60 SUBCHANNEL = 
0015
LNXCLF00 : DASD 0111 3390 VM2F61 R/W  10016 CYL ON DASD  2F61 SUBCHANNEL = 
0016
LNXCLF00 : DASD 0112 3390 VM2F62 R/W  10016 CYL ON DASD  2F62 SUBCHANNEL = 
0017
LNXCLF00 : DASD 0113 3390 VM2F63 R/W  10016 CYL ON DASD  2F63 SUBCHANNEL = 
0018
LNXCLF00 : DASD 0114 3390 VM2F64 R/W  10016 CYL ON DASD  2F64 SUBCHANNEL = 
0019
LNXCLF00 : DASD 0115 3390 VM2F65 R/W  10016 CYL ON DASD  2F65 SUBCHANNEL = 
001A
LNXCLF00 : DASD 0116 3390 VM2F66 R/W  10016 CYL ON DASD  2F66 SUBCHANNEL = 
001B
LNXCLF00 : DASD 0117 3390 VM2F67 R/W  10016 CYL ON DASD  2F67 SUBCHANNEL = 
001C
LNXCLF00 : DASD 0118 3390 VM2F68 R/W  10016 CYL ON DASD  2F68 SUBCHANNEL = 
001D
LNXCLF00 : DASD 0119 3390 VM2F69 R/W  10016 CYL ON DASD  2F69 SUBCHANNEL = 
001E
LNXCLF00 : DASD 011A 3390 VM2F6A R/W  10016 CYL ON DASD  2F6A SUBCHANNEL = 
001F
LNXCLF00 : DASD 011B 3390 VM2F6B R/W  10016 CYL ON DASD  2F6B SUBCHANNEL = 
0020
LNXCLF00 : DASD 011C 3390 VM2F6C R/W  10016 CYL ON DASD  2F6C SUBCHANNEL = 
0021
LNXCLF00 : DASD 011D 3390 VM2F6D R/W  10016 CYL ON DASD  2F6D SUBCHANNEL = 
0022
LNXCLF00 : DASD 011E 3390 VM2F6E R/W  10016 CYL ON DASD  2F6E SUBCHANNEL = 
0023
LNXCLF00 : DASD 011F 3390 VM2F6F R/W  10016 CYL ON DASD  2F6F SUBCHANNEL = 
0024
LNXCLF00 : DASD 0120 3390 VM2F70 R/W  10016 CYL ON DASD  2F70 SUBCHANNEL = 
0025
LNXCLF00 : DASD 0121 3390 VM2F71 R/W  10016 CYL ON DASD  2F71 SUBCHANNEL = 
0026
LNXCLF00 : DASD 0122 3390 VM2F72 R/W  10016 CYL ON DASD  2F72 SUBCHANNEL = 
0027
LNXCLF00 : DASD 0123 3390 VM2F73 R/W  10016 CYL ON DASD  2F73 SUBCHANNEL = 
0028
LNXCLF00 : DASD 0124 3390 VM2F74 R/W  10016 CYL ON DASD  2F74 SUBCHANNEL = 
0029
LNXCLF00 : DASD 0125 3390 VM2F75 R/W  10016 CYL ON DASD  2F75 SUBCHANNEL = 
002A
LNXCLF00 : DASD 0126 3390 VM2F76 R/W  10016 CYL ON DASD  2F76 SUBCHANNEL = 
002B
LNXCLF00 : DASD 0127 3390 VM2F77 R/W  10016 CYL ON DASD  2F77 SUBCHANNEL = 
002C
LNXCLF00 : DASD 0190 3390 M01RES R/O214 CYL ON DASD  2F82 SUBCHANNEL = 
0037
LNXCLF00 : DASD 0191 3390 M01U02 R/O   1000 CYL ON DASD  2FA2 SUBCHANNEL = 
003A
LNXCLF00 : DASD 019D 3390 M01RES R/O292 CYL ON DASD  2F82 SUBCHANNEL = 
0038
LNXCLF00 : DASD 019E 3390 M01RES R/O500 CYL ON DASD  2F82 SUBCHANNEL = 
0039
LNXCLF00 : DASD 0300 9336 (VDSK) R/W 524288 BLK ON DASD  VDSK SUBCHANNEL = 
003C
LNXCLF00 : DASD 0301 9336 (VDSK) R/W1048576 BLK ON DASD  VDSK SUBCHANNEL = 
003D
LNXCLF00 : DASD 0592 3390 M01RES R/O240 CYL ON DASD  2F82 SUBCHANNEL = 
003B

cat /proc/dasd/devices  
  
cat /proc/dasd/devices  
  
0.0.0100(ECKD) at ( 94: 0) is dasda   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0101(ECKD) at ( 94: 4) is dasdb   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0102(ECKD) at ( 94: 8) is dasdc   : active at blocksize: 4096, 
1802880 blocks, 7042

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
0.0.0107(ECKD) at ( 94:28) is dasdh   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010a(ECKD) at ( 94:32) is dasdi   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010d(ECKD) at ( 94:36) is dasdj   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0109(ECKD) at ( 94:40) is dasdk   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010f(ECKD) at ( 94:44) is dasdl   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010b(ECKD) at ( 94:48) is dasdm   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010c(ECKD) at ( 94:52) is dasdn   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.010e(ECKD) at ( 94:56) is dasdo   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0110(ECKD) at ( 94:60) is dasdp   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0108(ECKD) at ( 94:64) is dasdq   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0111(ECKD) at ( 94:68) is dasdr   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0112(ECKD) at ( 94:72) is dasds   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0118(ECKD) at ( 94:76) is dasdt   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0116(ECKD) at ( 94:80) is dasdu   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0117(ECKD) at ( 94:84) is dasdv   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0113(ECKD) at ( 94:88) is dasdw   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011a(ECKD) at ( 94:92) is dasdx   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0119(ECKD) at ( 94:96) is dasdy   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0114(ECKD) at ( 94:   100) is dasdz   : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0115(ECKD) at ( 94:   104) is dasdaa  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011b(ECKD) at ( 94:   108) is dasdab  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0122(ECKD) at ( 94:   112) is dasdac  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011c(ECKD) at ( 94:   116) is dasdad  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011e(ECKD) at ( 94:   120) is dasdae  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0120(ECKD) at ( 94:   124) is dasdaf  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011f(ECKD) at ( 94:   128) is dasdag  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0121(ECKD) at ( 94:   132) is dasdah  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.0123(ECKD) at ( 94:   136) is dasdai  : active at blocksize: 4096, 
1802880 blocks, 7042 MB
0.0.011d(ECKD) at ( 94:   140) is dasdaj  : active at blocksize: 4096, 
1802880 blocks, 7042 MB

...namely: 0123-0127

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 10:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

Are all the devices you see when you #CP Q V DA in /proc/dasd/devices? If not, 
what happens with a cio_ignore -R and chccwdev -e <0.0.> for those you 
cannot see?

On 2/27/23, 14:21, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:

pvscan 
WARNING: Device for PV GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx not found or 
rejected by a filter.
WARNING: Device for PV wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH not found or 
rejected by a filter.
WARNING: Device for PV CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U not found or 
rejected by a filter.
WARNING: Device for PV jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO not found or 
rejected by a filter.
Couldn't find device with uuid GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx. 
Couldn't find device with uuid wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH. 
Couldn't find device with uuid CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U. 
Couldn't find device with uuid jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO. 



--
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!pGOpcMcEDsNoYege46p6ajZuM8bqttYLqH4zc9auTYgF-G_6NIL1ip0GVACJcUWkLKU8HZ-RGxIIIE5P$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
Are all the devices you see when you #CP Q V DA in /proc/dasd/devices? If not, 
what happens with a cio_ignore -R and chccwdev -e <0.0.> for those you 
cannot see?

On 2/27/23, 14:21, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:

pvscan 
WARNING: Device for PV GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx not found or 
rejected by a filter.
WARNING: Device for PV wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH not found or 
rejected by a filter.
WARNING: Device for PV CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U not found or 
rejected by a filter.
WARNING: Device for PV jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO not found or 
rejected by a filter.
Couldn't find device with uuid GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx. 
Couldn't find device with uuid wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH. 
Couldn't find device with uuid CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U. 
Couldn't find device with uuid jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO. 



--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Don't really see any problems in dmesg.  Not sure where to get syslog, there is 
a /var/log/message, but don't really see anything there.

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 9:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

When you logged on the guest did you see any messages pertaining to disks not 
available? Did the z/VM system come up with all its DASD and if so did they all 
get attached to the system? Maybe you Linux guest is missing a minidisk or more 
such that LVM is not able to find everything it needs to mount volumes? Those 
messages appear to indicate it can't find everything it needs.

- If you are ECKD - Check with #CP Q V DA all that it has all the minidisks it 
expects
- If you are SCSI - Check with #CP Q V FCP that all the required subchannels 
are available for getting to the SAN
- Login to maintenance mode and use PVSCAN/VGSCAN/LVSCAN to verify all required 
pieces are present
- Use dmesg to review kernel messages
- Check syslog for any additional clues

On 2/27/23, 13:13, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


I had z/VM jerk the rug out from under our zLinux system and now I can't get it 
up.


Starting Crash recovery kernel arming...
Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
Ý Ý32m OK Ý0m¨ Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view 
system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to try 
again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):




ÝKÝ Ý1;31m TIME Ý0m¨ Timed out waiting for device 
dev-ma...-clefos_mfclef00\x2dhome.device.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for File System 
C...dev/mapper/clefos_mfclef00-home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for /home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Local File Systems.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Mark the need to relabel after reboot.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Migrate local... structure to the new 
structure.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Relabel all filesystems, if necessary.


--
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!rvW4rgMb5Z1mdDp57A0q2coUWw3kcEVSZaNHJx9UhQP1xZO1bQXvNI3TIB6zTpQX8LJ_ARRWF9drEM3q$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
;6.88 GiB / 0free¨   
  
  Total: 40 Ý274.00 GiB¨ / in use: 40 Ý274.00 GiB¨ / in no VG: 0 Ý0   ¨ 
  
 Ý1;31mroot@mflnxclef00 ~# Ý0m  
  

  
vgscan  
   
  Reading volume groups from cache. 
   
  WARNING: Device for PV GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx not found or 
rejected by a filter. 
  WARNING: Device for PV wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH not found or 
rejected by a filter. 
  WARNING: Device for PV CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U not found or 
rejected by a filter. 
  WARNING: Device for PV jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO not found or 
rejected by a filter. 
  Couldn't find device with uuid GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx.
   
  Couldn't find device with uuid wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH.
   
  Couldn't find device with uuid CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U.
   
  Couldn't find device with uuid jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO.
   
  Found volume group "clefos_mfclef00" using metadata type lvm2 
   

lvscan  
  
lvscan  
  
  WARNING: Device for PV GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx not found or 
rejected by a filter.
  WARNING: Device for PV wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH not found or 
rejected by a filter.
  WARNING: Device for PV CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U not found or 
rejected by a filter.
  WARNING: Device for PV jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO not found or 
rejected by a filter.
  Couldn't find device with uuid GQ9Cgw-Xwe7-oGPz-gqpI-G2dq-SqQm-vq0OAx.
  
  Couldn't find device with uuid wpYK2z-6fie-dcms-ug0b-C1gg-rgEZ-L3NEeH.
  
  Couldn't find device with uuid CdiU66-NfSx-vPDa-0Apb-jI5n-phvF-l5bG2U.
  
  Couldn't find device with uuid jwcY7B-hNVq-Sug3-ofmX-wFgr-Sfxu-coJTvO.
  
  ACTIVE'/dev/clefos_mfclef00/swap' Ý2.00 GiB¨ inherit  
  
  inactive  '/dev/clefos_mfclef00/home' Ý237.06 GiB¨ inherit
  
  ACTIVE'/dev/clefos_mfclef00/root' Ý<34.94 GiB¨ inherit
  

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 10:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

What about the other commands I suggested?

Also, what does systemctl status report? For any service that is down are you 
able to run:

systemctl list-dependencies  --all --reverse

On 2/27/23, 14:08, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


Yes, ECKD and they are all attached and available.


--
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!raftrVAg79n20WqHnBlSi25ZL1711qvcSSvcunQW6FlPdAtTWpQYHMmgDQnBHKxtMXRT002Z2uQisGu-$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Yeah, trying to get out of this line-by-line listingurg.

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 10:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

What about the other commands I suggested?

Also, what does systemctl status report? For any service that is down are you 
able to run:

systemctl list-dependencies  --all --reverse

On 2/27/23, 14:08, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


Yes, ECKD and they are all attached and available.


--
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!raftrVAg79n20WqHnBlSi25ZL1711qvcSSvcunQW6FlPdAtTWpQYHMmgDQnBHKxtMXRT002Z2uQisGu-$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
What about the other commands I suggested?

Also, what does systemctl status report? For any service that is down are you 
able to run:

systemctl list-dependencies  --all --reverse

On 2/27/23, 14:08, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:


Yes, ECKD and they are all attached and available.


--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
flnxclef00.ailife.com kernel: dasd-eckd 0.0.011d: DASD with 4 
K Ýmlines 430-452   
 Feb 26 20:53:39 mflnxclef00.ailife.com kernel:  dasdaj:VOL1/  0X011D: dasdaj1 
Ým   
lines 431-453   

 Feb 26 20:53:39 mflnxclef00.ailife.com kernel: qeth: register layer 2 
discipline Ýmlines 432-454   
 Feb 26 20:53:39 mflnxclef00.ailife.com kernel: qdio: 0.0.0602 OSA on SC 2f 
using Ýmlines 433-455   
 Feb 26 20:53:39 mflnxclef00.ailife.com kernel: netif_napi_add() called with 
weig Ýmlines 434-456   
 Feb 26 20:53:39 mflnxclef00.ailife.com kernel: qeth 0.0.0600: MAC address 
02:00: Ýmlines 435-457   
 Feb 26 20:53:39 mflnxclef00.ailife.com kernel: qeth 0.0.0600: Device is a 
Virtua Ýmlines 436-458   
with link type Virt.NIC QDIO 
(por Ýmlines 437-459   
 Feb 26 20:53:41 mflnxclef00.ailife.com systemdÝ1¨: Found device 
/dev/mapper/clef Ýmlines 438-460   
 -- Subject: Unit dev-mapper-clefos_mfclef00\x2droot.device has finished 
start-up Ýmlines 439-461   
 -- Defined-By: systemd Ým  
 
...

Dasd is at 100-127.

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 9:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ClefOS will not come up

External Message – Think Before You Click

When you logged on the guest did you see any messages pertaining to disks not 
available? Did the z/VM system come up with all its DASD and if so did they all 
get attached to the system? Maybe you Linux guest is missing a minidisk or more 
such that LVM is not able to find everything it needs to mount volumes? Those 
messages appear to indicate it can't find everything it needs.

- If you are ECKD - Check with #CP Q V DA all that it has all the minidisks it 
expects
- If you are SCSI - Check with #CP Q V FCP that all the required subchannels 
are available for getting to the SAN
- Login to maintenance mode and use PVSCAN/VGSCAN/LVSCAN to verify all required 
pieces are present
- Use dmesg to review kernel messages
- Check syslog for any additional clues

On 2/27/23, 13:13, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life <mailto:uisfrancism.ramaek...@globe.life>> 
wrote:


I had z/VM jerk the rug out from under our zLinux system and now I can't get it 
up.


Starting Crash recovery kernel arming...
Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
Ý Ý32m OK Ý0m¨ Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view 
system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to try 
again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):




ÝKÝ Ý1;31m TIME Ý0m¨ Timed out waiting for device 
dev-ma...-clefos_mfclef00\x2dhome.device.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for File System 
C...dev/mapper/clefos_mfclef00-home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for /home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Local File Systems.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Mark the need to relabel after reboot.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Migrate local... structure to the new 
structure.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Relabel all filesystems, if necessary.


--
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!rvW4rgMb5Z1mdDp57A0q2coUWw3kcEVSZaNHJx9UhQP1xZO1bQXvNI3TIB6zTpQX8LJ_ARRWF9drEM3q$
 

--
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

Re: ClefOS will not come up

2023-02-26 Thread Neale Ferguson 
When you logged on the guest did you see any messages pertaining to disks not 
available? Did the z/VM system come up with all its DASD and if so did they all 
get attached to the system? Maybe you Linux guest is missing a minidisk or more 
such that LVM is not able to find everything it needs to mount volumes? Those 
messages appear to indicate it can't find everything it needs.

- If you are ECKD - Check with #CP Q V DA all that it has all the minidisks it 
expects
- If you are SCSI - Check with #CP Q V FCP that all the required subchannels 
are available for getting to the SAN
- Login to maintenance mode and use PVSCAN/VGSCAN/LVSCAN to verify all required 
pieces are present
- Use dmesg to review kernel messages
- Check syslog for any additional clues

On 2/27/23, 13:13, "Linux on 390 Port on behalf of Frank M. Ramaekers" 
mailto:LINUX-390@VM.MARIST.EDU> on behalf of 
uisfrancism.ramaek...@globe.life > 
wrote:


I had z/VM jerk the rug out from under our zLinux system and now I can't get it 
up.


Starting Crash recovery kernel arming...
Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
See 'systemctl status kdump.service' for details.
Ý Ý32m OK Ý0m¨ Started Security Auditing Service.
Starting Update UTMP about System Boot/Shutdown...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes...
Ý Ý32m OK Ý0m¨ Started Update UTMP about System Runlevel Changes.
Welcome to emergency mode! After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to
try again to boot into default mode.
Give root password for maintenance
(or press Control-D to continue):




ÝKÝ Ý1;31m TIME Ý0m¨ Timed out waiting for device 
dev-ma...-clefos_mfclef00\x2dhome.device.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for File System 
C...dev/mapper/clefos_mfclef00-home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for /home.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Local File Systems.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Mark the need to relabel after reboot.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Migrate local... structure to the new 
structure.
Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Relabel all filesystems, if necessary.


--
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

Re: ClefOS will not come up

2023-02-26 Thread Frank M. Ramaekers 
Well, we were attempting to bring down z/VM 7.2, but some of the virtual 
machine wouldn't come down.  So we forced each of the virtual machine that were 
still up, then shutdown z/VM.  During this process we needed to change the 
clock, but we inadvertently set the time wrong (off 12 hours...am instead of 
pm.  So we performed a SHUTDOWN REIPL, but I hadn't noticed that the zLinux 
system had gotten autologged.  So I have no idea what state it was in when the 
REIPL was issued.

Frank Ramaekers | Senior Systems Administrator | CIS Mainframe Services 

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

External Message – Think Before You Click

Much of your console traffic is illegible in the mailing list e-mail and web 
page, but I can see that you mention z/VM "jerking the rug out from under" your 
Linux guest.  What do you mean?  Did you apply maintenance or something?  Or 
did you simply shutdown the guest and now it won't start?

Just trying to figure out if the issues is in z/VM or Linux. The vast majority 
of "won't reboot" Linux problems I have seen are the result of a broken file 
system in Linux.  What I do see is
  Timed out waiting for device dev-maclefos_mfclef00\x2dhome.device.

Regards,
Alan

Alan Altmark
IBM Senior z/VM Engineer
1 607 321 7556  (Mobile)
alan_altm...@us.ibm.com

> -Original Message-
> From: Linux on 390 Port  On Behalf Of Frank 
> M. Ramaekers
> Sent: Sunday, February 26, 2023 10:13 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [EXTERNAL] [LINUX-390] ClefOS will not come up
> Importance: High
> 
> I had z/VM jerk the rug out from under our zLinux system and now I 
> can't get it up.
> 
>  Starting Crash recovery kernel arming...
> Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
> See 'systemctl status kdump.service' for details.
> Ý Ý32m  OK   Ý0m¨ Started Security Auditing Service.
>  Starting Update UTMP about System Boot/Shutdown...
> Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Boot/Shutdown.
>  Starting Update UTMP about System Runlevel Changes...
> Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Runlevel Changes.
> Welcome to emergency mode! After logging in, type "journalctl -xb" to 
> view system logs, "systemctl reboot" to reboot, "systemctl default" or 
> ¬D to try again to boot into default mode.
> Give root password for maintenance
> (or press Control-D to continue):
> 
> 
>   ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 20s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m* Ý0m
> Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min 21s /
> 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*Ý0m¨ A start jo
> b is running for dev-mapp...ome.device (1min 21s / 1min 30s)  ÝKÝ Ý1;31m*
> Ý0m Ý31m* Ý0m¨ A start job is running for dev-mapp...o
> me.device (1min 22s / 1min 30s)  ÝKÝ Ý0m Ý31m*  Ý0m¨ A start job is
> running for dev-mapp...ome.device (1min 22s / 1min 30s)  ÝKÝ
> Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 23s / 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m* Ý 
> 0m¨ A start job is running for dev-mapp...ome.device (1min 23s / 1min 30s)
> ÝKÝ  Ý31m* Ý1;31m* Ý0m Ý31m*   Ý0m¨ A start job is runni
> ng for dev-mapp...ome.device (1min 24s / 1min 30s)  ÝKÝ   Ý31m* Ý1;31m*
> Ý0m Ý31m*  Ý0m¨ A start job is running for dev-mapp...ome.de
> vice (1min 24s / 1min 30s)  ÝKÝÝ31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job
> is running for dev-mapp...ome.device (1min 25s / 1min 30
> s)  ÝKÝ Ý31m* Ý1;31m* Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 25s / 1min 30s)  ÝKÝ  Ý31m* Ý0m¨ A start j
> ob is running for dev-mapp...ome.device (1min 26s / 1min 30s)  ÝKÝ Ý31m*
> Ý1;31m* Ý0m¨ A start job is running for dev-mapp...ome.
> device (1min 26s / 1min 30s)  ÝKÝÝ31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start
> job is running for dev-mapp...ome.device (1min 27s / 1min
> 30s)  ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 27s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m*
> Ý0m Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min
> 28s / 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*Ý0m¨ A star
> t job is running for dev-mapp...ome.device (1min 28s / 1min 30s)  ÝKÝ
> Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job is running for dev-mapp
> ...ome.device (1min 29s / 1min 30s)  ÝKÝ Ý0m Ý31m*  Ý0m¨ A start job is
> running for dev-mapp...ome.device (1min 29s / 1min 30s)  ÝKÝ Ý1;31m 
> TIME  Ý0m¨ Timed out waiting for device dev-ma...- 
> clefos_mfclef00\x2dhome.device.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency

Re: ClefOS will not come up

2023-02-26 Thread Alan Altmark 
Much of your console traffic is illegible in the mailing list e-mail and web 
page, but I can see that you mention z/VM "jerking the rug out from under" your 
Linux guest.  What do you mean?  Did you apply maintenance or something?  Or 
did you simply shutdown the guest and now it won't start?

Just trying to figure out if the issues is in z/VM or Linux. The vast majority 
of "won't reboot" Linux problems I have seen are the result of a broken file 
system in Linux.  What I do see is
  Timed out waiting for device dev-maclefos_mfclef00\x2dhome.device.

Regards,
Alan

Alan Altmark
IBM Senior z/VM Engineer
1 607 321 7556  (Mobile)
alan_altm...@us.ibm.com

> -Original Message-
> From: Linux on 390 Port  On Behalf Of Frank
> M. Ramaekers
> Sent: Sunday, February 26, 2023 10:13 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [EXTERNAL] [LINUX-390] ClefOS will not come up
> Importance: High
> 
> I had z/VM jerk the rug out from under our zLinux system and now I can't
> get it up.
> 
>  Starting Crash recovery kernel arming...
> Ý Ý1;31mFAILED Ý0m¨ Failed to start Crash recovery kernel arming.
> See 'systemctl status kdump.service' for details.
> Ý Ý32m  OK   Ý0m¨ Started Security Auditing Service.
>  Starting Update UTMP about System Boot/Shutdown...
> Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Boot/Shutdown.
>  Starting Update UTMP about System Runlevel Changes...
> Ý Ý32m  OK   Ý0m¨ Started Update UTMP about System Runlevel Changes.
> Welcome to emergency mode! After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or ¬D to try
> again to boot into default mode.
> Give root password for maintenance
> (or press Control-D to continue):
> 
> 
>   ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 20s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m* Ý0m
> Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min 21s /
> 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*Ý0m¨ A start jo
> b is running for dev-mapp...ome.device (1min 21s / 1min 30s)  ÝKÝ Ý1;31m*
> Ý0m Ý31m* Ý0m¨ A start job is running for dev-mapp...o
> me.device (1min 22s / 1min 30s)  ÝKÝ Ý0m Ý31m*  Ý0m¨ A start job is
> running for dev-mapp...ome.device (1min 22s / 1min 30s)  ÝKÝ
> Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 23s / 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*
> Ý
> 0m¨ A start job is running for dev-mapp...ome.device (1min 23s / 1min 30s)
> ÝKÝ  Ý31m* Ý1;31m* Ý0m Ý31m*   Ý0m¨ A start job is runni
> ng for dev-mapp...ome.device (1min 24s / 1min 30s)  ÝKÝ   Ý31m* Ý1;31m*
> Ý0m Ý31m*  Ý0m¨ A start job is running for dev-mapp...ome.de
> vice (1min 24s / 1min 30s)  ÝKÝÝ31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job
> is running for dev-mapp...ome.device (1min 25s / 1min 30
> s)  ÝKÝ Ý31m* Ý1;31m* Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 25s / 1min 30s)  ÝKÝ  Ý31m* Ý0m¨ A start j
> ob is running for dev-mapp...ome.device (1min 26s / 1min 30s)  ÝKÝ Ý31m*
> Ý1;31m* Ý0m¨ A start job is running for dev-mapp...ome.
> device (1min 26s / 1min 30s)  ÝKÝÝ31m* Ý1;31m* Ý0m Ý31m* Ý0m¨ A start
> job is running for dev-mapp...ome.device (1min 27s / 1min
> 30s)  ÝKÝ   Ý31m* Ý1;31m* Ý0m Ý31m*  Ý0m¨ A start job is running for dev-
> mapp...ome.device (1min 27s / 1min 30s)  ÝKÝ  Ý31m* Ý1;31m*
> Ý0m Ý31m*   Ý0m¨ A start job is running for dev-mapp...ome.device (1min
> 28s / 1min 30s)  ÝKÝ Ý31m* Ý1;31m* Ý0m Ý31m*Ý0m¨ A star
> t job is running for dev-mapp...ome.device (1min 28s / 1min 30s)  ÝKÝ
> Ý1;31m* Ý0m Ý31m* Ý0m¨ A start job is running for dev-mapp
> ...ome.device (1min 29s / 1min 30s)  ÝKÝ Ý0m Ý31m*  Ý0m¨ A start job is
> running for dev-mapp...ome.device (1min 29s / 1min 30s)
>  ÝKÝ Ý1;31m TIME  Ý0m¨ Timed out waiting for device dev-ma...-
> clefos_mfclef00\x2dhome.device.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for File System
> C...dev/mapper/clefos_mfclef00-home.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for /home.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Local File Systems.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Mark the need to relabel
> after reboot.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Migrate local... structure to
> the new structure.
> Ý Ý1;33mDEPEND Ý0m¨ Dependency failed for Relabel all filesystems, if
> necessary.
>  Starting Preprocess NFS configuration...
> 
> Okay, so I tried the above, but:
>  Starting Logout off all iSCSI sessions on shutdown...
> Ý Ý32m  OK   Ý0m¨ Reached target Timers.
> Ý Ý32m  OK   Ý0m¨ Reached target Login Prompts.
> Ý Ý32m  OK   Ý0m¨ Reached target Network is Online.
> Ý Ý32m  OK   Ý0m¨ Reached target Paths.
> Ý Ý32m  OK   Ý0m¨ Reached target Sockets.
>  Starting Tell Plymouth To Write Out Runtime Data...
>  Starting Import network configuration from initramfs...
> Ý Ý32m  OK   Ý0m¨ Started Logout off all iSCSI sessions on shutdown.
>  Starting