[SOLVED] Other internal HDD has become inaccessible

pianomoverjones · 06-29-2018, 03:53 PM

Evening all,

Thanks for your help with my previous problem. Something else has now popped up. My second HD which up until yesterday could be read is now giving me an error when I try to access it via Linux Mint Cinnamon. This 2nd HD drive has Win10 on it and Win 10 will boot and work fine. But for some reason I can on longer access it from Linux. Error message below:

Click image for larger version

Name: HD error.jpg
Views: 33
Size: 61.2 KB
ID: 28025

Any ideas?

Thanks

jsbjsb001 · 06-29-2018, 04:28 PM

Quote:

Originally Posted by pianomoverjones

Evening all,

Thanks for your help with my previous problem. Something else has now popped up. My second HD which up until yesterday could be read is now giving me an error when I try to access it via Linux Mint Cinnamon. This 2nd HD drive has Win10 on it and Win 10 will boot and work fine. But for some reason I can on longer access it from Linux. Error message below:

Attachment 28025

Any ideas?

Thanks

Yup, exactly what you're error message is telling you... start Windows and then fully shut Windows down. One sure fire way; Choose the shutdown option IN Windows so it powers off your system and then turn your system back on and start it into Linux.

Hopefully that clears it up for you.

syg00 · 06-29-2018, 05:35 PM

As logical as it seems that won't solve the issue. M$oft use fast start by default (?) so you have to force it not to hibernate. Either change the EFI option or you can set it from a cmd session.

Edit: found this - seems to cover things. I've used the command usually.

rknichols · 06-29-2018, 05:50 PM

There are actually three states to consider:

Hibernated. This is the most volatile state. When Windows comes back up, your desktop and running apps will be restored to the same state they were in before.
Shut down, but with "fast startup" enabled. Windows will come back up as from a full reboot, but the filesystem is left in at state from which Windows can come back up with minimal initialization. Linux might allow read-only access to the filesystem in this state.
Fully shut down with "fast boot" disabled. This is the only state in which another OS can have full access to the filesystem.

If you tell Windows to "Restart" rather than shut down, it always does a full shutdown regardless of the "fast boot" option setting. Telling Windows to restart and then directing the reboot into Linux is another way to ensure that the NTFS filesystem is in a safe state.

pianomoverjones · 06-30-2018, 03:56 AM

Thanks everyone. A full shutdown and boot up has solved this problem. I'll look out for it in the future.