Hardware/Dell: Difference between revisions
Add efivars full |
m Add category hardware |
||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
Encountered this issue on A Dell server | Encountered this issue on A Dell server | ||
<code>Failed to create EFI Boot variable entry: No space left on device.</code> during bootloader install | |||
Googling | Googling <code>DbocBoot</code> only shows one result <nowiki>https://bbs.archlinux.org/viewtopic.php?id=276175</nowiki> | ||
Running | Running <code>strings</code> on the <code>DbocBoot</code> entries show that they contain strings like <code>Windows Boot Manager</code> and <code>Ubuntu</code> and other old efi boot entries | ||
<code>bcfg boot dump -v</code> in EFI shell does not show these variables, only <code>Boot*</code> variables | |||
====== The fix is to remove | ====== The fix is to remove the <code>DbocBoot</code> entries ====== | ||
Normally the files are protected therefore it is necessary to remove the protection | Normally the files are protected therefore it is necessary to remove the protection | ||
<code>chattr -i /sys/firmware/efi/efivars/DbocBoot*</code> | |||
Then they can be removed | Then they can be removed | ||
<code>rm -vi /sys/firmware/efi/efivars/DbocBoot*</code> | |||
During the next boot there may be a warning | During the next boot there may be a warning | ||
<code>Warning: Corrupted BootOrder variable detected... Repaired</code> and the boot will continue as normal. | |||
[[Category:Hardware]] |