datahoarder

6756 readers

6 users here now

Who are we?

We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.

We are one. We are legion. And we're trying really hard not to forget.

-- 5-4-3-2-1-bang from this thread

founded 4 years ago

MODERATORS

[email protected]

What do you do with damaged drives? (lemmy.sdf.org)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

11 comments fedilink hide all child comments

My old laptop died so I took the SSD from it in hope to use it as external drive. I wanted to just overwrite it with dd for security but I decided to go with f3 as that would also give me the opportunity to test the drive. Sadly, bad results came back

Data OK: 111.75 GB (234352247 sectors)
Data LOST: 14.13 MB (28937 sectors)
       Corrupted: 14.11 MB (28905 sectors)
Slightly changed: 0.00 Byte (0 sectors)
     Overwritten: 16.00 KB (32 sectors)
Average reading speed: 250.69 MB/s

S.M.A.R.T. data if you're curious

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
  5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       359
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       995
161 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       236
163 Unknown_Attribute       0x0003   100   100   050    Pre-fail  Always       -       96
165 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       84
166 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
167 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       56
172 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       339
194 Temperature_Celsius     0x0023   059   059   000    Pre-fail  Always       -       41 (Min/Max 33/41)
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0012   100   100   000    Old_age   Always       -       0
241 Total_LBAs_Written      0x0012   100   100   000    Old_age   Always       -       1847
242 Total_LBAs_Read         0x0012   100   100   000    Old_age   Always       -       2424

Yeah, barely used. Just the LBAs written/read doesn't seem to make sense.

Any better ideas than paperweight?
I have tested it when it was new, it had no errors.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 1 year ago

I've used badblocks in the past to get an extra few years out of a failing drive in the past. But this was in the 64gb being a large drive days, and it only delayed problems