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...Rs\w........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 0Checked 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...Rs\w........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.7 Answers
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.
8Happened 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/sda1it will remove any logfile created by windows.
worked for me.
8The 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-3gThis 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.
4If it happens in case of dual booting with Windows 10, you need to uncheck turn on fast startup in Control Panel --> Power Options --> Choose what the power buttons do and then shutdown, not reboot. Once it's done properly you'll be able to access the NTFS partitions normally with read/write permissions.
This happens due to the Windows 10 update resets it to the default fast startup which is a form of hibernation.
Follow these steps:
Open terminal and type:
$ blkidFind the partition (if you have a single HDD then it will be
/dev/sdaxand another HDD will besdbx).Run the following command, where
ais the HDD's position and5is the partition's position:$ sudo ntfsfix /dev/sda5
It's worked for me!
try below solution only if last resort only
I tried all solution. none of them work. this may be due to windows disk error(bad sector) & wasn't shutdown properly.
Only work solution me for delete everything from nvme drive.Note that this will remove everything on storage/nvme drive.
apt-get install nvme-cliTo delete everything or format drive I used tool called "nvme-format"
nvme format /dev/nvmeXY # where nvmeXY is device namenote: this will erase everything from drive.
2In dual(multi) boot system, When you tries logout from Windows OS, to achieve fastboot Windows keeps claim on drives by locking write access. And due to that in other OS, Windows specific partitions are mounted as read-only. Using "Disable Fastboot" feature we can, stop this action.
But sometimes the feature "Disable Fastboot" is prohibited to change by non-admin user by group policy restriction.
The below solution will help for all situations.
Login to windows, close all opened windows if any and execute following, from Run dialog
shutdown /f /r /t 0/f Force running applications to close without forewarning users.
/r Full shutdown and restart the computer.
/t xxx Set the time-out period before shutdown to xxx seconds.
1
