I just started receiving alerts yesterday on disk 4 have errors, and I noticed the hard drive light on the machine stays on. Disk 4 currently does not have any data on it. When I tried to see what was going on, I can no longer get to the webpage.

 

Recieved from server in email:

 

Subject:unRaid Failure Notification - One or more disks are disabled or invalid.

Status update for unRAID  Tower

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Status:

 

ERROR: The unRaid array needs attention. One or more disks are disabled or invalid.

 

 

Disk 4=DISK_DSBL

Server Name: Tower

Server IP: 10.1.1.2

Date: Sun Apr 22 12:53:07 EDT 2012

Filesystem          1K-blocks      Used Available Use% Mounted on

/dev/sda1              3908120    120112  3788008  4% /boot

/dev/sdb1            1953454872  20136348 1933318524  2% /mnt/cache

/dev/md4            1953454928    32840 1953422088  1% /mnt/disk4

/dev/md3            1953454928    32840 1953422088  1% /mnt/disk3

/dev/md2            1953454928 1311196648 642258280  68% /mnt/disk2

/dev/md1            1953454928 1176254304 777200624  61% /mnt/disk1

shfs                3906909856 2487450952 1419458904  64% /mnt/user

rdevNumErrors.0=160931

rdevLastIO.0=1335113550

rdevSpinupGroup.0=0

diskNumber.1=1

diskName.1=md1

diskSize.1=1953514552

diskState.1=7

diskId.1=Hitachi_HDS5C3020ALA632_ML0220F311XMKD

rdevNumber.1=1

rdevStatus.1=DISK_OK

rdevName.1=sdd

rdevSize.1=1953514552

rdevId.1=Hitachi_HDS5C3020ALA632_ML0220F311XMKD

rdevNumErrors.1=0

rdevLastIO.1=1335113586

 

I have also attached the syslog where I see this: (I had to delete some of the end of the syslog because it was to large.)

 

Apr 22 13:51:58 Tower kernel: md: disk0 read error

Apr 22 13:51:58 Tower kernel: handle_stripe read error: 3702259720/0, count: 1

 

 

And this over and over:

 

Apr 22 13:57:44 Tower kernel: ata2.00: error: { UNC }

Apr 22 13:57:44 Tower kernel: ata2.00: configured for UDMA/133

Apr 22 13:57:44 Tower kernel: ata2: EH complete

Apr 22 13:57:47 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Apr 22 13:57:47 Tower kernel: ata2.00: irq_stat 0x40000001

Apr 22 13:57:47 Tower kernel: ata2.00: failed command: READ DMA EXT

Apr 22 13:57:47 Tower kernel: ata2.00: cmd 25/00:08:08:9d:bd/00:00:dc:00:00/e0 tag 0 dma 4096 in

Apr 22 13:57:47 Tower kernel:          res 51/40:08:08:9d:bd/00:00:dc:00:00/0c Emask 0x9 (media error)

Apr 22 13:57:47 Tower kernel: ata2.00: status: { DRDY ERR }

 

I am not sure where to go from here.

 

 

Edit: I was trying to find out the version, and I think it is 5 beta-7. That is the last entry in the readme.txt file in /boot/

10.1.1.2-04-22-140449.txt

The drive light finally went off, and I now able to access the web interface. I did notice when I got into it, drive 4 is now showing "not installed". I did figure out that drive 0 is actually the parity drive. I am currently running a parity check before doing anything else.

The drive light finally went off, and I now able to access the web interface. I did notice when I got into it, drive 4 is now showing "not installed". I did figure out that drive 0 is actually the parity drive. I am currently running a parity check before doing anything else.

I'm not sure what you've done, but you cannot perform a parity check with a disabled or missing drive.

(To do so would effectively clobber parity and prevent re-construction of the missing drive)

 

Post a syslog, request guidance. 

 

Joe L.

Well I went to start the parity check, and realized it didn't do anything. It appears I have a dual drive failure. The good thing is I already have two drives in the machine that have nothing on them. One of them was a failure, and it looks like the parity drive also failed. I now see errors on it in the web interface.

 

I cleared the config, removed disk 4, set the parity drive as one of the spares, and set the machine to trust the drives to rebuild parity. I only have disk 1 and disk 2 with data on them, and I have never seen these two drives with any disk errors in the past. I also have never seen any errors during parity checks in the past either.

 

I think i got really lucky, and will be ok.  If something does get corrupted, it can be replaced.