Swap space dissapeared after last update

DJSupertel

terry@terry ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <fs>      <mountpoint> <type> <opts>      <dump/pass>

# /dev/ROOT   /            ext3    noatime        0 1
# /dev/SWAP   none         swap    sw             0 0
# /dev/fd0    /mnt/floppy  auto    noauto         0 0
none        /proc        proc    nosuid,noexec  0 0
none        /dev/shm     tmpfs   defaults       0 0
UUID=43c7b7da-a5f3-4e25-b7dd-f5542e0b108a       swap    swap    sw      0       0
# /dev/sda3 at time of installation
UUID=93194f05-2013-4b1a-9284-dc3185c4d4e1       /       ext4    rw,relatime,errors=remount-ro       0       1
terry@terry ~ $ sudo lsblk -f
[sudo] password for terry:
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                         
├─sda1
│    ext4   1.0         fb17f707-b52f-457d-8aee-4fb9791db74a                
├─sda2
│    swap   1           43c7b7da-a5f3-4e25-b7dd-f5542e0b108a                
└─sda3
     ext4   1.0         93194f05-2013-4b1a-9284-dc3185c4d4e1  222.6G    12% /
sdb                                                                         
sdc                                                                         
sdd                                                                         
sde                                                                         
sdf                                                                         
sr0                                                                         
terry@terry ~ $

Mod Edit: Formatted the post using ``` to wrap the contents so they appear nicely.

DJSupertel

This above is what was returned from instructions.

ermo

DJSupertel This above is what was returned from instructions.

Thank You.

And yes, looking at the output you helpfully provided, there's no obvious issue with your /etc/fstab configuration, as the UUID for the swap partition clearly matches the one shown by sudo lsblk -f.

At least we've ruled out device renames as the cause of the issue you're seeing at this point.

ReillyBrogan

I want to see the output of sudo mount -a, and the output of sudo journalctl -b0 > swap.log (upload it to Pastebin and post the link here.)

DJSupertel

For some reason I am getting no return at all to those commands in the terminal. I thought the terminal was playing up but sudo eopkg upgrade worked. Very strange!

ReillyBrogan

DJSupertel The first command told your system to mount every partition listed in /etc/fstab. If it exited without an error then that means it succeeded. The second command created a file swap.log in the directory where you ran that command. I need that log file if I am to help you debug this issue. Upload it to Pastebin and post the link here.

DJSupertel

I just took an update on my KDE Neon part of the drive and now when I boot in to solus I find my Swap has reactivated! Don't ask me how or wheter this was really involved in its resoration only to say I am baffled but pleased its back

DJSupertel

I will report back if the swap disconnects again but it certainly is a weird problem I have never come across before, especially as when I checked KDE Neon its using a Swap file and not the swap partition. Would it be a good idea to create a swap file for Solus should it lose the swap partition again?????

DJSupertel

Yes! I am not signed up for pastebin. there is a an error because today I booted and the swap was not mounted again. When I tried the commands I executed successfully before such as cat /etc/fstab it works but your other commands return this

terry@terry ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <fs>      <mountpoint> <type> <opts>      <dump/pass>

# /dev/ROOT   /            ext3    noatime        0 1
# /dev/SWAP   none         swap    sw             0 0
# /dev/fd0    /mnt/floppy  auto    noauto         0 0
none        /proc        proc    nosuid,noexec  0 0
none        /dev/shm     tmpfs   defaults       0 0
UUID=43c7b7da-a5f3-4e25-b7dd-f5542e0b108a       swap    swap    sw      0       0
# /dev/sda3 at time of installation
UUID=93194f05-2013-4b1a-9284-dc3185c4d4e1       /       ext4    rw,relatime,errors=remount-ro       0       1
terry@terry ~ $ sudo mount -a
[sudo] password for terry:
terry@terry ~ $ sudo journalctl -b0 >swap.log
terry@terry ~ $

MOD EDIT: Used backticks ``` to make terminal output appear correctly
Please use three backticks before and after terminal or code output in your posts. Thanks.

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

ermo Yes

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.

« Previous Page