this post was submitted on 04 Jan 2024
626 points (94.7% liked)
linuxmemes
20408 readers
961 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.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.