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

[Robert Moskowitz]

On 01/07/2014 05:49 PM, Michal Jaegermann wrote:
> On Tue, Jan 07, 2014 at 02:49:13PM -0500, Robert Moskowitz wrote:
>> 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
> ....
>
> Are you sure that swap is not already in use?  What 'swapon -s' has to
> say?

]# swapon -s
Filename                Type        Size    Used    Priority
/dev/sda4                                  partition    8191996 54332    -1

>
>> UUID=46dd3a72-50e9-4f43-b024-2e3dc6d35129 swap swap    defaults        0 0
>>
>> So what to do?  Just # out that swap entry?
> Is this a correct UUID? 'blikid' confirms that?

# blikid
bash: blikid: command not found...


> If swap indeed is not turned on then I would think that trying to remake
> swap with 'mkswap' would be a good idea.  UUID will likely change so
> you would have to edit your fstab afterwards (or you may use a label a
> mount through that).  In any case try to switch your swap "on" manually
> before attempting doing that automatically on boot.

Unfortunately, I will need a more precise set of instructions to carry 
this out.

> Maybe your disk is indeed going bad and that is why you see "read failed
> after 0 of 4096 at 4096"?

Brand new Crucial M500 240GB SSD drive.