If your hard drive is fine and your fsck comes out clean, then I'm not entirely sure what is the likeliest cause. There's no use switching to windows either it'd just give you a BSOD. If even a single test fails, your drive is failing and you should back up your data and try to find a replacement. This should tell you if your hard drive is failing or not. Test will complete after Tue Jan 14 13:54:05 2020Īnd after the mentioned time you run smartctl -l selftest /dev/sdaĪnd see what can be gleaned from the results. Please wait 2 minutes for test to complete. Sending command: "Execute SMART Short self-test routine immediately in off-line mode".ĭrive command "Execute SMART Short self-test routine immediately in off-line mode" successful. The output will tell you to wait until a specific time to check and see the results, it will look like this: = START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION = If support is available and enabled, then run a smart test. If support is available but not enabled, enable it. In your specific question that would be /dev/sda) to find out if the hard drive supports SMART (the bottom line of this output). (where sda is the hard drive you want to test. To do this you need to install smartmontools, alternatively you can use a graphical front-end for smart tests like GSmartControl but below is a guide for how to use smartmontools to test. Uninstall / Remove x4d-icons package Please follow the guidelines below to uninstall x4d-icons package: sudo apt remove x4d-icons Copy sudo apt autoclean & sudo apt autoremove Copy 3. To check if your hard drive is failing I suggest you run S.M.A.R.T tests. Install x4d-icons package Learn how to install x4d-icons package: sudo apt update Copy sudo apt install x4d-icons Copy 2. Chief among them would be that your hard drive is failing (especially if this happened between formats). If it really is a corrupted filesystem then there are many possible causes for it. This should show you when your filesystem got mounted as read-only and hopefully the exact reason why. Preferably after you encounter the issue. Try this: dmesg | grep -B 5 -A 5 filesystem The output you're seeing on the terminal screen can be accessed with the dmesg command (may require sudo). Like NoMad suggested, try running (as root) fsck.ext4 -f -n /dev/sda5 to see what the level of file system corruption is on your partition (note: just because there's corruption doesn't mean everything breaks, I got 7 unfixed errors and 2 unoptimized warnings, with a warning that the filesystem still has errors, but everything still works fine.) A possible but unlikely reason for this problem is that you have somehow disabled this automatic file system checking. Most linux distributions run a file system check (fsck) command on boot to check for and repair filesystem and partition errors. When Linux detects a partition is corrupted it is automatically re-mounted as read-only which is most likely what's happening here. Your hard drive partition is most likely corrupted.
0 Comments
Leave a Reply. |