I built a new unRAID server with 2 Promise SATAII 300 and 6 WD 500gig drives on an old ASUS board (using SIS chipset).

 

Caught read errors on 1 drive very early in parity sync.  handle_stripe read error.  Should I worry about that?  I hope it doesn't fail...  syslog is below:

 

Oct 18 19:11:47 Tower emhttp[1238]: driver cmd: start NEW_ARRAY

Oct 18 19:11:47 Tower kernel: [  430.215702] mdcmd (5): start

Oct 18 19:11:47 Tower kernel: [  430.215808] md0: new disk

Oct 18 19:11:47 Tower kernel: [  430.215859] md1: new disk

Oct 18 19:11:47 Tower kernel: [  430.215908] md2: new disk

Oct 18 19:11:47 Tower kernel: [  430.215957] md3: new disk

Oct 18 19:11:47 Tower kernel: [  430.216005] md4: new disk

Oct 18 19:11:47 Tower kernel: [  430.216053] md5: new disk

Oct 18 19:11:47 Tower kernel: [  430.217353] unraid: allocated 13174kB

Oct 18 19:11:47 Tower kernel: [  430.217546] md1: running, size: 488386552 blocks

Oct 18 19:11:47 Tower kernel: [  430.217562] md2: running, size: 488386552 blocks

Oct 18 19:11:47 Tower kernel: [  430.217576] md3: running, size: 488386552 blocks

Oct 18 19:11:47 Tower kernel: [  430.217591] md4: running, size: 488386552 blocks

Oct 18 19:11:47 Tower kernel: [  430.217610] md5: running, size: 488386552 blocks

Oct 18 19:11:47 Tower emhttp[1238]: driver cmd: check

Oct 18 19:11:47 Tower kernel: [  430.267207] mdcmd (7): check

Oct 18 19:11:47 Tower kernel: [  430.267216] md: recovery thread got woken up ...

Oct 18 19:11:47 Tower kernel: [  430.267218] md: recovery thread syncing parity disk...

Oct 18 19:11:47 Tower emhttp[1238]: shcmd (31): udevsettle

Oct 18 19:11:47 Tower kernel: [  430.269305] md: using 1152k window, over a total of 488386552 blocks.

Oct 18 19:11:47 Tower emhttp[1490]: shcmd (32): mkdir /mnt/disk1

Oct 18 19:11:47 Tower emhttp[1490]: shcmd (32): exit status: 1

Oct 18 19:11:47 Tower emhttp[1490]: shcmd (33): mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1  >/dev/null 2>&1

Oct 18 19:11:47 Tower emhttp[1494]: shcmd (32): mkdir /mnt/disk2

Oct 18 19:11:47 Tower emhttp[1494]: shcmd (32): exit status: 1

Oct 18 19:11:47 Tower emhttp[1494]: shcmd (33): mount -t reiserfs -o noatime,nodiratime /dev/md2 /mnt/disk2  >/dev/null 2>&1

Oct 18 19:11:47 Tower emhttp[1498]: shcmd (32): mkdir /mnt/disk3

Oct 18 19:11:47 Tower emhttp[1500]: shcmd (32): mkdir /mnt/disk4

Oct 18 19:11:47 Tower emhttp[1502]: shcmd (32): mkdir /mnt/disk5

Oct 18 19:11:47 Tower emhttp[1502]: shcmd (33): mount -t reiserfs -o noatime,nodiratime /dev/md5 /mnt/disk5  >/dev/null 2>&1

Oct 18 19:11:47 Tower emhttp[1498]: shcmd (33): mount -t reiserfs -o noatime,nodiratime /dev/md3 /mnt/disk3  >/dev/null 2>&1

Oct 18 19:11:47 Tower emhttp[1500]: shcmd (33): mount -t reiserfs -o noatime,nodiratime /dev/md4 /mnt/disk4  >/dev/null 2>&1

Oct 18 19:11:47 Tower kernel: [  430.613047] ReiserFS: md1: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md1

Oct 18 19:11:47 Tower emhttp[1490]: shcmd (33): exit status: 32

Oct 18 19:11:47 Tower emhttp[1238]: disk1 mount error: 32

Oct 18 19:11:48 Tower kernel: [  430.676278] ReiserFS: md5: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md5

Oct 18 19:11:48 Tower kernel: [  430.676562] ReiserFS: md4: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md4

Oct 18 19:11:48 Tower kernel: [  430.676716] ReiserFS: md3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md3

Oct 18 19:11:48 Tower kernel: [  430.676936] ReiserFS: md2: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md2

Oct 18 19:11:48 Tower emhttp[1502]: shcmd (33): exit status: 32

Oct 18 19:11:48 Tower emhttp[1500]: shcmd (33): exit status: 32

Oct 18 19:11:48 Tower emhttp[1498]: shcmd (33): exit status: 32

Oct 18 19:11:48 Tower emhttp[1494]: shcmd (33): exit status: 32

Oct 18 19:11:48 Tower emhttp[1238]: disk2 mount error: 32

Oct 18 19:11:48 Tower emhttp[1238]: disk3 mount error: 32

Oct 18 19:11:48 Tower emhttp[1238]: disk4 mount error: 32

Oct 18 19:11:48 Tower emhttp[1238]: disk5 mount error: 32

Oct 18 19:11:48 Tower emhttp[1238]: shcmd (32): killall -HUP smbd

Oct 18 19:13:02 Tower kernel: [  505.391615] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:02 Tower kernel: [  505.391620] ata6.00: (port_status 0x20200000)

Oct 18 19:13:02 Tower kernel: [  505.391627] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:02 Tower kernel: [  505.391629]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:02 Tower kernel: [  505.427515] ata6.00: configured for UDMA/133

Oct 18 19:13:02 Tower kernel: [  505.427523] ata6: EH complete

Oct 18 19:13:05 Tower kernel: [  508.332157] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:05 Tower kernel: [  508.332161] ata6.00: (port_status 0x20200000)

Oct 18 19:13:05 Tower kernel: [  508.332167] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:05 Tower kernel: [  508.332169]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:05 Tower kernel: [  508.392053] ata6.00: configured for UDMA/133

Oct 18 19:13:05 Tower kernel: [  508.392060] ata6: EH complete

Oct 18 19:13:08 Tower kernel: [  511.289683] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:08 Tower kernel: [  511.289687] ata6.00: (port_status 0x20200000)

Oct 18 19:13:08 Tower kernel: [  511.289692] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:08 Tower kernel: [  511.289694]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:08 Tower kernel: [  511.346567] ata6.00: configured for UDMA/133

Oct 18 19:13:08 Tower kernel: [  511.346575] ata6: EH complete

Oct 18 19:13:11 Tower kernel: [  514.246215] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:11 Tower kernel: [  514.246220] ata6.00: (port_status 0x20200000)

Oct 18 19:13:11 Tower kernel: [  514.246227] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:11 Tower kernel: [  514.246229]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:11 Tower kernel: [  514.301098] ata6.00: configured for UDMA/133

Oct 18 19:13:11 Tower kernel: [  514.301111] ata6: EH complete

Oct 18 19:13:14 Tower kernel: [  517.203698] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:14 Tower kernel: [  517.203702] ata6.00: (port_status 0x20200000)

Oct 18 19:13:14 Tower kernel: [  517.203708] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:14 Tower kernel: [  517.203709]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:14 Tower kernel: [  517.255611] ata6.00: configured for UDMA/133

Oct 18 19:13:14 Tower kernel: [  517.255618] ata6: EH complete

Oct 18 19:13:17 Tower kernel: [  520.160221] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Oct 18 19:13:17 Tower kernel: [  520.160224] ata6.00: (port_status 0x20200000)

Oct 18 19:13:17 Tower kernel: [  520.160230] ata6.00: cmd 25/00:00:6f:96:2a/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 in

Oct 18 19:13:17 Tower kernel: [  520.160232]          res 51/01:00:2e:98:2a/01:00:00:00:00/e0 Emask 0x1 (device error)

Oct 18 19:13:17 Tower kernel: [  520.220121] ata6.00: configured for UDMA/133

Oct 18 19:13:17 Tower kernel: [  520.220171] sd 6:0:0:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08

Oct 18 19:13:17 Tower kernel: [  520.220174] sd 6:0:0:0: [sdf] Sense Key : 0x3 [current] [descriptor]

Oct 18 19:13:17 Tower kernel: [  520.220178] Descriptor sense data with sense descriptors (in hex):

Oct 18 19:13:17 Tower kernel: [  520.220181]        72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Oct 18 19:13:17 Tower kernel: [  520.220187]        00 2a 98 2e

Oct 18 19:13:17 Tower kernel: [  520.220190] sd 6:0:0:0: [sdf] ASC=0x13 ASCQ=0x0

Oct 18 19:13:17 Tower kernel: [  520.220193] end_request: I/O error, dev sdf, sector 2791470

Oct 18 19:13:17 Tower kernel: [  520.220221] ata6: EH complete

Oct 18 19:13:17 Tower kernel: [  520.221004] md4: read error!

Oct 18 19:13:17 Tower kernel: [  520.221008] handle_stripe read error: 2791400/4, count: 1

Oct 18 19:13:17 Tower kernel: [  520.221013] md4: read error!

Oct 18 19:13:17 Tower kernel: [  520.221015] handle_stripe read error: 2791408/4, count: 1

Oct 18 19:13:17 Tower kernel: [  520.221018] md4: read error!

Oct 18 19:13:17 Tower kernel: [  520.221019] handle_stripe read error: 2791416/4, count: 1

Oct 18 19:13:17 Tower kernel: [  520.221022] md4: read error!

Oct 18 19:13:17 Tower kernel: [  520.221024] handle_stripe read error: 2791424/4, count: 1

Oct 18 19:13:17 Tower kernel: [  520.221027] md4: read error!

Oct 18 19:13:17 Tower kernel: [  520.221028] handle_stripe read error: 2791432/4, count: 1

 

Parity sync still continuing, drives unformatted (of course) since this is new install.  Have 73 errors on 1 disk, that's it.  Hope it completes in 6 hrs...

Parity sync done.  It works. 

 

Can view/access the shares from my windows machine.  Not having much luck connecting from my linux (opensuse 10.3) machine.  Getting timeout / connection errors from konquerer if going through smb://tower/  Maybe my linux machine isn't resolving the unraid server IP correctly?

 

 

I'm glad it seems to be working fine for you now, but I would definitely keep an eye on Drive 4, I assume is sdf.  Those errors are NOT normal, and often indicate a bad drive, or sometimes a bad cable.

 

Before you store anything on it, I would pull it and try WD's diagnostics on it, and possibly SpinRite.  Seems better to me to know if you can trust the drive sooner than later.

 

Yeah, will do WD diagnostics on md4 drive, just in case.  Better to RMA / warranty exchange sooner than later.

WD diagnostic quick check returned md4 was ok, but had bad sectors after full scan.  Repaired, now to rebuild array, again.