Secondary drive randomly unmounts, Again!

Almost exactly a year ago after having my secondary NVMe unmount randomly, beginning as an infrequent occurrence and ending with it being completely unusable. I have now had the same thing happen to me again, this time a on a completely new drive and from a completely different brand. (previous drive was a Kingston NV2 and the new one a WD Black SSD SN770)

The conclusion before the re:occurrence was that this was a unlucky draw from the silicon lottery. But now that it has happened to two different drives, mounted on the exact same motherboard NVMe slot, on the same install of EndevourOS.

Could this be a software issue or is my motherboard killing my drives?

edit 1: It shows up normally right now and unmounts as soon as I try updating Marvel Rivals a game I have downloaded on my main drive.

That’d be where I start investigating. It could be a motherboard physical or firmware fault, or it could be environmental, such as a contact issue, or temperature.

What’s the output of:

inxi -Mdsxxx --za
lsblk -f

inxi

Machine:
Type: Desktop System: Gigabyte product: X570 I AORUS PRO WIFI v: -CF
serial:
Mobo: Gigabyte model: X570 I AORUS PRO WIFI serial:
uuid: BIOS: American Megatrends LLC. v: F36d
date: 07/20/2022
Drives:
Local Storage: total: 2.95 TiB used: 2.09 TiB (70.8%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 2000GB
size: 1.82 TiB speed: 63.2 Gb/s lanes: 4 tech: SSD serial:
fw-rev: 620361WD temp: 37.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Western Digital model: WDS100T3X0C-00SJG0
size: 931.51 GiB speed: 31.6 Gb/s lanes: 4 tech: SSD serial:
fw-rev: 111110WD temp: 41.9 C scheme: MBR
ID-3: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB
speed: 6.0 Gb/s tech: SSD serial: fw-rev: T1.3 scheme: GPT
Message: No optical or floppy data found.
Sensors:
System Temperatures: cpu: 38.2 C mobo: 30.0 C gpu: nvidia temp: 29 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 53%

lsblk

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /var/lib/snapd/snap/bare/5
/var/lib/snapd/snap/bare/5
loop1 squashfs 4.0 0 100% /var/lib/snapd/snap/core18/2846
/var/lib/snapd/snap/core18/2846
loop2 squashfs 4.0 0 100% /var/lib/snapd/snap/core18/2855
/var/lib/snapd/snap/core18/2855
loop3 squashfs 4.0 0 100% /var/lib/snapd/snap/core20/2434
/var/lib/snapd/snap/core20/2434
loop4 squashfs 4.0 0 100% /var/lib/snapd/snap/core20/2379
/var/lib/snapd/snap/core20/2379
loop5 squashfs 4.0 0 100% /var/lib/snapd/snap/core22/1963
/var/lib/snapd/snap/core22/1963
loop6 squashfs 4.0 0 100% /var/lib/snapd/snap/core24/888
/var/lib/snapd/snap/core24/888
loop7 squashfs 4.0 0 100% /var/lib/snapd/snap/core22/1981
/var/lib/snapd/snap/core22/1981
loop8 squashfs 4.0 0 100% /var/lib/snapd/snap/core24/988
/var/lib/snapd/snap/core24/988
loop9 squashfs 4.0 0 100% /var/lib/snapd/snap/discord/239
/var/lib/snapd/snap/discord/239
loop10 squashfs 4.0 0 100% /var/lib/snapd/snap/discord/240
/var/lib/snapd/snap/discord/240
loop11 squashfs 4.0 0 100% /var/lib/snapd/snap/foobar2000/505
/var/lib/snapd/snap/foobar2000/505
loop12 squashfs 4.0 0 100% /var/lib/snapd/snap/foobar2000/506
/var/lib/snapd/snap/foobar2000/506
loop13 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-3-28-1804/194
/var/lib/snapd/snap/gnome-3-28-1804/194
loop14 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198
/var/lib/snapd/snap/gnome-3-28-1804/198
loop15 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-3-38-2004/140
/var/lib/snapd/snap/gnome-3-38-2004/140
loop16 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-3-38-2004/143
/var/lib/snapd/snap/gnome-3-38-2004/143
loop17 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-42-2204/176
/var/lib/snapd/snap/gnome-42-2204/176
loop18 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-42-2204/202
/var/lib/snapd/snap/gnome-42-2204/202
loop19 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-46-2404/90
/var/lib/snapd/snap/gnome-46-2404/90
loop20 squashfs 4.0 0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/var/lib/snapd/snap/gtk-common-themes/1535
loop21 squashfs 4.0 0 100% /var/lib/snapd/snap/gnome-46-2404/77
/var/lib/snapd/snap/gnome-46-2404/77
loop22 squashfs 4.0 0 100% /var/lib/snapd/snap/mesa-2404/143
/var/lib/snapd/snap/mesa-2404/143
loop23 squashfs 4.0 0 100% /var/lib/snapd/snap/mesa-2404/495
/var/lib/snapd/snap/mesa-2404/495
loop24 squashfs 4.0 0 100% /var/lib/snapd/snap/snapd/23771
/var/lib/snapd/snap/snapd/23771
loop25 squashfs 4.0 0 100% /var/lib/snapd/snap/snapd/24505
/var/lib/snapd/snap/snapd/24505
loop26 squashfs 4.0 0 100% /var/lib/snapd/snap/spotify/86
/var/lib/snapd/snap/spotify/86
loop27 squashfs 4.0 0 100% /var/lib/snapd/snap/spotify/87
/var/lib/snapd/snap/spotify/87
loop28 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-7-devel-core20/24
/var/lib/snapd/snap/wine-platform-7-devel-core20/24
loop29 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-9-devel-core22/33
/var/lib/snapd/snap/wine-platform-9-devel-core22/33
loop30 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-runtime-core20/148
/var/lib/snapd/snap/wine-platform-runtime-core20/148
loop31 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-runtime-core20/149
/var/lib/snapd/snap/wine-platform-runtime-core20/149
loop32 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-runtime-core22/100
/var/lib/snapd/snap/wine-platform-runtime-core22/100
loop33 squashfs 4.0 0 100% /var/lib/snapd/snap/wine-platform-runtime-core22/99
/var/lib/snapd/snap/wine-platform-runtime-core22/99
sda
├─sda1 vfat FAT32 16A1-64F0
├─sda2
├─sda3 ntfs 9442A30942A2EF64
└─sda4 ntfs B834743C34740024
nvme1n1
├─nvme1n1p1 ext4 1.0 06f74ddf-3856-4967-921d-674b0979b038 172G 75% /var/lib/snapd/snap
│ /
└─nvme1n1p2 swap 1 swap 528736e4-482b-4455-8d49-3512100062bd [SWAP]
nvme0n1
└─nvme0n1p1 ext4 1.0 548e1b6e-c5da-4c87-9903-e25450448e11 267G 80% /home/susie/WD2T

Have been looking at your BIOS with version 36d, on the Gigabyte site I couldn’t find a 36d bios version, so maybe it was a Beta? Anyway the BIOS is somewhat outdated, a update might or might not solve your problem, and I guess if there is a serious problem with the motherboard, the update might fail, but at least you know where you are at.

I’ve been sick for the last couple days but finally managed to to get the time to update the BIOS. But it still just unmounts my drive as soon as i update a steam game stored on the secondary drive.

Managed to find someone on the manjaro forums who seems to have had a similar problem but no solution seems to have been found.

edit: If it’s faulty hardware destroying my drives, what hardware would be the cause/need to be changed.

If I understand right your inxi-output, you’re driving all your nvme’s as SSD (-serial), not native nvme (don’t just remember the correct name)?
Did you check in your MoBo-manual, if there is some shared port (nvme/SATA) like in mine MoBo?
And do you some over-/undervolting or overclocking?
Furthermore in the c’t magazine they wrote, sometimes the nvme’s get too hot in some MoBo’s because the fan(s) are too poor?
Some idea’s only…

Not touched overclocking (except enabling XMP)
The sata drive you see is not connected by default because its a windows boot disk for playing Fortnite with my younger cousins.