Smartmon error message in the installer

[tascoast]

The disk with the partition you selected for installation passes the S.M.A.R.T. monitor test (smartctl) but the tests indicate it will have a higher than average failure rate in the upcoming year.

Do you want to continue?

That wouldn't scare me

Please take my comment as imagining 'Uncle Bob' who might just panic faced with HDD alert and being in no way critical of the awesome testing and revisions being done, more like an aside. My sincere apologies to be taken otherwise. I had a friend in mind when mentioning it and imagined them getting into a flap over such a message. I do think a disc scan might be unexpected (with a possible mention beforehand during install?), but increasingly the default in time, in linux, MX-14 setting a trend. My own mind was at rest soon after posting the query and my own system of data backup makes inevitable disc failure little more than a trip to the computer store for a replacement and an afternoon partitioning and installing/updating again. Thank you all so much for the fantastic work being done.

Kindly
Mick

Edit: - Just to confirm that MX-14.1.1 installed without any problems at all.
I skipped installing grub first off then decided just to let MX-14 update the MBR with Grub 2 by repeating the Live install, instead of repairing and keeping my old system (with a chainload to M12). MX-14.1.1 picked up M11 and M12 and have simplified things in addition. No disk warning was issued the second time I installed by the way.
Kindly
Mick

[Richard]

I saw the message while installing on my first generation
Aspire One. I ignored it and continued. I'll check SMART later.

When I installed on my 32GB Imation USB, ther was no message.

[m_pav]

The text is misleading as the installer does not initiate a S.M.A.R.T. monitor test, therefore, the drive has not actually passed a S.M.A.R.T. test. The installer only reads and reports the drives current S.M.A.R.T. status, which may change after running a full test, which should be done if the drive has a non-zero value in any of the 4 fields selected by the script.

Have a look at the snapshot below of my drive below and you'll see that no S.M.A.R.T. tests have ever been run. Let's say peradventure that my drive had the following values:
2 in #5 (reallocated sectors),
2 in 196 (reallocation event count) and
1 in 197 (current pending sector count)

The low values are not enough to trigger an automatic S.M.A.R.T. analysis, so in my case, the text would correctly say the tests indicate it will have a higher than average failure rate in the upcoming year, but it would incorrectly say that the drive has passed a S.M.A.R.T. test.

The matching 2's show that no data was lost as the damaged sectors were successfully remapped to the drives reserved space, but what is left out in the interpretation is that there is an uncorrectable sector, so the drive has a definitive platter flaw.

I like the way the text is going, but it shouldn't be sent as is, unless we added an option to run a short self test which takes about 3 minutes on most drives, which is simply not acceptable if it's done without the users knowledge.

I propose the following change

The disk with the partition you selected for installation has not reported a S.M.A.R.T. failure (smartctl) but the tests indicate it will have a higher than average failure rate in the upcoming year. Performing a short drive analysis on this drive is recommended, which could take up to 3 minutes.

Continue with a short analysis (1-3 min) ? --> installer initiates smartctl --test=short <drive> and returns to this screen with the result displayed.
Continue with a full analysis (1-3 hrs) ? --> installer initiates smartctl --test=long <drive> and returns to this screen with the result displayed
Continue with install?

I personally think the comprehensive test option would be too much for the average punter and the installer is not really the right place to do this, but I was thinking of a way to have the operators interest peaked such that they would seek further assistance from the forums.

[tascoast]

Perhaps the message is just akin to telling someone "Your HDD is getting a bit old".

'What then?' becomes the question for user and thus, what does one do with such a 'diagnosis'?

Kindly
Mick

[Jerry3904]

Important questions, thanks. We could create SMART documentation and then add the line to the installer:

If you are unsure how to proceed, please exit the Installer and consult http://www.mepiscommunity.org/doc_mx/ad ... SMART.html

[duane]

I like this suggestion to provide a link.
How about putting where it could be easily found from the MX -14 documentation when a new user opens a browser?

Last week I picked up a couple used PC's cheap. I got the error message when installing on both of them.
Because they were boxes I knew nothing about I initially stuck another hard drive in but when I got the message on another hard drive that I knew the history of I ran a check I found in the bios and upon it testing OK I installed it.

A message providing more info and pointing the user in the right direction would be better in my opinion.

Just my two cents.
Duane

[m_pav]

Perhaps the message is just akin to telling someone "Your HDD is getting a bit old".

The message does not indicate age and has no relevance to age in many cases. I have seen 2 week old drives with such failures. It indicates a surface defect and they most often come from the manufacturer as such. Surface defects are discovered after the heads try to write to the defective part of the drive and often, it takes some time before such a failure is found with the size of todays drives.

Older IDE drives were notorious for faults, newer SATA drives seem to fair much better, unless you have one of the Toshiba laptops with a 640GB drive, not a single one of these I have seen has passed the extended test after a surface defect has been found.

If you want to be sure of a drive, before you use it, run a badblock test on it first, then you will have written to and read from every available part of the disk surface and regular smart tests thereafter should be sufficient. Bad blocks on such a drive will be from old age.

[antiX-Dave]

If I am reading the thread correctly, the error / check that is being discussed is more for the general information / knowledge of the user.
As in:
You may be interested to know that the installer has detected that the disk you have chosen for installation is becoming prone to file loss / data corruption and possible failure in the near to late future. You may notice disk activity causing slow response and or "brain farts" in day to day use.

Where as the second included in the installer, and mentioned here is more the important one.
That is that:
smart has detected that the drive *is* failing and installing on this disk is guarenteed to be a bad idea. Therefor you should replace your disk but you are not forced to do so. Data loss / corruption is imminent and pc performance will be hindered in use.


I do not see the actual command string from the installer so I am not exactly sure on what it is doing... maybe I missed it, if not could someone copy it here?... but by the sounds of it the error is more of a warning or info than a true error. (If it was my mail servers it would probably fall under mail.info or mail.warn rather than mail.err.)

[Jooj]

Can someone help me?
I got this message and even after reading this topic I'm still worried about it.
So after reading this message i opened GSmartControl and read the log, and that`s when i got afraid.
I don't know if I'm being paranoid or it is something to worry about.


Error Log:

Complete error log:

SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 38454 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 38454 [13] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:42.848 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:42.847 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:40.283 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:40.283 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:37.840 READ FPDMA QUEUED

Error 38453 [12] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:37.840 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:37.839 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:35.363 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:35.363 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:32.931 READ FPDMA QUEUED

Error 38452 [11] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:35.363 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:35.363 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:32.931 READ FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 00 00 4d+06:41:32.931 READ LOG EXT
60 00 00 08 00 00 00 00 5f 82 c0 40 00 4d+06:41:30.521 READ FPDMA QUEUED

Error 38451 [10] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 20 00 00 00 62 c2 60 40 00 4d+06:41:27.807 READ FPDMA QUEUED
61 00 00 00 08 00 00 00 62 c1 88 40 00 4d+06:41:27.806 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 06 42 2a d8 40 00 4d+06:41:27.803 READ FPDMA QUEUED
61 00 00 00 60 00 00 23 2b 2b 40 40 00 4d+06:41:27.803 WRITE FPDMA QUEUED
60 00 00 00 60 00 00 03 a7 ff 40 40 00 4d+06:41:27.768 READ FPDMA QUEUED

Error 38450 [9] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 08 00 00 00 08 ef df 68 40 00 4d+06:41:25.345 WRITE FPDMA QUEUED
61 00 00 00 40 00 00 23 2b 2a a0 40 00 4d+06:41:25.287 WRITE FPDMA QUEUED
61 00 00 00 40 00 00 23 2b 2a 60 40 00 4d+06:41:25.280 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 03 88 eb 68 40 00 4d+06:41:25.255 READ FPDMA QUEUED
61 00 00 00 20 00 00 23 29 a8 c0 40 00 4d+06:41:25.238 WRITE FPDMA QUEUED

Error 38449 [8] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 29 a8 c0 40 00 4d+06:41:22.561 WRITE FPDMA QUEUED
60 00 00 00 60 00 00 03 a4 8c 00 40 00 4d+06:41:22.561 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1b 1a a0 40 00 4d+06:41:22.560 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1b 18 a0 40 00 4d+06:41:22.560 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1b 16 a0 40 00 4d+06:41:22.559 READ FPDMA QUEUED

Error 38448 [7] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 00 0d 36 60 40 00 4d+06:41:19.511 READ FPDMA QUEUED
60 00 00 00 08 00 00 06 4e d4 d0 40 00 4d+06:41:19.511 READ FPDMA QUEUED
61 00 00 00 20 00 00 23 2b 08 a0 40 00 4d+06:41:19.510 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 29 a8 c0 40 00 4d+06:41:19.510 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 00 62 c1 70 40 00 4d+06:41:19.509 WRITE FPDMA QUEUED

Error 38447 [6] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 10 00 00 03 ce c1 58 40 00 4d+06:41:12.105 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 00 03 e1 30 40 00 4d+06:41:12.104 READ FPDMA QUEUED
60 00 00 00 08 00 00 00 88 9a f0 40 00 4d+06:41:12.103 READ FPDMA QUEUED
60 00 00 02 00 00 00 18 da a0 e0 40 00 4d+06:41:12.102 READ FPDMA QUEUED
60 00 00 02 00 00 00 18 da 9e e0 40 00 4d+06:41:12.101 READ FPDMA QUEUED

Error 38446 [5] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 05 88 25 a8 40 00 4d+06:41:09.043 READ FPDMA QUEUED
61 00 00 00 60 00 00 23 2a fe e0 40 00 4d+06:41:08.998 WRITE FPDMA QUEUED
60 00 00 02 00 00 00 04 1b 02 a0 40 00 4d+06:41:08.991 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1b 00 a0 40 00 4d+06:41:08.991 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a fe a0 40 00 4d+06:41:08.991 READ FPDMA QUEUED

Error 38445 [4] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a ed a0 40 00 4d+06:41:01.153 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 2a ed 80 40 00 4d+06:41:01.118 WRITE FPDMA QUEUED
60 00 00 00 20 00 00 16 9a 84 e0 40 00 4d+06:41:01.081 READ FPDMA QUEUED
60 00 00 00 20 00 00 1c ec 0f 80 40 00 4d+06:41:01.077 READ FPDMA QUEUED
61 00 00 08 00 00 00 1c ec 07 00 40 00 4d+06:41:01.052 WRITE FPDMA QUEUED

Error 38444 [3] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 05 88 25 a0 40 00 4d+06:40:58.391 READ FPDMA QUEUED
60 00 00 00 08 00 00 05 88 25 58 40 00 4d+06:40:58.360 READ FPDMA QUEUED
61 00 00 00 20 00 00 23 2a e5 60 40 00 4d+06:40:58.353 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 2a e5 40 40 00 4d+06:40:58.340 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 03 9d 40 b8 40 00 4d+06:40:58.316 READ FPDMA QUEUED

Error 38443 [2] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 05 88 25 40 40 00 4d+06:40:53.236 READ FPDMA QUEUED
60 00 00 00 08 00 00 00 ab 6e 00 40 00 4d+06:40:53.233 READ FPDMA QUEUED
60 00 00 00 08 00 00 00 88 9a 70 40 00 4d+06:40:53.227 READ FPDMA QUEUED
60 00 00 00 20 00 00 12 04 1e a0 40 00 4d+06:40:53.209 READ FPDMA QUEUED
61 00 00 00 08 00 00 03 27 27 d0 40 00 4d+06:40:53.209 WRITE FPDMA QUEUED

Error 38442 [1] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a e5 00 40 00 4d+06:40:50.790 WRITE FPDMA QUEUED
60 00 00 00 20 00 00 36 cf f3 e0 40 00 4d+06:40:50.688 READ FPDMA QUEUED
61 00 00 00 08 00 00 05 8b bc 30 40 00 4d+06:40:50.687 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a e3 00 40 00 4d+06:40:50.687 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a e1 00 40 00 4d+06:40:50.686 WRITE FPDMA QUEUED

Error 38441 [0] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a dc c0 40 00 4d+06:40:45.679 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 00 5e b3 88 40 00 4d+06:40:45.611 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 00 5e b3 98 40 00 4d+06:40:45.611 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 00 60 43 c8 40 00 4d+06:40:45.610 WRITE FPDMA QUEUED
60 00 00 02 00 00 00 18 da 80 e0 40 00 4d+06:40:45.609 READ FPDMA QUEUED

Error 38440 [19] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a dc a0 40 00 4d+06:40:43.105 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a da a0 40 00 4d+06:40:43.001 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a d8 a0 40 00 4d+06:40:42.999 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a d6 a0 40 00 4d+06:40:42.996 WRITE FPDMA QUEUED
61 00 00 02 00 00 00 23 2a d4 a0 40 00 4d+06:40:42.993 WRITE FPDMA QUEUED

Error 38439 [18] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 02 00 00 00 04 1a f2 a0 40 00 4d+06:40:37.768 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a f0 a0 40 00 4d+06:40:37.768 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a ee a0 40 00 4d+06:40:37.767 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a ec a0 40 00 4d+06:40:37.767 READ FPDMA QUEUED
61 00 00 00 40 00 00 23 2a d3 c0 40 00 4d+06:40:37.748 WRITE FPDMA QUEUED

Error 38438 [17] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a d3 40 40 00 4d+06:40:35.299 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 00 ab 75 48 40 00 4d+06:40:35.294 READ FPDMA QUEUED
61 00 00 00 08 00 00 03 84 35 f8 40 00 4d+06:40:35.271 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 29 a8 a0 40 00 4d+06:40:35.268 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 2a d3 20 40 00 4d+06:40:35.264 WRITE FPDMA QUEUED

Error 38437 [16] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 60 00 00 06 40 55 00 40 00 4d+06:40:27.497 READ FPDMA QUEUED
60 00 00 00 40 00 00 04 2b 11 00 40 00 4d+06:40:27.478 READ FPDMA QUEUED
61 00 00 00 18 00 00 07 09 7d 28 40 00 4d+06:40:27.477 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 08 a9 c0 50 40 00 4d+06:40:27.474 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 14 35 a5 f8 40 00 4d+06:40:27.473 WRITE FPDMA QUEUED

Error 38436 [15] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: UNC at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 02 00 00 00 04 1a e2 a0 40 00 4d+06:40:24.910 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a e0 a0 40 00 4d+06:40:24.910 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a de a0 40 00 4d+06:40:24.909 READ FPDMA QUEUED
60 00 00 02 00 00 00 04 1a dc a0 40 00 4d+06:40:24.909 READ FPDMA QUEUED
60 00 00 00 40 00 00 03 9a 11 48 40 00 4d+06:40:24.905 READ FPDMA QUEUED

Error 38435 [14] occurred at disk power-on lifetime: 6478 hours (269 days + 22 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 5f 82 c0 00 00 Error: WP at LBA = 0x005f82c0 = 6259392

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
61 00 00 00 20 00 00 23 2a c2 00 40 00 4d+06:40:19.338 WRITE FPDMA QUEUED
61 00 00 00 20 00 00 23 2a c1 e0 40 00 4d+06:40:19.314 WRITE FPDMA QUEUED
60 00 00 00 40 00 00 03 9a 14 88 40 00 4d+06:40:19.310 READ FPDMA QUEUED
60 00 00 00 40 00 00 03 9a 14 48 40 00 4d+06:40:19.309 READ FPDMA QUEUED
60 00 00 00 40 00 00 03 9a 14 08 40 00 4d+06:40:19.308 READ FPDMA QUEUED

I've read the log and found it strange when it started "repeating" the same errors/sentences.

And after seeing the "Attributes" i got a little more scared

Screenshot_2020-06-27_19-19-19.png

Screenshot_2020-06-27_19-18-43.png

I just wanna know if i have to worry about it or can just install MX normally. I don't have a better choice then installing it. I made the dumb mistake of deleting the partition where Windows was installed and now i don't have any OS other than MX in my bootable pendrive.

I installed MX Linux in two devices and in none of them i got this message (despite the two of them being older than this one )
I'm kinda new to all this stuff so any help it's appreciated.
Thanks.

[JayM]

Please start a new topic for your issue rather than bumping an ancient thread, and when you post log entries use the code button </> not the quote button.