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.
Unless u have a ntfs shared drive which gets locked by windows if u don’t restart (or disable fast startup for a real shutdown) so it releases the lock without having to unlock it inside Linux (and sometimes failing because it’s not always locked the same)
“locked” the drive is read-only in Linux until windows unlocks it or Linux does using a tool
Unless u have a ntfs shared drive which gets locked by windows if u don’t restart…
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.
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.
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
same thought when hard rebooting the last time before formatting
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).
Unless u have a ntfs shared drive which gets locked by windows if u don’t restart (or disable fast startup for a real shutdown) so it releases the lock without having to unlock it inside Linux (and sometimes failing because it’s not always locked the same)
“locked” the drive is read-only in Linux until windows unlocks it or Linux does using a tool
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 mountmy 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.deleted by creator
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.
deleted by creator
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.