Error encountered while trying to access "swap /swapfile" following changes in "/etc/fstab" for NTFS Steam games.

M

mineblork
Member

208

09-02-2016, 07:56 PM

#1

I believe I followed all the instructions given, using my basic Linux knowledge. When I ran "sudo reboot" to implement the changes, the swapfile issue started. Luckily, I had a live CD and managed to back up a clean copy of "fstab" after making edits. This gave me a fresh version for the UUIDs of my NTFS drives—though I might have forgotten to mount them as "ntfs-3g" volumes. I didn’t try the troubleshooting fix since I no longer use Windows 10. I kept updating "fstab" repeatedly, adjusting entries in hopes of resolving the swapfile loading problem, but it didn’t work. I began looking for alternative solutions, even reconfiguring the swapfile via the recovery root command line. Still nothing. Eventually, I decided to boot from a new Linux installation on my SSD, planning to save whatever I could if fixing the issue proves impossible. I’d rather keep my current broken setup than start fresh. (That said, if it helps move snap packages between Linux distributions of the same distro, that would be a decent compromise.)

M

Manic_Kobold
Junior Member

29

09-05-2016, 11:26 AM

#2

The issue you encounter during startup after GRUB appears as an error message.

W

Wiicarbon
Member

234

09-05-2016, 01:00 PM

#3

Hello, I noticed two issues: one error says "Initramfs unpacking failed," which shouldn't stop you now, and another states "Failed to activate swap /swapfile." Could you share your /etc/fstab file?

M

Mordigal
Junior Member

8

09-05-2016, 02:59 PM

#4

The initial fstab file was the one I removed the adjustments from "fstab" to include the UUIDs for the two NTFS partitions where my Steam library was transferred from Windows 10 following the migration. fstab fstab

E

EPIC_GT
Member

219

09-10-2016, 05:17 AM

#5

You're asking why the swap file should be mounted after the swap device, not before. Also, you're confused about its location and visibility in the system settings.

L

Llyodsk
Member

164

09-10-2016, 06:29 AM

#6

I’m not sure how the mount priority order was altered. I only added the two UUIDs at the end and didn’t make any other changes. The top entry should match what my fstab looks like. I’m wondering if this update will actually solve my issue, especially since the SSD Linux installation comparison shows almost no visible difference. I plan to save the change using the recovery root command line and then restart the system to check the outcome.

C

ChubbsPlaysYT
Member

51

09-26-2016, 10:53 PM

#7

basic fstab example: # /etc/fstab: storage details. # Use blkid for unique IDs; this helps when disks change. See fstab(5). # <device> <mountpoint> <type> <options> <dump> <pass> # / was mounted on /dev/sde1 during setup UUID=1612f07a-04c3-4015-88f0-7aa10eed4e2b / ext4 errors=remount-ro 0 1 # swap was active on /dev/sde5 during setup UUID=8f45bef7-0848-43b6-8c3b-a444cf35606b none swap sw 0 0 You need an entry pointing to /, but that's missing in your file. If / doesn't exist, the system won't locate /swapfile. There should be a line right after the installation comment. Run ls -lha /dev/disk/by-uuid and verify the UUID for /dev/nvme0n1p1 Then insert: UUID=<found_uuid> / ext4 errors=remount-ro 0 1 Into your /etc/fstab follow the advice above

C

creepergirl678
Junior Member

18

09-27-2016, 12:07 AM

#8

You can use the same UUID line directly in your fstab file. It’s better to manually specify the correct partition instead of relying on defaults, which could cause more issues.

G

Gid2000
Member

52

09-27-2016, 12:26 AM

#9

Copy the existing fstab entry and ensure the UUID matches exactly.

E

EliteChicagoan
Member

228

09-28-2016, 11:39 PM

#10

Sure, you can paste lines 13 and 14 directly. Just let me know if you need any adjustments or further help.