You are not logged in.

#1 2022-05-05 16:52:27

Abzie
Member
Registered: 2016-03-14
Posts: 6

[SOLVED] NVRAM full - DbocBoot

Hello all,

I have been flirting with the idea of moving my Dell box over to Proxmox and for my sins, my NVRAM is now borked.

Where I would usually clear all boot entries with efibootmgr, when restoring back to Arch and setting up the bootloader again, I am now faced with the Failed to create EFI Boot variable entry: No space left on device.

A cursory search yielded no results for DbocBoot, but I did a quick ls on efivars searching for dump-* files, but an alarmingly high number of DbocBoot****--1ba4c901-eb4a-493f-aeef-90a6136da384 files were found:

ls /sys/firmware/efi/efivars/
2151678336-417acee0-6fa9-4a82-99d7-f9b1dd271e48         DbocBoot000E-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot002C-1ba4c901-eb4a-493f-aeef-90a6136da384  DDLOG-052b7547-40f0-4be5-918e-aa1c601c663c
2151678337-417acee0-6fa9-4a82-99d7-f9b1dd271e48         DbocBoot000F-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot002D-1ba4c901-eb4a-493f-aeef-90a6136da384  DefaultIplBootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
334-71db7b7e-4165-48fa-ac9d-f9af4cefc534                DbocBoot0010-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot002E-1ba4c901-eb4a-493f-aeef-90a6136da384  DefaultUefiBootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot0011-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot002F-1ba4c901-eb4a-493f-aeef-90a6136da384  ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot0012-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0030-1ba4c901-eb4a-493f-aeef-90a6136da384  ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot0013-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0031-1ba4c901-eb4a-493f-aeef-90a6136da384  HDDP-fab7e9e1-39dd-4f2b-8408-e20e906cb6de
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot0014-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0032-1ba4c901-eb4a-493f-aeef-90a6136da384  Lang-8be4df61-93ca-11d2-aa0d-00e098032b8c
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot0015-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0033-1ba4c901-eb4a-493f-aeef-90a6136da384  LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8c        DbocBoot0016-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0034-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderDevicePartUUID-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8c  DbocBoot0017-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0035-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c          DbocBoot0018-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0036-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c              DbocBoot0019-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0037-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8c           DbocBoot001A-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0038-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderFirmwareInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c             DbocBoot001B-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0039-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderFirmwareType-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8c          DbocBoot001C-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003A-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderImageIdentifier-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
CurrentPolicy-77fa9abd-0359-4d32-bd60-28f4e78f784b      DbocBoot001D-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003B-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0000-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot001E-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003C-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderRandomSeed-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0001-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot001F-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003D-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderSystemToken-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0002-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0020-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003E-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderTimeExecUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0003-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0021-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot003F-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderTimeInitUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0004-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0022-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0040-1ba4c901-eb4a-493f-aeef-90a6136da384  LoaderTimeMenuUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f
DbocBoot0005-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0023-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0041-1ba4c901-eb4a-493f-aeef-90a6136da384  MemoryOverwriteRequestControl-e20939be-32d4-41be-a150-897f85d49829
DbocBoot0006-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0024-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0042-1ba4c901-eb4a-493f-aeef-90a6136da384  MTC-eb704011-1402-11d3-8e77-00a0c969723b
DbocBoot0007-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0025-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0043-1ba4c901-eb4a-493f-aeef-90a6136da384  PerfDataMemAddr-76b6bdfa-2acd-4462-9e3f-cb58c969d937
DbocBoot0008-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0026-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0044-1ba4c901-eb4a-493f-aeef-90a6136da384  PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8c
DbocBoot0009-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0027-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0045-1ba4c901-eb4a-493f-aeef-90a6136da384  PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8c
DbocBoot000A-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0028-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0046-1ba4c901-eb4a-493f-aeef-90a6136da384  RTC-378d7b65-8da9-4773-b6e4-a47826a833e1
DbocBoot000B-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot0029-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0047-1ba4c901-eb4a-493f-aeef-90a6136da384  Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8c
DbocBoot000C-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot002A-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0048-1ba4c901-eb4a-493f-aeef-90a6136da384  UnlockIDCopy-eaec226f-c9a3-477a-a826-ddc716cdc0e3
DbocBoot000D-1ba4c901-eb4a-493f-aeef-90a6136da384       DbocBoot002B-1ba4c901-eb4a-493f-aeef-90a6136da384  DbocBoot0049-1ba4c901-eb4a-493f-aeef-90a6136da384  USER_SETTINGS_VAR-56f0edc4-25ae-4236-aca3-0bcd410aa2ae

So my questions are:

  • has anyone seen this before,

  • where do these come from, and

  • Are these DbocBoot files safe to delete?

TIA

EDIT - formatting
EDIT2 - not even google has heard of DbocBoot!

https://i.imgur.com/8enEQf6.png

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by Abzie (2022-05-08 15:31:10)

Offline

#2 2022-05-05 19:13:08

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,347

Re: [SOLVED] NVRAM full - DbocBoot

Perhaps you can fix it via UEFI Shell?

Offline

#3 2022-05-05 19:29:44

Abzie
Member
Registered: 2016-03-14
Posts: 6

Re: [SOLVED] NVRAM full - DbocBoot

d_fajardo wrote:

Perhaps you can fix it via UEFI Shell?

I should have added in the OP that I have already reset the BIOS by using the jumper pins, and when that failed, pulled the CMOS battery for a minute or so... These entries still persist.

I ran cat on a few of them and they appear to be EFI entries:
Output of cat on several DbocBoot entries

I don't remember ever running Windows on this server so these must be cached somewhere in iDRAC? I'll have a dig around.

Offline

#4 2022-05-05 21:48:10

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,347

Re: [SOLVED] NVRAM full - DbocBoot

The NVRAM entries could possibly persist even with CMOS reset in which case shell might be the best way to scrutinize, modify or delete the entries.

Offline

#5 2022-05-05 22:20:59

Abzie
Member
Registered: 2016-03-14
Posts: 6

Re: [SOLVED] NVRAM full - DbocBoot

The EFI shell reports the same entries as egibootmgr:

https://i.imgur.com/yKRsX77.png

However, after viewing the entries, efibootmgr entries are now duplicated!

[mrabz@Apollo ~]$ efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0002,0005,0007,0008
Boot0000* Optiarc DVD RW AD-7170S
Boot0001* Linux Boot Manager
Boot0002* Optiarc DVD RW AD-7170S
Boot0003* EFI Network 1
Boot0004* EFI Network 2
Boot0005* EFI Fixed Disk Boot Device 1
Boot0006* EFI Fixed Disk Boot Device 1
Boot0007* EFI Network 1
Boot0008* EFI Network 2

Still unsure what is causing this and whether the DbocBoot files are the culprits...

EDIT - and now we've gone from DbocBoot0049-1ba4c901-eb4a-493f-aeef-90a6136da384 to DbocBoot004A-1ba4c901-eb4a-493f-aeef-90a6136da384 so something is generating these on boot

moderator edit -- replaced oversized image with link.
Pasting pictures and code

Last edited by 2ManyDogs (2022-05-05 23:01:47)

Offline

#6 2022-05-05 23:02:08

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 3,889

Re: [SOLVED] NVRAM full - DbocBoot

Please read the Code of Conduct and post only thumbnails or links to images.


How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

Offline

#7 2022-05-06 06:20:25

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,347

Re: [SOLVED] NVRAM full - DbocBoot

However, after viewing the entries, efibootmgr entries are now duplicated!

But what is the actual output of

bcfg boot dump -v

in the UEFI shell? The output usually gives you more info regarding the boot entries and you can use it to clean up / delete unneeded entries.

Offline

#8 2022-05-06 16:49:07

Abzie
Member
Registered: 2016-03-14
Posts: 6

Re: [SOLVED] NVRAM full - DbocBoot

2ManyDogs wrote:

Please read the Code of Conduct and post only thumbnails or links to images.

Apologies 2ManyDogs, and noted. Thanks for scrubbing the thread to comply with the house rules!

d_fajardo wrote:

But what is the actual output of

bcfg boot dump -v

Output is attached in this image: https://i.imgur.com/R8QEHJu.png These are still showing the expected EFI entries.

Offline

#9 2022-05-07 07:37:05

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,347

Re: [SOLVED] NVRAM full - DbocBoot

Your NVRAM has the curious Fixed Disk Device 1 (Option 02). That device entry looks like a duplicate of the Linux Boot Manager. The curious thing for that entry is it seems to be registering as a USB device according to your bcfg.
Are you dual booting Windows? From your previous post it looks like the Fixed Device is being triggered by Windows bootloader bootmgfw.efi. It is as if that bootloader is trying to fix something everytime and in trying to do the fix it spits out the DbocBoot entries. This is a pure guess and simply what my intuition is telling me.
Can you post your lsblk with UUID's and Part-UUID's? Curious to know if PartUUID-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f shows up.
Also perhaps fsck your EFI.

EDIT: I tried searching for DbocBoot as well with no luck.

Last edited by d_fajardo (2022-05-07 07:58:27)

Offline

#10 2022-05-08 15:29:40

Abzie
Member
Registered: 2016-03-14
Posts: 6

Re: [SOLVED] NVRAM full - DbocBoot

Thanks for the help d_fajardo, I took the plunge and changed the attributes and deleted the Dboc* files from the efivars. It doesn't appear to have made any impact and have rebooted several times since. I'd just chalk this up Dell's 'amazing' UEFI implementation on their older hardware.

I can't remember for sure, but I am fairly certain I still had the archiso USB stick still plugged in which would explain the odd entry?

I'll mark this as solved as deleting the entries has not affected the handover from EFI to systemd-boot.

There is no `4a67b082-0a4c-41cf-b6c7-440b29bb8c4f` in the lsblk output:

lsblk -o NAME,MOUNTPOINTS,UUID,PartUUID
NAME        MOUNTPOINTS          UUID                                 PARTUUID
sda
└─sda1                           a5602fa0-2e95-4abf-adae-c792f72c6832 4dd3564a-fcfb-4588-93e5-521a06ba2e50
sdb
sdc
├─sdc1                           7962133415006295510                  ccabf9f2-9bd2-7941-86de-747507a33ae2
└─sdc9                                                                73a93f3b-12ae-4d43-bef1-553b187c277b
sdd
├─sdd1                           7962133415006295510                  5dd30a6b-848a-684f-bb99-ec4cd9053410
└─sdd9                                                                ffd2598c-f284-5d4f-80e3-539f8829ea66
sde
├─sde1                           7962133415006295510                  56be9010-fefd-a549-a9b5-c23482f5b019
└─sde9                                                                926af324-8b41-8946-b000-e1b5467830f7
sdf
├─sdf1                           7962133415006295510                  35eeee15-7f22-3a4c-894d-1469b44b59c9
└─sdf9                                                                5993cfc9-df1b-5146-a406-57bdcde39c8b
sdg
├─sdg1                           7962133415006295510                  2ada1665-0ed8-8348-b863-b83a6a2353e8
└─sdg9                                                                6b939ab4-c547-8547-ab5b-cfaf087a0623
sdh
├─sdh1                           7962133415006295510                  f50f16bb-e917-0247-a658-1574b61687cf
└─sdh9                                                                f0d3e9c8-d29a-6140-a625-903329116551
sdi
├─sdi1                           7962133415006295510                  5529072f-f8b6-9d4d-8348-e0f48b2fdf2f
└─sdi9                                                                5d49d662-d756-b944-aec6-ab955f49cc1c
sdj
├─sdj1                           7962133415006295510                  ae3bd60b-7eda-5a40-bea8-1295a2c9899d
└─sdj9                                                                f015647e-ff35-2246-adf8-29802c56a642
sdl
└─sdl1      /boot                A078-970E                            0982af13-5c65-4188-aa75-6a9a906a1965
sr0
nvme1n1
├─nvme1n1p1                                                           7f280931-54eb-d643-8c17-801a66c23745
└─nvme1n1p9                                                           19321058-41f5-3441-83c6-c4bb7568a0d7
nvme2n1
└─nvme2n1p1 /home/mrabz          c27a5971-56e0-4060-8ff4-1d0993e2b46c 2e838b28-b2ed-49ca-a6f7-4c19506e1ee8
nvme0n1
├─nvme0n1p1 /                    9fec842f-bb5d-4bfc-bf7f-94c029ed8fad c94a676b-6615-4842-ad45-8fe65ab28e2b
└─nvme0n1p2 [SWAP]               3972cb1d-14e6-498f-985f-2bac0d8a9b24 5832f44c-f115-41b2-9752-79e75a55e7b5

Offline

Board footer

Powered by FluxBB