March 12, 200818 yr Check will start a Parity-Check. (Last checked on 1/5/2002 6:47:34 AM, finding 1451058 errors.) There doesn't seem to ba any obvious problems with the array. it had five drives plus parity, all 750GB. Three of the data drives are Sata and two are IDE. For on eof the IDE drives it isn't reporting the temp.
March 12, 200818 yr If my memory serves me correctly, there were very few reliable 750 Gig drives in January 2002. On the other hand, I'd also be VERY surprised if you had an unRaid array in January 2002 that supported a mix of SATA and IDE drives. Even if you did have an unRaid array back then, If that was the last time you did a full parity check it probably would be out of date. I don't think you can trust any of your older parity check results to be accurate. With that in mind, run a full parity check now and see if any errors are detected. Then, you can react as needed. Joe L.
March 12, 200818 yr Assuming that the 2002 date is a BIOS problem with the internal clock. I am not sure how this could happen (so many parity errors). I am wondering if somehow, during the parity build, the process died and somehow unRAID thought parity was valid. My guess is that something bad happened and fooled unRAID into thinking it had valid parity when it didn't. The good news is that parity corrects itself. And it corrects itself by correcting the parity data. It doesn't try to change DATA on any of your drives. So when you ran parity check, it rebuilt parity. It is good news that your parity check finished. As a result, it attempted to FIX each and every one of those errors. If you run parity check again, it shoujld be clean. If it is, I wouldn't be too worried. But if you get another ton of parity errors, you've got a more serious problem. You should not get ANY errors.
March 12, 200818 yr Assuming that the 2002 date is a BIOS problem with the internal clock. Even if he built his unRaid array into a DeLoriian? Like we both said, run another parity check... let us know what happens. Joe L.
March 12, 200818 yr Author It seems that when I was having problems getting it to recognize an ide drive I decided to start again from scratch - including resetting the cmos. In my haste I forgot that that would also reset the bios clock... Anyway, I set the clock to the right time and am runnig another parity check overnight. Other than that my unraid seems to be chugging along quite happily. I have 5 750GB data discs with about 290GB free after transferring all my data on to it. I put in a D-link NIC which seems to have improved the data transfer rate somewhat, but I'm really looking forward to (hopefully) resolving that properly with the imminent update
Archived
This topic is now archived and is closed to further replies.