I’m a recent unRaid Pro user and I need some help.

 

My hardware is:

 

Asus A8N-SLI Deluxe

 

Onboard Nforce controller with 4 x Seagate 500gb SATA

Onboard Sil3114 with 1 x Seagate 500gb SATA + 1 x WD 250gb SATA

PCI Sil3112 with 2 x WD 250gb SATA

Another PCI Sil3112 with 2 x WD 250gb SATA

 

At first I was only using 6 drives (without the Sil3112 controllers), parity was built with 0 errors, after a power failure and starting the array the parity check returned 6 errors, I though this was normal.

 

Yesterday I added the 4 WD drives on 2 x Sil3112 controllers, the array expanded without problems.

 

Today I swapped the WD 250gb on the Sil3114 onboard controller with a Samsung 500gb. The rebuild was OK but got 6 parity errors again. Started another parity check, it’s now at 1% with 4 sync errors.

 

From the log:

 

Dec  7 22:58:13 Tower kernel: [32925.313813]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.422940] ata2.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.422948] ata2: EH complete

Dec  7 22:58:13 Tower kernel: [32925.442695] ata3.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.442700] ata3: EH complete

Dec  7 22:58:13 Tower kernel: [32925.444888] ata1.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.444893] ata1: EH complete

Dec  7 22:58:13 Tower kernel: [32925.445554] ata4.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.445559] ata4: EH complete

Dec  7 22:58:13 Tower kernel: [32925.450307] ata9.00: configured for UDMA/100

Dec  7 22:58:13 Tower kernel: [32925.450314] ata9: EH complete

Dec  7 22:58:13 Tower kernel: [32925.597108] ata2.00: exception Emask 0x0 SAct 0

x0 SErr 0x0 action 0x0

Dec  7 22:58:13 Tower kernel: [32925.597116] ata2.00: cmd b0/d0:01:00:4f:c2/00:0

0:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:58:13 Tower kernel: [32925.597119]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.616845] ata3.00: exception Emask 0x0 SAct 0

x0 SErr 0x0 action 0x0

Dec  7 22:58:13 Tower kernel: [32925.616852] ata3.00: cmd b0/d0:01:00:4f:c2/00:0

0:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:58:13 Tower kernel: [32925.616855]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.619043] ata1.00: exception Emask 0x0 SAct 0

x0 SErr 0x0 action 0x0

Dec  7 22:58:13 Tower kernel: [32925.619051] ata1.00: cmd b0/d0:01:00:4f:c2/00:0

0:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:58:13 Tower kernel: [32925.619054]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.619737] ata4.00: exception Emask 0x0 SAct 0

x0 SErr 0x0 action 0x0

Dec  7 22:58:13 Tower kernel: [32925.619744] ata4.00: cmd b0/d0:01:00:4f:c2/00:0

0:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:58:13 Tower kernel: [32925.619747]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.624523] ata9.00: exception Emask 0x0 SAct 0

x0 SErr 0x0 action 0x0

Dec  7 22:58:13 Tower kernel: [32925.624530] ata9.00: cmd b0/d0:01:00:4f:c2/00:0

0:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:58:13 Tower kernel: [32925.624533]          res 51/04:01:00:4f:c2/00:0

0:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:58:13 Tower kernel: [32925.752514] ata1.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.752521] ata1: EH complete

Dec  7 22:58:13 Tower kernel: [32925.753174] ata4.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.753179] ata4: EH complete

Dec  7 22:58:13 Tower kernel: [32925.754904] sd 1:0:0:0: [sda] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:13 Tower kernel: [32925.755526] ata2.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.755530] ata2: EH complete

Dec  7 22:58:13 Tower kernel: [32925.757936] ata9.00: configured for UDMA/100

Dec  7 22:58:13 Tower kernel: [32925.757943] ata9: EH complete

Dec  7 22:58:13 Tower kernel: [32925.758635] ata3.00: configured for UDMA/133

Dec  7 22:58:13 Tower kernel: [32925.758640] ata3: EH complete

 

 

 

 

 

 

There are no read errors on the unraid webpage, just the sync errors.

Although I’m getting some errors the array seems to be functioning ok, also when I tail the log (before I started parity checking),  I kept getting these messages:

 

Dec  7 22:58:14 Tower kernel: [32926.994972] sd 2:0:0:0: [sdb] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32926.995027] sd 2:0:0:0: [sdb] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32926.995031] sd 2:0:0:0: [sdb] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32926.995088] sd 2:0:0:0: [sdb] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:58:14 Tower kernel: [32926.997008] ata9.00: configured for UDMA/100

Dec  7 22:58:14 Tower kernel: [32926.997019] ata9: EH complete

Dec  7 22:58:14 Tower emhttp[1942]: get_temperature: ioctl (smart): Input/output

error

Dec  7 22:58:14 Tower kernel: [32926.997684] ata3.00: configured for UDMA/133

Dec  7 22:58:14 Tower kernel: [32926.997695] ata3: EH complete

Dec  7 22:58:14 Tower emhttp[1940]: get_temperature: ioctl (smart): Input/output

error

Dec  7 22:58:14 Tower kernel: [32926.999952] sd 3:0:0:0: [sdd] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32927.000012] sd 3:0:0:0: [sdd] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32927.000016] sd 3:0:0:0: [sdd] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32927.000093] sd 3:0:0:0: [sdd] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:58:14 Tower kernel: [32927.000185] sd 4:0:0:0: [sde] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32927.000207] sd 4:0:0:0: [sde] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32927.000210] sd 4:0:0:0: [sde] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32927.000277] sd 4:0:0:0: [sde] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:58:14 Tower kernel: [32927.053405] sd 9:0:0:0: [sdj] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32927.057495] sd 9:0:0:0: [sdj] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32927.057500] sd 9:0:0:0: [sdj] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32927.081806] sd 9:0:0:0: [sdj] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:58:14 Tower kernel: [32927.081905] sd 1:0:0:0: [sda] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32927.081948] sd 1:0:0:0: [sda] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32927.081952] sd 1:0:0:0: [sda] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32927.082008] sd 1:0:0:0: [sda] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:58:14 Tower kernel: [32927.082056] sd 2:0:0:0: [sdb] 976773168 512-byt

e hardware sectors (500108 MB)

Dec  7 22:58:14 Tower kernel: [32927.082095] sd 2:0:0:0: [sdb] Write Protect is

off

Dec  7 22:58:14 Tower kernel: [32927.082099] sd 2:0:0:0: [sdb] Mode Sense: 00 3a

00 00

Dec  7 22:58:14 Tower kernel: [32927.082154] sd 2:0:0:0: [sdb] Write cache: enab

led, read cache: enabled, doesn't support DPO or FUA

 

Are these errors?

 

Any help appreciated, I plan to add 2 more drives to the onboard Sil3114 controller but I want to be sure it’s working ok first.

 

(The parity check is now at 8% with the same 4 errors)

 

The 2 syslog sections you have included are part of the drive setup phase, prior to unRAID becoming fully operational.  The first section does have some exception Emask errors (device errors it says), which are a little worrisome, but there may not be much you can do about them.  I used to see them too with my previous nForce4 board, often associated with drive problems.  If after your unRAID boots up and everything seems fine, then they can probably be ignored.  The second section is more of the same setup stuff, except for 2 get temp I/O errors, which are probably harmless.  Are your temps showing for every drive, and do they look like reasonable numbers?  If so, this too may be harmless.

 

What would be more interesting/troubling are the errors associated with the parity sync errors you reported.  They would be toward the end/tail of the syslog.

 

I'd love to comment on what I think of nForce4 boards, but don't want to discourage you.  You at least have one of the best ones.

 

Thanks for the reply, I can't see the temperature from the drives connected to the Nforce.

 

Parity check completed with 4 errors.

Copy from the syslog

 

 

Dec  7 22:51:48 Tower kernel: [32541.482569] md: recovery thread checking parity...

Dec  7 22:51:48 Tower kernel: [32541.596296] md: using 1152k window, over a total of 488386552 blocks.

Dec  7 22:51:50 Tower kernel: [32543.671387] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:50 Tower kernel: [32543.671398] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:50 Tower kernel: [32543.671401]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:50 Tower kernel: [32543.672555] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:50 Tower kernel: [32543.672563] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:50 Tower kernel: [32543.672566]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:50 Tower kernel: [32543.672705] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:50 Tower kernel: [32543.672712] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:50 Tower kernel: [32543.672715]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:50 Tower kernel: [32543.673301] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:50 Tower kernel: [32543.673308] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:50 Tower kernel: [32543.673311]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:50 Tower kernel: [32543.736493] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:50 Tower kernel: [32543.736500] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:50 Tower kernel: [32543.736503]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:50 Tower kernel: [32543.815951] ata3.00: configured for UDMA/133

Dec  7 22:51:50 Tower kernel: [32543.815963] ata3: EH complete

Dec  7 22:51:50 Tower kernel: [32543.816926] ata2.00: configured for UDMA/133

Dec  7 22:51:50 Tower kernel: [32543.816934] ata2: EH complete

Dec  7 22:51:50 Tower kernel: [32543.821870] ata9.00: configured for UDMA/100

Dec  7 22:51:50 Tower kernel: [32543.821878] ata9: EH complete

Dec  7 22:51:50 Tower kernel: [32543.821942] ata4.00: configured for UDMA/133

Dec  7 22:51:50 Tower kernel: [32543.821949] ata4: EH complete

Dec  7 22:51:50 Tower kernel: [32543.887372] ata1.00: configured for UDMA/133

Dec  7 22:51:50 Tower kernel: [32543.887378] ata1: EH complete

Dec  7 22:51:51 Tower kernel: [32543.990067] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:51 Tower kernel: [32543.990075] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:51 Tower kernel: [32543.990078]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:51 Tower kernel: [32543.991072] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:51 Tower kernel: [32543.991079] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:51 Tower kernel: [32543.991082]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:51 Tower kernel: [32543.996015] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:51 Tower kernel: [32543.996022] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:51 Tower kernel: [32543.996025]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:51 Tower kernel: [32543.996104] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:51 Tower kernel: [32543.996111] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:51 Tower kernel: [32543.996114]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:51 Tower kernel: [32544.061539] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:51 Tower kernel: [32544.061547] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:51 Tower kernel: [32544.061550]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.123579] ata3.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.123583] ata3: EH complete

Dec  7 22:51:52 Tower kernel: [32544.124552] ata2.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.124556] ata2: EH complete

Dec  7 22:51:52 Tower kernel: [32544.129497] ata9.00: configured for UDMA/100

Dec  7 22:51:52 Tower kernel: [32544.129502] ata9: EH complete

Dec  7 22:51:52 Tower kernel: [32544.129565] ata4.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.129569] ata4: EH complete

Dec  7 22:51:52 Tower kernel: [32544.186712] ata1.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.186715] ata1: EH complete

Dec  7 22:51:52 Tower kernel: [32544.297760] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.297767] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.297770]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.298770] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.298777] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.298780]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.303626] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.303633] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.303636]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.303716] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.303723] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.303726]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.360935] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.360942] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.360945]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.437177] ata9.00: configured for UDMA/100

Dec  7 22:51:52 Tower kernel: [32544.437182] ata9: EH complete

Dec  7 22:51:52 Tower kernel: [32544.437245] ata4.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.437249] ata4: EH complete

Dec  7 22:51:52 Tower kernel: [32544.439566] ata3.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.439569] ata3: EH complete

Dec  7 22:51:52 Tower kernel: [32544.440551] ata2.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.440554] ata2: EH complete

Dec  7 22:51:52 Tower kernel: [32544.502710] ata1.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.502713] ata1: EH complete

Dec  7 22:51:52 Tower kernel: [32544.611324] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.611331] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.611334]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.611419] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.611426] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.611429]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.613796] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.613803] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.613806]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.614696] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.614703] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.614706]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.676850] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.676857] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.676860]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.736545] ata9.00: configured for UDMA/100

Dec  7 22:51:52 Tower kernel: [32544.736551] ata9: EH complete

Dec  7 22:51:52 Tower kernel: [32544.736615] ata4.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.736618] ata4: EH complete

Dec  7 22:51:52 Tower kernel: [32544.738948] ata3.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.738952] ata3: EH complete

Dec  7 22:51:52 Tower kernel: [32544.739923] ata2.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.739927] ata2: EH complete

Dec  7 22:51:52 Tower kernel: [32544.802075] ata1.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32544.802079] ata1: EH complete

Dec  7 22:51:52 Tower kernel: [32544.910696] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.910703] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.910706]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.910783] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.910790] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.910793]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.913177] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.913184] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.913187]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.914072] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.914079] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.914082]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32544.976222] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32544.976229] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32544.976232]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.035917] ata9.00: configured for UDMA/100

Dec  7 22:51:52 Tower kernel: [32545.035922] ata9: EH complete

Dec  7 22:51:52 Tower kernel: [32545.035985] ata4.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.035989] ata4: EH complete

Dec  7 22:51:52 Tower kernel: [32545.038319] ata3.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.038323] ata3: EH complete

Dec  7 22:51:52 Tower kernel: [32545.039293] ata2.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.039297] ata2: EH complete

Dec  7 22:51:52 Tower kernel: [32545.101440] ata1.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.101443] ata1: EH complete

Dec  7 22:51:52 Tower kernel: [32545.210096] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32545.210103] ata9.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32545.210106]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.210186] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32545.210193] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32545.210196]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.212457] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32545.212464] ata3.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32545.212467]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.213467] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32545.213474] ata2.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32545.213477]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.275611] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec  7 22:51:52 Tower kernel: [32545.275618] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 512 in

Dec  7 22:51:52 Tower kernel: [32545.275621]          res 51/04:01:00:4f:c2/00:00:00:00:00/00 Emask 0x1 (device error)

Dec  7 22:51:52 Tower kernel: [32545.335286] ata9.00: configured for UDMA/100

Dec  7 22:51:52 Tower kernel: [32545.335295] ata9: EH complete

Dec  7 22:51:52 Tower kernel: [32545.335324] ata4.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.335330] ata4: EH complete

Dec  7 22:51:52 Tower kernel: [32545.335553] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.335566] sd 9:0:0:0: [sdj] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.335569] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.335582] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:52 Tower kernel: [32545.335597] sd 4:0:0:0: [sde] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.335605] sd 4:0:0:0: [sde] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.335609] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.335620] sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:52 Tower kernel: [32545.337688] ata3.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.337694] ata3: EH complete

Dec  7 22:51:52 Tower kernel: [32545.337791] sd 3:0:0:0: [sdd] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.337799] sd 3:0:0:0: [sdd] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.337803] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.337814] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:52 Tower kernel: [32545.338663] ata2.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.338669] ata2: EH complete

Dec  7 22:51:52 Tower kernel: [32545.338770] sd 2:0:0:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.338779] sd 2:0:0:0: [sdb] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.338782] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.338793] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:52 Tower emhttp[1903]: get_temperature: ioctl (smart): Input/output error

Dec  7 22:51:52 Tower emhttp[1902]: get_temperature: ioctl (smart): Input/output error

Dec  7 22:51:52 Tower emhttp[1901]: get_temperature: ioctl (smart): Input/output error

Dec  7 22:51:52 Tower emhttp[1900]: get_temperature: ioctl (smart): Input/output error

Dec  7 22:51:52 Tower kernel: [32545.400816] ata1.00: configured for UDMA/133

Dec  7 22:51:52 Tower kernel: [32545.400840] ata1: EH complete

Dec  7 22:51:52 Tower emhttp[1899]: get_temperature: ioctl (smart): Input/output error

Dec  7 22:51:52 Tower kernel: [32545.401341] sd 1:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.401392] sd 1:0:0:0: [sda] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.401396] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.401452] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:52 Tower kernel: [32545.401500] sd 9:0:0:0: [sdj] 976773168 512-byte hardware sectors (500108 MB)

Dec  7 22:51:52 Tower kernel: [32545.401539] sd 9:0:0:0: [sdj] Write Protect is off

Dec  7 22:51:52 Tower kernel: [32545.401543] sd 9:0:0:0: [sdj] Mode Sense: 00 3a 00 00

Dec  7 22:51:52 Tower kernel: [32545.401596] sd 9:0:0:0: [sdj] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Dec  7 22:51:55 Tower kernel: [32548.474273] md0: parity incorrect: 23016

Dec  7 22:51:55 Tower kernel: [32548.474305] md0: parity incorrect: 23024

Dec  7 22:51:55 Tower kernel: [32548.504857] md0: parity incorrect: 23040

Dec  7 22:51:55 Tower kernel: [32548.505008] md0: parity incorrect: 23048

Dec  7 22:56:33 Tower kernel: [32825.582404] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

 

 

Started a new parity check, now at 10% with 0 errors, will report back when it ends.

I owe you an apology, I mis-identified your earlier syslog sections.  There's a definite repeating pattern of the same device errors and get_temperature errors for 5 drives, probably the 5 Seagate 500's, on ATA1 to ATA4 and ATA9 (sda, sdb, sdd, sde, sdj).  The first 4 are probably the nForce4 onboard SATA support, and sdj the first 3114 connector (I'm guessing).  Although I'm somewhat biased against the nForce4 and want to blame it, I can't rule out a problem with the Seagates.  Are they all the same model and firmware?

 

These errors appear to me to be resetting the devices, so I imagine you are seeing some slowdown because of them.

 

I don't know but it might be worth checking your CMOS settings, perhaps there will be something there to tweak, as to SATA, IDE, AHCI, S.M.A.R.T., etc.  If SMART were turned off, that could explain a lot of the above.

 

The 4 parity errors are not related to the above, and occur extremely early, probably in the Reiser file system structures.  That leads me to guess an improper shutdown the previous session, possibly another power failure?  I noticed you mentioned a power failure in your first post.  I strongly recommend a UPS, even a cheap one, to cover  short power failures.  There are one or more threads on UPS recommendations elsewhere.  I like APC myself, I live in a very high lightning area.

 

Thanks again for you help, you were right about S.M.A.R.T. , it was disable, now I can get temperature readings from the 4 x Seagates on the Nforce4 controller, you’re are also right that the other Seagate drive on the first Sil 3114 port is not showing temperature and as expect the CMOS setting didn’t change that.

 

The repeating error is now only for ATA9 , is there anything I can do to enable smart support for this drive on the Sil controller? The Samsung drive connected on the Sil 3114 port 2 is correctly reporting temperature.

 

 

 

The last parity check completed with 0 errors, I guess the problems were because of the power failure, I didn’t had the UPS connected at the time because the case was on a table still in test, it’s connected now.

 

only for ATA9 , is there anything I can do to enable smart support for this drive on the Sil controller? The Samsung drive connected on the Sil 3114 port 2 is correctly reporting temperature.

Since the Samsung and the previous Western Digital were fine, I suspect not.  It's slightly possible that a firmware upgrade for the 3114 chipset might help.  If you don't mind another parity rebuild, you could try swapping a Western Digital for the 5th Seagate, since the WD worked fine here before, and perhaps the Seagate will respond better on a different card.

 

Glad you are making progress...

 

Just an aside but instead of mapping all of those drives as drive letters you might want to look into using UNC naming ala \\machinename\sharename\  For me with a NAS named Pugsly that would be \\pugsly\disk1 through disk11 for a 12 disk array. Likewise if you have shares turned on those show up at top level too. Note that not all software is UNC savvy and neither is the commandline but so far nearly everything I've worked with has had no issues with it. If I used a drive letter for every share I'd literally not have any letters left