Pulling an image of a RAID 1 Drive



  • We have a situation where a system that is using a RAID 1 is on it’s lst leg. We have backups of the system but we were wanting to grab an image of it to use for some testing. It is an old system and there is software on it that we no longer have the install media or license key for and are unable to locate the license key even through the company that we purchased it from all those years ago.

    I tried booting to FOG from the machine but it was having issues getting the undionly.kpxe, so I pulled the drive out and connected it to another machine and was able to get FOG to Image it, but it appears that due to it being in a RAID it is looking for either the RAID Card or the other drive.

    Anyone have any experience pulling an image from a RAIDed machine?

    Thanks!



  • Thanks, I will test this out incase this issue comes up again. My colleague was able to get a license from a reseller of the old application.


  • Moderator

    I’ve had to switch SATA mode a few times in the past. This article covers what you need to do:

    [URL=‘http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation’]http://www.overclock.net/t/1227636/how-to-cha[/URL][URL='http://www.overclock.net/t/1227636/how-to-change-sata-modes-after-windows-installation’]nge-sata-modes-after-windows-installation[/URL]

    So I would remove the referenced registry entries, then shut down and upload an image. That way, when you start the source machine back up, it continues to work as is. But when you push the image to a new machine, Windows sees the trigger to recheck what storage driver to use. Just FYI, that first boot on the new machine could take a while as Windows sorts out its driver business.


  • Developer

    [quote=“Tim.Trageser, post: 47298, member: 29173”]Yes I verified that it was RAID 1 through the RAID controller. I may try undionly.kkpxe. Basically it pulled the image fine into FOG, but when I push the image to a Test system it Blue Screens with INACCESSIBLE_BOOT_DEVICE.[/quote]

    i don’t remember the exact details on what you need to do for this, but as i recall, this is because the hardware drivers that windows thinks it needs are being loaded. but because the hardware has changed, so what is actually needed is not. what drivers it loads on system startup are defined in the registry and can be changed with offline registry edits. the tricks used to switch a computer from ide mode to ahci mode are relevant here. you need to tell windows to load a standard hard drive controller at system startup, it thinks it only needs a raid controller.


  • Moderator

    [quote=“Tim.Trageser, post: 47298, member: 29173”]Yes I verified that it was RAID 1 through the RAID controller. I may try undionly.kkpxe. Basically it pulled the image fine into FOG, but when I push the image to a Test system it Blue Screens with INACCESSIBLE_BOOT_DEVICE.[/quote]

    Maybe double check the mode the HDD was operating in on the BIOS of the computer it came from, then try to set those options on the system you just imaged to.

    If that fails, you could try windows repair / recovery ?



  • Yes I verified that it was RAID 1 through the RAID controller. I may try undionly.kkpxe. Basically it pulled the image fine into FOG, but when I push the image to a Test system it Blue Screens with INACCESSIBLE_BOOT_DEVICE.


  • Moderator

    Hopefully it’s RAID 1, and not 0, 5, or 10.

    I don’t see why it wouldn’t pull an image normally if the drive has been placed into a regular computer. It’s a SATA drive, right?

    Maybe the RAID controller has some proprietary stuff going on with how the data is organized on the drive?

    Perhaps try undionly.kkpxe ?


Log in to reply
 

449
Online

39174
Users

10821
Topics

102951
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.