also sprach Moshe Yudkowsky <[EMAIL PROTECTED]> [2005.05.23.2136 +0200]: > ii initrd-tools 0.1.79 tools to create initrd image for > prepackaged > ii mdadm 1.9.0-2.1 Manage MD devices aka Linux Software Raid > > The new packages are: > > ii initrd-tools 0.1.80 tools to create initrd image for > prepackaged > ii mdadm 1.9.0-2.3 Manage MD devices aka Linux Software Raid
okay, this sucks. initrd-tools 0.1.80 broke a lot of things, but
it's hard to say whether it's responsible here too.
> /dev/md1 mounted, read only. As far as I can tell, so did /dev/md2
> (swap). Then when it was time for /dev/md3 to mount, reiserfsck
> failed to find the superblock and the boot stopped and waited for
> me to intervence. Linux would continue to boot if I control-D to
> ignore the problem, but of course without my /home directories.
this is valuable information which makes me want to believe it's
mdadm...
> I *think* that counts as "not able to boot." Please forgive me for
> starting a panic if I'm not right.
you are doing the right thing. in the future, it's always good to be
as precise as possible and always include error messages and context
information when possible.
> >I am trying to reproduce the problem right now, so if I fail,
> >I would have to ask you to go back to the broken version.
>
> I should be able to do that.
Please do; I cannot reproduce. When you do, press ctrl-d and start
the system without /home. Make sure to enable bootlogd.
Then, please give me /var/log/boot, /var/log/dmesg, an `ls -l
/dev/md*`, your mdadm.conf file, and an output of mount.
If possible, hold your system there and get in touch with me
(ideally on IRC) so we can test further.
If that's not possible, please run the following commands and report
the output. If a command is successful, please run `mdadm --stop
/dev/md3` or `mdadm --stop /dev/md/3` before the next command.
- mdadm -A -s
- mdadm -A -s -a
- mdadm -A /dev/md/3 /dev/sda3 /dev/hda3 (or whatever those devices were)
- mdadm -A /dev/md/3
- mdadm -A /dev/md3 /dev/sda3 /dev/hda3 (or whatever those devices were)
- mdadm -A /dev/md3
> >Which devices failed?
>
> Just /dev/md3 didn't start. /dev/md1 and /dev/md2 did; combine
> that with the reiserfsck boot block report, and I was about ready
> to panic.
Hehe, sorry about that. Yeah, if this is an mdadm+devfs issue, we
should learn about it, even though it might have to be ignored for
sarge since devfs is deprecated.
> >This *could* be related to Steve's patch. I'll check it out.
>
> Let me know if you need any further information.
Steve's patch was already in -2.1, which worked for you. So it's
either initrd or my changes to mdadm.
--
.''`. 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!
"be the change you want to see in the world"
-- mahatma gandhi
signature.asc
Description: Digital signature
