Hi, first post here but long time EndevourOS user.
I have in the past couple weeks started having trouble with my SSD unmounting during gaming sessions. This behavior has grown more frequent as time has passed and is now an almost daily occurrence. My drive only reappears after a restart of my system.
First thing I would do is check the drive out and make sure its still good. Have you run a disk check on it?
also give us some useful information about the system, DE/WM
Post the actual print and not take a picture please.
also that has nothing to do with the file system and if it has errors or not. I guess I should have been more specific you need to check the filesytem.
what file system is it?
both drives are using ext4.
unmount the drive in question and then run this command
e2fsck -c /dev/???
this will check for badblocks as well as filesytem
replace ??? with the actual drive letter that
as always run
man e2fsck to learn more
output for e2fsck -c
[susie@susie-linux ~]$ sudo e2fsck -c /dev/nvme1n1p1
e2fsck 1.47.0 (5-Feb-2023)
Checking for bad blocks (read-only test): done
/dev/nvme1n1p1: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Inode 95947738 extent tree (at level 2) could be narrower. Optimize? yes
Inode 95948729 extent tree (at level 1) could be narrower. Optimize? yes
Inode 95951971 extent tree (at level 2) could be narrower. Optimize? yes
Inode 95951977 extent tree (at level 2) could be narrower. Optimize? yes
Inode 95951978 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96078639 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96082672 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083232 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083234 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083235 extent tree (at level 1) could be narrower. Optimize (‘a’ enables ‘yes’ to all) ? yes to all
Inode 96083237 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083238 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083239 extent tree (at level 2) could be narrower. Optimize? yes
Inode 96083244 extent tree (at level 2) could be narrower. Optimize? yes
Inode 97649665 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043565 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043570 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043574 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043579 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043595 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043599 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043606 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043607 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043620 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043624 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043630 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043631 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043632 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043633 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043634 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043635 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043636 extent tree (at level 2) could be narrower. Optimize? yes
Inode 98043637 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98043638 extent tree (at level 1) could be narrower. Optimize? yes
Inode 98045648 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908000 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908009 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105908010 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908020 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908021 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908025 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908032 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908042 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105908317 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105915377 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105915477 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105915485 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105915528 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105927935 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105927937 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105927953 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105927970 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105927993 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105927995 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105927996 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105928215 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105928956 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105929366 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105929377 extent tree (at level 1) could be narrower. Optimize? yes
Inode 105929378 extent tree (at level 2) could be narrower. Optimize? yes
Inode 105929379 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106045636 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106054324 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106061942 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106061955 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106061962 extent tree (at level 1) could be narrower. Optimize? yes
Inode 106061982 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106061998 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106062016 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106062022 extent tree (at level 2) could be narrower. Optimize? yes
Inode 106062033 extent tree (at level 2) could be narrower. Optimize? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/nvme1n1p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/nvme1n1p1: 275983/122101760 files (4.6% non-contiguous), 414435859/488378368 blocks
[susie@susie-linux ~]$
Took 5hrs so sorry for the late response.
looks like it fixed some things so i would try it and see if it continues to unmount on its own
It just randomly unmounted again so i tried running “smartctl -a” on the drive and got this error
log
[susie@susie-linux ~]$ sudo smartctl -a /dev/nvme1n1p1
[sudo] password for susie:
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.2-arch2-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output error
[susie@susie-linux ~]$
Its possible the nvme is bad. I don’t know a lot about them so not very helpful with further diagnosis. I would take it to a professional if your not familiar with using disk tools. Until that time I would keep it unplugged as to keep data loss to a minimum and look to replace it. Maybe someone else can chime in who has better knowledge of these drives.
Most of my drive is filled with games and I’ve backed up the few important files I had on that drive. I will see if it gets worse than now (random unmount 1-2 times a day) until i get a replacement drive.
1 Like