3 ms·
Huh. I had that same problem on two machines running Tumbleweed a couple of months ago. In both cases, the only working approach I found was to wipe the root pa
by krylon 9y ago
Huh. I had that same problem on two machines running Tumbleweed a couple of months ago. In both cases, the only working approach I found was to wipe the root partition and install from scratch.
/home was in a separate partition, so it was not a tragedy, but annoying nevertheless. This has never happened to me before, unless the underlying hardware was about to retire.
- Mister_Snuggles 9y agoI wasn't so lucky since I had everything as one big BTRFS filesystem. I did recover it by booting the installer in recovery mode, mounting the fs read-only, and doing a backup. Then I blew away the partition table and reinstalled. I also learned a lesson about backups, mainly that I should have them.
- pnutjam 9y agoTumbleweed is a rolling edge release. I get wonky desktops and other problems all the time when I update.
- krylon 9y agoThat is true. But I have used Gentoo, another rolling release distro, before that (way before that, actually), and I never had such a problem with Gentoo, even on the unstable branch. From what I hear Arch users tell about their distro of choice, Arch does not give them this kind of headache, either. And last but not least, the reason I took the plunge and went for Tumbleweed was that the project uses extensive automatic testing to ensure they do not break anything. Do not get me wrong, I still use Tumbleweed on both machines and do not see that changing for the foreseeable future. I know what I signed up for. ;-)