It’s the same Gateway GWTN-141-10 as before. There was a short update that didn’t require password, so I installed it and then got this error again.
I didn’t reinstall the os, as it seemed to work well for the last three days, and just after the topic was closed, started a couple hours later. Same error. I tried changing the secure boot mode setup and that didn’t do anything. I first noticed a problem in the time section in BIOS. which was off about 12 hours. So, I corrected it and the same error showed up.
Hi
The warning “Volume Full” indicates there no room to store the file the boot is trying to create.
So, how big is the boot partition and how full is it?
You will need a USB with a Linux version on it to be able to determine this I think.
If it is 100% full, I would re-partition you drive so the the Boot partition is 20MB bigger and then reinstall your operating system.
If it is 100% full, how much space is left? If it is very small it may not be big enough for the files that Grub is trying to create so again make the boot partition bigger and reinstall.
You likely need to delete unused efi boot entries as discussed at the link below because your nvram is full on the system board. Several methods explained.
Uefi settings > Security (probably) > Reset To Setup Mode
Disable Secure Boot
Disable TPM (and/or other similar trust options)
Boot the PC
Can’t find any TPM to disable
===============
Blockquote rubi1200
Boot from a live USB and then run the following command and post the output back here:
sudo efibootmgr -v
When posting back, please highlight the output and wrap with code tags (can use either </> in the composer or Ctrl+E on the keyboard).
=============== So, you want me to go into BIOS and select the USB option in the Boot section under boot order?, which would be ? USB Key or Floppy? Then insert the USB and restart? Right? ==============
Blockquote yancek
You likely need to delete unused efi boot entries as discussed at the link below because your nvram is full on the system board. Several methods explained.
=============
Blockquote
prcowley
The warning “Volume Full” indicates there no room to store the file the boot is trying to create.
So, how big is the boot partition and how full is it?
You will need a USB with a Linux version on it to be able to determine this I think.
If it is 100% full, I would re-partition you drive so the the Boot partition is 20MB bigger and then reinstall your operating system.
If it is 100% full, how much space is left? If it is very small it may not be big enough for the files that Grub is trying to create so again make the boot partition bigger and reinstall.
===============
Can I do that thru the BIOS menu? Because I can’t load past this error statement to check anything else? Doesn’t Grub auto delete unused files to fill up this space?
Uefi settings > Security (probably) > Reset To Setup Mode
Disable Secure Boot
Disable TPM (and/or other similar trust options)
Boot the PC
Ok, that worked, but will it stay working 3 days from now? I think I did similar last time and 3 days later it error stated that Volume Full again. So, how to make sure this doesn’t repeat? I’m reading up on yancek’s "need to delete unused efi boot entries. PRCrowley and one of the guys last time mentioned this size of partition issue. Will that keep this ‘Volume’ near empty all the time to prevent a requrrence of this problem? Aren’t those files in BIOS? Or, since this is a Gateway GWTN141-10, maybe all files are stored on the HD?
No or Yes, I can’t get past those error message… at the time, but using tea-for-one’ suggestion, I can boot back up no problem. My concern now is that this is what happened last time and 3 days later, the same thing happened with the same error messages about ‘Volume Full’. So, I need to edit the old efi boot entries, no? I’m looking at yancek’s response on that issue, currently trying this one: How to Remove Old EFI Boot Entries in Linux – DigitalRobin.net
So, I installed EFI BootMgr which shows up as ‘Windows Recover’
So, following that example from “How to Remove EFI…”, it seems I can remove all the numbers that aren’t Ubuntu? Keep the BootCurrent (Ubuntu), which is 0003 and remove all the others? Is that right and safe? I see that 0004 is USB Entry for Windows to Go , is that removable as well? It doesn’t affect the Boot Order in BIOS, right? It would’ve been from the install from the USB stick with Ubuntu startup on it.
TPM 2.0 (or FTPM, PTT etc where the letter T indicates Trust) has been part of UEFI firmware for more than 10 years and it must be present on your PC.
It may not be under Security in your UEFI settings, but it’s there somewhere.
Volume Full should not repeat if you disable TPM and Secure Boot.
You may have to disable these as well.
They may be sub menu items of Security Device Support and be automatically disabled when the top menu item is de-activated.
Now that you have located these settings, it’s a matter of experimentation to establish which setting to enable/disable.
Have you compared these UEFI settings with your other similar PC?
The black one is the one with the problems, but I see that the silver one is showing the same screen in BIOS. ‘Security Device Support’ is enabled in both. The only difference I see is under ‘Security’ under HDD Security Configuration; on the black one that previously had it in ‘secure boot mode’, that P0: Team TM8PS75126, which is for password changes (user and master). It seems ‘secure boot mode’ added that as well as ‘Windows Recover’. I think that was added recently trying to fix this.
No difference between the silver/black models under that Advanced/Trusted Sources/ section with TPM 2.0 Device Found. Both models had the same data. So, should I leave the ‘Security Device Support’ in the ‘Enabled’ position instead of disabling it?
One thing that is different is in BIOS, the clock both is always 8 hours ahead, no matter how many times I change it, but corrects after BIOS as Ubuntu starts. I think having both on at the same time is doing it? I think the ‘mirroring’ affect… whatever it’s called, to keep them aligned is doing this? I noticed that changes in the favorites is mirrored on the other as well.
There is a small error upon startup after BIOS on the black one.
“EFI: Failed to measure data for event ----------” (a number sequence) which lasts a second and goes away as Ubuntu comes up.
Checked again and separated the two models under some pillows… same… time is off with both of them, no matter how many times I correct it in BIOS, then as Ubuntu kicks up, it shows the correct time.
I see that Windows Recover is in both… not just the black one. Guess that’s why I stated they were the same. Oops? The only real difference seems to be that P0: Team… under HDD Security Configurations in Security section of BIOS menu… and that seems to only deal with user/master passwords.
I’m going to check the black one again for that inital EFI: Failed to measure… error statement on startup from BIOS to Ubuntu… I think it was… I’ll recheck now.
=====
Ok, on the black one… same thing… time is always off by 8 hrs. Same little error message after BIOS but before Ubuntu starts up [ EFI: Failed to measure data for 1 event: 0x00000 etc…]
So, again, other than that added user/master password change in Security section under HDD Configuration… the P0: Team… no difference… [I think the two were sincing because the phone was on… I forgot, that’s how they are setup]
So, to keep the units the same now with ‘Secure Boot’ in disabled mode, should I leave ‘Security Device Support’ as is? That being ‘enabled’ on both units?
Yes, booting fine, just that clock issue… 8 hrs off in BIOS, but fine in Ubuntu. That little "EFI: failed to measure… " happens but it’s only a second or two.
What does the ‘Security Device Support’ actually do?
That sent me to this video link: https://www.youtube.com/watch?v=MN-Q5h2Iv8A
When that guy did a sudo fdisk -l , he got a standard list, but I got 38 loops, and this seems to be the problem about why it’s always ‘Full’, right?
