Here's what happened to me. Some unexplained phenomenon hammered my swap partition, so it lost its UUID. My system simply booted without incident or warning -- but also without any swap!
mount and swapon, run from command line, complained that the UUID was invalid.
One could argue that this is the price of UUID-based fstab mounts; how the heck should the system know that the dangling UUID once pointed to some unused partition on the disk.
Aside from that, I would like to have been yelled at for the fact that my fstab contained an invalid swap mount line, even if it couldn't have given me a ton of help in recovering from the problem.
Further, I could imagine some sort of maintenance tool that would look at the partition table, find a lonely, under-appreciated swap partition, and offer to rehabilitate it.
I'd like to join this issue.
Here's what happened to me. Some unexplained phenomenon hammered my swap partition, so it lost its UUID. My system simply booted without incident or warning -- but also without any swap!
mount and swapon, run from command line, complained that the UUID was invalid.
One could argue that this is the price of UUID-based fstab mounts; how the heck should the system know that the dangling UUID once pointed to some unused partition on the disk.
Aside from that, I would like to have been yelled at for the fact that my fstab contained an invalid swap mount line, even if it couldn't have given me a ton of help in recovering from the problem.
Further, I could imagine some sort of maintenance tool that would look at the partition table, find a lonely, under-appreciated swap partition, and offer to rehabilitate it.