[Phoenix32]

David, DC4,

As I eluded to in my previous message, while the OS (for the most part) is in flashram for the 4000, there is "part" of it being stored in a hidden directory on the disk(s). I am not sure if it is on all drives or just the first drive. Speculations David? Anywise, as near as I could tell for 100% sure, it "looked" like just help type files in this hidden directory on the drive, but I have always been suspect that there is more of the OS there than just this, but no way to verify for sure (for me at least). I suspect some of his problems were not having the whole OS available, but when he got the OS installed fully, it made correction possible.

Next, another one of my "speculations" that I cannot prove. I suspect the format on the drives, as you hinted at David, from one version of the OS to another can be different, at least with the RAID configurations. Now I do not mean just from v2 to v3 or v3 to v4, I mean even within main versions, say v3.3.x to v3.4.x. After reading a zillion messages here on the forum, it seems we get weird never explained problems, particularly with the RAID configs that magicly go away when an OS change is done and the drives get reinitialized/formatted. Thinking about it, the Linux/Unix that the SNAP OS is "based" on, well, it does not support the type of RAID configurations and boundaries we see with the SNAPs, at least to my knowledge (I could be wrong). This leads me to speculate that Meridian/Quantum/Adaptec wrote their own RAID routines into the OS. This leads me to believe that some of those "unknown" changes from one version to another may also contain changes in this "proprietary" portions of the OS. As I said, I can't prove it, but it sure seems funny to me how many RAID issues we see here and there happen after OS changes (even small ones), and then magicly disappear after the drives get a reinit/format. Now before you go off and think I am a nut, think on this a moment. The 4000 and some of the 2x00 units operate on a software RAID. This means it is all in the OS. Do you really think a version change in the OS might not affect this? Next, many of the OS changes around here are to change from a non LBA48 bit OS to an LBA48 bit supported OS. Ya think maybe messing with the LBA48 bit OS stuff just might have an effect on how a drive is formatted and/or how a RAID might work on it? Just some things to think about, nothing I can prove.

DC4, I would absolutely love it if you would be the test guy for us since you have the drives. Can you provide the following information please;

1. Model number of your 4000? Specificly if it ends with -01 -02, -03, or -04 (David, I still suspect there are some differences in the revisions).

2. List the basics of your 4000 (OS, Hardware, BIOS)?

3. The exact model hard drives you are using (Seagate STxxxxxx).

4. The time it took for the RAID 5 to build...

Then do a little experiementing for us/me (you may save me a lot of money I don't have to spend). After the RAID is built, tell us the specs on the drives.

1. Actual formatted capacity (each)

2. Actual RAID 5 capacity

Then store a crapload of data on the arrary. Not just a little tiny bit, I mean like a couple hundred gigs (at least 100GB minimum). Then, after all this test data is on there, unplug one of the drives (unit powered down for safety to hardware). Check the logs and see what it actualy reports after you power it back on. Let's see if it reports properly. Then, wipe that drive you removed form the array (put it in a PC and low level it). If you do not have a utility, let me know, but I am guessing Seagate has an init utility on their website that will do just fine. Then put the drive back in, and let the SNAP reinitialiaze/format the drive. Report how long it took for this format to take place. Then when it is done, try to put the drive back into the array and let it rebuild (let's see if it rebuilds the array properly). Then report how long it took for this rebuild of the array (and let us know how much test data you used. In short form;

1. Store test data (report amount of test data used)
2. Remove a drive from the array (power the SNAP down first)
3. Check SNAP logs to see if it reports the loss properly (and let us know too)
4. Wipe (low level format) the drive you removed from the array (on a PC)
5. Reinstall the drive into the SNAP and let it initialize (report time to initialize)
6. Place driva back into RAID 5 array and let it rebuild (report time to rebuild)

DC4, I know this is a lot of effort, but you will be probably saving me some money, helping us out with needed information, and even helping yourself as well in the process. Think about it this way.... You have your SNAP working now, but.... If/when a drive fails down the road some day, wouldn't you like to know for sure you are going to be able to replace that drive and rebuild the array without losing your real, and probably valuable, data in the process? I know I would, and there has been some question about this with these larger hard drives...

David, I think I answered your question(s) here, but if not, say so. But, I do not think you need to go above 3.4.805 to use these 320GB drives. Version 4 may have some other goodies we do not know of (more efficient, faster, better recovery, etc.), but I doubt it is required. I wish we knew what the changes were between 3.4.805 and .807 as well as the changes between 3.4.80x and 4.0.860 beyond the MS AD stuff. I bet there are some little tweaks and fixes, but with it's extra memory usage, I just don't see it worth doing without knowing for sure. It would have eben nice if we coudl try it, and go backwards in OS if we wanted to go back, but alas, no can do, or so I have heard. I also wonder if the 4.0.860 woudl allow us to go past the 1.2TB limit we know of (keep in mind, so far all theactual people trying it were using 3.4.80x). I do think if DC4 follows this, we may in fact get some of our questions answered and be helpful down the road.

As a side note, I do not think the hardware is making any diference here on the limits or int he problems we are seeing/saw here. I am however convinced that if you are going to use RAID, at least RAID 5, and you change the OS, you need to reinstall your OS and reinitialize the drives afterwards if you change the hard drives in a 4000 (and maybe some 2x00 units). There is my whole nickels worth...