| View previous topic :: View next topic |
| Author |
Message |
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
 Posted: Sun Aug 06, 2023 11:07 am Post subject: Is my SSD dying ? |
 |
|
Hello,
For the 2nd time in a week, my BananaPI lost it's disk.
Having a look on the log, I can see only :
| Code: | ug 6 12:18:09 bPI kernel: [ 1.658891] ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 88
...
Aug 6 12:18:09 bPI kernel: [ 2.017550] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Aug 6 12:18:09 bPI kernel: [ 2.029959] ata1.00: supports DRM functions and may not be fully accessible
Aug 6 12:18:09 bPI kernel: [ 2.042930] ata1.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ01B6Q, max UDMA/133
Aug 6 12:18:09 bPI kernel: [ 2.055728] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 31/32)
...
Aug 6 12:18:09 bPI kernel: [ 2.143697] ata1.00: supports DRM functions and may not be fully accessible
Aug 6 12:18:09 bPI kernel: [ 2.153901] ata1.00: configured for UDMA/133
...
Aug 6 12:18:09 bPI kernel: [ 2.208733] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 SVQ0 PQ: 0 ANSI: 5
Aug 6 12:18:09 bPI kernel: [ 2.224196] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Aug 6 12:18:09 bPI kernel: [ 2.235986] sd 0:0:0:0: [sda] Write Protect is off
Aug 6 12:18:09 bPI kernel: [ 2.244796] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Aug 6 12:18:09 bPI kernel: [ 2.257941] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Aug 6 12:18:09 bPI kernel: [ 2.280736] sda: sda1 sda2
|
So the disk seems correctly detected but
| Code: | Aug 6 12:18:09 bPI kernel: [ 2.986665] ata1: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen
Aug 6 12:18:09 bPI kernel: [ 2.997948] ata1: irq_stat 0x00400000, PHY RDY changed
Aug 6 12:18:09 bPI kernel: [ 3.006543] ata1: SError: { Persist PHYRdyChg }
Aug 6 12:18:09 bPI kernel: [ 3.013664] ata1: hard resetting link
...
Aug 6 12:18:09 bPI kernel: [ 3.756766] ata1: SATA link down (SStatus 0 SControl 300)
...
ug 6 12:18:09 bPI kernel: [ 8.755130] ata1: hard resetting link
Aug 6 12:18:09 bPI kernel: [ 9.106845] ata1: SATA link down (SStatus 0 SControl 300)
Aug 6 12:18:09 bPI kernel: [ 9.116372] ata1: limiting SATA link speed to 1.5 Gbps
Aug 6 12:18:09 bPI kernel: [ 14.105100] ata1: hard resetting link
...
Aug 6 12:18:09 bPI kernel: [ 14.456902] ata1: SATA link down (SStatus 0 SControl 310)
Aug 6 12:18:09 bPI kernel: [ 14.464284] ata1.00: disabled
Aug 6 12:18:09 bPI kernel: [ 14.469361] ata1: EH complete
Aug 6 12:18:09 bPI kernel: [ 14.482536] ata1.00: detaching (SCSI 0:0:0:0)
Aug 6 12:18:09 bPI kernel: [ 14.492483] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Aug 6 12:18:09 bPI kernel: [ 14.499865] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Aug 6 12:18:09 bPI kernel: [ 14.515465] sd 0:0:0:0: [sda] Stopping disk
Aug 6 12:18:09 bPI kernel: [ 14.523455] sd 0:0:0:0: [sda] START_STOP FAILED
Aug 6 12:18:09 bPI kernel: [ 14.530009] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
|
Does its meaning the disk is dying ? The problem is at SBC side ?
If I mount this disk on another machine, is anyway to fully test it (if possible w/o destroying its content) ?
This disk is not very old (probably 3 year) with frequent write, but if it's dying due to endurance problem, I was expecting r/w issue, but not such one, isn't it ? |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Aug 06, 2023 11:25 am Post subject: |
|
|
destroyedlolo,
Step 1. Run | Code: | | smartctl -x /dev/... |
If its USB connected that may fail.
Step 2. Use smartctl to run the long test. That reads the entire drive and throws all the data away, without any data transfer over the interface.
Step 3. Run | Code: | | smartctl -x /dev/... |
again so we can see what changed.
You need to post or pastebin both sets of smartctl outputs.
Your | Code: | | ata1: limiting SATA link speed to 1.5 Gbps |
hints at an interface problem.
smartctl will tell us the drives internal view of what it sees happening.
My Pi4 has a | Code: | === START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: Samsung SSD 870 EVO 1TB |
That needs | Code: | Extended self-test routine
recommended polling time: ( 85) minutes |
for the long test.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sun Aug 06, 2023 11:33 am Post subject: |
|
|
Can I run smartctl with the disk mounted (it's the system disk).
But unfortunately, it doesn't appear in /dev : I have no /dev/sd??? anymore 
Will try again after some minutes in case keeping it unpowered for a while help (it did at the first incident). |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Aug 06, 2023 12:13 pm Post subject: |
|
|
destroyedlolo,
Yes. You need its device node. Mounted is OK.
smantctl reads a couple of data blocks from the drive firmware, so its harmless to filesystems.
You can do it in any system. USB/SATA converters can get in the way.
Some of my SSDs do trim at power up and do not come ready until trim completes.
That can be scary. I've had to leave one drive powered up over 24 hours before it appeared in /dev
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sun Aug 06, 2023 3:43 pm Post subject: |
|
|
| Disk stopped for 2h ... at bootup, survived 1 minutes but it disappeared again. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Aug 06, 2023 4:56 pm Post subject: |
|
|
destroyedlolo,
Given the hint that points to an interface problem, try a different SATA data cable, or a different SATA port on the motherboard or both.
If you don't have a spare SATA data cable, try plugging and unplugging tho data cable a couple of times to 'wipe' the contacts.
Do both ends.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sun Aug 06, 2023 5:35 pm Post subject: |
|
|
I tried with another cable : no change.
The bananaPI has only 1 Sata and I can't swap this device without large impact. So I tried the easiest way : swap the disk with another one (mecanical). It's working.
So, this disk is dead.
By the way, this system is running a very old Gentoo with 3.14 kernel (I can't upgrade gentoo has I'm stuck with PHP 5.4 and I even don't have suited DTB to upgrade the kernel). This disk contains only a datas (database, website, ...) and logs. I need to check is this ancient kernel can run zram to save its endurance. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Aug 06, 2023 6:43 pm Post subject: |
|
|
destroyedlolo,
End of life SSD normally go read only, so I suspect it not that.
Are you able to connect it to another system. Over USB if you need to.
USB3 with UAS support would be best.
Any arch will do as you do not want to run the code on the drive.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sun Aug 06, 2023 7:00 pm Post subject: |
|
|
It's what I was thinking too.
But my emergency is to restart (otherwise, I'm missing my home automation). So I'll buy another disk and do some stress test on this one on another system. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Mon Aug 07, 2023 9:49 am Post subject: |
|
|
Hi @NeddySeagoon,
I think you were right : it seems the problem was due to a weak contact on the bPI power supply.
I enforced the connection and the disk survived for 10h (which turning out in record numbers since this issue raised).
Surprisingly, the SBC itself or its PMU didn't crash or issue an alert, but the SATA controler that failed.
Crossing my finger for coming hours  |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Mon Aug 07, 2023 11:16 am Post subject: |
|
|
destroyedlolo,
Get that smart data while you can.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Mon Aug 07, 2023 7:45 pm Post subject: |
|
|
So my system is up for 23h now, and counting.
Here the output of smartctl
| Code: | bPI ~ # smartctl -x /dev/sda
smartctl 7.0 2018-12-30 r4883 [armv7l-linux-3.4.103] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Samsung SSD 870 QVO 1TB
Serial Number: S5SVNG0N724435E
LU WWN Device Id: 5 002538 f70706e91
Firmware Version: SVQ01B6Q
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is: SATA 3.3, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Aug 7 21:44:52 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 85) 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: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
9 Power_On_Hours -O--CK 095 095 000 - 24894
12 Power_Cycle_Count -O--CK 099 099 000 - 51
177 Wear_Leveling_Count PO--C- 099 099 000 - 2
179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010 - 0
181 Program_Fail_Cnt_Total -O--CK 100 100 010 - 0
182 Erase_Fail_Count_Total -O--CK 100 100 010 - 0
183 Runtime_Bad_Block PO--C- 100 100 010 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
190 Airflow_Temperature_Cel -O--CK 078 064 000 - 22
195 Hardware_ECC_Recovered -O-RC- 200 200 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 100 100 000 - 0
235 Unknown_Attribute -O--C- 099 099 000 - 23
241 Total_LBAs_Written -O--CK 099 099 000 - 4880290840
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 1 Comprehensive SMART error log
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x13 GPL R/O 1 SATA NCQ Send and Receive log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 SL VS 16 Device vendor specific log
0xa5 SL VS 16 Device vendor specific log
0xce SL VS 16 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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
256 0 65535 Read_scanning was never started
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.
SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 22 Celsius
Power Cycle Min/Max Temperature: 21/31 Celsius
Lifetime Min/Max Temperature: 7/40 Celsius
Specified Max Operating Temperature: 70 Celsius
Under/Over Temperature Limit Count: 0/0
SMART Status: 0xc24f (PASSED)
SCT Temperature History Version: 2
Temperature Sampling Period: 10 minutes
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/70 Celsius
Min/Max Temperature Limit: 0/70 Celsius
Temperature History Size (Index): 128 (2)
Index Estimated Time Temperature Celsius
3 2023-08-07 00:30 23 ****
4 2023-08-07 00:40 23 ****
5 2023-08-07 00:50 23 ****
6 2023-08-07 01:00 29 **********
7 2023-08-07 01:10 24 *****
8 2023-08-07 01:20 23 ****
9 2023-08-07 01:30 22 ***
... ..( 10 skipped). .. ***
20 2023-08-07 03:20 22 ***
21 2023-08-07 03:30 27 ********
22 2023-08-07 03:40 23 ****
23 2023-08-07 03:50 22 ***
24 2023-08-07 04:00 24 *****
25 2023-08-07 04:10 22 ***
... ..( 3 skipped). .. ***
29 2023-08-07 04:50 22 ***
30 2023-08-07 05:00 21 **
31 2023-08-07 05:10 31 ************
32 2023-08-07 05:20 22 ***
33 2023-08-07 05:30 22 ***
34 2023-08-07 05:40 22 ***
35 2023-08-07 05:50 21 **
... ..( 2 skipped). .. **
38 2023-08-07 06:20 21 **
39 2023-08-07 06:30 22 ***
40 2023-08-07 06:40 23 ****
41 2023-08-07 06:50 22 ***
42 2023-08-07 07:00 21 **
43 2023-08-07 07:10 21 **
44 2023-08-07 07:20 21 **
45 2023-08-07 07:30 30 ***********
46 2023-08-07 07:40 23 ****
47 2023-08-07 07:50 22 ***
48 2023-08-07 08:00 21 **
... ..( 3 skipped). .. **
52 2023-08-07 08:40 21 **
53 2023-08-07 08:50 25 ******
54 2023-08-07 09:00 22 ***
55 2023-08-07 09:10 21 **
... ..( 7 skipped). .. **
63 2023-08-07 10:30 21 **
64 2023-08-07 10:40 24 *****
65 2023-08-07 10:50 22 ***
66 2023-08-07 11:00 22 ***
67 2023-08-07 11:10 22 ***
68 2023-08-07 11:20 21 **
69 2023-08-07 11:30 22 ***
... ..( 2 skipped). .. ***
72 2023-08-07 12:00 22 ***
73 2023-08-07 12:10 21 **
74 2023-08-07 12:20 21 **
75 2023-08-07 12:30 22 ***
76 2023-08-07 12:40 22 ***
77 2023-08-07 12:50 22 ***
78 2023-08-07 13:00 28 *********
79 2023-08-07 13:10 23 ****
80 2023-08-07 13:20 23 ****
81 2023-08-07 13:30 22 ***
... ..( 24 skipped). .. ***
106 2023-08-07 17:40 22 ***
107 2023-08-07 17:50 23 ****
108 2023-08-07 18:00 22 ***
... ..( 6 skipped). .. ***
115 2023-08-07 19:10 22 ***
116 2023-08-07 19:20 29 **********
117 2023-08-07 19:30 23 ****
118 2023-08-07 19:40 22 ***
... ..( 11 skipped). .. ***
2 2023-08-07 21:40 22 ***
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x008 4 51 --- Lifetime Power-On Resets
0x01 0x010 4 24894 --- Power-on Hours
0x01 0x018 6 4880290840 --- Logical Sectors Written
0x01 0x020 6 199281982 --- Number of Write Commands
0x01 0x028 6 214918161 --- Logical Sectors Read
0x01 0x030 6 4914849 --- Number of Read Commands
0x01 0x038 6 2593000 --- Date and Time TimeStamp
0x04 ===== = = === == General Errors Statistics (rev 1) ==
0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors
0x04 0x010 4 0 --- Resets Between Cmd Acceptance and Completion
0x05 ===== = = === == Temperature Statistics (rev 1) ==
0x05 0x008 1 22 --- Current Temperature
0x05 0x020 1 40 --- Highest Temperature
0x05 0x028 1 7 --- Lowest Temperature
0x05 0x058 1 70 --- Specified Maximum Operating Temperature
0x06 ===== = = === == Transport Statistics (rev 1) ==
0x06 0x008 4 93 --- Number of Hardware Resets
0x06 0x010 4 0 --- Number of ASR Events
0x06 0x018 4 0 --- Number of Interface CRC Errors
0x07 ===== = = === == Solid State Device Statistics (rev 1) ==
0x07 0x008 1 0 N-- Percentage Used Endurance Indicator
|||_ C monitored condition met
||__ D supports DSN
|___ N normalized value
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0008 2 0 Device-to-host non-data FIS retries
0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Mon Aug 07, 2023 8:10 pm Post subject: |
|
|
destroyedlolo,
The values of VALUE WORST THRESH are all normalised.
If VALUE or WORST <= THRESH that parameter has failed.
| Code: | ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
9 Power_On_Hours -O--CK 095 095 000 - 24894
177 Wear_Leveling_Count PO--C- 099 099 000 - 2
179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010 - 0
181 Program_Fail_Cnt_Total -O--CK 100 100 010 - 0
182 Erase_Fail_Count_Total -O--CK 100 100 010 - 0
183 Runtime_Bad_Block PO--C- 100 100 010 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
|
That all says that after 24894 power on hours the drive is good.
| Code: | ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
199 UDMA_CRC_Error_Count -OSRCK 100 100 000 - 0 |
The drive has not even noticed any interface errors.
| Code: | Device Statistics (GP Log 0x04)
Page Offset Size Value Flags Description
0x01 ===== = = === == General Statistics (rev 1) ==
0x01 0x018 6 4880290840 --- Logical Sectors Written
0x01 0x020 6 199281982 --- Number of Write Commands
0x01 0x028 6 214918161 --- Logical Sectors Read
0x01 0x030 6 4914849 --- Number of Read Commands
|
The drive has 1,953,525,168 logical sectors available to the user.
Its written 4,880,290,840 so its on its third time round the drive. Its rated 600 times, so it's not close to end of life.
The way you are using it, wear out is over 24894*200 operating hours away.
If its 3 years old now, it should last 600 years. You won't care by then :) because you will have replaced it.
Its written a lot more that its read. Some of that will be putting portage build space there, The write are never read as they are still in the cache when they are needed.
With an estimated life of 600 years from now (at least), don't worry about it.
What all that says, is that the drive is good, so that is not your problem.
If you want to do the long test,
| Code: | Extended self-test routine
recommended polling time: ( 85) minutes. |
so give it a couple of hours.
There is nothing there to suggest that it would show anything.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Mon Aug 07, 2023 10:20 pm Post subject: |
|
|
Thanks for your detailed explanation. Very appreciated.
For the high write vs read ratio, it's not due to portage (this system is frozen for years due to PHP leak of upward compatibility) but because this machine is hosting a database containing all my smart home figures. With 600 years expectancy, I'm safe for a moment |
|
| Back to top |
|
|
destroyedlolo
l33t
Joined: 17 Jun 2011
Posts: 846
Location: Close to Annecy (France)
|
| Posted: Sat Sep 09, 2023 10:10 pm Post subject: |
|
|
Hello,
Back to this old issue : so the problem was an oxidation of the SATA connector.
After some cleaning, it's running now for a month w/o issue.
First time I encountered this kind of issue.
Thanks for the help and the explanation. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
|
| Posted: Sun Sep 10, 2023 9:35 am Post subject: |
|
|
destroyedlolo,
That will fix it for 6 to 9 months. Thank you for the update.
Its probably the gold worn off the SATA data cable. Next time replace the cable.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Other Things Gentoo
