Acronis Rescue Media Builder does detect Intel Z77 Raid 0 incorrect
Hi,
I am using the Acronis 2014 Premium version (build 6614).
I use it under Windows 7 x64.
My system has an Asus P8Z77V board with Intel Z77 chipset.
I have a simple SSD and hard disc for regular use (system&data).
To use as backup space I have in addition two WD 3TB discs which I did setup as a hardware Raid-0 (so they span a 6TB volume).
On the 6GB volume there is just one single basic primary NTFS partition.
I can use the 6TB space for backup from Acronis out of Windows.
However when I boot the rescue media builder (matching above Acronis version) then the rescue media builder does not properly detect the hardware raid.
It detects all of the regular drives and partitions (system&data) but not the Raid-0 hardware stripe. All it detects is an additional unformatted/"unsupported" disc with about the size of 1.458TB.
When I switch to the command line I see that the rescue media builder did use the device mapper to address the raid.
kpartx -l /dev/mapper/isw_bafjacfacb_WDRAID shows
Alternate GPT is invalid, using primary GPT.
isw_bafjacfacb_WDRAID1 : 0 262144 isw_bafjacfacb_WDRAID 34
isw_bafjacfacb_WDRAID2: 0 3130855424 isw_bafjacfacb_WDRAID 264192
Any idea how to get rescue media builder so i see the entire 6TB hardware raid0 stripe ntfs partition?
with best regards,
- Log in to post comments
Yes - native motherboard raid which is not really a "hardware" raid. Sorry for the confusion. The rescue media linux does use the dmraid isw (Intel software raid) for it as the "driver" has to do all the raid "calculations".
The harddisk is GPT format - yes. Only GPT format supports 6TB volume with a 6TB (basic windows) partition on it.
MBR format only supports 2TB partition/4TB drive.
Though GPT/MBT describe the partitioning - not the filesystem. So stripe "raid" partition in question is GPT/NTFS.
My best guess is that dmraid (or some other component of the rescue media linux busybox) also runs into a 4TB limitation (similar like the MBR) and has a counter overflow and therefore cannot map the entire 6GB.
- Log in to post comments
Diffie,
You just might have something there with the 4GB limitation. Do or are you using Intel software raid on your system? There could be a conflict of drivers if you are using say a brand X software raid then trying to restore with the Intel drivers. Seems like I read somewhere in this forum about a way to use a script to add drivers to a restore for such things as this. You may want to do some research here and see what you can uncover. You never know you might get lucky!
- Log in to post comments