I have an old assembled system. I have two SSDs one for Windows and another for Linux running Leap 15.2 and an external 3TB HDD with NTFS. I was running Windows 7 32 bit with two partitions on SSD, one for the OS and programs and other for data. I could mount and read all partitions and the external HDD from Leap.
I just changed from Windows 7 32 bit to Windows 10 64 bit on the partition for OS. No changes were made to the partition for data or the external HDD. However I find that I cannot access these from Leap. What I now understand is that partitions accessed from Windows with fast boot on are no longer accessible from Linux. Is it correct?
I have not been able to find how to turn off the fast boot option. Can anyone help me?
Trying to use (from Linux) Windows file systems that are not closed properly (e.g. by using the Windows fast boot feature) has never worked. Probably your old Windows did not use fast boot, thus you never have experienced this.
Yes, you have to turn off fast boot in your Windows. As I know almost nothing about Windows I can not tell you how to do that. But I assume that that can not be too difficult to find. Else wait for someone her who knows also things about Windows, or als in a Windows forums.
Hi
The other way is to do a full shutdown of windows, either when pressing shutdown hold the shiftkey and select shutdown, or create a shortcut shutdown /s /t 3 where t 3 equals 3 seconds.
Thanks. Found it with “disable windows 10 fast boot”! Hidden in plain sight.
Control Panel -> search for power options -> click -> click choose what power buttons do -> click change settings that are currently unavailable -> click to unselect fast start up -> save changes
I have managed to get rid of fastboot in windows 10. The internal partitions on SSDs are now again accessible from Leap. However, the external HDD is not even detected by Windows 10 itself or by Leap or even the partitioner or Qphotorec. I have checked in various Windows forums and found mention of the problem mentioned in only one place but no solutions. It is reported there that Parted Magic also does not help.
I now understand that Windows when shutting down with fastboot writes to the storage media some (each time a new) code which helps it come out of hibernation quickly when booted next. However if a drive is not connected when the systems boots again the code becomes meaningless and the drive is blocked. **From what I can make out Microsoft will not even acknowledge the problem and put out a warning much less find or put out a solution.
**
Any suggestions for recovering the HDD?
AFAIK fastboot is a hibernate/shutdown hybrid, you really should eject any removable media, like USB disks, pendrives, etc., before shutting down - unless you didn’t write anything to it since it was mounted, of course.
Is that what is added to your “follow” when you connect/switch on the device? Or that that only what was shown already direct after giving the command?
The idea of the “follow” functionality is that you see a short list of the last logs and after that you will see every fresh log entry that is made. Thus allows one to see the direct effect of an action in the logs. Thus only the entries that are made as a result of the action (connecting) are important.
I ask because I see nothing in relation to device connection.
In Microsoft community some one has reported being able to retrieve data fro the locked drive using UBCD software and Parted Magic.
Anyone has experience with UBCD?
I have been trawling through posts on Windows 10 hoping to find a way to reach into the external HDD but without any success. However whenever I turn on the PC either with Leap 15.2 or Windows 10 I switch on the affected HDD hoping for a miracle.
Today while working with Windows 10 the drive suddenly showed signs of life! And I could access the data. After shutdown restarted with Leap and the HDD was still working. No idea what happened.
