Pop!_OS (Linux)

5183 readers

8 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 2 years ago

MODERATORS

[email protected]

Why did I need to restart to upgrade my recovery partition? (self.pop_os)

submitted 1 year ago* (last edited 1 year ago) by jbrains to c/[email protected]

7 comments fedilink hide all child comments

I tried to upgrade my recovery partition today and it failed with "No such device"/OS error 19.

I found this discussion on Reddit in which @mmstick suggested restarting, but with no explanation as to why that was needed or would work. It worked for me.

https://www.reddit.com/r/pop_os/comments/xun8vu/error_updating_recovery_partition_no_such_device/

I'd like to know why it worked and why it was needed, mostly for two reasons: to generally understand the situation better and to imagine what I might have been able to do that didn't require restarting.

Thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

Standard IT practice to turn it off and on again. Some updates require system restarts to apply the update to the running system, otherwise you may see some broken behavior where something's inaccessible because the installed drivers don't match the kernel you're using.

[–] jbrains 1 points 1 year ago* (last edited 1 year ago) (1 children)

I am familiar with this. It also doesn't help me understand much more than "it's complicated". I already suspected as much. 😉

[–] [email protected] 1 points 1 year ago (1 children)

Emphasis on "running system". Similar to how you can't fully re-partition a disk you're currently using.

[–] jbrains 1 points 1 year ago (1 children)

I understand the general concept.

I have also upgraded the recovery partition on this machine every 3 months for over 3 years before needing to reboot to make it work this time. I'm curious what might account for the difference.

Also, I'm not sure how upgrading a recovery partition constitutes updating a running system. I had not booted from the recovery partition. I was not running anything from the recovery partition.

[–] [email protected] 1 points 1 year ago (1 children)

Did you check if the recovery partition was recognised and mounted? Maybe some voodoo made it fail to mount, but it worked after a reboot.

[–] jbrains 1 points 1 year ago

Yes, it was. I checked by unmounting it, then running the upgrade command, which resulted in a clear error message about the partition not being mounted. I don't remember the specific message, but I remember it was different than the one I got when it was mounted. This leads me to believe that the OS error 19 message is some kind of red herring.

Thanks.