Hello World,
Aaahhh crap, help, so I deleted me old swap partition and created a new bigger one and while I modified fstab to put the uuid of this new parition I probably did it wrong cause now it’s stuck on boot, I’m guessing still trying to mount the old partition… So any way I can tell it to boot without mounting that uuid so I can try to fix my mistake?
P.S. Also I still have the Eos install usb stick in case that could help solve my issue…
Boot off the install media, get the correct UUID using sudo blkid then edit fstab and copy and paste it in, save, reboot.
It does have the correct uuid according to that command.
Here’s how things looked before in partition manager(except that giant bloob of unallocated space is now a new ext4 games partition)
and here is the previos fstab(I saved it before doing all this)
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=700B-3CE7 /efi vfat fmask=0137,dmask=0027 0 2
UUID=99f26c27-a79d-45db-9ede-8766aaa00eb6 swap swap defaults 0 0
UUID=c80258e4-cb53-4de2-8915-88fdd0fbede1 / ext4 noatime 0 1
UUID=838c049a-d0f4-4b9f-88f6-6e55e32ee49e /home ext4 noatime 0 2
tmpfs /tmp tmpfs noatime,mode=1777 0 0
LABEL=D /mnt/Local\040Disk\040D ntfs defaults 0 0
LABEL=E /mnt/Local\040Disk\040E ntfs defaults 0 0
UUID=CC64249A642488F2 /mnt/Local\040Disk\040F ntfs defaults 0 0
/dev/nvme0n1p9 /mnt/Games ext4 nofail 0 0
And this is how the partitions look now, as you can see I deleted the small 2gb swap one I had before, took some space from the big games partition and created a new swap.
and here is how my current fstab looks, I basically just took the uuid of the new 20gb swap partition and copied it in the old fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=700B-3CE7 /efi vfat fmask=0137,dmask=0027 0 2
UUID=07c2ae0d-a570-4bb3-a765-e0773f526ac2 swap swap defaults 0 0
UUID=c80258e4-cb53-4de2-8915-88fdd0fbede1 / ext4 noatime 0 1
UUID=838c049a-d0f4-4b9f-88f6-6e55e32ee49e /home ext4 noatime 0 2
tmpfs /tmp tmpfs noatime,mode=1777 0 0
LABEL=D /mnt/Local\040Disk\040D ntfs defaults 0 0
LABEL=E /mnt/Local\040Disk\040E ntfs defaults 0 0
UUID=CC64249A642488F2 /mnt/Local\040Disk\040F ntfs defaults 0 0
/dev/nvme0n1p9 /mnt/Games ext4 nofail 0 0
P.S. I even tried this Stuck on "A start job is running for /dev/disk/by-uuid/..." while booting please help - #30 by pebcak to see if I could at least boot into it instead of being stuck in windows, and it didn’t work, it was still trying to resume it…
Check your kernel cmd line for (don’t remember exact verbiage) something like RESUME_UUID .
If you’re talking about pressing e on the endeavourosboot option and removing the problematic uuid like I said above I tried it and it didn’t work. 
Actually no, I’m talking about editing the configuration that generates that line (grub/dracut/systemd-boot/etc). However, if you directly edited the temporary boot line and that didn’t help that once…then it must be elsewhere (and /etc/fstab is the only other place I can think of).
when you created the swap partition did you flag is as swap?
Yeah, here’s a screenshot of what it looks when you create a new partition in KDE partition manager that I took from a video I found on youtube.
I selected linuxswap, though now that I think about it I don’t think I selected anything at permissions and I don’t think anything was selected by default like in this picture. Could that be the problem?
ok we are not discussing the same thing. that looks like the file system I’m talking about flagging the partition as swap. Not sure about KDE as I don’t use it but in Gparted you can right click the device and choose manage flags and select swap from there. However I’m not sure that is the issue I think I can see the picture a bit better and your still calling the uuid of the old swap.
can you share with us what it does do?
did you shutdown wait a few and then turn back on?
Ok, booted from the usb stick, here’s how it looks in gparted:
Not sure how clear this is, but here is a short video, I press e, delete the resume=uuid in question the one that ends with aaa00eb6, then press enter.
As for shutting down the pc and waiting, yeah I did wait, 2 mins or so maybe…
LE: I know it was probably useless/futile but out of curiosity, just to see what would happen, I tried 2 more things. First I edited the fstab file and removed the entire swap line. Then I replaced it’s contents with the ones from the old fstab file(the one that has that aaa00eb6 uuid).
And it didn’t matter, in either case crazy linux is still trying to resume that uuid. Please please please don’t tell me I have to reinstall linux!!!.. 
It’s always possible to fix it, you just have to find where to fix it. Reinstall may be easier, but you don’t learn anything doing it that way.
when you removed the uuid from the command did you let it continue and time out or did you just reboot? I’m curious if it will now time out after you remove the uuid for it to load. Try and see if after about minute in a half if it times out and puts you into a command line.
Uuum, no, that is exactly what I am trying to say, reinstall would mean(and I am not exagerating) at least 4-5 entire days, probably more to get everything back set up and configured the way I like it.
So I really don’t wanna have to do that until I switch hard sometimes next year…
LE: Ok, I’ll give it 5 full minutes @thefrog brb
And when looking where to fix it, find and grep are your friends (used together especially).
Ok, first the super good news!!!
I went back to do that whole press e, delete resume=uuid so I can give it that 5 minutes.
But this time after deleting the resume=uuid part something(not sure what) made me keep going and check and what the F do you know, if you keep going the resume=uuid thing appears again, hhhhrrrrrrrrr!!!
And if I delete both of them then Eos launches just fine!!! 
And my new swap seems to be in place and working fine, at least this is what the terminal says:
[vikings@VIKINGSKINGDOM ~]$ swapon -s
Filename Type Size Used Priority
/dev/nvme0n1p6 partition 20479996 0 -2
[vikings@VIKINGSKINGDOM ~]$
The bad news however is it seems I have to press e and delete those things at every restart/power off. 
In the grand scheme of things it won’t actually kill me if I have to keep doing that for the next who knows how many months, but is there any way we can make it so I don’t have to do it? 
LE:
Uuum, my bad mate I probably should have mentioned that I am a complete newb with only 4 months or so thus far of linux experience. So unless you are trying to say that simply doing a couple of google searches on find and grep is gonna give me the info needed, then I am gonna need more from you on that. 
after you boot look for this file and edit it out of the file and it will no longer ask for it.
Uuummm, ok just to make sure I don’t mess things up again, I don’t have a grub folder in my /.
So I did a search for systemd-boot and dracut and this is what came up, which of those files exactly are you talking about?
if your using systemd-boot
try in the efi folder
/efi
I don’t have a swap partition I just use a swap file. but it should be in a conf file
remember you have to edit the file with root so make a backup before making changes
Sorry, been having a nap 
So if it is systemd-boot check /etc/kernel/cmdline the UUID needs changing there, if grub it will be in /etc/default/grub I think…???
