this post was submitted on 04 Jan 2024
632 points (94.6% liked)
linuxmemes
24211 readers
1757 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Just hold the power button until it gets quiet.
... shush, don't fight it, it will be over soon.
I always imagine this when hard rebooting any device
Oh yeah, deleting partition tables always felt a bit like (mini) scorched earth past-denying genocide. Gone but not forgotten. But also mostly forgotten. Nevertheless you legacy will live onwards through volume labels that I always use.
I know, I know... we were just not meant to be, sorry...
It could be installing updates
You are right, but I always risk it (restore points work most of the time anyway).
One of the main reasons why I let ot boot all the way. If nothing else, it'll mark the partition as dirty π. Sure, I can
sudo mount
my way into it, but I really have no idea if everything's OK with it. So, I have to reboot, boot into Windows, mark the partition for a consistency check, reboot, boot into Windows again so it could do the check, then reboot again and (finally!) boot into Linux π... I mean, just let it boot all the way the first time, it'll be over rather quickly.Really? I think it shows the files as locked, but you can actually do whatever in root π€.
In either case, it's just more painless to actually let it boot all the way than to interrupt the boot process.
lol π€£. Good info though π, I will have it in mind.
Oh yeah, I've had that happen to me (only the one time, like a decade ago), once I realized what gives I solved it easily with GParted 'repair' or something like that (iirc?).
Edit: ohh, I think it was a (full distro) live-boot CD that I used.