Hacked my hacked 2000>4000:fixed with question
I've been playing around with a 2000 (ser# 38XXX hardware version 2.0) for a while now configured as a 4000.
Operating system was 3.4803 with the drives set up as M/S (mix of 40GB quantum, IBM, Maxtors of different vintages). Yeah, I know, this was just a test.
Memory boosted to 128MB, standard IDE cables, external ATX power supply for drive cage and cooling fans controlled by relay powered by the snap's 12vt line. Raid 5 was functioning well thoughout 100GB of file transfers over months of trials.
I updated to 4.0855 and again to 4.0860. I lost 2 of the drives and the raid5 array was gone.
After testing all the drives with the manufacturer's utilities and finding no problems I thought about how I hacked the 2000 into a 4000 in the first place. I only changed the model number in the bios to 2 (4 drives).
So I changed the PlatformBytes from 2.0.0 (2000) to 2.0.1 (4000) and rebooted with the array intact and functioning.
If you're hacking a 2000 into a 4000 and update from V3 to V4 watch out for the PlatformBytes.
Now the questions. I've read in several threads that there is a mod for the drive cable to allow C/S on my old hardware version. I can't find it anywhere by searching. Could someone fill me in on the process? I'd really like to keep this running as a Raid5 but I know what happens if a drive really fails with M/S.
Think I really need to have Hardware version 2.0.1?
|