I got one of those 2.5INCH HDD caddies that mount in place of optical drives. Mounted under Windows 10, It boots fine and works fine. but after doing I/O operations and rebooting for whatever reason. It starts sabotaging the booting process. it takes Windows too long to boot. after it finally starts up. task manager shows disk activity for that drive as 100% 0KB read and 0KB write. and can't be accessed by file explorer. and built int disk management utility gets stuck while trying to read my partition tables.
It can boot normally after pulling out the caddy
OR by rebooting into linux, linux can boot just fine, access the HDD just fine and do I/O just fine.
after doing and I/O operations on linux and rebooting back into Windows 10. Windows can finally boot up successfully and do I/O normally AND does not show 100% disk activity for no reason.
HDD is 2.5inch seagate. GUID partition table with only 1 NTFS volume (formatted yesterday, hardly anything on it).
No OS' are installed on it. Windows is installed on a separate SSD and linux boots from a USB thumb.
So, can there be any explanation for what's going on? what does Windows do to leave this volume in such state where it prevents Windows from working properly from here until the disk is accessed by a linux OS?
are there any means of fixing this>
It can boot normally after pulling out the caddy
OR by rebooting into linux, linux can boot just fine, access the HDD just fine and do I/O just fine.
after doing and I/O operations on linux and rebooting back into Windows 10. Windows can finally boot up successfully and do I/O normally AND does not show 100% disk activity for no reason.
HDD is 2.5inch seagate. GUID partition table with only 1 NTFS volume (formatted yesterday, hardly anything on it).
No OS' are installed on it. Windows is installed on a separate SSD and linux boots from a USB thumb.
So, can there be any explanation for what's going on? what does Windows do to leave this volume in such state where it prevents Windows from working properly from here until the disk is accessed by a linux OS?
are there any means of fixing this>