Hello,

 

I am attempting to add space to my array. My parity drive was a 2TB drive and have 3TB drives to add ot the array, so first step, replace parity drive with new 3TB drive. I fail at this step, the sync fails, array starts but with red/orange ball next to parity drive. When I go to start the array and do a parity sync, the process fails after a couple of hours with write errors. I have run the short smartctl test and everything passes. See the attached smart report. I am now in process of the long smartctl report and will post if needed.

 

What I am looking for is ideas on what might be going wrong. I have already reseated the power and SATA cables but that has not helped.

 

Thanks in advance for any assistance.

 

erik

smart_report_sda_3-28.txt

We would really need to see the syslog during the parity build when errors are happening to determine what was going on.  The Smart report looks clean

Alright then. When this smart test finishes, I will restart the array and see what happens. It takes a couple of hours before the errors start, so it will likely be late tonight before I can post the system log.

Please see attached syslog after another failure to complete parity sync.

 

Any ideas on the cause would be greatly appreciated.

Syslog_3-28.txt

Please see attached syslog after another failure to complete parity sync.

 

Any ideas on the cause would be greatly appreciated.

 

Your problem is here:

Mar 29 00:53:10 Tower kernel: attempt to access beyond end of device
Mar 29 00:53:10 Tower kernel: sda1: rw=1, want=3382673944, limit=1565565808
Mar 29 00:53:10 Tower kernel: md: disk0 write error
Mar 29 00:53:10 Tower kernel: handle_stripe write error: 3382673936/0, count: 1
Mar 29 00:53:10 Tower kernel: md: md_do_sync: got signal, exit...
Mar 29 00:53:10 Tower kernel: md: recovery thread sync completion status: -4
Mar 29 00:53:10 Tower kernel: md: recovery thread woken up ...
Mar 29 00:53:10 Tower kernel: md: recovery thread has nothing to resync

 

It looks to me like your 3tb drive thinks that its only a 1.5tb  Not really sure how to proceed.  Perhaps someone more familiar could pipe in.

 

Also, you're running 5.0beta 6a.  You should upgrade to at least 5.06.  I don't know if that is a side affect of running such an early beta or not.

 

Just dug this out from way back in the announcement thread:

 

Changes from 5.0-beta6b to 5.0-beta7

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

- added GPT support for drives larger than 2TB

- added 'gdisk' program

- webGui: remove SpinUp/SpinDown buttons when array is Stopped

- webGui: other misc changes

- driver: added SCSI/SAS device spin up/down support via SG_IO.

- linux: upgraded to version 2.6.37.6

 

 

Ahhhh, that makes sense. I haven't upgraded because it has been running very well and very stable. I don't like to fix it if it ain't broke...but now its broke

 

Thanks for catching that squid. When I get back in town later this week I will upgrade. I guess I should put the old parity drive back in, re-sync parity and THEN upgrade.

Ahhhh, that makes sense. I haven't upgraded because it has been running very well and very stable. I don't like to fix it if it ain't broke...but now its broke

 

Thanks for catching that squid. When I get back in town later this week I will upgrade. I guess I should put the old parity drive back in, re-sync parity and THEN upgrade.

That would be a good plan.

That would be a good plan.