ermo DJSupertel Please add triple backticks (```) before and after the stuff you're pasting. When you edit things, it will look like this: ``` (the stuff you're editing) ``` When you preview the post, you'll see: (the stuff you're editing) Thanks.
DJSupertel Sorry ermo, Never had problems with my Solus install before so never needed to paste stuff here! Amazingly I booted into my KDE Neon install today and more updates, but after completion did a reboot from Neon into Solus and the damned Swap partition is active again. But if I shut down or reboot from Solus to Solus it fails to load again. Baffled is an understatement.
ermo DJSupertel Sorry ermo, Never had problems with my Solus install before so never needed to paste stuff here! In case it wasn't clear enough, I'm asking you to edit your existing post with the terminal command output and put the output itself in triple backticks like I showed you in the post above? Could you try doing that for me, please? 🙂
ReillyBrogan I really need someone who is experiencing this issue to hop into Matrix today so that I can interactively debug it. I have an idea of what the cause might be but I have some ideas and some test packages that I want someone with the issue to test.
ReillyBrogan If you add x-systemd.mount-timeout=60s,x-systemd.device-timeout=60s to the swap arguments in fstab does it start working reliably again on reboots?
ermo ReillyBrogan If you add x-systemd.mount-timeout=60s,x-systemd.device-timeout=60s to the swap arguments in fstab does it start working reliably again on reboots? So you are saying you want the swap device line in /etc/fstab to look like this: UUID=43c7b7da-a5f3-4e25-b7dd-f5542e0b108a swap swap sw,x-systemd.mount-timeout=60s,x-systemd.device-timeout=60s 0 0 Correct?
ReillyBrogan @DJSupertel Please ignore my previous instructions to edit /etc/fstab. That would work too, but what would be easier for you would be to follow the steps here
DJSupertel OK, many thanks for your help! I will try and get around to that soon! I am a carer for my elderly frail parents and am time severely time limited so please don't think I am ignoring you by taking so long to respond. I get but a few hours a day to do what I need to for myself. FYI, Today the system decided to boot up with Swap back on again.
ReillyBrogan DJSupertel FYI, Today the system decided to boot up with Swap back on again. That's because it's a timeout issue, and how long it takes to mount the swap can be inconsistent. If it completes in less than 5 seconds then great, otherwise the mount job will get killed and you won't have swap. I've adjusted the timeout to a more reasonable 30 seconds which should be sufficient for the vast majority of systems.
