Hi,

just two short ideas: 

1. did you apply all patches? I think I remember that something has
been fixed in that area.

2. please make sure with lsblk that all of the used devices have a UUID
set. Dracut does require a UUID by default and fails if it does not
find any on this block device. In doubt, change /etc/dracut.conf and add
  persistent_policy=by-path
then: 
  1. grub2-install
  2. dracut -f


Berthold

On Wed, 11 Mar 2015 16:12:33 +0200
Offer Baruch <[email protected]> wrote:

> Hi list,
> 
> I am facing a strange issue with SLES12.
> 
> Whenever I add a new DASD (using dasd_configure) and add it to the
> fstab the next boot will fail with:
> 
> Timed out waiting for device dev-disk-by\x2dpath-ccw...2dpart1.device
> Dependency failed for /mountpoint
> Dependency failed for Local File Systems.
> 
> As the device needed for that mountpoint (/dev/dasdb1) did not start
> in time.
> I then get into maintenance mode. Device /dev/dasdb1 is online and
> /mountpoint is already mounted.
> 
> 
> 
> So it looks like the device is ok but it starts too late in the boot
> process (a new feature in systemd will automatically mount the device
> when it goes online if it is in the fstab).
> 
> I have made sure of the following:
> 1.       New udev rule for the device is in place
> 2.       /boot/zipl/active_device.txt includes the new device
> 
> The following workarounds worked for me (but no real solution):
> 1.       Remove the mountpoint from the fstab (just to get out of
> maintenance mode)
> 2.       Remove the device from cio_ignore in grub (boot process will
> finish ok)
>     a.       I don’t want to edit grub every time I add a device
> 3.       Make a new initrd using dracut. As it will add the device to
> the rd.cio_accept parameter in the initrd (boot process will finish
> ok) a.       I don’t want to make a new initrd every time I add a
> device
> 
> Something is very wrong here… am I missing some new configuration
> file that needs to be updated (other than active_devices.txt)?
> 
> Any idea? Make initrd or editing grub is not a real solution…
> 
> Thanks in advance
> Offer Baruch
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390
> or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/



-- 
----------------------------------------------------------------------
 Berthold Gunreben                                  Build Service Team
 http://www.suse.de/                                     Maxfeldstr. 5
 SUSE LINUX GmbH                            D-90409 Nuernberg, Germany
 GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton HRB 21284 (AG Nürnberg) 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to