Comment 2 for bug 165316

The first time it happened, I had used gparted to move the swap partition forward, but I still don't know what might have caused it the second time. Yes, I was awake and paying some attention, but something strange happened. I don't even know enough about UUIDs to imagine what causes them to change, but my suggestion was that it should be a simple sanity check when fstab includes an incorrect reference to a partition that does not exist.

The blkid command seems to be the correct solution, but I did not know about it and still have no idea how to find it. What I did at the time was stuff like "man -k partition", which led to some information about various other kinds of stuff. I was pretty quickly able to figure out which partition I was supposed to be dealing with, but it still took a long time to find a name that worked in the fstab file.

I don't know why--but my larger point is that most people don't want to know why. They don't even want to know how to fix a broken fstab file. They just want it to work.