Why does my NTFS partition mount as read only?
23
Until recently both my Windows Partition (C:) and my Data Partition (E:) would mount as read/write. Now both seem to only mount as read-only.
GParted Resize (Error)
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda4
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 86207623680 bytes (86208 MB)
Current device size: 86207627264 bytes (86208 MB)
New volume size : 78662066688 bytes (78663 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 62126 MB (72.1%)
Collecting resizing constraints ...
Needed relocations : 1606868 (6582 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
chkdsk Output:
Checking file system on E:
The type of the file system is NTFS.
Volume label is Data.
A disk check has been scheduled.
Windows will now check the disk.
99482 file records processed.
495 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
104412 index entries processed.
0 unindexed files processed.
99482 security descriptors processed.
2466 data files processed.
CHKDSK is verifying Usn Journal...
4479208 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
84187132 KB total disk space.
60479688 KB in 69969 files.
15520 KB in 2467 indexes.
0 KB in bad sectors.
174336 KB in use by the system.
65536 KB occupied by the log file.
23517588 KB available on disk.
4096 bytes in each allocation unit.
21046783 total allocation units on disk.
5879397 allocation units available on disk.
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=8213cc89-2438-41b9-899f-13b4c5b299af / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=45873767-d9ae-4f0c-baab-ffc2726ac24e none swap sw 0 0
Checked the drive in GParted, GSmartControl and with ntfsfix, all completed successfully, no change.
Partitions
dev/sda1 NTFS WinRE
dev/sda2 NTFS Windows C:
dev/sda3 Extended
dev/sda4 NTFS Data E:
dev/sda5 EXT4 Ubuntu
dev/sda6 linux-swap
I am looking for an explanation of:
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
and
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
mount ntfs read-only
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
add a comment |
23
Until recently both my Windows Partition (C:) and my Data Partition (E:) would mount as read/write. Now both seem to only mount as read-only.
GParted Resize (Error)
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda4
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 86207623680 bytes (86208 MB)
Current device size: 86207627264 bytes (86208 MB)
New volume size : 78662066688 bytes (78663 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 62126 MB (72.1%)
Collecting resizing constraints ...
Needed relocations : 1606868 (6582 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
chkdsk Output:
Checking file system on E:
The type of the file system is NTFS.
Volume label is Data.
A disk check has been scheduled.
Windows will now check the disk.
99482 file records processed.
495 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
104412 index entries processed.
0 unindexed files processed.
99482 security descriptors processed.
2466 data files processed.
CHKDSK is verifying Usn Journal...
4479208 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
84187132 KB total disk space.
60479688 KB in 69969 files.
15520 KB in 2467 indexes.
0 KB in bad sectors.
174336 KB in use by the system.
65536 KB occupied by the log file.
23517588 KB available on disk.
4096 bytes in each allocation unit.
21046783 total allocation units on disk.
5879397 allocation units available on disk.
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=8213cc89-2438-41b9-899f-13b4c5b299af / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=45873767-d9ae-4f0c-baab-ffc2726ac24e none swap sw 0 0
Checked the drive in GParted, GSmartControl and with ntfsfix, all completed successfully, no change.
Partitions
dev/sda1 NTFS WinRE
dev/sda2 NTFS Windows C:
dev/sda3 Extended
dev/sda4 NTFS Data E:
dev/sda5 EXT4 Ubuntu
dev/sda6 linux-swap
I am looking for an explanation of:
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
and
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
mount ntfs read-only
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36
add a comment |
23
23
23
15
Until recently both my Windows Partition (C:) and my Data Partition (E:) would mount as read/write. Now both seem to only mount as read-only.
GParted Resize (Error)
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda4
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 86207623680 bytes (86208 MB)
Current device size: 86207627264 bytes (86208 MB)
New volume size : 78662066688 bytes (78663 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 62126 MB (72.1%)
Collecting resizing constraints ...
Needed relocations : 1606868 (6582 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
chkdsk Output:
Checking file system on E:
The type of the file system is NTFS.
Volume label is Data.
A disk check has been scheduled.
Windows will now check the disk.
99482 file records processed.
495 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
104412 index entries processed.
0 unindexed files processed.
99482 security descriptors processed.
2466 data files processed.
CHKDSK is verifying Usn Journal...
4479208 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
84187132 KB total disk space.
60479688 KB in 69969 files.
15520 KB in 2467 indexes.
0 KB in bad sectors.
174336 KB in use by the system.
65536 KB occupied by the log file.
23517588 KB available on disk.
4096 bytes in each allocation unit.
21046783 total allocation units on disk.
5879397 allocation units available on disk.
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=8213cc89-2438-41b9-899f-13b4c5b299af / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=45873767-d9ae-4f0c-baab-ffc2726ac24e none swap sw 0 0
Checked the drive in GParted, GSmartControl and with ntfsfix, all completed successfully, no change.
Partitions
dev/sda1 NTFS WinRE
dev/sda2 NTFS Windows C:
dev/sda3 Extended
dev/sda4 NTFS Data E:
dev/sda5 EXT4 Ubuntu
dev/sda6 linux-swap
I am looking for an explanation of:
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
and
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
mount ntfs read-only
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
Until recently both my Windows Partition (C:) and my Data Partition (E:) would mount as read/write. Now both seem to only mount as read-only.
GParted Resize (Error)
ntfsresize v2.0.0 (libntfs 10:0:0)
Device name : /dev/sda4
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 86207623680 bytes (86208 MB)
Current device size: 86207627264 bytes (86208 MB)
New volume size : 78662066688 bytes (78663 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 62126 MB (72.1%)
Collecting resizing constraints ...
Needed relocations : 1606868 (6582 MB)
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
chkdsk Output:
Checking file system on E:
The type of the file system is NTFS.
Volume label is Data.
A disk check has been scheduled.
Windows will now check the disk.
99482 file records processed.
495 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
104412 index entries processed.
0 unindexed files processed.
99482 security descriptors processed.
2466 data files processed.
CHKDSK is verifying Usn Journal...
4479208 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
84187132 KB total disk space.
60479688 KB in 69969 files.
15520 KB in 2467 indexes.
0 KB in bad sectors.
174336 KB in use by the system.
65536 KB occupied by the log file.
23517588 KB available on disk.
4096 bytes in each allocation unit.
21046783 total allocation units on disk.
5879397 allocation units available on disk.
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda5 during installation
UUID=8213cc89-2438-41b9-899f-13b4c5b299af / ext4 errors=remount-ro 0 1
# swap was on /dev/sda6 during installation
UUID=45873767-d9ae-4f0c-baab-ffc2726ac24e none swap sw 0 0
Checked the drive in GParted, GSmartControl and with ntfsfix, all completed successfully, no change.
Partitions
dev/sda1 NTFS WinRE
dev/sda2 NTFS Windows C:
dev/sda3 Extended
dev/sda4 NTFS Data E:
dev/sda5 EXT4 Ubuntu
dev/sda6 linux-swap
I am looking for an explanation of:
Internal Info:
9a 84 01 00 00 1b 01 00 fc 1a 01 00 00 00 00 00 ................
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
42 00 00 00 52 73 5c 77 b0 e7 1d 00 b0 df 1d 00 B...Rsw........
and
Resetting $LogFile ... (this might take a while)
Relocating needed data ...
ERROR: Extended record needed (1032 > 1024), not yet supported!
Please try to free less space.
mount ntfs read-only
mount ntfs read-only
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
edited Oct 21 '11 at 16:33
Lewis Goddard
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
asked Oct 21 '11 at 15:36
Lewis GoddardLewis Goddard
1,79342555
1,79342555
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36
add a comment |
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36
add a comment |
3 Answers
3
active
oldest
votes
24
The system might not have the files for writing to NTFS partitions installed.
Try this in terminal:
sudo apt-get remove ntfsprogs && sudo apt-get install ntfs-3g
This removes ntfsprogs if it's present on the system, and installs ntfs-3g which should allow you to write properly to NTFS partitions.
Then reboot your system, and attempt to open the NTFS drive for write access. You should now be able to write to the NTFS drive.
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
add a comment |
26
Performing a full shutdown of Windows will allow the drives to be fully mounted by Ubuntu. This can be accomplished by holding the SHIFT key as you press the "Shut down" button on the "Power" menu.
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and typepowercfg /h offand hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.
– Ben Johnson
Jul 19 '18 at 0:44
add a comment |
1
Happened to me, all I did was
sudo ntfsfix /dev/sdxX // where x is HDD and X is drive number, in my case it was /dev/sda1
it will remove any logfile created by windows.
worked for me.
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f70281%2fwhy-does-my-ntfs-partition-mount-as-read-only%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
24
The system might not have the files for writing to NTFS partitions installed.
Try this in terminal:
sudo apt-get remove ntfsprogs && sudo apt-get install ntfs-3g
This removes ntfsprogs if it's present on the system, and installs ntfs-3g which should allow you to write properly to NTFS partitions.
Then reboot your system, and attempt to open the NTFS drive for write access. You should now be able to write to the NTFS drive.
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
add a comment |
24
The system might not have the files for writing to NTFS partitions installed.
Try this in terminal:
sudo apt-get remove ntfsprogs && sudo apt-get install ntfs-3g
This removes ntfsprogs if it's present on the system, and installs ntfs-3g which should allow you to write properly to NTFS partitions.
Then reboot your system, and attempt to open the NTFS drive for write access. You should now be able to write to the NTFS drive.
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
add a comment |
24
24
24
The system might not have the files for writing to NTFS partitions installed.
Try this in terminal:
sudo apt-get remove ntfsprogs && sudo apt-get install ntfs-3g
This removes ntfsprogs if it's present on the system, and installs ntfs-3g which should allow you to write properly to NTFS partitions.
Then reboot your system, and attempt to open the NTFS drive for write access. You should now be able to write to the NTFS drive.
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
The system might not have the files for writing to NTFS partitions installed.
Try this in terminal:
sudo apt-get remove ntfsprogs && sudo apt-get install ntfs-3g
This removes ntfsprogs if it's present on the system, and installs ntfs-3g which should allow you to write properly to NTFS partitions.
Then reboot your system, and attempt to open the NTFS drive for write access. You should now be able to write to the NTFS drive.
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
edited Jul 5 '18 at 17:54
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
answered Oct 21 '11 at 16:34
Thomas Ward♦Thomas Ward
43.8k23121174
43.8k23121174
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
add a comment |
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Running that command results in the system prompting me to remove ntfsprogs, which i looked up, and doesn't seem to list anything about writing to ntfs generally, so i removed it. This seems to have fixed it, i think i installed ntfsprogs when looking to run a disk check under ubuntu due to bad sectors (10 of them). Thanks!
– Lewis Goddard
Oct 21 '11 at 16:39
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Yep. Your question was a bit misleading though, because of the data you attached. That data that is attached generally doesn't explain why you can't write to the drive - rather we see that you're trying to resize the drive in that data.
– Thomas Ward♦
Oct 21 '11 at 18:14
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Removing the ntfsprogs when installing ntfs-3g solved the read only problem.
– Luis Alvarado♦
Dec 13 '11 at 3:25
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
Got NTFS file creation working for me, cheers.
– Gerry
Jul 24 '12 at 15:56
add a comment |
26
Performing a full shutdown of Windows will allow the drives to be fully mounted by Ubuntu. This can be accomplished by holding the SHIFT key as you press the "Shut down" button on the "Power" menu.
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and typepowercfg /h offand hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.
– Ben Johnson
Jul 19 '18 at 0:44
add a comment |
26
Performing a full shutdown of Windows will allow the drives to be fully mounted by Ubuntu. This can be accomplished by holding the SHIFT key as you press the "Shut down" button on the "Power" menu.
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and typepowercfg /h offand hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.
– Ben Johnson
Jul 19 '18 at 0:44
add a comment |
26
26
26
Performing a full shutdown of Windows will allow the drives to be fully mounted by Ubuntu. This can be accomplished by holding the SHIFT key as you press the "Shut down" button on the "Power" menu.
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
Performing a full shutdown of Windows will allow the drives to be fully mounted by Ubuntu. This can be accomplished by holding the SHIFT key as you press the "Shut down" button on the "Power" menu.
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
answered Jun 2 '17 at 23:33
schulwitzschulwitz
36133
36133
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and typepowercfg /h offand hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.
– Ben Johnson
Jul 19 '18 at 0:44
add a comment |
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and typepowercfg /h offand hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.
– Ben Johnson
Jul 19 '18 at 0:44
1
1
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
Can this be done if the Windows partition is gone? Put another way, can I do this if Windows is no longer installed?
– epotter
Oct 30 '17 at 23:58
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
No, this trick is only useful if you have Windows installed as there is no "Shut down" button to click if you don't have Windows installed.
– schulwitz
Oct 31 '17 at 0:55
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
thanks, this worked for me... my windows 10 partition was read only before but after following instructions from the page , its not....
– waqar
Mar 25 '18 at 5:05
3
3
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and type
powercfg /h off and hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.– Ben Johnson
Jul 19 '18 at 0:44
To avoid having to hold-down Shift every time you shutdown Windows (it's easy to forget in a dual-boot configuration), you can simply disable Hibernation entirely, which also disables Hybrid Boot, thereby making this a non-issue. When booted into Windows, launch an elevated Command Prompt ("Run as Administrator") and type
powercfg /h off and hit Enter. Then, reboot into Ubuntu, and the NTFS drive will be writable. If you'd prefer not to disable Hibernation entirely, you can disable only Hybrid Boot using Control Panel (I couldn't find a command-line method); see link in the Answer for guide.– Ben Johnson
Jul 19 '18 at 0:44
add a comment |
1
Happened to me, all I did was
sudo ntfsfix /dev/sdxX // where x is HDD and X is drive number, in my case it was /dev/sda1
it will remove any logfile created by windows.
worked for me.
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
add a comment |
1
Happened to me, all I did was
sudo ntfsfix /dev/sdxX // where x is HDD and X is drive number, in my case it was /dev/sda1
it will remove any logfile created by windows.
worked for me.
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
add a comment |
1
1
1
Happened to me, all I did was
sudo ntfsfix /dev/sdxX // where x is HDD and X is drive number, in my case it was /dev/sda1
it will remove any logfile created by windows.
worked for me.
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
Happened to me, all I did was
sudo ntfsfix /dev/sdxX // where x is HDD and X is drive number, in my case it was /dev/sda1
it will remove any logfile created by windows.
worked for me.
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
answered Dec 26 '18 at 17:45
Hammad FarooqHammad Farooq
111
111
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f70281%2fwhy-does-my-ntfs-partition-mount-as-read-only%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you write data to the partition? If not then read my answer below. And are you trying to resize, and not able to, thus the assumption its read-only? or are you actually trying to write data to the drive?
– Thomas Ward♦
Oct 21 '11 at 16:36