also sprach Moshe Yudkowsky <[EMAIL PROTECTED]> [2005.05.23.2155 +0200]: > But even so, through some interaction, this particular kernel > update failed to go smoothly -- it left me in a state where > I could no longer boot up.
yeah, this is bad.
> >Why are you manually calling `mdadm --assemble` anyway? Doesn't the
> >/etc/init.d/mdadm-raid script do everything you need?
>
> It used to! I only called it manually because it failed to work
> automatically at startup this time around.
I think I have a faint idea of what the problem could be: devfs
creates /dev/md/3, but mdadm.conf needs /dev/md3. Usually it would
auto-create this device, but with devfs, this may well fail.
> I now have bootlogd enabled; let me know if you need me to
> reproduce the error. I don't know how to tell when mdadm-raid gets
> called, as I've never seen it in a log file that I can recall.
Just boot the system by pressing ctrl-d when it tells you it failed
to mount /dev/md3. Then I think the following will be true:
- /dev/md/3 exists
- /dev/md3 does not
- mdadm -A -s -a fails
- /dev/md3 still does not exist
- /dev/md/3 still exists.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, admin, user, and author
`. `'`
`- Debian - when you have better things to do than fixing a system
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
"syntactic sugar causes cancer of the semicolon."
-- epigrams in programming
signature.asc
Description: Digital signature
