View Single Post
Unread 11-12-2006, 12:16 PM   #24
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap Server Boot Image

dandrews,

There seams to be a problem that has poped up with early version of the 4000, v1 & 2. These units use a M/S setup for the drives. All 4000 have weak power supplies. To confirm the problem fail one drive in a raid 5 set, like drive 2. See if it reports the problem correctly. Re-boot the server then recheck drive status. You will discover what I'm talking about. If you have the v3+ it does not have this problem. Most all of these problems showed up when users started installing drives large than OEM. It wasnt till lately that Phoenix32 started doing some intensive testing of the 4000. Purposely failing drives to see how it responds. He has both v2 and v4 models.

There are no problems reported in JBOD, no one normaly uses these units in that configuration.

If your hd is not reporting the proper size. You either have to set the unit up as JBOD or remove all execpt drive 1, Before you can correct the size of the drive. Raid 5 is based off of drive 1 or the smallest in the set. Sorry I wasn't very clear with this.

The max ram the 4x00 can handle is 256meg. These must be low density. To check to see if the ram is read properly use the debug cmd "debug memory".
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote