Re: ClefOS will not come up

rom: 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 zLin

Re: ClefOS will not come up

: 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&qu

Re: ClefOS will not come up

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

Re: ClefOS will not come up

- 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

Re: ClefOS will not come up

-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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

.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

Re: ClefOS will not come up

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:

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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.

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

] 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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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?