I've just installed Boot Camp on my Mac Pro (2013) - Windows 10 Pro x64, fully updated to the Creators Update. I've also got a Thunderbay 4 mini which houses a Softraid RAID 5 array which I use in Sierra.
If the Thunderbay is connected to the Mac Pro when I boot into Windows, I get an error and Windows won't boot. If I disconnect the Thunderbay, Windows boots fine.
If I install Macdrive, Windows will boot fine even with the Thunderbay connected, but Macdrive doesn't actually support RAID 5 arrays as yet so I'd rather not have it installed at this stage because there's no Mac drives I want access to in Windows, other than that RAID 5 array.
Is there anything I can do to prevent Windows producing these errors with the Thunderbay connected on boot, without needing to install Macdrive?
Sorry no.
We understand that MacDrive is going to try to do a RAID 4/5 in the future and we will help them if they have any problems/questions.
This is a Windows problem for not booting, I don't think we can address that.
We would like to have a long term solution, also
Sorry no.
We understand that MacDrive is going to try to do a RAID 4/5 in the future and we will help them if they have any problems/questions.
This is a Windows problem for not booting, I don't think we can address that.
We would like to have a long term solution, also
In terms of Macdrive's ETA for RAID 4/5 support, it seems like it's not much of a priority - just got this reply from a support ticket:
We have discussed adding additional support for other SoftRAID volumes, but at this time there is no ETA on when that will be added to MacDrive.
In terms of this actual boot bug, simply having Macdrive (or Paragon HFS+) installed seems to fix the boot issue so I may as well just roll with that.
I've just installed Boot Camp on my Mac Pro (2013) - Windows 10 Pro x64, fully updated to the Creators Update. I've also got a Thunderbay 4 mini which houses a Softraid RAID 5 array which I use in Sierra.
If the Thunderbay is connected to the Mac Pro when I boot into Windows, I get an error and Windows won't boot. If I disconnect the Thunderbay, Windows boots fine.
If I install Macdrive, Windows will boot fine even with the Thunderbay connected, but Macdrive doesn't actually support RAID 5 arrays as yet so I'd rather not have assurance chien it installed at this stage because there's no Mac drives I want access to in Windows, other than that RAID 5 array.
Is there anything I can do to prevent Windows producing these errors with the Thunderbay connected on boot, without needing to install Macdrive?
Hello!
I'm a new user here and this is my first quote so i want to say that this is intersting.
Thanks!
This is actually a Windows bug, which we cannot prevent. What MacDrive is doing is putting a driver into Windows so the disks are recognized, even though it cannot mount the RAID 5 volume at this time.
Until we or MacDrive writes a windows driver to mount the volume, they cannot show up in Windows.
This is something we want to support, however, so some day, it will happen.

