You are not logged in.
Pages: 1
I just booted and noticed swap failed on bootup.
Opened a console, changed to root and tried:
[root@myhost ~]# swapon -a
swapon: /dev/hda2: Invalid argument
[root@myhost ~]#
dmesg tells me:
Unable to find swap-space signature
I've never had anything like this in my time with linux.
Absolutely nothing has changed since last boot, and it was cleanly shut down.
Any ideas?
Offline
After a bit of googling, I've re-prepared it with mkswap, but I'm curious as to why it suddenly wasn't recognised.
Any reason(s) this might happen that anybody knows about?
Thanks
Daren
Offline
Harddrive failure ?
Do you have smart on in the bios ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I'd have to check that.
There doesn't appear to be other issues with any other partitions though. I'll do a manual fsck to see if that shows anything up.
Offline
Well, it happens a lot if you experiment with software suspend etc.
Another unqualified guess is that the swap partition could have been uncleanly "unmounted".
Offline
Ah!
I did try the 'lock & suspend' on the KDE applet (it's a laptop). It did come back (seemingly) ok though :?
When I had Ubuntu on this (Gnome) the suspend worked perfectly.
Offline
Pages: 1