Your message dated Sat, 29 Jan 2011 08:00:57 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-sysvinit-devel] Bug#611379: Squeeze does not boot
from RAID1 with mdadm
has caused the Debian Bug report #611379,
regarding Squeeze does not boot from RAID1 with mdadm
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
611379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611379
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-13.1
A freshly installed, or upgraded debian squeeze, amd64, does not boot
from MD.
It is an RAID1. Using Grub2, root fs in lvm2.
Mdadm is called in the initscript but it does not assemble the arrays.
It drops to an busybox then.
The array can be assembled with mdadm --assemble --scan
without problems. The root fs can be mounted then.
The mdadm.conf does contain the correct information about the arrays
since installation.
$ cat /etc/mdadm/mdadm.conf
DEVICE partitions
ARRAY /dev/md/0 metadata=1.2 UUID=cb22ca02:2b4c253a:aadf93ce:88d9273c
name=vm-backup:0
ARRAY /dev/md/1 metadata=1.2 UUID=9d2de97c:0694b253:4e96d6d1:e3c62df4
name=vm-backup:1
It may be hardware related, since it did work on another machine,
with the exact same setup. Only the UUID and the name= are different.
The machine is a SUN V40Z
02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
Fusion-MPT Dual Ultra320 SCSI (rev 08)
Maybe the problem is related with the new mdadm version?
Package: mdadm
Version: 3.1.4-1+8efb9d1
--- End Message ---
--- Begin Message ---
also sprach Hendrik Fabelje <[email protected]> [2011.01.28.2319 +0100]:
> Yes this seams to help...
> But it is not clear to me, why the init scripts do not wait for the
> first hard drive controller to be ready :(
Either your hardware is buggy or the driver in the kernel. Hopefully
squeeze+1 will fix this for you — then we'll hopefully have
event-driven boot.
--
.''`. martin f. krafft <[email protected]> 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 truth is rarely pure and never simple. modern life would be very
tedious if it were either, and modern literature a complete
impossibility!"
-- oscar wilde
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
