One problem swapped for another ...

[Dan]

... is pretty much the norm around this little corner of Dan's realm.

Here's the most recent example. Ever since I phat-phingered this little adventure into my life, I've been getting this error/failure in the startup/dmesg.

[   27.792117] swapon[879]: swapon: /dev/sda2: swapon failed: Invalid argument
[   27.792526] systemd[1]: dev-sda2.swap swap process exited, code=exited status=255
[   27.801215] systemd[1]: Unit dev-sda2.swap entered failed state.

That partition (along with the rest of them) has been recovered, (or so I thought) but the error persists.

Howz come? <....>

[RHamel]

What does free show?


It's possible that you might have to run the mkswap command on the space.

[Dan]

As below ...

[dan@****** Desktop]$ free
total used free shared buffers cached
Mem: 8178148 1924332 6253816 0 79080 736416
-/+ buffers/cache: 1108836 7069312
Swap: 6691036 0 6691036
[dan@****** Desktop]$

Here's the beast in question (wait a few seconds and it will cycle through all three partitions.)

[RHamel]

What happens if you?

swapon /dev/sda2

[smr54]

What about fstab? What I've often seen, though in Ubuntu, is that for some reason or another a UUID will get changed and suddenly swap isn't working. If that doesn't seem a factor, I might try deleting the partition and recreating, then run partprobe, as Fedora's UUID hasn't seemed especially robust to me either--from time to time, after either an update or installing something else, the UUID won't match and it won't boot.

[Dan]

swapon: /dev/sda2: open failed: Permission denied

<....>

Let me try that again as root. <....>

EDIT: Well ... that wasn't a whole lot better results.

swapon: /dev/sda2: swapon failed: Invalid argument

[RHamel]

How about

swapon -s

[Dan]

Dunno. After Scott reminded me, <....> the lights came on, I checked /etc/fstab, and found this ...

#
# /etc/fstab
# Created by anaconda on Sun Jul 31 15:48:34 2011
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=9cc93dd7-dc60-4a7a-a2c9-f208b4a9cb91 / ext4 defaults 1 1
UUID=adf93159-34c1-4f32-b8b1-a71e56283e49 /boot ext2 defaults 1 2
# /dev/sda2 swap swap defaults 0 0
UUID=cced7f5e-34ac-40e1-b361-13d8a45165fc swap swap defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0

I remarked out the line and the problem went away. I really didn't want that drive getting a whole lot of traffic anyway.

[RHamel]

Well good, I'm glad we didn't shoot the other foot off.