* Re: [gentoo-user] routine maintenance.
@ 2021-02-18 13:12 99% ` Michael
0 siblings, 0 replies; 1+ results
From: Michael @ 2021-02-18 13:12 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]
On Thursday, 18 February 2021 06:54:29 GMT Alan Grimes wrote:
> The other discovery was that my /home drive is a 3.0 tb Toshiba unit
> from 2014... man time flies!!! =P This means that the thing should
> probably be replaced due to being old as hell...
I've got disks spinning around for more than 10 years before yours had
started. One has been showing similar errors for almost half its life.
> I'm not going to get too excited about 24 reallocated sectors on a drive
> this large... Actually I have a drive in my NAS that's going down hill
> rapidly, I think the power supply to the slot its in is weaker than the
> others and well...
>
> Any thoughts about running a drive this old, and what I should be
> looking at as a replacement?
I can't advise on a replacement, other than say check if any candidate uses
Shingled Magnetic Recording (SMR) technology and avoid it unless your use case
involves writing rarely, reading often. Conventional drives use Perpendicular
Magnetic Recording and will not suffer from the performance degradation of
SMRs when written to frequently and extensively.
> Root is a 256gb SATA Samsung SSD, no concerns about lifespan on that
> drive. I hadn't heard of M.2 yet when I bought it...
You'll be able to replace your spinning SATA with an SSD SATA using AHCI over
the same port. You won't be able to get an M.2 NVMe (M-key socket 3) doing
its magic without a PCIe 3.0x4 port on your MoBo.
Sadly my hardware is too old and it won't boot using NVMe.
> /dev/sdb1 2884152536 955486476 1782136424 35% /home
>
> 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 083 083 016 Pre-fail
> Always - 262570
> 2 Throughput_Performance 0x0005 139 139 054 Pre-fail
> Offline - 72
> 3 Spin_Up_Time 0x0007 159 159 024 Pre-fail
> Always - 405 (Average 316)
> 4 Start_Stop_Count 0x0012 100 100 000 Old_age
> Always - 244
> 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail
> Always - 24
> 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail
> Always - 0
> 8 Seek_Time_Performance 0x0005 119 119 020 Pre-fail
> Offline - 35
> 9 Power_On_Hours 0x0012 093 093 000 Old_age
> Always - 53677
> 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail
> Always - 0
> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age
> Always - 243
> 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age
> Always - 271
> 193 Load_Cycle_Count 0x0012 100 100 000 Old_age
> Always - 271
> 194 Temperature_Celsius 0x0002 181 181 000 Old_age
> Always - 33 (Min/Max 14/44)
> 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age
> Always - 27
> 197 Current_Pending_Sector 0x0022 029 029 000 Old_age
> Always - 1456
This value is worth considering further. Start with a backup of your data,
but do not overwrite your older backups.
Then consider zeroing the defective sectors.
https://www.thomas-krenn.com/en/wiki/
Analyzing_a_Faulty_Hard_Disk_using_Smartctl
With 1456 pending sectors you'll be there for a while. Alternatively ditch it
and get a new drive as you intend to do anyway.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
[not found] <14373b3e-e971-bed4-c70c-6de111dd63fe.ref@verizon.net>
2021-02-18 6:54 ` [gentoo-user] routine maintenance Alan Grimes
2021-02-18 13:12 99% ` Michael
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox