allora, ho analizzato il disco con smartmontools , tutto ok allora ho provato a reinserire il disco in raid con la procedura mdadm --add /dev/md0 /dev/sdc1
e ha reiniziato il sync ha finito, ho rigenerato init e ho riavviato ora ho una situazione del genere: mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Wed Dec 3 17:07:10 2008 Raid Level : raid1 Array Size : 309443904 (295.11 GiB 316.87 GB) Used Dev Size : 309443904 (295.11 GiB 316.87 GB) Raid Devices : 2 Total Devices : 2 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sun Dec 14 18:31:49 2008 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 8850bcba:1b398379:85ceab33:281aafb9 Events : 0.1788 Number Major Minor RaidDevice State 0 8 17 0 active sync /dev/sdb1 1 8 33 1 active sync /dev/sdc1 cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb1[0] sdc1[1] 309443904 blocks [2/2] [UU] ma cosa può essere stato??? calo di tensione? mentre riparavo tutto tenevo il case aperto mi è capitato per sbaglio di sfiorare i cavi di alimentazione di un harddisk serial ata appena l'ho toccato si è sentito un rumore strano provenire dall'hd siccome avevo aperto tail -f /var/log/messages mi è comparso questa lista di errori: Dec 14 18:00:46 plutone kernel: [ 7581.730055] dhfis 0x40 dmafis 0x40 sdbfis 0x20 Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] res 40/00:38:3f:73:69/00:38:3f:73:69/40 Emask 0x10 (ATA bus error) Dec 14 18:00:46 plutone kernel: [ 7581.730055] ata3: hard resetting link Dec 14 18:00:53 plutone kernel: [ 7588.289728] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Dec 14 18:00:53 plutone kernel: [ 7588.346699] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Dec 14 18:00:53 plutone kernel: [ 7588.401692] ata4.00: configured for UDMA/133 Dec 14 18:00:53 plutone kernel: [ 7588.401692] ata4: EH complete Dec 14 18:00:53 plutone kernel: [ 7588.401694] sd 3:0:0:0: [sdc] 625142448 512-byte hardware sectors (320073 MB) Dec 14 18:00:53 plutone kernel: [ 7588.401694] sd 3:0:0:0: [sdc] Write Protect is off Dec 14 18:00:53 plutone kernel: [ 7588.401694] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 14 18:00:53 plutone kernel: [ 7588.457694] ata3.00: configured for UDMA/133 Dec 14 18:00:53 plutone kernel: [ 7588.457694] ata3: EH complete ora il raid funziona e faccio qualche altra prova con smartmontools e poi si vedrà 2008/12/14 NN_il_Confusionario <pinkof.pal...@tiscalinet.it> > On Sun, Dec 14, 2008 at 05:35:49PM +0100, Alessandro A. wrote: > > che cosa può essere un bug?? oppure un problema hardware su sdc? > > praticamente certo un problema hardware. Che sia disco, cavi, controller > (scheda madre) o alimentatore (o meno probabilmente, ram o cpu), non so > dire. > > -- > Chi usa software non libero avvelena anche te. Digli di smettere. > Informatica=arsenico: minime dosi in rari casi patologici, altrimenti > letale. > Informatica=bomba: intelligente solo per gli stupidi che ci credono. > -- A.A.