Page 1 of 1

Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 6:19 pm
by JesusLinux
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.

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 6:24 pm
by Eadwine Rose
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.

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 7:01 pm
by j2mcgreg
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.

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 7:08 pm
by JesusLinux
j2mcgreg 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.
Yes that is the drive sdb hitachi

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 7:12 pm
by JesusLinux
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.
System info from live USB snapshot, sdb is not mounting. Does not show on gparted:

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

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 9:14 pm
by JesusLinux
Image
Image


This is what I get when I try to boot to mx.

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 9:30 pm
by CharlesV
I would run

Code: Select all

sudo  smartctl -a /dev/sdb

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

Re: Help Troubleshoot failed HDD?

Posted: Mon Mar 24, 2025 10:06 pm
by DukeComposed
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
This is what it looks like to me as well.
JesusLinux wrote: Mon Mar 24, 2025 7:12 pm System info from live USB snapshot, sdb is not mounting. Does not show on gparted
If sdb is not mounting, your course of action is to:
  1. Verify the partition table is correct with "fdisk -l /dev/sdb " and "parted /dev/sdb p"
  2. Prove that all partitions are visible with "lsblk -f"
  3. Run a fsck on the errant partition if possible
  4. Start reading up on ddrescue and prepare to transition from repair to recovery.
This presumes that Windows still does boot as expected and not that safe-mode, takes 10 minutes to get to a login screen, failover kind of boot, either. If the drive is 12 years old its best days are behind it and you should set your expectations realistically based on that fact.

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 3:34 am
by Eadwine Rose
Do not link to QSI when asked for it. Always post IN the thread, thanks.

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 3:49 pm
by JesusLinux
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.

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 3:57 pm
by JesusLinux
CharlesV wrote: Mon Mar 24, 2025 9:30 pm I would run

Code: Select all

sudo  smartctl -a /dev/sdb

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

The drive is sda:

Code: Select all

jesuslinux@A-9410:~
$ sudo lsblk
NAME       MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0        7:0    0  10,1G  1 loop /live/linux
sda          8:0    0 465,8G  0 disk 
sdb          8:16   0 223,6G  0 disk 
├─sdb1       8:17   0 144,7G  0 part 
├─sdb2       8:18   0   767M  0 part 
├─sdb3       8:19   0     1K  0 part 
├─sdb5       8:21   0   200M  0 part 
├─sdb6       8:22   0  69,3G  0 part 
└─sdb7       8:23   0   8,6G  0 part [SWAP]
sdc          8:32   1  58,6G  0 disk 
├─sdc1       8:33   1  58,6G  0 part 
│ ├─ventoy 254:0    0  10,2G  1 dm   /live/boot-dev
│ └─sdc1   254:1    0  58,6G  0 dm   
└─sdc2       8:34   1    32M  0 part 

I'm on a live USB MX Linux snapshot I made last month

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 4:35 pm
by JesusLinux
DukeComposed wrote: Mon Mar 24, 2025 10:06 pm
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
This is what it looks like to me as well.
JesusLinux wrote: Mon Mar 24, 2025 7:12 pm System info from live USB snapshot, sdb is not mounting. Does not show on gparted
If sdb is not mounting, your course of action is to:
  1. Verify the partition table is correct with "fdisk -l /dev/sdb " and "parted /dev/sdb p"
  2. Prove that all partitions are visible with "lsblk -f"
  3. Run a fsck on the errant partition if possible
  4. Start reading up on ddrescue and prepare to transition from repair to recovery.
This presumes that Windows still does boot as expected and not that safe-mode, takes 10 minutes to get to a login screen, failover kind of boot, either. If the drive is 12 years old its best days are behind it and you should set your expectations realistically based on that fact.

Code: Select all

jesuslinux@A-9410:~
$ sudo fdisk -l /dev/sda
fdisk: cannot open /dev/sda: Input/output error

jesuslinux@A-9410:~
$ sudo parted /dev/sda p
[sudo] password for jesuslinux:     
Error: /dev/sda: unrecognised disk label
Model: ATA Hitachi HTS54505 (scsi)                                        
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: unknown
Disk Flags: 

jesuslinux@A-9410:~
$ sudo lsblk -f
NAME       FSTYPE   FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0      squashfs 4.0                                                         0   100% /live/linux
sda                                                                                      
sdb                                                                                      
├─sdb1     ntfs                      2BF63B2333C30FC9                                    
├─sdb2     ntfs                      3634877B34873CBD                                    
├─sdb3                                                                                   
├─sdb5     vfat     FAT32 EFI-SYSTEM D356-17F5                                           
├─sdb6     ext4     1.0   rootMX23   163f3d75-4f37-4872-a39e-ae673eda6d74                
└─sdb7     swap     1     swapMX     ec23a03e-b833-4ef4-a229-121b6175593d                [SWAP]
sdc                                                                                      
├─sdc1     exfat    1.0   Ventoy     4E21-0000                                           
│ ├─ventoy                                                                      0   100% /live/boot-dev
│ └─sdc1                                                                                 
└─sdc2     vfat     FAT16 VTOYEFI    626B-4255    

Code: Select all

jesuslinux@A-9410:~
$ sudo umount /dev/sda
umount: /dev/sda: not mounted.
jesuslinux@A-9410:~
$ sudo fsck /dev/sda
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
fsck.ext2: Input/output error while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>
[/CDOE]

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 5:12 pm
by DukeComposed
JesusLinux wrote: Tue Mar 25, 2025 4:35 pm

Code: Select all

$ sudo fsck /dev/sda
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
fsck.ext2: Input/output error while trying to open /dev/sda
sda is a device, not a partition. fsck only works on file systems, so "fsck /dev/sda" won't do anything. In this case, it looks like that drive doesn't have a partition table anymore. Not a readable one, at least. Time to look into recovery.

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 5:48 pm
by JesusLinux
DukeComposed wrote: Tue Mar 25, 2025 5:12 pm
JesusLinux wrote: Tue Mar 25, 2025 4:35 pm

Code: Select all

$ sudo fsck /dev/sda
fsck from util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
fsck.ext2: Input/output error while trying to open /dev/sda
sda is a device, not a partition. fsck only works on file systems, so "fsck /dev/sda" won't do anything. In this case, it looks like that drive doesn't have a partition table anymore. Not a readable one, at least. Time to look into recovery.
Yes it's 500GB Hitachi hdd.
I had the MX Linux /home partition on it and a data partition for Win11/MX.
They are not mounted anymore that's why I can't boot to MX because home is on it.
SDB has Win11, boot,EFI/, MX root/ and swap/...

How should I proceed in trying to recover the /home partition and relocate to a sdb partition next to /root?
Or is it better to make a clean install of MX in the sdb SSD?

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 5:56 pm
by Eadwine Rose
i/o errors..

Ehhh.. I'd say buy a new SSD.

Re: Help Troubleshoot failed HDD?

Posted: Tue Mar 25, 2025 10:35 pm
by figueroa
Don't give up too quickly. Your 500 GB drive SDA has no partitions. Recreate you partitions on that drive, if you are able, then restore the contents from your backups, in particular /home. If you don't have backups, your data is likely toast. What is the state of your data backups?

Note: The drive may be bad if it has suddenly lost its partition table. Of course, the loss of the partition table may have been because of a fat finger error. But, if the drive is bad, it can be replaced.

The alternative is to become an expert in drive recovery tools. It doesn't sound like you are that person. Proceed with caution. Reinstalling MX linux again isn't going to solve the problem which appears to be loss of your /home partition.

Re: Help Troubleshoot failed HDD?

Posted: Wed Mar 26, 2025 4:36 pm
by JesusLinux
figueroa wrote: Tue Mar 25, 2025 10:35 pm Don't give up too quickly. Your 500 GB drive SDA has no partitions. Recreate you partitions on that drive, if you are able, then restore the contents from your backups, in particular /home. If you don't have backups, your data is likely toast. What is the state of your data backups?

Note: The drive may be bad if it has suddenly lost its partition table. Of course, the loss of the partition table may have been because of a fat finger error. But, if the drive is bad, it can be replaced.

The alternative is to become an expert in drive recovery tools. It doesn't sound like you are that person. Proceed with caution. Reinstalling MX linux again isn't going to solve the problem which appears to be loss of your /home partition.
I have a month old snapshot backup. This is a secondary laptop. I don't have important files.
It's just I never had a HDD fail.
This HDD had partitions a /home of Mx Linux and a W11/MX linux data partition.
Now those partitions are not recognized.
I just want to make sure that I can't salvage anything...
This drive was rarely in use. it was used as a data when I had W10 installed.
I upgraded to W11 and installed MX on dual boot. Several weeks later this happened

Re: Help Troubleshoot failed HDD?

Posted: Wed Mar 26, 2025 5:37 pm
by DukeComposed
JesusLinux wrote: Wed Mar 26, 2025 4:36 pm I have a month old snapshot backup. This is a secondary laptop. I don't have important files.
It's just I never had a HDD fail.
First time for everything. Now you know what a bad disk looks like. One day it works, the next it's toast. You have a backup. That's great. It means you can stop wasting your time trying to fix something you don't need.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 2:46 pm
by JesusLinux
Ok,
I ended up reinstalling MX from a one month old laptop on the 240GB SSD. This drive now has W11, mx boot-efi/, root/, home/ and /swap.
On the place I had the HDD CD-ROM caddy I put the DVD-RW back in the original one it came with.
On Win11 the DVDRW drive shows up in file explorer but on MX it does not show on devices...

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 3:19 pm
by Eadwine Rose
We need a new QSI now.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 3:51 pm
by jdc
Got the same error... hdd failed...

but was able to install anyway by activating the 2 accounts : root account and width the default account.

try and error attempt to install some 5 times until worked width double account

...

my error was :

install all good all files loaded to disk but on start up got hdd failed...

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 3:55 pm
by Eadwine Rose
Please start your own topic, do not tack onto other folks topics. Thanks.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 9:31 pm
by JesusLinux
Eadwine Rose wrote: Fri Mar 28, 2025 3:19 pm We need a new QSI now.

Code: Select all

Snapshot created on: 20250327_2331
System:
  Kernel: 6.1.0-32-amd64 [6.1.129-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-32-amd64 root=UUID=<filter> ro quiet splash
  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.5_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: 0x2F
  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: 1492 high: 1531 min/max: 800/2300 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1531 2: 1453 bogomips: 9179
  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 mitigation: Clear CPU buffers; 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 mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; 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-32-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: 223.57 GiB used: 17.16 GiB (7.7%)
  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
Partition:
  ID-1: / raw-size: 24.41 GiB size: 23.86 GiB (97.74%) used: 11.1 GiB (46.5%) fs: ext4
    dev: /dev/sda6 maj-min: 8:6
  ID-2: /boot/efi raw-size: 200 MiB size: 196.9 MiB (98.44%) used: 3 KiB (0.0%) fs: vfat
    dev: /dev/sda5 maj-min: 8:5
  ID-3: /home raw-size: 44.92 GiB size: 43.91 GiB (97.76%) used: 6.07 GiB (13.8%) fs: ext4
    dev: /dev/sda8 maj-min: 8:8
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: 54.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2295 pm: dpkg pkgs: 2283 libs: 1159
    tools: apt,apt-get,aptitude,gnome-software,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 12
  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://mirrors.ocf.berkeley.edu/mx-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: 212 Uptime: 1m wakeups: 2 Memory: 7.65 GiB used: 2.12 GiB (27.8%) 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)

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 10:39 pm
by DukeComposed
JesusLinux wrote: Fri Mar 28, 2025 2:46 pm On Win11 the DVDRW drive shows up in file explorer but on MX it does not show on devices...
Silly question: what disc did you put in the DVD-RW drive?

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 10:42 pm
by JesusLinux
The DVDR drive shows up in thunar under computer:/// but not on the "Devices" side pane, Does not show on the box to tick,
How do I put DVDR drive to show on devices side pane?

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 10:46 pm
by JesusLinux
DukeComposed wrote: Fri Mar 28, 2025 10:39 pm
JesusLinux wrote: Fri Mar 28, 2025 2:46 pm On Win11 the DVDRW drive shows up in file explorer but on MX it does not show on devices...
Silly question: what disc did you put in the DVD-RW drive?
There no disc inserted at the moment.
I tested the DVDR on Win11 and audio cds and dvds was working.
Then I had to go to other place to work I have the laptop with me but no cds or dvds here to test.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 11:12 pm
by DukeComposed
JesusLinux wrote: Fri Mar 28, 2025 10:42 pm The DVDR drive shows up in thunar under computer:/// but not on the "Devices" side pane, Does not show on the box to tick,
How do I put DVDR drive to show on devices side pane?
If you right-click on the word Devices in the panel on the side of Thunar, you should be able to see a menu of checkboxes that determine what gets displayed there.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 11:47 pm
by JesusLinux
DukeComposed wrote: Fri Mar 28, 2025 11:12 pm
JesusLinux wrote: Fri Mar 28, 2025 10:42 pm The DVDR drive shows up in thunar under computer:/// but not on the "Devices" side pane, Does not show on the box to tick,
How do I put DVDR drive to show on devices side pane?
If you right-click on the word Devices in the panel on the side of Thunar, you should be able to see a menu of checkboxes that determine what gets displayed there.
Yes, on that menu on the devices checkbox list only File System and the 155GB partition with Win11 drive shows up...no DVDR entry to checkbox,
On computer:/// the DVDR drive shows up.

Also I tried this on this page and nothing...

https://docs.xfce.org/xfce/thunar/using-removable-media

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 11:56 pm
by DukeComposed
JesusLinux wrote: Fri Mar 28, 2025 11:47 pm Also I tried this on this page and nothing...

https://docs.xfce.org/xfce/thunar/using-removable-media
Yes, it's time to investigate Thunar > Preferences > Advanced > Volume Management. This is what you you've linked, but you haven't specified what you actually tried.

Re: Help Troubleshoot failed HDD?

Posted: Fri Mar 28, 2025 11:59 pm
by JesusLinux
DukeComposed wrote: Fri Mar 28, 2025 11:56 pm
JesusLinux wrote: Fri Mar 28, 2025 11:47 pm Also I tried this on this page and nothing...

https://docs.xfce.org/xfce/thunar/using-removable-media
Yes, it's time to investigate Thunar > Preferences > Advanced > Volume Management. This is what you you've linked, but you haven't specified what you actually tried.
I ticked the checkboxes on that docs.xfce as described...

Re: Help Troubleshoot failed HDD?

Posted: Sat Mar 29, 2025 12:30 am
by DukeComposed
JesusLinux wrote: Fri Mar 28, 2025 11:59 pm I ticked the checkboxes on that docs.xfce as described...
I'm afraid that doesn't really narrow it down. There are a lot of checkboxes. Try putting a disc in the drive and seeing if Thunar detects it. Then try booting the system from a USB and checking to see if it appears in Thunar in the live session. This will at least tell you if it's a systemic problem or not.