Ubuntu being stupid.

        Ok, so I decided to change over to Ubuntu and live it on the desktop
for real like.
        This would be fine and dandy, but Ubuntu has a nasty little blind-spot
for RAID 10. It supports the RAID1 / fine, but since it does not
modprobe raid10 for some reason BEFORE it runs mdadm, I get a
non-functional RAID array for home! Then when it comes time to try and
mount it, it barfs.
        The only workaround (since they use a SysV init system and are
oh-so-kind as to point to an http://... instead of a text file in the
system, a pox on your house, Debian!) was to randomly frob the file
where the boot was failing to mdadm -S and then mdadm -A the array that
needed the module (after the module was inserted, allowing the array to
function, and me to get something approaching a normal setup).
        How am I really supposed to fix this? I can't, for the life of me,
find out where you specify the modules you for SURE want installed
before the system does anything else, and I don't know why it would be
trying to activate all RAID arrays before inserting the modules anyway
(frustrating, to say the least).

        I'd also like to file a bug about not docutmenting your boot scripts
for situations where you're staring at a terminal and may or may not
have network access. An http://.. reference is not an acceptable form
of documentation. Conrad?
Received on Mon May 8 02:10:57 2006