Drive failure


MvL

Recommended Posts

Hi,

 

It's a said day today.., my cat died and one of my drives died.

 

I want to ask how to proceed. I have a falling 3tb drive (it's not spinning). I want to replace this drive with a 2tb model. At the moment I have no parity drive installed in this machine so the data is lost but i have a backup from all important stuff. Can i remove the drive and replace the drive?

Link to comment

Sorry to hear about your very bad day.  :'( Since you have no parity drive, you can just pull the 3TB and put in the 2TB, and tell unraid to forget about your old drive assignments and assign the current drives in whatever logical slot you wish. The procedure for a new config varies according to the version of unraid you are running.

 

Just be very sure you don't assign a drive with data to the parity slot, or you will lose the data on that one as well.

 

At least you have backups.  :)

Link to comment

I've did some testing on the drive that failed. I thought it was not spinning anymore but that isn't true. I was mistaken.

Disk 1 attached to port: sdi
Num	Test Description	Status	Remaining	LifeTime(hours)	LBA of first error
1	Extended offline	Completed without error	00%	5721	None
2	Extended offline	Interrupted (host reset)	00%	5715	None
3	Short offline	Completed without error	00%	5714	None

 

Disk 1 attached to port: sdi
ID#	ATTRIBUTE NAME	FLAG	VALUE	WORST	THRESH	TYPE	UPDATED	FAILED	RAW VALUE
1	Raw Read Error Rate	0x000f	110	099	006	Pre-fail	Always	Never	27261272
3	Spin Up Time	0x0003	094	094	000	Pre-fail	Always	Never	0
4	Start Stop Count	0x0032	099	099	020	Old age	Always	Never	1905
5	Reallocated Sector Ct	0x0033	100	100	010	Pre-fail	Always	Never	0
7	Seek Error Rate	0x000f	039	038	030	Pre-fail	Always	Never	10204859896857
9	Power On Hours	0x0032	094	094	000	Old age	Always	Never	5739
10	Spin Retry Count	0x0013	100	100	097	Pre-fail	Always	Never	0
12	Power Cycle Count	0x0032	100	100	020	Old age	Always	Never	639
183	Runtime Bad Block	0x0032	100	100	000	Old age	Always	Never	0
184	End-to-End Error	0x0032	100	100	099	Old age	Always	Never	0
187	Reported Uncorrect	0x0032	100	100	000	Old age	Always	Never	0
188	Command Timeout	0x0032	100	100	000	Old age	Always	Never	0 0 0
189	High Fly Writes	0x003a	036	036	000	Old age	Always	Never	64
190	Airflow Temperature Cel	0x0022	067	059	045	Old age	Always	Never	33 (Min/Max 22/35)
191	G-Sense Error Rate	0x0032	100	100	000	Old age	Always	Never	0
192	Power-Off Retract Count	0x0032	100	100	000	Old age	Always	Never	19
193	Load Cycle Count	0x0032	093	093	000	Old age	Always	Never	15263
194	Temperature Celsius	0x0022	033	041	000	Old age	Always	Never	33 (0 16 0 0 0)
197	Current Pending Sector	0x0012	100	100	000	Old age	Always	Never	0
198	Offline Uncorrectable	0x0010	100	100	000	Old age	Offline	Never	0
199	UDMA CRC Error Count	0x003e	200	200	000	Old age	Always	Never	0
240	Head Flying Hours	0x0000	100	253	000	Old age	Offline	Never	2310h+35m+09.817s
241	Total LBAs Written	0x0000	100	253	000	Old age	Offline	Never	83755897173
242	Total LBAs Read	0x0000	100	253	000	Old age	Offline	Never	105916877331

 

Disk 1 attached to port: sdi
Model Family:	Seagate Barracuda 7200.14 (AF)
Device Model:	ST3000DM001-1CH166
Serial Number:	W1F2NKHP
LU WWN Device Id:	5 000c50 0603ef004
Firmware Version:	CC24
User Capacity:	3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:	512 bytes logical, 4096 bytes physical
Rotation Rate:	7200 rpm
Device is:	In smartctl database [for details use: -P show]
ATA Version is:	ATA8-ACS T13/1699-D revision 4
SATA Version is:	SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Wed Dec 10 20:37:40 2014 CET
==> WARNING:	A firmware update for this drive may be available,
see the following Seagate web pages:	
http:	//knowledge.seagate.com/articles/en_US/FAQ/207931en
http:	//knowledge.seagate.com/articles/en_US/FAQ/223651en
SMART support is:	Available - device has SMART capability.
SMART support is:	Enabled
SMART overall-health :	PASSED

 

It's passing the test but it dropped out of the array two times. What do you people think of this drive? Should I sent it back. It still in it's warranty period.

Link to comment

To know what happened and what is wrong, we would need to see the syslog that covered the period where it appeared to fail.  There are a number of things that could have happened, and johnodon's advice will correct some of them.  Also check the drive power cable and all connectors.

 

The drive itself does not appear to have been the problem, but can I assume there were no ATA errors listed?

 

However, the drive does have one alarming number - the Seek Error Rate.  It's currently 39, which is dangerously close to the failure threshold of 30.  For Seagates, it is usually in the 60's, and getting low if its in the 50's.  I would monitor this drive closely.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.