MSI K8N Neo RAID problems...

NStriker

Limp Gawd
Joined
Feb 22, 2001
Messages
162
I'm having some difficulty with my latest upgrade. I grabbed myself an MSI K8N Neo Platinum and an Athlon 64 DTR (wanted to be sure to get the CG revision core and no heat spreder for better cooling ;)). It all went together pretty well after a modification to the backplate to allow my Koolance waterblock to sit properly on the lower core of the DTR.

Anyway, I made a Ghost 2003 image of my old 2x40GB Maxtor RAID 0 array (used the Highpoint 374 on my old Abit IT7), and hooked those Maxtor drives up to the K8N using SATA to PATA converters (Highpoint Rocketheads). No problems yet, though it's starting to look an extra bit messy in my case with all that. :p

Anyway, the BIOS detects the drives fine and I set them for RAID usage. I then configure a RAID 0 array in the RAID BIOS and that works fine. Now comes the problems.

Problem 1) Ghost doesn't see a single 80GB array. It sees a single 40. If I use FDISK and make a partition (though it misreports the free space), Ghost will see an 80GB partition on a 40GB drive and let me start the restoring process, but eventually fails.

Problem 2) Booting from my Win2K with SP4 integrated CD, pressing F6 and installing both nForce drivers from the floppy causes the install to bluescreen after the "Starting Windows 2000" message. This is before you can even select to setup or repair Windows. It just churns the drives a few minutes (which it doesn't normally do during this early phase) and then BSOD with DRIVER_IRQ_NOT_LESS_THAN_OR_EQUAL. Same thing with WinXP with SP1 CD, though I don't thnk it actually gives me any real error message.

I'm going to be tinkering at it for a while yet. Any ideas?

-NStriker
 
If anyone cares, I have an update. Seems that, for some reason, the RAID functions oddly when using the SATA converters. Pluging the drives directly into the IDE ports works. Hopefully I can move them back to SATA after I have Win2K up and running, because I don't want my CD-RW and DVD on the same channels as the array, aside from cable nightmare that would create in my full tower.
 
Ahh, ive had problems with Raid setups in the past, seems like you never have the same problem twice hehe, Hope everything works out.
 
Thanks.

Well, it looks like the IDE thing only helped with getting Win2K's install not to lock up and to see the array. That'd be great, if all my info weren't in a Ghost image.

Ghost's knowledgebase says it doesn't support RAID. Great. It imaged it off the old controller with no problem. I guess Highpoint just did their RAID differently. It seems that with the nForce controller, I have use the -noide switch to force drive access via the BIOS for Ghost. Otherwise, it does direct IDE access and doesn't see the array. The problem with that? I'm currently getting about 100MB/s transfer rate and it's going to take over 7 hours for it to restore. I won't even know if it worked until then. Great.
 
Good luck with getting that ghost image to apply - but even if you can't (Ghost is a bitch with regard to RAID and computers in Domains)- there's a way to get your data back out of the image. Ghost Explorer lets you brose through a .GHO file like windows explorer on a HD. It's slow - but effective.

Did you ghost to CD? Compression used?

In general though - Ghost captures bit/byte level info - which makes copying RAID arrays between controllers generally impossible - because of the different ways controllers do things. If you put the drives in with the same controller you used to make the image you should find that you can restore them.
 
Yeah, I just thought about Ghost Explorer. I'll use it if I must, but I'm going to wait out this transfer first. If I don't have to reinstall all my programs, I'm not gonna. But if I must, I should now be able to install Windows on the array and then get all of my files from the image file.

Luckily my Aunt's computer broke at the same time I was upgrading, so I was able to use her near-empty HDD to store my image in a file. Tons faster than burning it (at least it would be, in normal circumstances). I didn't use compression, 'cause there was just enough space to dump the file without it.

Maybe I'm wrong, but I kinda thought that unless you told it to a raw dump, Ghost pretty much just copied the file system layout and then recreates it all. Including fun stuff like MBRs and whatnot. I guess we'll see in 7 hours, though, eh? :D
 
Back
Top