You are not logged in.
Pages: 1
I wasnt having any troubles with smart checks failing or anything until after i installed arch and switched to legacy bios and there is no option for me to disable the check in the bios.
Should i be worried about it and/or is there a way to fix it in arch since it didnt start doing this until i installed arch. When i get to the smart fail screen and i hit enter everything else works fine.
thanks for the help
Offline
Do you know what SMART is?
Yes, you should be worried. How worried depends on what is failing, but generally, when SMART reports that something is failing, it generally means it's time to replace the disk in question.
The output of
# smarctl -a /dev/sdawould tell us more (assuming sda is the device that's "failing").
Just for the record though, Arch isn't to blame here. Hardware failure can happen at any time, and installing Arch would only have caused a relatively tiny amount of wear and tear on your hard disk. It's just a coincidence that your disk is now reportedly failing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Do you know what SMART is?
Yes, you should be worried. How worried depends on what is failing, but generally, when SMART reports that something is failing, it generally means it's time to replace the disk in question.
The output of
# smarctl -a /dev/sdawould tell us more (assuming sda is the device that's "failing").
Just for the record though, Arch isn't to blame here. Hardware failure can happen at any time, and installing Arch would only have caused a relatively tiny amount of wear and tear on your hard disk. It's just a coincidence that your disk is now reportedly failing.
The output of smartctl -a /dev/sda is:
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.15.5-2-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST500LT012-9WS142
Serial Number: S0V3GN79
LU WWN Device Id: 5 000c50 05bd1152d
Firmware Version: 0001YAM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Jul 24 14:23:29 2014 UTC
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: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.
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: ( 0) seconds.
Offline data collection
capabilities: (0x53) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves 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: ( 100) minutes.
SCT capabilities: (0x103d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 111 094 006 Pre-fail Always - 41354832
3 Spin_Up_Time 0x0023 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 440
5 Reallocated_Sector_Ct 0x0033 029 029 036 Pre-fail Always FAILING_NOW 11736
7 Seek_Error_Rate 0x002f 064 060 030 Pre-fail Always - 17191941182
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1132
10 Spin_Retry_Count 0x0033 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440
183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 413
188 Command_Timeout 0x0032 100 097 000 Old_age Always - 51540393996
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 062 043 045 Old_age Always In_the_past 38 (0 1 39 35 0)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 122
192 Power-Off_Retract_Count 0x0022 100 100 000 Old_age Always - 8
193 Load_Cycle_Count 0x0032 089 089 000 Old_age Always - 23340
194 Temperature_Celsius 0x0022 038 057 000 Old_age Always - 38 (0 16 0 0 0)
196 Reallocated_Event_Count 0x0032 029 029 000 Old_age Always - 11736
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.Offline
Also it only started failed when i switched to legacy in the bios since grub wasnt working with uefi.
Offline
Also it only started failed when i switched to legacy in the bios since grub wasnt working with uefi.
That's just another coincidence, changing the boot method in your BIOS wont cause your hardware to spontaneously break.
Looking at the smartctl output, your drive is running out of reallocatable sectors, meaning that, if it develops additional bad sectors, it may not be able to remap them safely (resulting in data loss). If your disk is still under it's warranty period, you may be able to RMA it and get a replacement; otherwise, you'll just have to buy a new disk.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
It may not be a coincidence that the message started appearing when OP switched from UEFI to legacy. Perhaps his UEFI firmware doesn't support checking SMART, had SMART checking disabled, or has a bugged SMART implementation.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
If you just want to be sure if SMART is working, take the drive out and test it in a different computer. I'd expect rellocated sectors to increase, so it'd be wise to backup your data ASAP.
Offline
Just got a new hdd and replaced the old one with 2 different ones and the first thing it does on boot it says "SMART Failure. Hard disk failure iminent"
Offline
custom12,
This is beginning to look like a hardware or bios/uefi problem.
1. are you running latest bios/uefi firmware for your motherboard ?
2, a faulty cable or bad connector might cause this, try replacing the cables between mobo & hdd ,
3. test the drives in another system to verify the drives themselves are ok.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1