It doesn't seem likely that the file system is the culprit here. You may want to double-check the settings on the Seagate drive itself, as well as the settings in the BIOS for the RAID controller, to make sure nothing is amiss. For instance, if the Seagate drive is set to the wrong device ID for booting, that might explain it.
Dig deeper on Windows Operating System Management
Related Q&A from Serdar Yegulalp, WinIT
Frustrated admins have been dealing with extend.dat error messages since Outlook 97. Our expert sheds some light on this all-too-common Outlook error.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.