also sprach lrhorer <lrhorer@satx.rr.com> [2011.02.01.2123 +0100]:
> far too quickly to be seen, but then an error pops up concerning
> an address space collision of some PCI device. Then it shows three
> errors for RAID devices md1. md2, and md3, saying they are already
> in use.
This looks like a hardware problem, causing mdadm to fail to
assemble.
> Immediately thereafter the system shows errors concerning the RAID
> targets being already in use, after which point the system complains it
> can't mount / (md2), /dev, /sys, or /proc (in that order) because the
> sources do not exist (if /dev/md2 does not exist, how can it be busy?).
> Thereafter, of course, it fails to find init, since / is not mounted.
> It then tries to run BusyBox, but Busybox complains:
>
> /bin/sh: can't access tty; job control turned off
This is normal. Don't worry about that.
Instead, try to assemble the arrays manually. And provide me with
a lot more information, e.g.
ls -l /dev/md* /dev/[sh]d*
cat /proc/mdstat
mdadm -Es
dmesg
It would really help if you could also enable initramfs debugging
(http://wiki.debian.org/InitramfsDebug) and provide us with the
output file.
--
.''`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
"the mind of the thoroughly well-informed man is a dreadful thing.
it is like a bric-à-brac shop, all monsters and dust,
with everything priced above its proper value."
-- oscar wilde
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)