swap partition problems - Re: [Bug 1006304] BootLoaderError: failed to set new efi boot target

Robert Moskowitz rgm at htt-consult.com
Tue Jan 7 19:49:13 UTC 2014


On 01/06/2014 06:22 PM, Chris Murphy wrote:
> On Jan 6, 2014, at 4:08 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>
>> On 01/06/2014 05:57 PM, Chris Murphy wrote:
>>> On Jan 6, 2014, at 2:40 PM, Robert Moskowitz <rgm at htt-consult.com> wrote:
>>>> On reboot, it took some time with all sorts of messages.  Failed on my swap (though once running 'free' shows the swap space).  selinux having to do its thing and taking some time.
>>> OK at this point you're running into the GPT-swap commonbugs so you might go read all of that to see what applies to your situation. You can ignored the swap thing or you can # it out in fstab, systemd still activates it based on partitiontypeGUID.
>> Argh.  Well your last sentence explains why it works once running. Will eventually look into this.

  journalctl |grep fail|grep -i swap|more

shows

Jan 07 08:48:29 lx120e.htt-consult.com systemd[1]: Unit 
dev-disk-by\x2duuid-46dd3a72\x2d50e9\x2d4f43\x2db024\x2d2e3dc6d35129.swap entered 
failed state.
Jan 07 08:49:00 lx120e.htt-consult.com swapon[320]: swapon: /dev/sda4: 
swapon failed: Device or resource busy
Jan 07 08:49:00 lx120e.htt-consult.com systemd[1]: Unit dev-sda4.swap 
entered failed state.
Jan 07 09:22:58 lx120e.htt-consult.com systemd[1]: Unit dev-sda4.swap 
entered failed state.
Jan 07 09:23:37 lx120e.htt-consult.com swapon[333]: swapon: 
/dev/disk/by-uuid/46dd3a72-50e9-4f43-b024-2e3dc6d35129: swapon failed: 
Device or resource busy
Jan 07 09:23:37 lx120e.htt-consult.com systemd[1]: Dependency failed for 
Swap.
Jan 07 09:23:37 lx120e.htt-consult.com systemd[1]: Unit 
dev-disk-by\x2duuid-46dd3a72\x2d50e9\x2d4f43\x2db024\x2d2e3dc6d35129.swap entered 
failed state.
Jan 07 12:07:13 lx120e.htt-consult.com systemd[1]: Unit 
dev-disk-by\x2duuid-46dd3a72\x2d50e9\x2d4f43\x2db024\x2d2e3dc6d35129.swap entered 
failed state.
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]: /dev/fedora_19/swap: 
read failed after 0 of 4096 at 8388542464: Input/output error
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]: /dev/fedora_19/swap: 
read failed after 0 of 4096 at 8388599808: Input/output error
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]: /dev/fedora_19/swap: 
read failed after 0 of 4096 at 0: Input/output error
Jan 07 12:07:13 lx120e.htt-consult.com lvm[12503]: /dev/fedora_19/swap: 
read failed after 0 of 4096 at 4096: Input/output error
Jan 07 12:07:38 lx120e.htt-consult.com swapon[328]: swapon: /dev/sda4: 
swapon failed: Device or resource busy
Jan 07 12:07:38 lx120e.htt-consult.com systemd[1]: Unit dev-sda4.swap 
entered failed state.

cat /etc/fstab:

#
# /etc/fstab
# Created by anaconda on Mon Jan  6 14:56:01 2014
#
# 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=68aaf337-b29f-42ea-9053-cad852d6afaf / ext4    defaults        1 1
UUID=11c8b5bc-629f-4ca0-88e4-48d029db39af /boot ext4    defaults        1 2
UUID=3FFA-C023          /boot/efi               vfat 
umask=0077,shortname=winnt 0 0
UUID=e0915d05-7641-4de7-a970-fa3e33baa7f9 /home ext4    defaults        1 2
UUID=46dd3a72-50e9-4f43-b024-2e3dc6d35129 swap swap    defaults        0 0

So what to do?  Just # out that swap entry?




More information about the test mailing list