J
julian8888888
Windows XP Pro
AMD Athlon 64 3200+ Venice 2.2GHz 512KB L2 Cache Socket 754 Processor
- OEM
1GB RAM (2 sticks 512 MB Kingston 3700)
MSI Neo Platinum K8N NVIDIA nForce 3 250Gb chipset
2 Samsung Spin Point 2004C (200GB, 186 GB effective)
1 500 GB WD Caviar 16SE
Hi all, I tried moving a RAID 0 striped array to another motherboard.
The motherboard I currently have this RAID 0 on is the one listed
above using the nForce 3 chipset. The one I wanted to move the array
to is a Gigabyte K8 Triton with the nForce 4 chipset.
I found this wasn't possible since the new motherboard uses different
RAID drivers although the chipset manufacturer is Nvidia for both; So
I moved the RAID 0 array back to the MSI board it was originally
installed and working on as the OS drive.
However, instead of throwing out the spare parts of my older system I
bought another AMD socket 754 processor ( AMD Athlon 64 3200+ Venice
2.2GHz 512KB L2 Cache Socket 754 Processor - OEM) to use with the old
system. So the system is almost the same as before aside from the
processor and RAM and added WD drive as the OS disk. I plugged the
hard drives into the same SATA inputs as before and tried both
combinations (drive 1 to sata 3 and sata 4, drive 2 to sata and sata
4) of input arrangements in case it mattered.
The difference, I just realized, is that these drives used to be the
OS drives and startup drives and now I'm asking them to be the
secondary drives. I have already added the WD Caviar 16SE 500GB as
the main startup drive for this system. I just wanted to hook up the
RAID 0 array to back up some data before I move them as the OS drives
for my new system. So one thing I haven't tried yet is to use the
RAID 0 as the startup drives and unplug the WD drive. I will try that
now and see if they will boot without error. Typing this up made me
remember the differences.
Currently, this is the error I get at startup:
Warning: Have option ROM cannot be invoke (Vendor ID:10DEh, Device ID:
00Fh) Nvidia RAID IDE ROM BIOS 4.81 Copyright (C) 2004 Nvidia
Corporation
AMD Athlon 64 3200+ Venice 2.2GHz 512KB L2 Cache Socket 754 Processor
- OEM
1GB RAM (2 sticks 512 MB Kingston 3700)
MSI Neo Platinum K8N NVIDIA nForce 3 250Gb chipset
2 Samsung Spin Point 2004C (200GB, 186 GB effective)
1 500 GB WD Caviar 16SE
Hi all, I tried moving a RAID 0 striped array to another motherboard.
The motherboard I currently have this RAID 0 on is the one listed
above using the nForce 3 chipset. The one I wanted to move the array
to is a Gigabyte K8 Triton with the nForce 4 chipset.
I found this wasn't possible since the new motherboard uses different
RAID drivers although the chipset manufacturer is Nvidia for both; So
I moved the RAID 0 array back to the MSI board it was originally
installed and working on as the OS drive.
However, instead of throwing out the spare parts of my older system I
bought another AMD socket 754 processor ( AMD Athlon 64 3200+ Venice
2.2GHz 512KB L2 Cache Socket 754 Processor - OEM) to use with the old
system. So the system is almost the same as before aside from the
processor and RAM and added WD drive as the OS disk. I plugged the
hard drives into the same SATA inputs as before and tried both
combinations (drive 1 to sata 3 and sata 4, drive 2 to sata and sata
4) of input arrangements in case it mattered.
The difference, I just realized, is that these drives used to be the
OS drives and startup drives and now I'm asking them to be the
secondary drives. I have already added the WD Caviar 16SE 500GB as
the main startup drive for this system. I just wanted to hook up the
RAID 0 array to back up some data before I move them as the OS drives
for my new system. So one thing I haven't tried yet is to use the
RAID 0 as the startup drives and unplug the WD drive. I will try that
now and see if they will boot without error. Typing this up made me
remember the differences.
Currently, this is the error I get at startup:
Warning: Have option ROM cannot be invoke (Vendor ID:10DEh, Device ID:
00Fh) Nvidia RAID IDE ROM BIOS 4.81 Copyright (C) 2004 Nvidia
Corporation