MX Linux Forum

Hello.
Today, when I boot Mx Live w/persistence on a pc with windows 10, as I have been using since last year (we've been talking about mounting partitions on this device:viewtopic.php?f=107&t=47309) i find al the files of the ntfs (windows 10) partition mounted as read only.
I think this is a windows 10 thing. I have been able to solve this by restarting the windows machine before. But today I can't.

Do you know what could I try. How to disable fast boot on win 10?

edit: also, libreoffice cannot open files on that partitions (not even as read only)

Thanks.

With Windows 10 you need to be carefull to perform the FULL shutdown first, before you touch any files. Be warned.

Full shutdown (admin cmd):
After the FULL shutdown, you can start fiddling with the files.

Otherwise, you'll get more or less corrupt files, which will result in whatever happens and you notice.

As of the rest ...
https://www.google.com/search?source=hp ... v89Jp7szZA

ok. thank you very much.

It's called "Fast Startup" in Windows. It leaves the computer in a kind of hybrid suspended state in which files are rendered read-only when accessed from another OS. Disable Fast Startup (recommended) or perform a full shutdown before booting Linux.
"Fast boot" is an unrelated UEFI/BIOS option which skips some less essential POST checks.

Yes. I did meant "fast startup".
I checked and it seems to be disabled on this pc (the box is not ticked)

Well, did not work.

The files on ntfs partition keep on read only state when i boot on mx, although they all appear as owned by me.

I´ll keep searching...

1. If you are 10'000 % sure it's really, really, really completely shut down and you are really sure that you really checked 1001 time that it's really completely shut down ...

2. Make sure that it's really shut down.

3. Then you would check where the file partition is mounted. Usualy /media/FOLDER_NAME (if not, then it's somewhere under /run).

4. Afterwards, you could try to:

sudo chown -R YOUR_USER_NAME:YOUR_USER_NAME /media/FOLDER_NAME
sudo chmod -R 777 /media/FOLDER_NAME

One warning though:
If your 10th Windoze is not fully shut down, it might render all the files unusable beyond repair.
Also, I did that already on a USB (pen drive), but not on complete W10 NTFS partition ...

You cannot change file locations in Windows as Linux user session. One needs file manager opened as root 1st. That is admin in Windows.
in a terminal after typing in your password should do the trick.
Posted the above command because I am on my AntiX chromebook right now.

Good, noClue.

But how, for god's sake, may I check that windows is really, fully, completely shut down when the pc is off?

The only way I know, after trying to do it properly from within windows when the pc is on, like:
- checking that start up box is not checked on energy settings.
- clicking on "restart" button instead of shutdown button (this worked for several months)
- doing shutdown /s on cmd (this used to work)
- doing shutdown /s /f /t 0 (as suggested on this thread);
- also tried holding Shift key when clickin shut down (this never really worked to me)

is to start a linux distro on that pc.
As I did with mx and other distros

If partition is writable, then windows did its job and shut down.
If read-only, then I suspect that windows is not delivering well.

Since two days ago, the ntfs partitions appears read only to my mx os.
I tried also ubuntu 16.04 live usb. Same thing. Ubuntu is more explicit and suggest to shut down windows properly. So I don't think that there's something wrong with the way mx is mounting the partition. But I will recheck.

Anyway, I'll keep trying shutdown /s /f /t 0 another times.

I think I should try on a windows forum, also.

Thanks a lot.

That behaviour that you're describing is not a fault of Windows and not a fault of Linux.
The reason for it are, for some reason 'borked' FS-permissions.

If the #4 doesn't help, you might try checking/repairing the Windows with 'chkdsk' and then try again.
Why does it happen or why did it happen to you, I can't tell you, but I also noticed that it happens from time to time.

Probably related to windows fastboot, either disable it or try what i suggested here

Also, please show us the output of the "mount" command, so we can see if the filesystem is mounted read-only (or else you have a permission problem)