I don't know why the LS -L shows HTC.6500 etc We are running on a z9 BC.
ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-0X0150 -> ../../dasda lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-0X0150-part1 -> ../../dasda1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-0X0151 -> ../../dasdb lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-0X0151-part1 -> ../../dasdb1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-0X0152 -> ../../dasdc lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-0X0152-part1 -> ../../dasdc1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-0X0153 -> ../../dasdd lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-0X0153-part1 -> ../../dasdd1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0100.70 -> ../../d asdb lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0100.70-part1 -> . ./../dasda1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0100.70.0000000600 0000370000000000000000 -> ../../dasda lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0100.70.0000000600 0000370000000000000000-part1 -> ../../dasda1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0100.70.0000003800 000d0a0000000000000000 -> ../../dasdb lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0100.70.0000003800 000d0a0000000000000000-part1 -> ../../dasdb1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0300.4c -> ../../d asdc lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0300.4c-part1 -> . ./../dasdc1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0300.4c.0000000100 000d0a0000000000000000 -> ../../dasdc lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0300.4c.0000000100 000d0a0000000000000000-part1 -> ../../dasdc1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0800.3a -> ../../d asdd lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0800.3a-part1 -> . ./../dasdd1 lrwxrwxrwx 1 root root 11 Oct 29 15:04 ccw-HTC.65000000028194.0800.3a.0000000100 000d0a0000000000000000 -> ../../dasdd lrwxrwxrwx 1 root root 12 Oct 29 15:04 ccw-HTC.65000000028194.0800.3a.0000000100 000d0a0000000000000000-part1 -> ../../dasdd1 cat /proc/dasd/devices 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 9000 blocks, 35 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 59094 0 blocks, 2308 MB 0.0.0152(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 60084 0 blocks, 2347 MB 0.0.0153(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 60084 0 blocks, 2347 MB 0.0.0160(FBA ) at ( 94: 16) is dasde : active at blocksize: 512, 200000 blocks, 97 MB $ cat /proc/cmdline root=/dev/disk/by-id/ccw-HTC.55000000010772.0800.3a.0000000100000d0a000000000000 0000-part1 TERM=dumb BOOT_IMAGE=0 $ Ray Waters -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Ver Sent: Wednesday, October 28, 2009 11:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Waiting for device When it gives the "exiting to /bin/sh" message, use the shell to check what you have: ls -l /dev/disk/by-id/ cat /proc/dasd/devices cat /proc/cmdline As other folks have mentioned, maybe the by-id designation has changed for the device due to the added paths or the z/VM fix. Or maybe some other issue has caused the devices to disappear. Or perhaps there's a typo that crept unchecked into the initrd or zipl.conf since the last working boot attempt. Checking the above info should give some idea of what is actually there. Also if /proc/dasd/devices shows the correct dasd devices online you can even try an override to bring the system up all the way so you can log in and check and fix things from a full-screen session instead of being stuck on the z/VM console. If you're on a z10 you can try doing (assuming IPL device is 0150 and is showing up as dasda1): ipl 150 parm root=/dev/dasda1 If you're on a z9 and have the IPL going into an interactive boot menu, you can add kernel parameters to override the default while giving the boot section, ex: zIPL v1.6.3-0.24.5 interactive boot menu 0. default (ipl) 1. ipl 2. Failsafe Note: VM users please use '#cp vi vmsg <input>' Please choose (default will boot in 10 seconds): #cp vi vmsg 1 root=/dev/dasda1 The only thing with the second method is since you have a short time limit, you'll probably need to prepare the full statement ahead of time in some text editor so it can be pasted quickly onto the z/VM session when prompted. If the /proc/dasd/devices did not show the correct DASD devices then you can even bring a device online and continue with the rest of boot, ex: ... Loading ext3 Waiting for device /dev/disk/by-id/ccw-IBM.75000000029228.8421.86-part1 to appea r: ..............................not found -- exiting to /bin/sh $ cat /proc/dasd/devices $ echo 1 > /sys/bus/ccw/devices/0.0.8100/online dasd(eckd): 0.0.8100: 3390/0C(CU:3990/01) Cyl:10017 Head:15 Sec:224 dasd(eckd): 0.0.8100: (4kB blks): 7212240kB at 48kB/trk compatible disk layout dasda:VOL1/ 0X8186: dasda1 $ exit exit fsck 1.38 (30-Jun-2005) [/bin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/disk/by-id/ccw-IBM.75000000029228.84 21.86-part1 / (/dev/disk/by-id/ccw-IBM.75000000029228.8421.86-part1): clean, 141284/903168 f iles, 763757/1803036 blocks fsck succeeded. Mounting root device read-write. ... Cheers, - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] ---------------------------------------------------------------------- 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 NOTICE: This e-mail is intended solely for the use of the individual to whom it is addressed and may contain information that is privileged, confidential or otherwise exempt from disclosure. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by replying to the original message at the listed email address. Thank You. ---------------------------------------------------------------------- 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
