Using WindowsXP to Make RAID 5 Happen

By published

Unleashing RAID 5 Under WindowsXP

Limbering up WindowsXP in order to run RAID 5 requires a hex editor (e.g. Ultra Edit) as well as your WindowsXP CD. First of all we need to copy some files into a temporary folder:

C:\windows\system32\drivers\dmboot.sys

C:\windows\system32\dmconfig.dll
C:\windows\system32\Dmadmin.exe

Next, these files need to be opened using your hex editor:

dmboot.sys:
Before:0000f1f0h: 74 00 54 00 79 00 70 00 65 00 00 00 57 49 4E 4E ; t.T.y.p.e...WINN0000f200h: 54 00 00 00 53 45 52 56 45 52 4E 54 00 00 00 00 ; T...SERVERNT....After:0000f1f0h: 74 00 54 00 79 00 70 00 65 00 00 00 53 45 52 56 ; t.T.y.p.e...SERV0000f200h: 45 52 4E 54 57 49 4E 4E 54 00 00 00 00 00 00 00 ; ERNTWINNT.......
dmconfig.dll:
Before00005140h: 4C 41 4E 4D 41 4E 4E 54 00 00 00 00 53 45 52 56 ; LANMANNT....SERV00005150h: 45 52 4E 54 00 00 00 00 57 49 4E 4E 54 00 00 00 ; ERNT....WINNT...After00005140h: 4C 41 4E 4D 41 4E 4E 54 00 00 00 00 57 49 4E 4E ; LANMANNT....WINN00005150h: 54 00 00 00 00 00 00 00 53 45 52 56 45 52 4E 54 ; T.......SERVERNT
dmadmin.exe:
Before00001c30h: 73 65 72 76 65 72 6E 74 00 00 00 00 6C 61 6E 6D ; servernt....lanm00001c40h: 61 6E 6E 74 00 00 00 00 50 72 6F 64 75 63 74 54 ; annt....ProductTAfter00001c30h: 77 69 6E 6E 74 00 00 00 00 00 00 00 6C 61 6E 6D ; winnt.......lanm00001c40h: 61 6E 6E 74 00 00 00 00 50 72 6F 64 75 63 74 54 ; annt....ProductT

The original files in Windows' System32 directory need to be replaced by our modified versions now. However, simply exchanging the files by overwriting them will cause Windows to take notice, which eventually causes Windows to restore its original files by using backup files.

If your system drive is running FAT32, simply go ahead and boot any DOS operating system in order to overwrite the files manually. Since FAT32 does not cater for security at all, we do not recommend using this file system.

In an NTFS environment you will have to boot from the WindowsXP CD and launch the recovery console. This can be achieved by pressing 'R' in the first selection screen. At this point, you should have copied the modified files onto a floppy disk.

Let's go into the Windows directory first:

C: [ENTER]

cd\windows [ENTER]

Now, copy the files one by one by using the following commands. All files are located in two different directories each!

copy a:\dmboot.sys system32\drivers

copy a:\dmboot.sys system32\dllcache
copy a:\dmconfig.dll system32
copy a:\dmconfig.dll system32\dllcache
copy a:\dmadmin.exe system32
copy a:\dmadmin.exe system32\dllcache

Patrick Schmid
Topics
Storage
19 Comments Comment from the forums
  • Can I grow an array made this way? That is, add another disk without having to lose the data currently held on the raid?
    Reply
  • op365
    From past experience with Hardware RAID, you would have to first backup your data and then break the RAID and put in the higher capacity drives and create a new container.
    The feature that you want/asking about is called X-RAID
    Reply
  • micokeman
    I have used this hack and it works, but there are some problems that can occur. First of all, if you do this on SP2 and upgrade to SP3, XP will no longer see the RAID5 drives. Uninstalling SP3 allowed me to regain access to the RAID5 devices, but I would continuously get blue screens. After a repair of XP I no longer got blue screens, but I could also no longer see the data on the RAID5 drives. I suspect XP saw them as foreign drives and XP can't import foreign RAID drives!!! Yes, the hack works, but be aware that a service pack upgrade might render the data inaccessible.
    For those of you wondering, I was able to get my data back by installing Server 2003 and importing the RAID5 drives. No data lost, WHEW! You can also use a trial Windows Server 2003 to access your data for 30 days. Get the download from here.
    Reply
  • This works with SP3 and also with the x64 version of XP.

    To get it to work with SP3, you just have to redo the changes above.

    To get it to work with x64, just locate those same strings in the files and apply the changes. Notice how the changes are only swapping the locations of the words SERVERNT and WINNT. I'd post the exact changes here, but it would take forever to type out all of those hex values. UltraEdit doesn't seem to allow one to copy the hex data to the clipboard.

    Reply
  • I have also notice the problem when upgrading to SP3 that the RAID no longer works. Even after changing the files (dmboot.sys, dmconfig.dll, dmadmin.exe) on the SP3 release I still could not get RAID to work correctly. I have taken the 3 files from a system running SP2 and copied them to the system running SP3. It looks like the SP2 files work on SP3 but I have only had the system running for about a week.
    Reply
  • SlAoTkAiN
    I was lucky and installed sp3 and then used the hack and got a the raid working. The only problem I'm seeing is that XP doesn't start up the raid at boot. I have to go into manage and re-activate the drive. Anyone have any suggestions?
    Reply
  • I got it working again after migrating from sp2 to sp3, but I have to go into manage and re-activate the drive every time I reboot.
    Anyone has a solution for this?
    Reply
  • tiborakos
    After spent a week wondering what went wrong with my XP SP2 raid5 setup...i fell into this, and remembered i hd installed SP3 as well!!!
    Is there a way to get those SP2 files from somewhere please? Else i think i might try the server2003 solution.
    As for the "re-activate the drive every time I reboot" it has happened to me in my old PC after the mod, but could not find a way to solve it
    Reply
  • cwilk
    I am lost with the hex editing. I tried a fix from Randem Systems but that doesnt work. Anyone have a copy of the files i can get?
    Reply
  • tiborakos
    Cannot help with the files unless you want mine. btw, i managed to get the Raid5 volume working again, after uninstalling SP3 and getting back to SP2.
    What if i copy the files, install SP3 again and just replace them with the current ones? Do you think it might work? Or i will end up needing "reactivate the drive every time i reboot" ?
    Reply