View Single Post
Unread 08-02-2007, 11:26 AM   #5
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 2200 not holding o/s

50000 refers to a mirror RAID1 share. 10000 & 10010 are the actual drive ID's. Normally on a 2200 the top drive is 10000.

Now you say M/S is the only way the second drive will be reconized. This configuration refers to a 2000 model and not 2200 unless you are using Maxtor HD's. The 2000 has the drives side my side where the 2200 has the drives on top of each other. You can NOT mix CS and M/S. Must be one or the other. If you are using Maxtors drives on a 2200 the setting must be single drive or CS. I think CS worked better.

A few things to check. Make sure the system fan is working. The 2000v1 and 2200 both have a system fan. The 2000v2 may have a cpu fan. The CPU is normally temp controlled. I would recommend wiring it so it runs 24/7. Re-seat the ram, to clean up the contacts.

First do a reset to factory settings, if you have a copy of Assist. Check to see what OS version you are running by clicking on the SnapAppliance logo on the admin page. You have said it has not changed. V3.4 on up can be upgraded from the GUI. Must have a lot of paitence, at times it will act like it is hung. If you have your computer to go to sleep quickly, make sure you move the mouse a little every 30 sec or so. If this fails you can also upgrade it using assist. I and other have discovered that Assist seams to do a better job of upgrading, if you suspect you have corruption. If you are using Vista, throw it out the door, not compatable with these older units.

I would only work with 1 drive, top or master if a 2000. I would do a clean install using a image file. Init the drive. With it up, look at the Drive configuration. See if it's reporting drives missing/ mirror broken. If so you must use a debug cmd to reset it. Adding drives or mixing position can corrupt it's settings. If everything is good (drive cap) and OS v4. Install the second hd that has had a quick erase using the MFG utility. Power up and let the snap init the drive. Run "co de info" to verify that the starting position is the same, and the capacity is the same. MFG constanly update firmware, so HD with the same PN can have a different capacity. Make sure the capacity is correct. If OK you can now change the drive config to Raid1. If you have it out of the case, make sure the fans are running. If not it will over heat and generate errors.

I use SpinRite on all new HD's to locate and map out bad sectors. This takes time to run depending on capacity. New drives have not had the media checked, mfg rely on SMART to do it on the fly.

Since DD use a RAW copy, coping 1 drive to another may or may not be 100% correct. Particularly if it had some data corruption. If you do this run SpinRite to verify the data.
__________________
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