[blue68f100]

I just ask that you provide user input to the question we are unable to solve, will be proof enough. Paper means nothing to me. I have worked with PHD's all my life, all it means is they are capable of learning. Most when out side there field of expertise could not give you the time of day. Then there were those few that were execptional. I worked with the best of the best in a R & D lab. Most of my projects came to market 5-10 yrs.

Do you have a patch to allow the 4100's to support LBA48bit????

Please answer this for me ... It should be something your fammilar with.

1. RAID 5, 4 x 30 GB drives (all the exact same)...
2. Store Test Data on the array.
3. Pull the power plug on drive 2.
4. Refresh Disk Status display (web interface menu).
5. Nothing.
6. Check error logs.
7. Nothing.
8. Go to Server Setting (web interface) and tell it to do a system
restart (forces a disk check).
9. SNAP comes back online, go check Disk Status display.
10. Shows Disk 1 as orphaned (the unit was not even shut down, just a
restart) and the RAID as broken.
11. Shutdown unit (it does a proper shutdown).
12. Plug Drive 2 back in, power up the SNAP.
13. Unit comes up, go to Disk Status display
14. Drive 1 Orphaned, Drive 2 Orphaned, RAID Broken.
15. Logs show 2 drives missing from RADI set (duh).
16. Format Drive 2 (simulated bad drive).
17. Make Drive 2 a Spare.
18. Nothing.
19. Reboot the SNAP.
20. Nothing.
21. Drive Staus display still shows Drive 1 Orphaned, Drive 2 as a
spare, and RAID Broken.