Unsolved
This post is more than 5 years old
1 Rookie
•
18 Posts
0
4604
September 20th, 2005 21:00
Problem trying to get disk image from 2450 PER3/Si Raid5
I have Symantec Ghost 2003 and I'm trying to back up my Win2K ADVSRV OS to a ghost image on a USB HD. I looked around a bit and realize that Symantec states that Ghost 2003 doesn't "support" imaging RAID drives, but I don't quite believe it.
I have the A09 BIOS and the 2.8.0... firmware and I have the ASPI drivers ELITEAPI.SYS (file date: 11/12/2003) and MEGASPI6.SYS (file date: 6/21/2000) from the DOS ELITE Dell Diagnostic Disk (EDD) v5.30.10.
I took the device command line from the config.sys on the EDD for each driver and added it (and the files and their paths) to the config.sys on my ghost boot disk.
DEVICE = percraid\eliteapi.sys /M
DEVICE = percraid\MEGASPI6.SYS /a
However, when I boot to the disk when the driver loads for the perc3/si it displays each of the drives but shows them as NOT belonging to a container (which they are, Raid5 running server). Also, once Ghost starts, I only see one drive and since the USB drive is almost the same size as the system drive, the way it's displayed, it's difficult to tell which it's seeing.
Has anyone else out there gotten this to work? What am I missing? Please help. TIA
0 events found
No Events found!
cordia-kent
1 Rookie
•
18 Posts
0
September 21st, 2005 18:00
Well, I'll update you all in case someone else out there is unfortunate enough to be in the same situation as myself.
I removed the switches in the device reference lines of the CONFIG.SYS file on the GHOST Boot Disk (GBD). So, now when the system (a 2450 with PERC3/Si in RAID5) boots from the GBD it loads USB drivers, it sees/installs the external USB drive and then loads the RAID drivers and recognizes the individual drives in the enclosure and correctly notes that they are part of a container.
However, when the included utility "GUEST.EXE" is loaded - purportedly to assign drive letters to the USB device drives - the system hangs. It doesn't freeze, it just never progresses from that point.
"Finding drive letters for your Iomega devices..." or the like is the last thing you see.
SO I echo'd out guest.exe from the Autoexec.bat file on the GBD to check and sure enough GHOST loads. GHOST can see the NTFS system drive on the RAID and it sees the USB "disk". However you can't use it as an image destination since no DRIVE got MAPPED to your partition ON the disk.
So to I exit ghost to try to map the USB disk's partitions to drive letters using "GUEST.EXE" and the behavior is identical - it states it's finding drive letters and never progresses beyond that point.
I'm SO close to getting it to work I can smell it... kinda like a burnt out resistor.
I believe that there may be an issue with Ghost loading ONLY the driver to see NTFS or (exclusively) the driver to mount USB drives but not both.
PLEASE, if anyone out there has a way around this, or a manner by which to map the USB drive other than the included "GUEST.EXE" let me know. You'll be greatly rewarded in your next existence.:smileywink: