How to make Kali's file manager to mount Windows partition with write permissions

sevendogsbsd · 09-10-2020, 02:40 PM

Thank you for the clarification michaelk: that was what I was thinking of when I've seen some posts about problems with NTFS writes: I mis-remembered why the posters had issues.

Koles · 09-10-2020, 03:57 PM

Quote:

Originally Posted by michaelk

Koles,
Per the rules

The default Windows shutdown actually hibernates which leaves the filesystem in an unknown state. If the ntfs-3g driver detects hibernation it mounts the filesystem as read only versus just displaying a warning message. If you go back and restart Windows and then fully shutdown (disable fast start up) the system you should be able to mount the filesystem as read/write.

Writing to NTFS filesystems with the ntfs-3g driver has been stable for many years.

I love you man! This is what I needed. So simple and it just works! I just turned Windows 7 off (didn't hibernate, but I also didn't have to completely disable the hibernation) and booted Kali - writing works automatically in files manager, I didn't have to configure anything additional. I hope this won't break anything on Windows...

michaelk · 09-10-2020, 04:03 PM

I posted the rules above, please follow them.

Don't use vulgar words, they are not necessary.

Well, I don't know when ntfs-3g write was enabled but it is now

TB0ne · 09-10-2020, 06:19 PM

Quote:

Originally Posted by michaelk

I posted the rules above, please follow them.Don't use vulgar words, they are not necessary.

Well, I don't know when ntfs-3g write was enabled but it is now

It's been an option in Kali, but you have to manually specify it; same in the Kali file manager with a right-click. Using ntfsfix can reset that state without booting Windows as well. But we had no information to go on, and the OP never told us. I stand by the assertion that Kali is not only a poor choice for a new user, but even for an EXPERIENCED user as a 'daily driver'.

Chances are high that things further along are going to crop up, like video/audio issues, bluetooth, etc., all of which Kali wasn't made for.

michaelk · 09-10-2020, 06:49 PM

I don't disagree.

Koles · 09-11-2020, 08:54 AM

Quote:

Originally Posted by michaelk

I posted the rules above, please follow them.

Don't use vulgar words, they are not necessary.

Well, I don't know when ntfs-3g write was enabled but it is now

But what do you mean by "disable fast start up"? Does this mean just to shut down Windows (instead of using hibernation) or to completely turn off hibernation in system settings ?

michaelk · 09-11-2020, 09:22 AM

I had assumed you were running Windows 10 versus 7. Fast start up is the default mode for Windows 10.

Koles · 09-11-2020, 10:26 AM

I have Windows 7. I don't see anything like fast startup here. I only have hibernation (like in Windows XP I suppose).

TB0ne · 09-11-2020, 02:23 PM

Quote:

Originally Posted by Koles

I have Windows 7. I don't see anything like fast startup here. I only have hibernation (like in Windows XP I suppose).

As said, if you do a complete shutdown, you have a chance of this working. Since you don't HAVE fast start-up, you're obviously not using it. So long as you don't hibernate/sleep Windows, it has a chance.

And as you were told previously, ntfsfix should allow you to do what you're after; not sure why you ignore that. Again, that's in the Kali documentation.

andre@home · 09-12-2020, 03:15 PM

Quote:

Originally Posted by Koles

I have Kali ... and it shows me Windows partitions in file manager which I can mount, but they get mounted WITHOUT write permissions. It happens also on root. Hell, I don't know how to do this. How can I change some configuration so that this file manager mounts Windows partitions with WRITE permissions (also not as root)?Thanks

A week ago I had what at first site looks exactly the same as your problem.

My system was an Ubuntu distro (used for the tool Foxclone) and I could not mount my NTFS based data disk, which I normally under Windows 10, not in a dual boot (yes : I do have backups of my data..). I wanted to do some test with this rather new, but pretty cloning/backup tool, see https://foxclone.com/ .

NTFS fix solved my problem, see the terminal input/output below on an MX-Linux test system (this one can be installed very fast, has a lot of support onboard by deafult.
More reading on NTFSfix: https://www.addictivetips.com/ubuntu...rive-on-linux/

BUT this may not be your problem.... I do not have Kali Linux experience and it was already warned that normally such a NTFS disk will be mounted read-only by default..
But... there is a workaround, read this:
https://null-byte.wonderhowto.com/fo...guide-0186670/

Code:

test@mx:~
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 931.5G  0 disk 
├─sda1   8:1    0 259.7G  0 part 
├─sda2   8:2    0     1K  0 part 
└─sda3   8:3    0 667.8G  0 part /
sdb      8:16   0   2.7T  0 disk 
└─sdb1   8:17   0   1.9T  0 part 
sr0     11:0    1  1024M  0 rom  
test@mx:~
$ sudo ntfsfix /dev/sdb1
[sudo] password for test: 
Mounting volume... The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
FAILED
Attempting to correct errors... 
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb1 was processed successfully.
test@mx:~

test@mx:~
$ sudo ntfsfix --clear-bad-sectors /dev/sdb1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
Going to un-mark the bad clusters ($BadClus)... No bad clusters...OK
NTFS partition /dev/sdb1 was processed successfully.
test@mx:~