Hi All,
I’m not haveing a good day…
I’ve replaced my da2 disk twice, it’s failed each time. I now suspect the cable, I’ve bought a new one, but is there anything I can look at to point me to the cable and help me differenciate between cable and disk. I hope it’s not the onboard controller. as I have no slots spare to plug in a new on, so it would be a new server, which I can’t afford.
It failed in the middle of a pool scrub, will that create any additional problems?
Thank you for you help
Any info on the type of failure? Are you able to post the output of smartctl -a /dev/da2
Hi,
the disk is Ada2, sorry about the typo.
The email / message is;
table {white-space: normal; }
New alerts:
Pool TVShowsPool state is UNAVAIL: One or more devices are faulted in response
to IO failures.
The following devices are not healthy:
Disk TOSHIBA HDWG21E 2490A06NFP7G is REMOVED
The TVShows pool is offline.
root@truenas[~]# smartctl -a /dev/ada2
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p9 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Toshiba N300/MN NAS HDD
Device Model: TOSHIBA HDWG21E
Serial Number: 2490A06NFP7G
LU WWN Device Id: 5 000039 d18c9dba9
Firmware Version: 0601
User Capacity: 14,000,519,643,136 bytes [14.0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Mar 26 14:57:24 2025 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: (1325) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 2596
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 69
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 957
10 Spin_Retry_Count 0x0033 100 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 69
23 Helium_Condition_Lower 0x0023 100 100 075 Pre-fail Always - 0
24 Helium_Condition_Upper 0x0023 100 100 075 Pre-fail Always - 0
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 18
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 70
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 28 (Min/Max 16/33)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 35258369
222 Loaded_Hours 0x0032 098 098 000 Old_age Always - 952
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 590
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 945 -
# 2 Short offline Completed without error 00% 921 -
# 3 Short offline Completed without error 00% 913 -
# 4 Short offline Completed without error 00% 895 -
# 5 Short offline Completed without error 00% 877 -
# 6 Short offline Completed without error 00% 866 -
# 7 Short offline Completed without error 00% 850 -
# 8 Short offline Completed without error 00% 841 -
# 9 Short offline Completed without error 00% 833 -
#10 Short offline Completed without error 00% 809 -
#11 Short offline Completed without error 00% 785 -
#12 Short offline Completed without error 00% 761 -
#13 Short offline Completed without error 00% 737 -
#14 Short offline Completed without error 00% 713 -
#15 Short offline Completed without error 00% 675 -
#16 Short offline Completed without error 00% 665 -
#17 Short offline Completed without error 00% 647 -
#18 Short offline Completed without error 00% 628 -
#19 Short offline Completed without error 00% 619 -
#20 Short offline Completed without error 00% 602 -
#21 Short offline Completed without error 00% 591 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
I’m concerned that it was in the middle of scrubbing the pool when it died.
This is the pool’s status;
When it was powered off I opened up the server and reconnected ada2’s data connector, maybe that’s why the disk isthere now, even it it’s not in the pool
I know it’s a stripe0, and the data has potentially gone, but I have a good backup.
Thanks for your help.
I can’t see anything blindingly wrong with the drive and it seems fairly young based on its power on hours. As this isn’t the first time it’s happened to you then you are right to potentially suspect cabling/port. The fact the pool is a stripe of 4 drives is a different conversation but it sounds like you are well aware of the dangers of that.
I’d be tempted to make a note of your drive serial numbers and which SATA connector and port they are connected to and monitor perhaps even occasionally moving drives around (when powered off) to see if the issue stays with a particular cable/port or follows a specific drive.
Perhaps look around the forums for some burn-in test tools to stress the drives/connectors to try and find the weak spot before you but any data on them again.
PS: Why not share the specs and setup of your system incase there is anything odd there. Chassis, mobo how the drives are connected etc.
Thanks Johnny_Fartpants,
How do you define your system specs?
Thanks
Ideally create a signature with them in so that when you post forums members can understand your system setup almost as well as you do. Start with Chassis and work your way through. It doesn’t have to be exhaustive but if you could identify the key components that is always helpful.
Do you restart your system regularly?
It’s possible the reference to the drive in the alert has changed if you rebooted since the alert was generated. Device names like adaX or sdaX, etc, aren’t necessarily static. This is fine from a ZFS standpoint but can cause issues when troubleshooting, if you’re not aware of it.
If you aren’t sure, you can post the SMART report from all the drives, just in case the culprit is somewhere else.
Edit: I see I missed the last screenshot with the pool status clearly showing ada2 as REMOVED, that should be reliable enough so the above request isn’t really relevant. Still good to know of though so I will leave it.
@jujuh I recommend you perform a SMART Long test weekly, or at least monthly. I didn’t see that in the report.
Once I get the cable, later today, is there a way of adding the removed disk back into the pool to bring the pool online? Or is the pool effectivly dead and I’ll delete it, recreate it and start again?
Thanks
It is all gone. A stripe with a single failed drive is a complete failure of the entire pool. You need to treat a Stripe as if it were a single drive, any part of that drive fails and the entire thing fails.
You are better off creating a RAIDZ1 or bette a RAIDZ2, but that depends on how important the data is to you.
You might be lucky and it may jump back into life but like @joeschmuck said you have to assume it’s lost as by design losing a drive in a stripe loses the pool.
I will digress a little bit. For the correct amount of money, and using your old failed drive (preferred), you may be able to recover some of your data. The correct amount of money is a lot of money as you are likely going to need a data recovery company.
Thank you.
The data is backed up, it just takes 5 days to copy it over. And to be honest I can live without it while it’s copying.
It was my birthday yesterday, so I’m using my birthday money to buy an extra drive.
Thanks for your help, it’s much apprechiated.
The reason I had a stripe 0 was I didn’t have a spare port to plug in the extra drive. However thanks to Alister I have another look at the mother board and discovered a spare ODD sata port, after checking online Dell SATA ODD ports are no different to the other mini sas sata ports, so that gave me the extra port for the drive to give me raidz1, which I implemented,
I swapped the drives around, and the physical disk that was in ADA2 failed on a pool scrub again, although was perfectly ok before a throught check during the scrub. As I have Raidz1 all the data’s safe and I don’t have to wait 5 days for it to be restored.
GREAT news it’s the disk, not the controller, I’d swapped the cable. Weird in that fact it was in the same place as a previous one, but coincidental. It’s in warraty and waiting for UPS to pick it up.
Thank you for all your help.
