My Daily drivers 2TB SSD died this morning

For interesting topics. But remember this is a Linux Forum. Do not post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Message
Author
User avatar
m_pav
Developer
Posts: 1799
Joined: Sun Aug 06, 2006 3:02 pm

My Daily drivers 2TB SSD died this morning

#1 Post by m_pav »

It had to happen sooner or later, especially as I have been deliberately nonchalant about my use of this drive and I haven't been shy speaking about it here. I haven't been deliberately thrashing it, but I haven't been shy in my use of it either. I estimate my combined total volume of content on the drive has hovered around 1.2TB consistently throughout it's 5 year lifespan.

So how did it die? Very suddenly, no warning, so my understanding of hardware seems to indicate the fault was most likely from the drives controller because I've seen dying SSD's before and they often have some very tell-tale signs that make it easy to get data off the drive before it's too late - not so this time.

My Laptops cooling system started running at about half speed when I woke it from suspend the second time this morning. For this machine, a 9 year old Lenovo T560, that's a little odd because running MX, it's normally whisper quiet with the fan barely ticking over and only becoming audible when it's doing some heavy lifting. I checked my emails and let the updates run while I made a coffee, when I returned to it, the fan was still running at about half mast as it was earlier so I thought I'd reboot in case there was a memory leak or a dirty memory issue, as it used to have before I addressed the issue.

My Laptop booted to the Lenovo logo and stopped dead, nothing would make it go past it, could not boot into BIOS or do anything with it. Resetting it by pressing the pin-hole battery disconnect button made no difference so I cracked it open, removed the drive and the machine was happy to boot, so I knew the drive was the failure point. When I tried to read the drive from a USB drive enclosure, every machine I plugged it into just could not read the drive and watching the kernel messages revealed the kernel could not determine anything about the drive, it was as if it did not exist, other than pulling a few volts from the USB port. It was then I reaslised my last backup was 3 weeks ago and I had neglected to take them after doing my financial years end for 31st March - big oops.

All in all, only a minor loss as I retrieved much from emails I keep stored on my hosts mail server. Recalling I purchased this drive about 5 years ago, I looked up the invoice and it had 2 months left of its 5 year warranty, so I get to do it again for next to no financial outlay, other than a few dollars for a new 250GB SSD from stock to get the machine running again and a courier fee to return the dead drive. Home is encrypted, Windows had no value, so I have next to no concerns if they can get it to read, which I think is highly unlikely. I copied my 3 week old personal snapshot from my backup drive to my ventoy boot USB, booted into my snapshot, pulled in the updates while partitioning the new drive, run the installer and reboot. I then selectively rsync'd the minimal data needed to run the machine as if nothing ever happened and get on with it.

I believe the SSD failure was just pure bad luck, not a case of having worn out because I kept a close eye on its condition and it was nowhere near a point of concern showing 89 percent endurance remaining last time I checked. I have to admit, my last 3 weeks have been very busy in my work-from-home business with some new clients so I have slipped up with my backups, that's my bad, but overall a good enough result through having a good backup strategy, even when I missed one :duh:
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

User avatar
Eadwine Rose
Administrator
Posts: 14713
Joined: Wed Jul 12, 2006 2:10 am

Re: My Daily drivers 2TB SSD died this morning

#2 Post by Eadwine Rose »

I have had 4 SSDs die on me within the period of.. ohh... a few months. All bought around the same time, so... one could expect that they would go in succession. Guess they missed each other. I was JUST outside the warranty.

They die.. it sucks. With backups it sucks a little less. Glad you could use the warranty!

My condolences.
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

User avatar
chrispop99
Global Moderator
Posts: 3362
Joined: Tue Jan 27, 2009 2:07 pm

Re: My Daily drivers 2TB SSD died this morning

#3 Post by chrispop99 »

Out of interest,what make was the drive?

Chris
MX Facebook Group Administrator.
Home-built desktop - Core i5 9400, 970 EVO Plus, 8GB
DELL XPS 15
Lots of test machines

User avatar
MikeR
Posts: 221
Joined: Sun Jun 25, 2023 6:42 am

Re: My Daily drivers 2TB SSD died this morning

#4 Post by MikeR »

Apologizing for quoting myself, but:
If your backup schedule includes the word 'about', as in 'about monthly', 'more or less weekly' procrastination will hit you at the most inconvenient time
Mike
Old RSTS hack
Registered Linux user #542196

User avatar
oops
Posts: 1916
Joined: Tue Apr 10, 2018 5:07 pm

Re: My Daily drivers 2TB SSD died this morning

#5 Post by oops »

m_pav wrote: Mon Apr 07, 2025 3:53 am...

So how did it die? Very suddenly, no warning, so ...
... It is that why I prefer for the own data a HDD instead a SSD.
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32

User avatar
beardedragon
Posts: 164
Joined: Wed Mar 27, 2019 11:26 pm

Re: My Daily drivers 2TB SSD died this morning

#6 Post by beardedragon »

I've had two SATA SSD drives fail, both 512Gb. Bought at same time. So far three NVME drives are still slogging on. They are all tTB each. One primary, a backup and an archive which I never delete anything. Archive is only hooked up via USB-C once a week. The backup is daily, with only updated DATA from the primary. The primary I have reinstalled several times using Windows 11, and several Distros of Linux settling on MX 3.5 ahs. So far, so good.

Code: Select all

System:
  Kernel: 6.13.8-4-liquorix-amd64 [6.13-9~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: tsc
    avail: hpet,acpi_pm parameters: audit=0 intel_pstate=disable amd_pstate=disable
    BOOT_IMAGE=/boot/vmlinuz-6.13.8-4-liquorix-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 wm: xfwm4 v: 4.20.0 with: xfce4-panel
    tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_ahs_x64 Libretto Jan 12 2025
    base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Mini-pc System: BOSGAME product: EffiZen Series v: Version 1.0 serial: <superuser required>
  Mobo: BOSGAME model: ACB20 v: Version 1.0 serial: <superuser required> part-nu: 0001
    uuid: <superuser required> UEFI: American Megatrends LLC. v: 101 date: 03/11/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech ERGO M575 Trackball serial: <filter> charge: 55%
    rechargeable: yes status: discharging
CPU:
  Info: model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 2
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0x68 (104) stepping: 1 microcode: 0x8608107
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1800 min/max: 1400/1800 boost: enabled scaling: driver: acpi-cpufreq
    governor: ondemand cores: 1: 1800 2: 1800 3: 1800 4: 1800 5: 1800 6: 1800 7: 1800 8: 1800 9: 1800
    10: 1800 11: 1800 12: 1800 13: 1800 14: 1800 15: 1800 16: 1800 bogomips: 57487
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: Safe RET
  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; STIBP: always-on; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Lucienne driver: amdgpu v: kernel arch: GCN-5
    code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports:
    active: HDMI-A-2 empty: DP-1,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:164c class-ID: 0300
    temp: 43.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm4 v: 4.20.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: HDMI-A-2 mapped: HDMI-A-1 model: Sceptre F27 built: 2023 res: N/A dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.2.8-1mx23ahs glx-v: 1.4 es-v: 3.2 direct-render: yes
    renderer: AMD Radeon Graphics (radeonsi renoir LLVM 15.0.6 DRM 3.61 6.13.8-4-liquorix-amd64)
    device-ID: 1002:164c memory: 2.93 GiB unified: no
  API: Vulkan v: 1.4.304 layers: 3 device: 0 type: integrated-gpu name: AMD Radeon Graphics
    (RADV RENOIR) driver: mesa radv v: 24.2.8-1mx23ahs device-ID: 1002:164c surfaces: xcb,xlib
    device: 1 type: cpu name: llvmpipe (LLVM 15.0.6 256 bits) driver: mesa llvmpipe
    v: 24.2.8-1mx23ahs (LLVM 15.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: xfce4-display-settings x11: xdriinfo,
    xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir Radeon High Definition Audio
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.1
    chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio vendor: Conexant Systems
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 04:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.13.8-4-liquorix-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.1 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: Intel Ethernet I225-V driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    port: N/A bus-ID: 01:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e
    v: kernel modules: wl pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 14c3:0616
    class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, wpa_supplicant
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 0e8d:c616 class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2 lmp-v: 11
    sub-v: 2411 hci-v: 11 rev: 616 class-ID: 7c0104
  Info: acl-mtu: 1021:6 sco-mtu: 240:8 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 1.82 TiB used: 40.38 GiB (2.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 126 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 0B2QKXJ7 temp: 51.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: PSSD T7 size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B type: USB rev: 3.2 spd: 10 Gb/s lanes: 1 mode: 3.2 gen-2x1
    tech: SSD serial: <filter> scheme: MBR
Partition:
  ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 40.38 GiB (4.4%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 5 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 51.4 C mobo: 50.0 C gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: dpkg pkgs: 2253 libs: 1154 tools: apt, apt-get, aptitude, nala, synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https://brave-browser-apt-release.s3.brave.com/ stable main
  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/mx.list
    1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free
    2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs
Info:
  Memory: total: N/A available: 28.27 GiB used: 1.63 GiB (5.8%)
  Processes: 360 Power: uptime: 25m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 11.25 GiB
    services: upowerd,xfce4-power-manager Init: SysVinit v: 3.08 runlevel: 5 default: graphical
    tool: systemctl
  Compilers: gcc: 12.2.0 Client: shell wrapper v: 5.2.15-release inxi: 3.3.37
Boot Mode: UEFI
Rule #1 Backup Everything
Rule #2 Read Rule #1

User avatar
m_pav
Developer
Posts: 1799
Joined: Sun Aug 06, 2006 3:02 pm

Re: My Daily drivers 2TB SSD died this morning

#7 Post by m_pav »

chrispop99 wrote: Mon Apr 07, 2025 5:52 am Out of interest,what make was the drive?
It was only the hottest drive on the planet at the time, a Samsung 860 EVO 2TB Model MZ-76E2T0 2020.02.

When it came down from $NZ 795 Trade cost to $NZ 478, I snapped it up smartly. We get ripped blind here for computer hardware, so many folk buy bargain basement junk every 2 years and end up spending more per year than they would if they just spent another $400
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

User avatar
Stevo
Developer
Posts: 14612
Joined: Fri Dec 15, 2006 7:07 pm

Re: My Daily drivers 2TB SSD died this morning

#8 Post by Stevo »

Was this the one having trouble with hardinfo2?
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing

User avatar
m_pav
Developer
Posts: 1799
Joined: Sun Aug 06, 2006 3:02 pm

Re: My Daily drivers 2TB SSD died this morning

#9 Post by m_pav »

Stevo wrote: Mon Apr 07, 2025 6:22 pm Was this the one having trouble with hardinfo2?
No. The issue with that app is the verbage used for the 4 particular tests.

I'm just waiting for 2 more customers to send me back a copy of the PDF I sent them b4 the failure, I'll re-create them and I'll be all squared up again.
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

User avatar
m_pav
Developer
Posts: 1799
Joined: Sun Aug 06, 2006 3:02 pm

Re: My Daily drivers 2TB SSD died this morning

#10 Post by m_pav »

@Eadwine Rose
Thank you. Wow, to lose 4 SSDs' in such a short time frame, we need to go the extraneous section of different language dictionaries to explain that :footinmouth: At one point my brand new 1TB SSD backup appeared to not be working, so I was thinking I was in the worst possible scenario, turns out it was debris in the USB port, whew!

@MikeR
Exactly what I was thinking, and you can bet it will almost invariably be that exact scenario.

@oops
I used to be that way too, but a spinning platter controller can fail just as easily as SSD and I have seen incidences where that has happened in my nearly 30 years of doing this stuff. I think from memory, this is the 3rd time where I have been personally affected by drive failure. Every other incident was PEBCAK.
Mike P

Regd Linux User #472293
(Daily) Lenovo T560, i7-6600U, 16GB, 2.0TB SSD, MX_ahs
(ManCave) AMD Ryzen 5 5600G, 32G, 8TB mixed, MX_ahs
(Spare)2017 Macbook Air 7,2, 8GB, 256GB SSD, MX_ahs

Post Reply

Return to “General”