Properly boot from mdadm via findiso boot option.
authorMichael Prokop <mika@debian.org>
Tue, 15 Oct 2013 15:36:32 +0000 (17:36 +0200)
committerDaniel Baumann <mail@daniel-baumann.ch>
Tue, 15 Oct 2013 15:53:49 +0000 (17:53 +0200)
commit130f0d741827ba9fef3a02cc25e4ea3b619a4352
tree39857f234689d9048cd92562b1b4533dfb0b1289
parent1f307e532397bf92fca2856ae65547531150c584
Properly boot from mdadm via findiso boot option.

For example grml-rescueboot uses findiso for booting the ISO.
When booting from a software RAID using mdadm then
/scripts/local-top/mdadm being used inside
/scripts/boot/9990-misc-helpers.sh leaks its output to the
environment, causing invalid data used inside the
mount_images_in_directory function. Because the invalid data
results in a failing mount_images_in_directory execution we end
up with failed boot and error message:

  "No supported filesystem images found at ...."

So instead redirect output of /scripts/local-top/mdadm to
/boot.log. Also make sure to check for existence of
/conf/conf.d/md before accessing it (the file doesn't always
exist).

While at it also make sure the same logic is used for
/scripts/local-top/lvm2.

See http://bts.grml.org/grml/issue1270
components/9990-misc-helpers.sh