The above messages is thrown repeatedly in your log.
Like it or not - you are having a hardware error …
5 Likes
OK guys, I just want to say, this has to be the longest thread to get a diagnosis…but very well done to all of you!
At the risk of getting more hate, @randomidiot, you should be less combative (I think that’s thee right word.) when asking for help. If you are unhelpful, combative, confrontational and uncooperative, then you can’t blame anyone for treating you the same. And if you weren’t, well, then nobody here could know, seeing as we can’t see you physically.
2 Likes
I communicate through a translator, maybe it sounds rude from Russian? but i didn’t want it
2 Likes
You are very likely lucky actually that the disk didn’t fail completely, right now you can backup the stuff from it to some other place, and then booting live cd of manjaro and with gparted try to clean the disk I guess, that’s the best like chance to fix it, if it’s not the disk failure from my view,
but if it will persist even after cleaning the disk, or if it even won’t let you clean the disk, you need new disk
That makes everything different. I know translating software will never be able to perfectly match a human’s tone, meaning and more. So if we knew that, it might have been different.
You certainly came across as rude, uncooperative and combative.
I will not argue about, i mentioned how is by default, especially since fsck is present in /etc/mkinitcpio.conf … Remember ?
Should be in grub file right after quiet and once you edit it you have to run
sudo update-grub
No worries about that anymore, we passed that phase and we are all good. Hopefully your issue will have a solution after all was said, and you can get back a functional system.
1 Like
im sorry…
It’s OK now, but now we know in the future. 
Is this a desktop or a laptop? Are you able to use a different SATA cable or a different SATA port?
If you’ve tried that, and it still spits out errors, it could in fact be a faulty SSD.
1 Like
Or maybe remove ssd and try smartctl on a different computer that will rule out motherboard port failure.
1 Like
its a desktop.
first i will wait ending of the test
then i try to change grub conf, then i will open pc box and move ssd port
thank you everyone! i write about success later, and sorry about my eng
2 Likes
With this command you can view the results and current smart data for the specific disk, just if you didn’t know
“sudo smartctl -a <insert_disk_path_here>”
Surely it has completed by now.
nothing in terminal, how i can see result?
As I wrote above in post, you can view it with this command
Show us the whole output of this command
1 Like
To add to this, @randomidiot don’t include the partition.
So rather than /dev/sdb2, use /dev/sdb, for example.
2 Likes
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.19-2-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: R5SL128G
Serial Number: 03212221N0504
Firmware Version: S1211A0
User Capacity: 128 035 676 160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
TRIM Command: Available, deterministic, zeroed
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun Nov 14 02:56:32 2021 MSK
SMART support is: Available - device has SMART capability.
SMART support is: 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: ( 120) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save 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: ( 10) minutes.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 050 Old_age Always - 796
12 Power_Cycle_Count 0x0032 100 100 050 Old_age Always - 200
160 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 0
161 Unknown_Attribute 0x0033 100 100 050 Pre-fail Always - 100
163 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 7
164 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 9537
165 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 68
166 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 4
167 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 19
168 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 7000
169 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 100
175 Program_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
176 Erase_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
177 Wear_Leveling_Count 0x0032 100 100 050 Old_age Always - 0
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 050 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 050 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always - 32
194 Temperature_Celsius 0x0022 100 100 050 Old_age Always - 42
195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always - 5110
196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always - 0
198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 27544
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 100
241 Total_LBAs_Written 0x0030 100 100 050 Old_age Offline - 20635
242 Total_LBAs_Read 0x0030 100 100 050 Old_age Offline - 13434
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 20178
SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 1
ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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 -1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
Error -3 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Interrupted (host reset) 90% 753 -
Selective Self-tests/Logging not supported
hello again)
Hey,
the test didn’t complete, it stopped at 90% because the computer was turned off, that’s weird because it appeared you left the computer running for very long time,
the ssd is quite obscure one,
there is big amount of errors with this attribute UDMA_CRC_Error_Count 27544, it suggests the sata cable is damaged or something is wrong with it, maybe even some interference that could be caused by like power wire being too close to the sata cable,
it’s not that high but it should be 0, as all of my disks have that value at 0 too, so very likely there is problem with the sata cable or with the ports its plugged in,
something for sure is wrong on hardware level
the smart data also show that some error happened when the ssd had power on time 0, that’s kinda weird, it could mean the unit is faulty in some way
but all that failed was smart functions to read and log stuff shrugs
maybe important maybe not, not sure, but potentially it could mean the ssd is damaged,
sometimes its really hard to read smart data, every vendor does them little bit differently and its very confusing
if you haven’t yet tried re-plugging the sata cable etc… or maybe replacing it with different one, do that
if it continues causing problem then I guess the ssd is damaged and it looks like it was damaged at the factory, so faulty unit
EDIT:
if you can I would also try different motherboard too if it’s available to you as others wrote above
Please tell me, is it necessary to run the test again?
I think you don’t have to,
I would first try to do something about the sata cable
if that doesn’t help you can run the test again after that and post results here, maybe it could reveal something more but I think it’s not necessary