Dying Hard Disk - Revision history

Leo: /* April 1, 2021 */

2021-04-03T03:01:54Z

April 1, 2021

← Older revision		Revision as of 03:01, 3 April 2021
Line 92:		Line 92:
	1000+0 records out		1000+0 records out
	512000 bytes (512 kB, 500 KiB) copied, 3.23109 s, 158 kB/s		512000 bytes (512 kB, 500 KiB) copied, 3.23109 s, 158 kB/s

			# dd if=/dev/sdb of=/dev/null bs=512 status=progress
			509440 bytes (509 kB, 498 KiB) copied, 3 s, 158 kB/s
			dd: error reading '/dev/sdb': Input/output error
			1000+0 records in
			1000+0 records out
			512000 bytes (512 kB, 500 KiB) copied, 6.33653 s, 80.8 kB/s
	\| lang = terminal		\| lang = terminal
	}}		}}

Leo at 02:53, 3 April 2021

2021-04-03T02:53:06Z

Show changes

Leo: /* September 20, 2019 */

2020-07-31T16:01:37Z

September 20, 2019

Show changes

Leo: Text replacement - "Category:Hardware" to "{{Navbox Hardware}}Category:Hardware"

2020-06-15T00:49:55Z

Text replacement - "Category:Hardware" to "{{Navbox Hardware}}Category:Hardware"

← Older revision		Revision as of 00:49, 15 June 2020
Line 725:		Line 725:


	[[Category:Hardware]]		{{Navbox Hardware}}[[Category:Hardware]]

Leo at 15:26, 20 September 2019

2019-09-20T15:26:53Z

Show changes

Leo: recategorize

2019-09-01T02:41:28Z

recategorize

← Older revision		Revision as of 02:41, 1 September 2019
Line 500:		Line 500:

	So, lesson learned. Test backups and replace dead drives ASAP.		So, lesson learned. Test backups and replace dead drives ASAP.


			[[Category:Hardware]]

Leo: /* == */

2017-05-19T08:03:04Z

← Older revision		Revision as of 08:03, 19 May 2017
Line 270:		Line 270:

	Disks		Disks
	~~======~~
	{{highlight\|lang=text\|code=		{{highlight\|lang=text\|code=
	# zpool status storage		# zpool status storage

Leo: /* May 18, 2017 */

2017-05-19T08:02:29Z

May 18, 2017

← Older revision		Revision as of 08:02, 19 May 2017
Line 264:		Line 264:
	}}		}}

			The disk went offline pretty quick, so ZFS took it off the pool equally as quick.




			Disks
			======
			{{highlight\|lang=text\|code=
			# zpool status storage
			pool: storage
			state: DEGRADED
			status: One or more devices could not be used because the label is missing or
			invalid. Sufficient replicas exist for the pool to continue
			functioning in a degraded state.
			action: Replace the device using 'zpool replace'.
			see: http://zfsonlinux.org/msg/ZFS-8000-4J
			scan: scrub repaired 0 in 7h8m with 0 errors on Fri Apr 14 10:23:51 2017
			config:

			NAME STATE READ WRITE CKSUM
			storage DEGRADED 0 0 0
			raidz1-0 DEGRADED 0 0 0
			ata-WDC_WD20EARS-00J99B0_WD-WCAWZ0877352-part1 ONLINE 0 0 0
			ata-WDC_WD20EARS-00J99B0_WD-WCAWZ0840640-part1 ONLINE 0 0 0
			ata-ST2000DM001-9YN164_W2F0B1GV-part1 UNAVAIL 0 0 0
			ata-ST2000DM001-1CH164_Z1E37XQR-part1 ONLINE 0 0 0
			ata-ST2000DL003-9VT166_5YD3VR3A-part1 ONLINE 0 0 0

			errors: No known data errors


			}}

	== An older Entry ==		== An older Entry ==

Leo at 07:36, 19 May 2017

2017-05-19T07:36:11Z

Show changes

Leo: formatting

2017-03-30T20:15:02Z

formatting

← Older revision		Revision as of 20:15, 30 March 2017
Line 1:		Line 1:

	I noticed that one of the drives in my ZFS array went down last month, but I couldn't bother myself with fixing because it's only one drive and it's acting like a raid 0 (right?).		I noticed that one of the drives in my ZFS array went down last month, but I couldn't bother myself with fixing it because it's only one drive and it's acting like a raid 0 (right?).

	Unfortunately, my backups failed for a few files and then this turned up:		Unfortunately, my backups failed for a few files and then this turned up:

	~~<syntaxhighlight~~ lang=~~"text">~~		{{highlight\|lang=terminal\|code=
	root@nas:/mnt/nas4/images/christine/2015-01-25 Annual Dinner- we host# zpool status -xv		root@nas:/mnt/nas4/images/christine/2015-01-25 Annual Dinner- we host# zpool status -xv
	pool: data		pool: data
Line 31:		Line 31:
	/data/images/christine/2015-01-25 Annual Dinner- we host/IMG_3258.JPG		/data/images/christine/2015-01-25 Annual Dinner- we host/IMG_3258.JPG
	/data/images/christine/2015-01-25 Annual Dinner- we host/IMG_3259.JPG		/data/images/christine/2015-01-25 Annual Dinner- we host/IMG_3259.JPG
	~~</syntaxhighlight>~~		}}

	It seems like I lost 5 images that were recently saved on the storage pool. The drive is so far gone that I couldn't even run smartctl on it:		It seems like I lost 5 images that were recently saved on the storage pool. The drive is so far gone that I couldn't even run smartctl on it:

	~~<syntaxhighlight~~ lang=~~"text">~~		{{highlight\|lang=terminal\|code=
	smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-431.17.1.el6.x86_64] (local build)		smartctl 5.43 2012-06-30 r3573 [x86_64-linux-2.6.32-431.17.1.el6.x86_64] (local build)
	Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net		Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
Line 45:		Line 45:
	>> Terminate command early due to bad response to IEC mode page		>> Terminate command early due to bad response to IEC mode page
	A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.		A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
			}}
	~~</syntaxhighlight>~~

	The logs show the drive failing:		The logs show the drive failing:

	~~<syntaxhighlight~~ lang=~~"text">~~		{{highlight\|lang=terminal\|code=
	2268 Jan 25 22:13:54 nas kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0xd0000 action 0xe frozen		2268 Jan 25 22:13:54 nas kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0xd0000 action 0xe frozen
	2269 Jan 25 22:13:54 nas kernel: ata7: SError: { PHYRdyChg CommWake 10B8B }		2269 Jan 25 22:13:54 nas kernel: ata7: SError: { PHYRdyChg CommWake 10B8B }
Line 196:		Line 195:
	2409 Jan 25 22:16:29 nas kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)		2409 Jan 25 22:16:29 nas kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
	2410 Jan 25 22:16:29 nas kernel: ata7.00: configured for UDMA/33		2410 Jan 25 22:16:29 nas kernel: ata7.00: configured for UDMA/33
			}}

			... this goes on for another 12 minutes.

	~~</syntaxhighlight>~~

	.~~. this goes on for another 12 minutes~~.		So, lesson learned. Test backups and replace dead drives ASAP.