(Solved) STARTED, 5 disks in array. PARITY NOT VALID: DISK_DSBL

[onehunghig]

Hi

I am using unRAID Server Pro

version: 5.0-rc6-r8168-test on a Msi P67A G43(43) motherboard Bios Ver 5.3

with Intel Celeron.

I tried to mount a parity disk Seagate 3T

ST3000DM001-1CH166_Z1F0XRQS (sdb) 2930266532.

After about 8 Hours I get the result that Parity not valid. Can some experts bpls check the attached log and advice me what to do to rectify this.

Thanks

syslog-2012-09-17_Pariiy_Disk.txt

[pantner]

open the log file and go right to the bottom

 

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530184/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530192/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530200/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530208/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530216/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530224/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530232/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530240/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530248/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530256/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530264/0, count: 1

Sep 17 01:01:21 Tower kernel: md: disk0 write error

Sep 17 01:01:21 Tower kernel: handle_stripe write error: 5860530272/0, count: 1

 

it seems there was an error writing to disk0 which i expect is your parity disk.

 

Did you pre-clear it before adding to the array?

Run a Smart report on it.

Try changing the SATA/Power connectors

[onehunghig]

Hi  pantner thanks for the quick response.

I changed the SATA/Power connectors as suggested

I started the server up and now I have a green button on the parity disk and parity is checking.

 

Started Stop will take the array off-line.

Parity-Check in progress. Cancel will stop the Parity-Check.

Correct any Parity-Check errors by writing the Parity disk with corrected parity.

Total size: 3 TB

Current position: 56.17 GB (2%)

Estimated speed: 104.95 MB/sec

Estimated finish: 468 minutes

Sync errors corrected: 193

I did preclear the disk and it was ok.

 

And this is from unMenu

 

Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free

OK parity /dev/sdc ST3000DM001-1CH166_Z1F0XRQS 28°C 971647 49

OK /dev/md1 /mnt/disk1 /dev/sdf ST2000DL001-9VT156_5YD3AQK3 31°C 828377 11 2.00T 947.23G 48% 1.05T

OK /dev/md2 /mnt/disk2 /dev/sdb WDC_WD20EADS-00W4B0_WD-WCAVY6299533 29°C 369496 10 2.00T 1.15T 58% 849.23G

OK /dev/md3 /mnt/disk3 /dev/sdd Hitachi_HDS722020ALA330_JK1121YAG61RJS 33°C 951907 10 2.00T 1.43T 72% 574.98G

OK /dev/md4 /mnt/disk4 /dev/sde WDC_WD20EARS-00J2GB0_WD-WCAYY0010518 35°C 704080 10 2.00T 1.42T 71% 580.54G

Total: 8.00T 4.94T 61% 3.06T

 

System Log (last 6 lines)  Legend => Errors Minor Issues Lime Tech unRAID engine System Drive related Network Logins Misc Other emhttp

Sep 17 05:51:19 Tower kernel: md: parity incorrect: 13800

Sep 17 05:51:19 Tower kernel: md: parity incorrect: 13808

Sep 17 05:51:19 Tower kernel: md: parity incorrect: 13816

Sep 17 05:52:09 Tower emhttp: mdcmd: write: Invalid argument

Sep 17 05:52:09 Tower kernel: mdcmd (41): check CORRECT

Sep 17 05:52:09 Tower kernel: md: check_array: recovery already active

Can any pls help me what to make out of these

How do you run a smart report?

 

[funhur]

Hi, refer here on running and getting smart report

 

http://lime-technology.com/wiki/index.php/Troubleshooting#Running_a_SMART_test

http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report

[onehunghig]

This is my 3rd 3T drive that have failed the parity syn.

I have 6 more to try.

Maybe my motherboard is the problem.

Motherboard is a MSI P67A G43 with the latest 5.3 bios firmware 8 gig mem.

and a Celeron processor.

2 Supermicro 5in3 cage and supermicro AOC saslp MV8 card.

Can someone pls let me know if my problem is the mother board.

I have no problem with 2T drives.

I am on unRAID Server Pro

version: 5.0-rc6-r8168-test

Preclear_and_parity_sync_ST3000DM001-1CH166_Z1F0XRQS_sdg_2930266532.txt

[bcbgboy13]

1. The parity disk should be on the motherboard as these ports are superior to the ones from the SM SASLP card (especially if fully loaded with 8 drives)

 

2. I believe that you need the newer firmware 0.21 for the SASLP card for 3 TB drives - but in theory you should connect the 3TB drives to the motherboard SATA ports and not SASLP.

 

It also looks like you are not fully pre-clearing the disks but instead only zeroing it.

Since the preclear of 3TB disk should take more than 24 hours if you do not have clean power where you live you may not be able to finish properly - that does not mean something is wrong with your system, motherboard or any other hardware - you just need a UPS.

[Joe L.]

This is my 3rd 3T drive that have failed the parity syn.

I have 6 more to try.

Maybe my motherboard is the problem.

Motherboard is a MSI P67A G43 with the latest 5.3 bios firmware 8 gig mem.

and a Celeron processor.

2 Supermicro 5in3 cage and supermicro AOC saslp MV8 card.

Can someone pls let me know if my problem is the mother board.

I have no problem with 2T drives.

I am on unRAID Server Pro

version: 5.0-rc6-r8168-test

Your disk controller appears to not be able to handle disks > 2.2TB.  You need to update its firmware, of if on the MB, perhaps a BIOS update will help... Or, a new disk controller card that can handle disks >2.2TB.

The last sector it can get to is 4294967295.

4,294,967,295 sectors * 512 bytes/sectors = 2,199,023,255,040 bytes or 2.2TB.

 

See the error messages when your parity calc attempts to access a block > 2.2TB.

Sep 20 19:09:49 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks.

Sep 21 02:26:09 Tower kernel: attempt to access beyond end of device

Sep 21 02:26:09 Tower kernel: sdg1: rw=1, want=4294967296, limit=4294967295

Sep 21 02:26:09 Tower kernel: attempt to access beyond end of device

Sep 21 02:26:09 Tower kernel: sdg1: rw=1, want=4294967304, limit=4294967295

Sep 21 02:26:09 Tower kernel: attempt to access beyond end of device

Sep 21 02:26:09 Tower kernel: sdg1: rw=1, want=4294967312, limit=4294967295

[onehunghig]

Thanks everyone for helping out.

I think my troubles with the 3T drives is with my motherboard. I do not think that it supports 3T drives in an unRaid server. I will be changing the motherboard.Can anyone please let me know if this mother board support 3T drives in an unRaid server, ASRock B75 PRO3-M LGA 1155 Intel B75 HDMI SATA 6Gb/s USB 3.0 Micro ATX Intel Motherboard.

http://www.newegg.ca/Product/Product.aspx?Item=N82E16813157329&RandomID=338509923310224720120923025359

Thanks.

[onehunghig]

Finally my 3T parity disk was mounted with no errors. I followed this thread http://lime-technology.com/forum/index.php?topic=22265.0 by Hoopster and thanks to Joe.

My usb boot stick had the same problem like Hoopster the gdisk does not work. I have to install unRaid on a new usb stick and use it to preclear my 3T drive.

I tried to rename this thread "Solved" but I don't know how to do it. Can a Mod please do it for me

thanks