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…
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.
I’m not completely sure but I think u can’t sudo mount rw, the only way I get it to work is with ntfsfix which does magic and releases the windows lock (but even this doesn’t always work)
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
deleted by creator
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).
deleted by creator
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.I’m not completely sure but I think u can’t sudo mount rw, the only way I get it to work is with ntfsfix which does magic and releases the windows lock (but even this doesn’t always work)
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.
I wasn’t able to force it to mount rw without unlocking the drive first
In fact the whole process is with sudo to begin with, so do we do sudo of sudo to force sudo to do the thing? (jk, but yea it needs sudo in any case)
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.