[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-390
Subject:    Re: Waiting for device
From:       Mark Ver <markver () us ! ibm ! com>
Date:       2009-10-30 22:13:03
Message-ID: OFCFDE6DE1.2D2A3E10-ON8525765F.0076BD17-8525765F.007A0C69 () us ! ibm ! com
[Download RAW message or body]

Either these really are different DASD now or the DASD has changed IDs
from what used to be there.  As mentioned, the /dev/disk/by-id/ entries
are based on information coming directly from the storage device.   None
of the current ids for DASD 0150-0153 match what was there before (as
shown by the kernel parameters from /proc/cmdline and by what the initrd
was looking for).

Working with SUSE or IBM support may be able to give a definitive answer
as to which of the changes (the z/VM patch, or the new paths) lead to the
change.

If you're just looking to fix the system you can try to use a rescue
system to access the disks so that you could chroot in and modify
/etc/zipl.conf,  /etc/fstab, and then run mkinitrd and zipl to make the
changes effective.    If any of the workarounds I described in my original
note work and allow you to boot up in full, you can do the modifications
directly with out having to boot up a separate rescue system.


- 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 LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
[prev in list] [next in list] [prev in thread] [next in thread]