Quote:
|
Originally Posted by radio
I'm posting this here because it seems it's where everyone is looking.
I have successfully built a raid 5 with 4 320Gb disks, but it will not rebuild after an error (power outage) detailed description here: http://forums.procooling.com/vbb/showthread.php?t=13488
My best guess is that I need more that 64Gb because of the large disk size. Can anyone offer more than a hunch? Is there any data/evidence available on this? Does anyone have any experience with this error message:
File System Check : FSCK fatal error = 8 Disk 60000 RAID 5 9/17/2006 2:00:45 AM
File System Check : Failed to allocate 10930276 bytes for update bitmap!!! Disk 60000 |
To be honest, I am not sure... What you are seeing is the $10,000.00 question it seems and why I have asked DC4 to do that testing. Here is about all I can add, and it is guesses, speculations, and shots in the dark (so take it that way please).
1. It is possible that 64 megs of RAM is just not enough for an array of that size in a SNAP OS environment, and more so because if I remember right you are using v4 OS (the memory hog of the SNAP OSes). I do admit I am doubtful here, but it is possible. RAM size should make a difference as to how fast it works, initializes, rebuilds, etc, but it should not affect if it can or cannot do the array. In most OS environments, if the data being used was too large for the available memory, it would just parse it down to enough chunks to fit. It would slow it down dramaticly, but not stop it from working. In the SNAP OS, who knows? So back to it being the possible problem, but....
2. As speculated in one of my earlier posts, there is the issue of how the different SNAP OS initialize a drive. I do not recall your original steps in making this all work, but is it possible your drives got initialized on one SNAP OS and now trying to rebuild the array in a different OS? Not to mention what OS the RAID 5 was built on? So who knows, maybe?
3. Then there is the issue of SNAP OS limits which we been working o for a while now. Does 4x320Gb really work? Is it to much? Sure, it "seems" to format and build fine. But, what about this extraordinary amount of time it seems to take building the array? And will it actually rebuild the arrary? Maybe, just maybe, even though it "seems" to work, 4x320GB might just be a little too much, just over the limit of what the OS can actaully handle? Part of what we are trying to determine here with DC4.
4. Maybe you have a hardware problem. Maybe a couple drives got scrambled data, not just one. Remember, you can only lose one drive in the array and do a recovery. Now I do not mean drive FAILURE, I mean just got scrambled data in the power outage you had...
Best I can suggest is to look at and investigate these things, watch and see what happens with the test DC4 is doing, and go from there.... I know it aint much, but that's all I got....
