Re: Documentation? failure to update-initramfs causes Infinite md loop on boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



maximilian attems wrote:

pretty simple, you change mdadm.conf put it also on initramfs:
update-initramfs -u -k all

Sure, that's what I did after boot on rescue, chroot, etc. However, I wonder if the *documentation* -- Wiki, or even the man page discussion on boot -- should mention that changes in the mdadm.conf have to be propogated to /boot?

In fact, that's an interesting question: which changes have to propagate to /boot? I'd think any change that affects md devices with /etc/fstab entries set to "auto" would have to be followed by update-initramfs. That's quite some bit of hidden knowledge if true.

--
Moshe Yudkowsky * moshe@xxxxxxxxx * www.pobox.com/~moshe
  "All friends have real and imaginary components."
                     -- Moshe Yudkowsky
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux