Announcement
Collapse
No announcement yet.
Is it possible to make my Windows drive writable?
Collapse
This topic is closed.
X
X
-
Well, that turned out to be useful, because it had indeed re-enabled fast startup, so I turned that off, and it definitely went through a full shutdown because it displayed the "Waiting for programs to close" screen. But it's still not writable. As for fstab, I kind of like not having all my drives auto-mount, especially if I'm going to mount them in writable form. Plus, again, my old drive is writable despite not being mounted at boot time either.
- Top
- Bottom
-
I did not approach this problem to find the answer, merely to fix the problem by covering all bases, however a quick dash to my still functioning logic cells tells me it was following https://www.windowscentral.com/how-d...0-fast-startup because I am obviously a bit strange as I fstab all my disks and I assumed it to be common practice. Just goes to prove the old saying: assume makes an ass out of you and me.
- Top
- Bottom
Leave a comment:
-
Well, it's probably hybernated/somehow-locked by Windows, isn't it.
Shag00 tells us that by either mounting it in fstab, disabling hybernate with "powercfg /h off" or both, it can be written to - but doesn't tell us which.
Why not try those? You don't tell us you have...
- Top
- Bottom
Leave a comment:
-
OK, I was playing around with some stuff, and by accident I discovered something interesting. I currently have two internal Windows drives plugged in, my current one and my old one that I quit using because it started showing signs of hardware failure. (As for why it's plugged in right now, it's complicated.) Turns out, I can actually write to the old drive, but not the new one. This is especially weird because when it was my active boot disk, I definitely remember that I was not able to write to it from Linux. Again, both drives were mounted after boot by clicking them in Dolphin. Neither drive is listed in fstab. And if I right-click on either disk and hit Properties, then Permissions, both drives are showing "Can View and Modify Content" in all categories. If there's any other procedure I could use that would show that there's some difference between them, I'd love to know it.
- Top
- Bottom
Leave a comment:
-
Cannot see why you cannot have read/write one the LAN. My android devices can access my PC's SMB shares with read/write. But that is a different topic
- Top
- Bottom
Leave a comment:
-
By mounting it in fstab, disabling hybernate, either, or both?Originally posted by shag00 View PostI can read and write to my local Windows disks.
- Top
- Bottom
Leave a comment:
-
Ooops, let me retract most everything I have said. It's the ownership I can't change and the Windows disks on remote PCs in my LAN I have write issues with. I can read and write to my local Windows disks. Apologies to all.
- Top
- Bottom
Leave a comment:
-
Well, I guess if there is no way to write to a windowized disk, copying the files to an external drive, or from Windows itself (with a linux-filesystem-reading utlity) would be the next best thing then.
One would not be able to use the stuff in Windows unless they've booted it, right?
- Top
- Bottom
Leave a comment:
-
The drives can/are be mounted and can be read they just cannot be written to despite appearances to the contrary.
My fstab:
My ls -al from above post:Code:/swapfile none swap sw 0 0 UUID=C100-521F /boot/efi vfat umask=0077 0 1 UUID=98913ab1-6347-4a71-99ae-fea6aa5fbca7 / ext4 errors=remount-ro 0 1 UUID=8068D5D368D5C854 /media/disk0 ntfs defaults 0 2 UUID=7872060B7D3B8B8A /media/disk1 ntfs defaults 0 2 UUID=744CF41C4CF3D738 /media/disk2 ntfs defaults 0 2 UUID=22C8783D7121C3B5 /media/disk3 ntfs defaults 0 2
drwxrwxrwx 1 root root 4096 Dec 28 21:13 disk1
My blkid entry for disk1
/dev/nvme1n1p1: LABEL="Data 1" UUID="7872060B7D3B8B8A" TYPE="ntfs" PTTYPE="dos" PARTUUID="03f3f3cf-7b2a-41b6-910c-f106fddcf8c8"
Hybernate is disabled as well as any combination of hibernate or sleep, refer https://www.windowscentral.com/how-d...0-fast-startupLast edited by shag00; Jan 05, 2020, 04:02 AM.
- Top
- Bottom
Leave a comment:
-
Well, why not try one or both:
If the second one doesn't let you mount the drive with Dolphin, the first one might just mount it read-write at boot.Originally posted by hallergard View PostDo you have the correct entry for the Windows drive in /etc/fstab?
Is Windows hybernated? If yes, enter "powercfg /h off" in a Windows administrator terminal!
- Top
- Bottom
Leave a comment:
-
Claydon, this is not correct, just tried it on my Windows 10 (Settings>Power Options). Also, my system does not have a BIOS entry for fast start or similar.Originally posted by claydoh View PostYou need to disable 'fast startup" from within Windows settings, not the bio/firmware settings. This is not the same as fast boot, which of course is highly confusing
Last edited by shag00; Jan 05, 2020, 02:25 AM.
- Top
- Bottom
Leave a comment:
-
I don't have a listing for the drive in fstab; it mounts when I access it through Dolphin's left panel. Is that a problem?
Also, when I said I disabled "quick shutdown", fast startup is what I was talking about.
- Top
- Bottom
Leave a comment:
-
You need to disable 'fast startup" from within Windows settings, not the bio/firmware settings. This is not the same as fast boot, which of course is highly confusingOriginally posted by jlittle View PostTo explain, in a default install, Windows "shutdown" doesn't shut down fully, it "hibernates", or "hybrid hibernates" (contracted to "hybernates'). This leaves the NTFS marked as "in use" so that Linux makes it read-only. This is called "fast boot", or "fast startup" in Windows 10. I used to tell people with this problem to disable "fast boot" or "quick boot" in the firmware (aka "BIOS" or "UEFI") settings.
This is better than fiddling with firmware settings. I might dig out a Windows box from somewhere to try this.
- Top
- Bottom
Leave a comment:
-
To explain, in a default install, Windows "shutdown" doesn't shut down fully, it "hibernates", or "hybrid hibernates" (contracted to "hybernates'). This leaves the NTFS marked as "in use" so that Linux makes it read-only. This is called "fast boot", or "fast startup" in Windows 10. I used to tell people with this problem to disable "fast boot" or "quick boot" in the firmware (aka "BIOS" or "UEFI") settings.
This is better than fiddling with firmware settings. I might dig out a Windows box from somewhere to try this.Originally posted by hallergard View PostIs Windows hybernated? If yes, enter "powercfg /h off" in a Windows administrator terminal!
- Top
- Bottom
Leave a comment:
Users Viewing This Topic
Collapse
There are 0 users viewing this topic.
Leave a comment: