Welcome to snaps.
But I don’t think it’s to do with your boot problem.
I do not think that you have found the culprit. I have Ubuntu 24.04.3 LTS and It records /dev/loop0 to /dev/loop39. This sort of printout is normal. So what are loop devices?
/dev/loop*are loop devices making plain files accessible as block devices. They have nothing to do with RAM occupation. They are typically used for mounting disk images, in your case apparently for Ubuntu Snap. See this Wikipedia article about loop devices for details.
Also note that it is a Good Thing(™) your RAM is full. Unused RAM is wasted RAM, so Linux makes an effort to put all of your RAM to good use. See this info page for details.
There are other information sources accessible on the internet.
I suggest that you re-state the actual problem. You have created a new topic. So, let us treat it as a new topic.
Regards
On that yancek link, at the end, the poster said this:
As you can see, I have way more than that guy with 77… I have 421
graymech: the problem is the same, the first fix lasted 3 days, the second lasted 3 -4 weeks
It is this error message:
The first link in my post above was to the 2nd fix attempt. After looking at yancek’s post again, I found that guy at the end talking about those 'forbidden signature keys in Key Management in secure boot mode. I don’t have secure enabled now, but the link to key and forbidden are there.
To be honest, this is pretty confusing for users.
Is this a continuation of the previous topic that was marked as solved or a new issue?
If a continuation of the old topic, please ask us to re-open it instead of starting a new topic.
If this is a new issue, even slightly different, then please edit your title to be more descriptive of the new situation.
Thanks
Yes, it is a continuation of the old topic. So, how do I ask to have it re-opened?
By messaging any moderator and requesting it be re-opened.
Moderators have the shield icon next to their names in the profile or you can just send a generic message to @moderators asking that a topic be opened.
Would you like us to re-open that original topic and move all these posts there?
Yes, thank you. I thought it would be easier that way, but didn’t know how, or that is was possible, as the end comment says the thread is closed.
Again, thank you.
1 Like
Done. Topics merged, keeping chronological order for clarity.
Removed the check for solution since this is an ongoing issue that needs more support.
I see that I didn’t disable the Security Device Support that tea-for-one suggested, is that the reason this happened again? Are those Forbidden Signature Keys in Key Mangement the issue?
The other (silver) model is ok, but perhaps that’s because I really don’t use it much. It seems to have close to the same number of Forbidden Signature Keys. Maybe if I used it, it would have the same problem. I think I didn’t disable the Security Device Support because of that. I would like to keep the two models in the same configuration. Not that it really matters I guess. Whatever works long term is really best.
The UEFI Secure Boot Revocation List, or the Secure Boot Forbidden Signature Database (dbx), is a list that identifies software that Secure Boot no longer allows to run.
So, maybe that Forbidden or Revocation List doesn’t matter especially since I now have secure boot disabled? Then I need to look for another reason, but is having that many in the list a problem or should I update it as stated in that article?
prcowley asked about my boot partition size, which looks fine, right?:
Here’s the efibootmgr asked for:
The errors you report are unrelated to your /boot partition which is on the hard drive as the problem is on your system board. Do you have a Windows install on an external drive which is what the Windows To Go is? It was designed specifically for Enterprise/Education systems as explained at the Microsoft site below and was problematic for many users. If you don’t have it you can safely delete that entry also.
Those errors are in reference to Secure Boot and if you did not have Secure Boot enables at any time, you would not have had those errors. Turning off Secure Boot now will not rid you of the errors. The link below discusses several options to eliminate this error and would be worth reading if you have not tried the suggestions already.
yancek: No, I don’t have MS on the laptops anymore. They both came with MS10 installed, but I got rid of it after making a startup disk for Ubuntu. So, I’ll get rid of that entry for Boot0004 as well.
I think Secure Boot was installed with that MS10 or 11 ( Which was part of an update later before I deleted it all, as MS11 was worse than 10, which I was used until I got Ubuntu installed). I’ll read that unix link. Thanks.
Do you know whether those Forbidden Sigs are needed or should be deleted, since I’m not in Secure Boot mode?
Forbidden Signatures are not affecting your PC.
Currently, I have 373.
I deleted them and they eventually re-appeared in the list - it doesn’t matter.
Just for the record, Secure Boot and TPM are permanently disabled on my PC.
In post 31, the first screenshot shows that your ESP (sdb1) is mounted at /boot/efi, indicating that your PC booted successfully.
Is Startup Failure now fixed?
It started up ok after clearing those files, so the question is whether it fills back up again. I still wonder about those Forbidden files as I have 421 keys. Is that a problem if Secure Boot is disenabled? Ok, I see that you had 373 as well, so it shouldn’t be a problem. Everything seems ok today. thanks everyone.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.