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

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.

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 found

Re: ClefOS will not come up

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

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

Sorry, but I don't work on this (low-level unix trouble shooting). Okay, I only have access via TN3270, so full-screen editing is not an option. My /etc/zipl.conf: cat /etc/zipl.conf Ý

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: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/chap-p

Re: ClefOS will not come up

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 1

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

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

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 b

Re: ClefOS will not come up

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 P

Re: ClefOS will not come up

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

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 uisfrancism

Re: ClefOS will not come up

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

Re: ClefOS will not come up

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.

Re: ClefOS will not come up

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

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 o

Re: ClefOS will not come up

Yes, ECKD and they are all attached and available. I now have it spewing out the following one line at a time (after hitting twice): Feb 26 20:53:38 mflnxclef00.ailife.com kernel: Initializing cgroup subsys cpuacc ÝmFeb 26 20:53:38 mflnxclef00.ailife.com kernel: Li nux version 3.10.0-1160.62.1.

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 m

Re: ClefOS will not come up

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 in

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

ClefOS will not come up

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 Ser