Unsolved
1 Rookie
•
3 Posts
•
5 Points
0
16
June 3rd, 2026 21:43
Linux-based imaging works with RAID ON/IRST when it "shouldn't"??
PROBLEM/OBJECTIVE: Solve mystery of why my preferred drive imaging/restoration method has always been successful, when I now read that it should never have worked. Then determine if I will be able to keep using that method on the new computers I'll be getting.
EXISTING COMPUTERS: Dell Latitude 6430u laptops with single SSD and Optiplex 9010 towers with single HDD. Business class, so came in RAID ON mode with IRST drivers. Legacy BIOS, not using secure boot or Bit Locker. Originally had Windows 7 Pro and were later upgraded to Windows 10 Pro.
PREFERRED IMAGING/RESTORATION METHOD: Cold offline imaging using only the generic Linux-based bootable rescue media from a backup program like Acronis True Image. (I don't like leaving backup programs installed, so I create rescue media once and then roll back to uninstalled state.)
I'll be picking out new Dell computers soon, only for personal use with single drives, but business-class models for build quality. So they will again come in RAID ON mode.
The mystery is that info I find in searches online is telling me that not only would generic Linux-based rescue media not work with new computers that are in RAID ON mode, but that it shouldn't have worked with my existing RAID ON/IRST driver computers either. Says the generic media wouldn't be able to see the internal drive, and that I'd either need to switch mode to AHCI or create the version of rescue media that incorporates WinPE/WinRE. But I've imaged and restored many times with the generic media and have never had to take any of those extra steps. Why??
Even though there are workarounds such as the above, first I want to determine why this very simple combo has always worked for me in the past, so I can figure out whether I may indeed be able to keep using it. Time is very short and I'd love to keep this part super simple. (It would be ideal if I could even keep using the 2019 version of Linux-based bootable rescue media that I already have, so I wouldn't even have to temporarily install something different.)
Thanks for any insights on this.
anne_droid
5 Journeyman
•
1.6K Posts
•
6.3K Points
0
June 4th, 2026 09:58
Hi
The internet reports (all gobble-degook to me actually)....
Linux imaging on RAID ON/IRST usually works because Linux can read Intel RST metadata and assemble the array with mdadm-compatible tools, so the OS sees a RAID volume rather than plain AHCI disks.
Intel’s Linux paper says the recommended Linux software RAID stack is md RAID, and that Intel enhanced it to support RST metadata/OROM; it also notes that boot and assembly happen by loading the MD RAID driver and then assembling the volume from the metadata on disk.
What is happening
With RAID ON enabled, the controller presents disks using Intel RST metadata, and Linux can often assemble that configuration during boot or from a live environment using mdadm. Intel describes this as an OROM/BIOS layer exposing the RAID volume, then Linux loading the MD RAID driver and assembling the array before mounting the filesystem.
Why imaging tools still work
Many imaging tools do not need to understand “Intel RAID” directly if the Linux environment has already assembled the array. In that case, the imager just sees a normal block device like
/dev/md126or a mounted filesystem and copies it like any other disk or volume. That is why a Linux-based imaging workflow can succeed even when the storage mode is RAID ON/IRST.Which software to use
For Linux-side RAID assembly, the core tool is mdadm; Intel’s paper specifically recommends MD RAID for Linux RST support. For imaging after assembly, common choices are Clonezilla, dd, partclone, or a forensic imager, but the important part is that they run on top of the assembled md device rather than the raw member disks.
Intel also notes that Linux installers like Anaconda and YaST use mdadm to assemble such arrays.
Practical note
If you are dealing with a Dell system in RAID ON mode and want reliable imaging, the safest approach is usually to boot a Linux live environment, confirm the array assembles, and image the resulting
/dev/md*device rather than individual member disks. If the array does not auto-assemble,mdadm --examine,mdadm --assemble, and/etc/mdadm.confare the usual recovery path.Important caveat
This is not the same as imaging a true hardware RAID controller; Intel RST is a firmware/software RAID scheme, and Linux support depends on mdadm-compatible metadata being readable. Intel notes that MD RAID supports RST metadata, while older DM RAID support is limited and effectively deprecated.
The shortest answer is: use a Linux live environment plus mdadm, then image the assembled RAID volume with your preferred imaging tool.
mia777
1 Rookie
•
3 Posts
•
5 Points
0
June 4th, 2026 20:53
@anne_droid
Thank you very much, that gave me lots of new terms and concepts to try to digest... Very interesting, even though much is gobble-degook to me also!
My initial mission has been to find out whether my exact current imaging/restoration method would continue to work on my forthcoming Dell business computers with Windows 11 that will also come in (unwanted) RAID ON mode, and I gather that the bottom line is No, it won't. But then the following occurred to me:
When I run into the answer that cold offline imaging with generic Linux-based bootable media such as from Acronis True Image won't work on FakeRAID/IRST (even tho it always has for me), what it usually says will happen is that "Drives will likely appear as separate, individual disks rather than a combined RAID volume."
However, maybe that result is exactly what's wanted in my case, since I always have and will continue to be using a single drive in each machine, not utilizing any form of RAID? So I indeed only need the imaging software to see an individual disk? Maybe that's the actual reason why this exact imaging & restoration method has always worked for me, when it "shouldn't" without jumping through additional workaround hoops? (My existing old machines all use SATA III, in case that makes any difference.)
Per your caveat and MD RAID info, in case the above isn't the ticket and I do need to use something different, I searched whether Rescuezilla has MD RAID support, and apparently it does. (Thought that might be easier for me to understand than Clonezilla.)