All of a sudden, my tumbleweed + KDE system stops responding. It happened several times before and came back to normal after hard reboot. But this time it is different. I need some advices on how to recover it.
I have not upgraded this system for about ten days but it works well until just now. I suspended it to RAM yesterday night before going to sleep and did not use it for a day. I resumed it about one hour ago and it worked as normal. After a while, the system stopped responding while I was copying a file to USB stick. I hard rebooted it and it successfully entered the desktop. When I tried to check system log for the problem, it halted again for about one minute and rebooted itself. But this time it cannot successfully boot into desktop. I find out that the root partition was reported as read only. It is a btrfs partition on a nvme ssd.
I tried to reboot the laptop by hard pressing on the power button and it booted into emergency mode saying btrfs error on device nvme0n1p6 (my root) and cannot mount /sysroot .
Please advice on how to recover it. Should I reinstall it instead of rescue?
Sorry for the error in the post and no further details. I found it is very challenging to post on mobile phone. I will check back after about 23 hours because of being fully occupied tomorrow.
What you have described are symptoms of hardware failure. Does a live media or external HD boot behave any better? From a live Linux media boot you should try running smartctl. This includes selecting “Rescue System” from TW installation media. Have you looked on the support site of your nvme device maker for instructions how to test the condition of the device?
Thank you for your reply. Sorry that I could not provide more detail at the moment. I had not prepared a rescue media. Maybe I’ll try to rescue it before I reinstall after making an installation media.
Does anybody know a way to rescue from emergency mode?
As of this morning’s update I cannot boot into my Tumbleweed install. I get numerous failures in systemd and the root partition (which is XFS) is mounted as read-only. This happened immediately after an update and reboot and the SSD is brand new so I don’t believe there is a hardware failure going on. My situtation sounds fairly similar to what else has been reported here.
But the quoted problem is not solved. So I just re-installed the system. The installer cannot recognise the aforementioned partition either so I just formatted this specific partition. After installation, the system works as expected.
Sorry to hear that but we might have different problems.
For general info since you reinstalled as a solution. The error indicates file system corruption. Sometimes running fsck can fix these things some times not depend on how bad the corruption is ad the FS in question…
I had the same problem. After re-formatting, the drive now works again for months, so it does not look like a HW problem. After some research here, I thought that it might be related to BTRFS snapshots on drives with little capacity left. But as I needed the disk, I could not research further, reformatted it and disabled snapshots. No problems since then.