On Wed, Oct 29, 2014 at 09:19:26PM -0300, Ibirisol wrote:
>Hi there,
>
>I have the same problem here. I'm using rEFInd to boot.
Sorry, but I think you're seeing a slightly different bug here.
># efibootmgr -c -l "\\EFI\\debian\\grubx64.efi" -L "Debian" -v
>Alternate GPT is invalid, using primary GPT.
>Alternate GPT is invalid, using primary GPT.
>
>Could not prepare boot variable: No such file or directory
>---
>
>In attachment follow the strace output for the above command.
Going right to the end of the log you've posted:
...
>access("/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/data",
> F_OK) = -1 ENOENT (No such file or directory)
>open("/sys/firmware/efi/vars/new_var", O_WRONLY) = 3
>write(3,
>"B\0o\0o\0t\0000\0000\0000\0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) =
>-1 ENOSPC (No space left on device)
>umask(0) = 022
...
That ENOSPC error is the cause of your problem - your firmware has
filled up the EFI variable space, so the system cannot add new EFI
variables. I suggest you look for documentation on ow to fix that -
it'll depend on the type of computer you have.
--
Steve McIntyre, Cambridge, UK. st...@einval.com
< liw> everything I know about UK hotels I learned from "Fawlty Towers"
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
