On 12:29 Mon 17 Aug , Benjamin Block wrote:
> Hej Mark,
>
> On 13:04 Sat 15 Aug , Mark Post wrote:
> > >>> On 8/14/2015 at 10:49 AM, Benjamin Block <bbl...@linux.vnet.ibm.com>
> > >>> wrote:
> > > In my case the system would not boot anymore because the second DASD was
> > > still masked by cio-ignores and the kernel couldn't build the btrfs (no
> > > support for degraded raids). I have not found a solution that would
> > > cover this out-of-the-box in SLES 12 (that included rebuilding the
> > > initrd loaded by zipl and the one loaded by grub2). The dependency
> > > tracking doesn't seem to take btrf-volumes into account.
> >
> > It looks like after adding the additional DASD volume to the file system
> > with "btrfs device add" the proper incantation is "grub2-install". After
> > that, rebooting the system works just fine.
> >
> > Just make sure you use YaST, or the dasd_configure command to bring the new
> > DASD volumes online initially. Simply using "chccwdev -e" won't cause the
> > udev rule(s) to be written, nor will it update
> > /boot/zipl/active_devices.txt.
> >
>
> I will try this as soon as I get a chance to. The test-system from back
> then is a bit different right now. I am pretty sure I used
> dasd_configure to activate the dasd and I definitly used the btrfs
> command, but I may have missed the call to grub2-install.
>
Just to follow up on that. I just gave it a try and that still doesn't
cut it completely. You still have to update the initrd of the kernel you
want to use, otherwise the system remains un-bootable.
Which means, if you use the feature, you have to do the same steps as I
have wrote for the LVM example: update the zipl-initrd (grub2-install,
update-bootloader) and update the kernel-initrd (dracut, mkinitrd). Plus
ofc using dasd_configure, as you have said, to activate the DASD in the
first place.
If you, for some reason, end up with an un-bootable system because you
missed something, you might try to specify the additional DASD manually
with the IPL. E.g.: if you added DASD 0.0.e10b in addition to the
original DASD that you have used during installation (lets say 0.0.e109)
try the IPL with [1]:
#cp ipl e109 parm rd.dasd=0.0.e10b
This should at least get you back into the system, but you'll still have to
update the said parts.
[1] -
http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html#sles12
- Device Drivers Book - Chp. 5
Beste Grüße / Best regards,
- Benjamin Block
--
Linux on z Systems Development / IBM Systems & Technology Group
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp / Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
