I was doing a lot of work on that drive in Manjaro before the problem and didn't use windows for weeks.
I am pretty sure that linux caused the problem on the drive not the windows shutdown. But I can see that restarting windows can fix it.

I would really like to fix it in linux as this is where the problem is exhibited.

I imagine a dirty Manjaro shutdown could have left the NTFS filesystem in a state that only Windows could repair.

I have updated now and works great.

Thanks to everyone who contributed to this problem, especially mrmazda for finding the cause of the problem and then a solution.

Isn't this our old bogie "Fast boot"? By default, Windows does not shut down but instead carries out what Linux would call a hibernation. The contents of memory are written out to disk and then the whole thing stops. When you switch on again, the memory image is retrieved and all the usual initialisations can be skipped. People booting from a UEFI are always instructed to switch "Fast boot" off.

After searching this on the internet I found out that this Fast Boot on Windows started with Windows 8.
I am running Wndows 7 and cannot find the setting they talk about to turn this on or off. So, this was not the cause of my problem.
I also don't boot from a UEFI.

However, doing a restart on my Windows into Grub did fix the drive and booted into Manjaro correctly with access to that drive.

I don't know what M$ calls it, but that describes the process as I understand it of leaving its filesystem(s) in a state Linux won't touch. At some point Windows started using a separate partition on GPT to facilitate the process.

I think I found the cause of my problem.

I have setup my Manjaro to share the ntfs Data drive on in the Workgroup windows network. This appeared to work fine.

However, I just copied a file from a windows machine by windows explorer onto the Data drive under Manjaro. It appears to have copied fine.
But, when I rebooted the machine I have the same problem.

Launching windows and then restarting as before and shutting down from grub did not fix it.
I tried again but no good.

Looks like my problem is not solved after all.

I think that it is a linux problem because I can launch a live USB and it has no problem mounting and accessing that drive.

More info.
On the internet I found a command 'lbsblk'.
There it showed the Data drive mounted as /srv/samba/ntfs.
Had a look at the contents and indeed it is my Data drive.
Had a look at the entry in fstab and my drive is defined as /home/frank/Data where it should be. But this is not how it is mounted.

How do I get samba to mount it in /home/frank/Data?

It's entirely unclear to me what this means. Was this a copy across a network from a Windows-booted PC #1 to a Manjaro-booted PC #2 that has a Windows filesystem mounted, which is shared on the network, and to which Windows Explorer on PC #1 copied a file? If so, there may be a CIFS or Samba bug causing the problem.

Your original thread has been solved. This separate problem needs its own thread, apparently in networking instead of newbie, so that CIFS/Samba-interested people will notice. There you need to be clear about how many computers are running and where this "data" drive is connected, and how. It seems as though you are dealing with more than one mount for your data drive, one under Manjaro, and another on Windows via Manjaro.

1 members found this post helpful.