Re: RAID failed and machine freeze. Help me please! (Poor story about my RAID)
Andrea Ganduglia wrote:
> Hi@all, dear friends and sorry for my English.
>
> This is a poor story about my RAID software onto Debian Sarge (Kernel
> 2.6.8-2-386). Few days ago I founded on /dev/tty12 this message:
>
> end-request: I/O error dev sda sector 2923593
> ATA abnormal status 0x00 on port 0xAC07
>
> Machine was freeze, login from local or remote (ssh) disabled. I had
> reboot machine (from reset button) and it blocked at this message:
>
> Starting mdam monitor
>
> but I have access to filesystem (RW) from remote login (ssh), and I have
> copy all /var/log directory.
>
> kernel.log said:
>
> Sep 21 17:43:55 backup kernel: md: raid5 personality registered as nr 4
> Sep 21 17:43:55 backup kernel: md: md0 stopped.
> Sep 21 17:43:55 backup kernel: md: bind<sdb1>
> Sep 21 17:43:55 backup kernel: md: bind<sdc1>
> Sep 21 17:43:55 backup kernel: md: bind<sdd1>
> Sep 21 17:43:55 backup kernel: md: bind<sda1>
> Sep 21 17:43:55 backup kernel: md: kicking non-fresh sdc1 from array!
> Sep 21 17:43:55 backup kernel: md: unbind<sdc1>
> Sep 21 17:43:55 backup kernel: md: export_rdev(sdc1)
> Sep 21 17:43:55 backup kernel: raid1: raid set md0 active with 3 out
> of 4 mirrors
>
> and :~# cat /proc/mdstat
>
> Personalities : [raid0] [raid1] [raid5]
> md1 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
> 873293184 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
>
> md0 : active raid1 sda1[0] sdd1[3] sdb1[1]
> 1461760 blocks [4/3] [UU_U]
>
> unused devices: <none>
>
> On boot machine send me email message:
>
> This is an automatically generated mail message from mdadm
> running on backup
>
> A DegradedArray event had been detected on md device /dev/md0.
>
> Faithfully yours, etc.
>
> My machine have 4 disk SATA, and filesystem is composed by 2 RAID sf.
>
> /dev/md0 is a RAID1 (sda1,sdb1,sdc3,sdd4)
> /dev/md1 is a RAID5 (sda3,sdb3,sdc3,sdd3)
> swap is normal swap (sda2,sdb2,sdc2,sdd2)
>
> You can view fstab and most important logs into /var/log at this
> address:
> http://www.openclose.it/var/raidfailed/
>
> I don't know there is/are disk/s where problem is located, and I don't
> know how I can repaire it. I don't know, again, if problem are HD, swap,
> or other hardware parts.
>
> thx@all
Try adding the non-fresh partition back to md0. It should work if the
disk is good. I have had a couple of non-fresh disks kicked from arrays
recently, and all my attempts to find out what this means have been met
with the wind howling through the trees.
mdadm /dev/md0 -a /dev/sdc1
Reply to: