Unsolved
This post is more than 5 years old
4 Posts
0
8738
April 2nd, 2004 16:00
Wierd happenings with RAID array, Think it's hosed?
System: Precision 420 WS
SCSI: Adaptec ARO-1302 (64MB cache) config'd as RAID-0
HDs: Twin Fujisu 17GB Ultra160 drives, Using SCSI ID 0, 1
O/S: WinXP Pro (booting from the array)
Initially I setup the array and called it "ARRAY0" I've been running this setup well over a year now without a hitch until rescently (I just used the Win2000 driver with installing XP)
Yesterday started up the machine and it kept spontaneously rebooting. The system would display the black WinXP splash screen, a quick 1/4 second flash of the "blue screen of death", then a sudden reboot. Tried booting with each option in the WinXP startup menu (safe mode, safe mode with network, etc) all had the same result.
DLed and ran the ARO-1302 config utility from the floppy and noticed I now have two arrays!
Array1: Name: "ARRAY0" (the one I created)
Member: 0 - DRIVE: Fujistu Ultra160 - SCSI ID: 0 - Status: OKAY - Size: 17334GB
Member: 1 DRIVE MISSING
Array2: Name: "ARRAQ0"
Member: 0 DRIVE MISSING
Member: 1 - DRIVE: Fujistu Ultra160 - SCSI ID: 1 - Status: OKAY - Size: 17334GB
It appears the two drives have become separated somehow. The only option I currently have is delete the array, create a new one. But I don't want to do that unless I absolutely have too. (have important data that hasn't been backed up for a while)
Has anyone seen this happen before? And, can something like this be fixed / recovered?
Think the problem lies with the RAID adapter or the drives?
At this point, I'm not sure what to think.
Thanks in Advance,
-Mike
Malinim
3 Posts
0
April 2nd, 2004 18:00
Yeah, that same thing happened to me yesterday. I upgraded fromWindows 2000 server to Windows 2003 Enterprise Server, adn it kept rebooting, and saying about the AAA-UDMA driver DMA page fault, or something like that. So I pulled the card, finished the install, and put the card back in and it was OK. But I looked and found my drive space had tripled. I opened the case cover, and found six more drives in there that weren't there before, go fiquire...... It must have downloaded the drives right from Maxtor into the server. Cool. Now I have lots of space.
Malinim
3 Posts
0
April 2nd, 2004 18:00
mjm0771
4 Posts
0
April 5th, 2004 13:00
Problem Solved:
I deleted both arrays using the RAID configuration utility. Then I created a new RAID-0 using all the same parameters used originally and called it 'ARRAY0' (same as the original). When promted, I SKIPPED initialization and formatting.
So now the container was bebuilt, but I had another issue, the partition was unaccessable. I reconfigured the
system to boot from an IDE drive and installed a fresh copy of WinXP there.
After the installation of XP was complete, I loaded the AR-1302 drivers and a data recovery program.
Since the file system and data structure was still intact, recovery was a snap.
After recovering the stuff I needed, I rebuilt the array as a RAID-1 and now serves as a FAT32 storage drive
for the 'My Documents' folder. (I did this using TweakUI for WinXP)
It also now houses a Symantec Ghost image for my new C:\ drive for when it decides to break.
Only thing left to do is test the System Restore using a Ghost boot disk (to verify the DOS version of Ghost can see the Array drive that the Ghost image is located on)
-Mike
Malinim
3 Posts
0
April 5th, 2004 13:00