-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 22/07/2010 09:04, Neil Brown a écrit : >
> > I wonder if it could be > commit b179246f4f519082158279b2f45e5fd51842cc42 > causing this. > > Can you report the contents of /etc/mdadm/mdadm.conf ?? Please find it attached > > Can you boot of a live CDROM and see if > mdadm -As > > works, or spins or does something else bad? Well: the latest version of madm works on kernel version older the 2.6.34… and I've not found a live CD with ealier version (2.6.34 or 3.6.65.rc)… Should the version on the live CD of importance? BTW, I tried to left the system for a couple of years waiting something happens. Finally, I got an udev message: "no space left on device". The device was not indicated and I've no device (disk) short of room... Regards Jean-Luc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMR/OHUdGGXzzGnNARAmKoAJ4yMTZf2GLvLj5/vBcJmgOWE+Vs1ACfVeDn UcZ7D06PS/IY00m1v0KRQWo= =sMq4 -----END PGP SIGNATURE-----
# mdadm.conf # # Please refer to mdadm.conf(5) for information about this file. # # by default, scan all partitions (/proc/partitions) for MD superblocks. # alternatively, specify devices to scan, using wildcards if desired. DEVICE partitions # auto-create devices with Debian standard permissions CREATE owner=root group=disk mode=0660 auto=yes # automatically tag new arrays as belonging to the local system HOMEHOST <system> # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md3 UUID=a14b6e84:366c9fff:fd4061fc:100c5d56 ARRAY /dev/md4 UUID=3075c036:528fe022:fd4061fc:100c5d56 ARRAY /dev/md5 UUID=4e8929f4:f9b54516:fd4061fc:100c5d56 # This configuration was auto-generated on Wed, 16 Sep 2009 19:09:44 +0200 # by mkconf 3.0-2
mdadm.conf.sig
Description: PGP signature
