Help Troubleshoot failed HDD?
- JesusLinux
- Posts: 74
- Joined: Fri Aug 16, 2024 4:47 pm
Help Troubleshoot failed HDD?
Hello,
I'm having a problem with an HP laptop that I recently installed MX Linux.
This machine dual boots Win11 and MX Linux.
This HP has a 240GB SSD where Win11 is installed along with MX Linux EFI/boot partition (GRUB), root/partition and /swap.
It has a 500GB HDD where mx/home and a data partition.
Everything was working fine until this morning. Dual boot was working fine.
Now I can't boot to MX Linux it stays in loop for a while saying messages errors a then login appears and after password it goes back to login.
I can boot to Win11 fine. I went to W11 disk management and the 500GB is not recognized (says unallocated).
I suspect MX Linux is not mounting the 500GB HDD where /home is located.
I'm asking for help to troubleshoot this problem.
I intend to open the laptop reconnect the HDD.
Thank you for any advice.
I'm having a problem with an HP laptop that I recently installed MX Linux.
This machine dual boots Win11 and MX Linux.
This HP has a 240GB SSD where Win11 is installed along with MX Linux EFI/boot partition (GRUB), root/partition and /swap.
It has a 500GB HDD where mx/home and a data partition.
Everything was working fine until this morning. Dual boot was working fine.
Now I can't boot to MX Linux it stays in loop for a while saying messages errors a then login appears and after password it goes back to login.
I can boot to Win11 fine. I went to W11 disk management and the 500GB is not recognized (says unallocated).
I suspect MX Linux is not mounting the 500GB HDD where /home is located.
I'm asking for help to troubleshoot this problem.
I intend to open the laptop reconnect the HDD.
Thank you for any advice.
- Eadwine Rose
- Administrator
- Posts: 14666
- Joined: Wed Jul 12, 2006 2:10 am
Re: Help Troubleshoot failed HDD?
According to the forum rules (please read): Please provide full Quick System Info, use copy for forum button, no edits.
LiveUSB version is OK if needed.
LiveUSB version is OK if needed.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Help Troubleshoot failed HDD?
If the QSI shown in post #17 of this thread:
viewtopic.php?p=811172#p811172
is still valid, that Hitachi HDD is around twelve years old and has likely died. See here for age confirmation:
https://hdd.userbenchmark.com/SpeedTest ... 5050A7E380
You might try removing it from the laptop and then try to access it via a SATA adaptor or dock but I wouldn't advise you to spend much money in the attempt.
viewtopic.php?p=811172#p811172
is still valid, that Hitachi HDD is around twelve years old and has likely died. See here for age confirmation:
https://hdd.userbenchmark.com/SpeedTest ... 5050A7E380
You might try removing it from the laptop and then try to access it via a SATA adaptor or dock but I wouldn't advise you to spend much money in the attempt.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;
In Linux, newer isn't always better. The best solution is the one that works.
- JesusLinux
- Posts: 74
- Joined: Fri Aug 16, 2024 4:47 pm
Re: Help Troubleshoot failed HDD?
Yes that is the drive sdb hitachij2mcgreg wrote: Mon Mar 24, 2025 7:01 pm If the QSI shown in post #17 of this thread:
viewtopic.php?p=811172#p811172
is still valid, that Hitachi HDD is around twelve years old and has likely died. See here for age confirmation:
https://hdd.userbenchmark.com/SpeedTest ... 5050A7E380
You might try removing it from the laptop and then try to access it via a SATA adaptor or dock but I wouldn't advise you to spend much money in the attempt.
- JesusLinux
- Posts: 74
- Joined: Fri Aug 16, 2024 4:47 pm
Re: Help Troubleshoot failed HDD?
System info from live USB snapshot, sdb is not mounting. Does not show on gparted:Eadwine Rose wrote: Mon Mar 24, 2025 6:24 pm According to the forum rules (please read): Please provide full Quick System Info, use copy for forum button, no edits.
LiveUSB version is OK if needed.
Code: Select all
Snapshot created on: 20250202_2320
System:
Kernel: 6.1.0-28-amd64 [6.1.119-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: lang=en_US
kbd=pt tz=Europe/Lisbon
Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
dm: LightDM v: 1.32.0 Distro: MX-23.3_x64 Libretto August 15 2024 base: Debian GNU/Linux 12
(bookworm)
Machine:
Type: Laptop System: Hewlett-Packard product: HP Pavilion g6 Notebook PC
v: 0791100000205610000620100 serial: <superuser required> Chassis: type: 10
serial: <superuser required>
Mobo: Hewlett-Packard model: 1840 v: 56.32 serial: <superuser required> UEFI-[Legacy]: Insyde
v: F.27 date: 09/07/2016
CPU:
Info: model: Intel Pentium B970 bits: 64 type: MCP arch: Sandy Bridge level: v2 built: 2010-12
process: Intel 32nm family: 6 model-id: 0x2A (42) stepping: 7 microcode: 0x28
Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB desc: 2x256 KiB L3: 2 MiB desc: 1x2 MiB
Speed (MHz): avg: 917 high: 980 min/max: 800/2300 scaling: driver: intel_cpufreq
governor: ondemand cores: 1: 980 2: 855 bogomips: 9178
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not
affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-6 code: Sandybridge process: Intel 32nm built: 2011 ports:
active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0106 class-ID: 0300
Device-2: AMD Thames [Radeon HD 7500M/7600M Series] vendor: Hewlett-Packard driver: N/A
alternate: radeon, amdgpu arch: TeraScale-2 code: Evergreen process: TSMC 32-40nm built: 2009-15
pcie: gen: 1 speed: 2.5 GT/s lanes: 8 link-max: lanes: 16 bus-ID: 01:00.0 chip-ID: 1002:6840
class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 362x204mm (14.25x8.03") s-diag: 416mm (16.36")
Monitor-1: LVDS-1 model: LG Display 0x02f2 built: 2011 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 2000 (SNB GT1)
direct-render: Yes
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard 7
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
API: ALSA v: k6.1.0-28-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Ralink vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 modules: wl pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 1814:539a class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 08:00.0 chip-ID: 10ec:8136
class-ID: 0200
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 747.93 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37240G size: 223.57 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 1103 scheme: MBR
ID-2: /dev/sdb maj-min: 8:16 vendor: Hitachi model: HTS545050A7E380 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5400 serial: <filter>
rev: A7A0
ID-3: /dev/sdc maj-min: 8:32 type: USB model: N/A size: 58.59 GiB block-size: physical: 512 B
logical: 512 B type: N/A serial: <filter> rev: 2.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.59 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda7
maj-min: 8:7
Sensors:
System Temperatures: cpu: 46.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: 2291 pm: dpkg pkgs: 2282 libs: 1159
tools: apt,apt-get,aptitude,gnome-software,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 9
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://ftp.rnl.tecnico.ulisboa.pt/pub/mxlinux-packages/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com stable non-free
Info:
Processes: 209 Uptime: 9m wakeups: 2 Memory: 7.65 GiB used: 2.22 GiB (29.0%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Video Tweaks:
Detected possible Hybrid Graphics
- JesusLinux
- Posts: 74
- Joined: Fri Aug 16, 2024 4:47 pm
Re: Help Troubleshoot failed HDD?
I would run
and post those results.
You could try a to run fsck on it, but it looks like your HD has indeed failed. Smartctl results may show us for sure
Code: Select all
sudo smartctl -a /dev/sdb
You could try a to run fsck on it, but it looks like your HD has indeed failed. Smartctl results may show us for sure
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!
- DukeComposed
- Posts: 1410
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Help Troubleshoot failed HDD?
This is what it looks like to me as well.CharlesV wrote: Mon Mar 24, 2025 9:30 pm You could try a to run fsck on it, but it looks like your HD has indeed failed. Smartctl results may show us for sure
If sdb is not mounting, your course of action is to:JesusLinux wrote: Mon Mar 24, 2025 7:12 pm System info from live USB snapshot, sdb is not mounting. Does not show on gparted
- Verify the partition table is correct with "fdisk -l /dev/sdb " and "parted /dev/sdb p"
- Prove that all partitions are visible with "lsblk -f"
- Run a fsck on the errant partition if possible
- Start reading up on ddrescue and prepare to transition from repair to recovery.
- Eadwine Rose
- Administrator
- Posts: 14666
- Joined: Wed Jul 12, 2006 2:10 am
Re: Help Troubleshoot failed HDD?
Do not link to QSI when asked for it. Always post IN the thread, thanks.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
- JesusLinux
- Posts: 74
- Joined: Fri Aug 16, 2024 4:47 pm
Re: Help Troubleshoot failed HDD?
Hello again, here are the results about the drive:
Code: Select all
$ sudo smartctl -a /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-28-amd64] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Hitachi/HGST Travelstar Z5K500
Device Model: Hitachi HTS545050A7E380
Serial Number: TE85323Q2BLE4W
LU WWN Device Id: 5 000cca 6e4e17440
Firmware Version: GG2OA7A0
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database 7.3/5319
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Tue Mar 25 19:45:45 2025 WET
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
See vendor-specific Attribute list for marginal 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: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 111) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
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 086 086 062 Pre-fail Always - 11862016
2 Throughput_Performance 0x0025 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0023 214 100 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 5484
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 664 (0 82)
7 Seek_Error_Rate 0x002f 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 043 043 000 Old_age Always - 25077
10 Spin_Retry_Count 0x0033 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 5053
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 27715562045620
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 68727865362
190 Airflow_Temperature_Cel 0x0022 076 043 045 Old_age Always In_the_past 24 (Min/Max 15/24)
191 G-Sense_Error_Rate 0x0032 095 095 000 Old_age Always - 1488
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2228258
193 Load_Cycle_Count 0x0032 050 050 000 Old_age Always - 508751
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 82
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 32
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 0
223 Load_Retry_Count 0x002a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 180 (device log contains only the most recent five errors)
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 180 occurred at disk power-on lifetime: 25077 hours (1044 days + 21 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
-- -- -- -- -- -- --
40 41 08 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 20 00 00 00 40 00 00:01:42.995 READ FPDMA QUEUED
ef 05 fe 00 00 00 40 00 00:01:42.995 SET FEATURES [Enable APM]
ef 10 03 00 00 00 a0 00 00:01:42.995 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:01:42.982 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:01:42.980 IDENTIFY DEVICE
Error 179 occurred at disk power-on lifetime: 25077 hours (1044 days + 21 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
-- -- -- -- -- -- --
40 41 08 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 e8 00 00 00 40 00 00:01:38.538 READ FPDMA QUEUED
60 08 e0 20 60 38 40 00 00:01:38.535 READ FPDMA QUEUED
60 08 d8 80 5f 38 40 00 00:01:38.501 READ FPDMA QUEUED
ec 00 01 00 00 00 00 00 00:01:38.499 IDENTIFY DEVICE
ef 10 03 00 00 00 a0 00 00:01:35.592 SET FEATURES [Enable SATA feature]
Error 178 occurred at disk power-on lifetime: 25077 hours (1044 days + 21 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
-- -- -- -- -- -- --
40 41 08 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 68 00 00 00 40 00 00:01:32.092 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:01:32.092 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:01:32.081 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:01:32.080 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:32.080 SET FEATURES [Set transfer mode]
Error 177 occurred at disk power-on lifetime: 25077 hours (1044 days + 21 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
-- -- -- -- -- -- --
40 41 08 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b8 00 00 00 40 00 00:01:28.583 READ FPDMA QUEUED
60 08 b0 20 60 38 40 00 00:01:28.580 READ FPDMA QUEUED
60 08 a8 80 5f 38 40 00 00:01:28.266 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:01:25.568 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:01:25.558 SET FEATURES [Enable SATA feature]
Error 176 occurred at disk power-on lifetime: 25077 hours (1044 days + 21 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
-- -- -- -- -- -- --
40 41 08 00 00 00 00 Error: UNC at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 a0 00 00 00 40 00 00:01:22.068 READ FPDMA QUEUED
ef 10 03 00 00 00 a0 00 00:01:22.068 SET FEATURES [Enable SATA feature]
ef 10 02 00 00 00 a0 00 00:01:22.057 SET FEATURES [Enable SATA feature]
ec 00 00 00 00 00 a0 00 00:01:22.056 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:01:22.056 SET FEATURES [Set transfer mode]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 21353 -
# 2 Short offline Completed without error 00% 21318 -
# 3 Short offline Completed without error 00% 21230 -
# 4 Short offline Aborted by host 40% 21182 -
# 5 Short offline Completed without error 00% 21024 -
# 6 Short offline Aborted by host 30% 20919 -
# 7 Short offline Completed without error 00% 20779 -
# 8 Short offline Aborted by host 60% 20755 -
# 9 Short offline Aborted by host 40% 20704 -
#10 Short offline Completed without error 00% 20606 -
#11 Short offline Aborted by host 40% 20486 -
#12 Short offline Completed without error 00% 20457 -
#13 Short offline Completed without error 00% 3605 -
#14 Short offline Completed without error 00% 3599 -
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.