Sucess of: “Save often save early”
Brave men!
1 Like
Ok, the drive arrived today! I had no problem replacing the drive and installing Manjaro, but I’m still concerned… One of the first things I did after install was to install GSmartControl and see if anything poped up. Most of the errors are gone, but for some reason GSmartControl still says the “Number of Reported Uncorrectable Errors” is 420.
The drive is brand-new, same model as the one that was initially installed in the machine (Seagate ST1000LM035). Could this be some artifact left-over from the old drive? Perhaps an incorrect reading? At this point I think I’ll just set the entire machine on fire if the new drive doesn’t work, can’t bare this anymore.
Still, everything is working fine for now as far as I can tell, haven’t encountered any problems with the FS. Also, I’ve been monitoring the “Number of Reported Uncorrectable Errors” throughout the day and it hasn’t increased since the first reading (about 6 hours ago). I’m running an extended self-test to see if anything comes up. @omano @GaVenga Any ideas on what could this possibly be caused by?
Where do you get these statistics?
You right click the disk, then go to details, and check the Attributes tab?
In the Statistics tab, it showed up in red.
And what does the SMART says (Attributes)?
There are no errors (things highlighted in red) reported in the Attributes tab, nor an entry named “Number of Reported Uncorrectable Errors”. Here’s the full data from the Attributes tab: smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.49-1-MANJARO] (local build)Co - Pastebin.com
Post the content of the Attributes tab now.
Something I don’t understand is the disk has already 130 power on cycles. It also seem to have huge number of Read/Seek errors (but the tooltip in GSmartControl may give indications about that).
Here it is:
| ID | Name | Failed | Norm-ed value | Worst | Threshold | Raw value | Type | Flags |
|---|---|---|---|---|---|---|---|---|
| 1 | Raw Read Error Rate | never | 71 | 57 | 6 | 12.719.512 | pre-failure | POSR– |
| 3 | Spin-Up Time | never | 100 | 100 | 0 | 0 | pre-failure | PO---- |
| 4 | Start / Stop Count | never | 100 | 100 | 20 | 130 | old age | -O–CK |
| 5 | Reallocated Sector Count | never | 100 | 100 | 36 | 0 | pre-failure | PO–CK |
| 7 | Seek Error Rate | never | 100 | 253 | 45 | 917.727 | pre-failure | POSR– |
| 9 | Power-On Time | never | 100 | 100 | 0 | 13 (49 150 0) | old age | -O–CK |
| 10 | Spin-Up Retry Count | never | 100 | 100 | 97 | 0 | pre-failure | PO–C- |
| 12 | Power Cycle Count | never | 100 | 100 | 20 | 132 | old age | -O–CK |
| 184 | End to End Error | never | 100 | 100 | 99 | 0 | old age | -O–CK |
| 187 | Reported Uncorrectable | never | 100 | 100 | 0 | 0 | old age | -O–CK |
| 188 | Command Timeout | never | 100 | 100 | 0 | 0 | old age | -O–CK |
| 189 | High Fly Writes | never | 100 | 100 | 0 | 0 | old age | -O-RCK |
| 190 | Airflow Temperature | never | 61 | 59 | 40 | 39 (Min/Max 32/41) | old age | -O—K |
| 191 | G-Sense Error Rate | never | 100 | 100 | 0 | 1 | old age | -O–CK |
| 192 | Head Retract Cycle Count | never | 100 | 100 | 0 | 7 | old age | -O–CK |
| 193 | Load / Unload Cycle | never | 100 | 100 | 0 | 292 | old age | -O–CK |
| 194 | Temperature (Celsius) | never | 39 | 41 | 0 | 39 (0 22 0 0 0) | old age | -O—K |
| 197 | Current Pending Sector Count | never | 100 | 100 | 0 | 0 | old age | -O–C- |
| 198 | Offline Uncorrectable | never | 100 | 100 | 0 | 0 | old age | ----C- |
| 199 | UDMA CRC Error Count | never | 200 | 200 | 0 | 0 | old age | -OSRCK |
| 240 | Head Flying Hours | never | 100 | 253 | 0 | 9 (159 58 0) | old age | ------ |
| 241 | Total LBAs Written | never | 100 | 253 | 0 | 475.259.072 | old age | ------ |
| 242 | Total LBAs Read | never | 100 | 253 | 0 | 270.032.748 | old age | ------ |
| 254 | Free Fall Protection | never | 100 | 100 | 0 | 0 | old age | -O–CK |
OK it is the same as in the other page where you copied all the details. If you compare to the other SMART report, you can see you have no sectors reallocated on the new disk, which is good.
I don’t have a clue for the “Number of Reported Uncorrectable Errors” at some point if the HDD firmware is reporting false information, nothing we can do (it may be the case for Read/Seek errors according to the tooltips in GSmartControl, so maybe it is the same and has factory value there when it should be ZERO (like in none, nothing, nada, 0)).
On a side note: this is a 2.5" laptop HDD. By definition this is dog 
these HDD break when you breath on them. So be gentle with the new HDD (why would you buy that kind of crap 
, SSD nowaday are affordable (OK, twice the price of HDD, around 50€ for your 1TB HDD, but 88€ for a brand name 1TB SSD on my local Amazon), and it is on another level of durability and performance).
1 Like
Cached - this is normal. May be Windoofs has another opinion?
Clear config by using “Stacer” may help or/and un-install, clear remains of installation
and install new.
OR - your EFI-Bios registered all SMART things - did not update BIOS-Cache
as you replaced the drive by a “twin” (with only serial-number different).
1 Like
I was thinking about getting an SSD, but I needed to get this fixed as quickly as possible and I couldn’t afford it. Also, I live in Brazil, things are not that cheap in here. The drive was already about half of what I earn in a month (bought on Amazon) – I don’t make that much money though.
I sincerely hope this is the case I’ll try to check for health issues in the drive with other tools in the near future. For now, I guess everything is working fine. Thanks everyone for the help!
Ho yeah Brazil 
I know the pricing situation there. It’s bad.
1 Like
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.