Hi @servimo,
It might be, or “simply” the filesystem. It’s relaticely easy to confirm or eliminate the disk, though. Then the filesystem is all that remains/ Or it will confirm the disk, ruining your day.
Simply use smartctl
from a chroot live environment to check.
Ignore this.
How to chroot
-
Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.
-
Write/copy/
dd
the ISO to a USB thumb drive. -
When done, boot with the above mentioned USB thumb drive into the live environment.
-
Once booted, open a terminal and enter the following command to enter the
chroot
environment:
manjaro-chroot -a
- If you have more than one Linux installation, select the correct one to use from the list provided.
When done, you should now be in the chroot
environment.
But, be careful, as you’re now in an actual root environment on your computer, so any changes you make will persist after a restart.
Using smartctl
I have no idea whether the smartmontools
package is installed on the live environment, so test this first. run:
smartctl -h
…and if you get an error that means it’s not installed, so install it first:
pacmac install smartmontools
When/if it is there, run the following to identify the disk first:
lsblk
Mine, for example:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
└─sda1 8:1 0 3.6T 0 part
sdb 8:16 0 4.5T 0 disk
└─sdb1 8:17 0 4.5T 0 part /home/mirdarthos/virtualbox
/home/mirdarthos/Video
/home/mirdarthos/Pictures
/home/mirdarthos/Music
/home/mirdarthos/KeePass
/home/mirdarthos/Documents
/mnt/5TB
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 500M 0 part /boot/efi
├─nvme0n1p2 259:2 0 7.8G 0 part [SWAP]
└─nvme0n1p3 259:3 0 224.6G 0 part /
I know my SSD is 250GB, and I have 2 x HDDs in my PC, so my SSD is /dev/nvme0n1
.
Then doing the smartctl
test is as easy as:
sudo smartctl --all <identifiedDisk>
Where <identifiedDisk>
is the disk previously identified.
The problem could ALSO be because of a faulty connector, which is possibly easy the fix if you are using a SATA SSD, and AFAIK impossible if you use NVME. Luckily from the photo it looks like it is SATA.