View Single Post
Unread 07-28-2010, 01:05 PM   #6
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Snap 1000 Error - no access

Not all 1000's are the same, there is 3 different HW versions that I know of. If you can access the GUI with out a HD you have the later v2 or v3. There is a memory size difference between the earlier models. If you only have 32meg your size and OS is very limited. With the 64 meg version it will run the latest v4 SnapOS. If you only have 32 meg you do not want to go past v3 due to memory restraints.

Since it has reported and fatal error, did it go into PANIC mode. LED Blinking rapidly. If in Panic some time a system reset starts it backup and it will try running fsck again. Now if its trying to run fsck and you keep interupting it, you make it worst. The SnapOS will not mount the share till it knows the drive is clean with NO Errors. Now with large HD and A very very slow CPU, this can take days and even weeks if it is low on ram or have a HD >90% full.

Now remember these are not very fast so Give the SnapOS time to execute what it's doing. If you interrupt it it just make the process take longer.

If your testing with the case off, put a book over the top for the cooling to work correctly. Other wise you will over heat the cpu and HD.
__________________
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