I'm in the process of upgrading some drives in my server, I've just swapped out the parity for a 1.5tb and the parity sync completed ok.

 

I've then swappped a 500gb in the array for another 1.5tb. Unraid noticed the change and said about expanding the array across the disc. After about 5 minutes the disc had mounted and its written about 96000 bytes to the drive having reads miliar amounts from the others but has now stopped and I still have a red dot next to the drive and the array just says started.

 

Am I just being impatient and its still working or is something wrong?

 

EDIT: I've captured the syslog and there is an error on disc 6 which is the new one.

 

A bad disc or an unraid problem?

 

Thanks

I'm in the process of upgrading some drives in my server, I've just swapped out the parity for a 1.5tb and the parity sync completed ok.

 

I've then swappped a 500gb in the array for another 1.5tb. Unraid noticed the change and said about expanding the array across the disc. After about 5 minutes the disc had mounted and its written about 96000 bytes to the drive having reads miliar amounts from the others but has now stopped and I still have a red dot next to the drive and the array just says started.

 

Am I just being impatient and its still working or is something wrong?

 

EDIT: I've captured the syslog and there is an error on disc 6 which is the new one.

 

A bad disc or an unraid problem?

 

Thanks

System log shows an inability to communicate with the failed drive.

It could be a loose cable to the drive, or a bad cable to the drive, or a drive not seated properly in a removable tray, or a bad drive. 

(Pick 1 or more)

 

Joe L.

Thanks Joe,

 

I've RMA'd it.

there are MANY threads all around that talk about the firmware in the 1.5tb's which are prone to dropping out of arrays...

I have three of these drives at the moement, all the same firmware and two are fine, its just this third one. I forget the firmware number but its not the early one that was being quoted as problamatic. Lets hope its just a DOA problem.

I'm in the process of upgrading some drives in my server, I've just swapped out the parity for a 1.5tb and the parity sync completed ok.

 

I've then swappped a 500gb in the array for another 1.5tb. Unraid noticed the change and said about expanding the array across the disc. After about 5 minutes the disc had mounted and its written about 96000 bytes to the drive having reads miliar amounts from the others but has now stopped and I still have a red dot next to the drive and the array just says started.

 

Am I just being impatient and its still working or is something wrong?

 

EDIT: I've captured the syslog and there is an error on disc 6 which is the new one.

 

A bad disc or an unraid problem?

 

Did you run a burn-in test on the drives before adding them to the array?  If not, you should.  New drives have a relatively high failure rate.  After burning them in for a day or two you will KNOW the disk is good before putting it into the unRAID array.

Although all drives have a small percentage that are DOA, these 1.5TB drives seem to have a somewhat higher than normal DOA or early failure percentage.  From reports, Drobo has dropped their recommendation of this drive, for the present (not that we care about Drobo!).  Also see the Newegg reviews:  http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16822148337

there seems to be a problem in the firmware, that when a flush cache comand is received, the drive goes offline for so long that many raid setups mark them permanently offline, twice means catastrophe 

bjp999

 

Any recommendations for "burn in" software?

 

Thanks

I documented a 2 drive burn in procedure that just uses a test unRaid setup (the free version). Follow the "Best of" link in my.sig and you'll find the link there.

 

For a single drive, I would run the smartctl long test (using smartctl 5.38). You can find instructions on the "Troubleshooting" wiki page, also linked in my sig.