![]() | ||
|
|
Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides |
![]() |
Thread Tools |
![]() |
#1 |
Cooling Neophyte
Join Date: Feb 2007
Location: In A Van Down By The River
Posts: 12
|
![]()
I have a 2200 that the BIOS appears to be bad on. I cannot connect to it and it is in panic mode. It will also not shut down properly. Is there a way to force flash the BIOS or return it to original or is it a doorstop?
|
![]() |
![]() |
![]() |
#2 |
Thermophile
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
|
![]()
A 2200 will go into panic mode even on a failed HD. What you have to do is do factory reset and see if it clears. If it goes into panic mode again, pull the power and reset to factory again. A double reset is required to clear some panic's. Then connect if it boot and find which HD has failed. All of the OS is stored on the HD on a 2200.
__________________
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 |
![]() |
![]() |
![]() |
#3 |
Cooling Savant
Join Date: Oct 2001
Location: Dallas, Tx
Posts: 469
|
![]()
IF there is a bad hard drive try pulling them one at a time. Oddly enough the OS is stored on both of them and you can boot it with only one good hard drive in either slot believe it or not. I discovered this when i got a snap with one drive missing, which was the primary drive. It still booted fine.
Shane
__________________
Snap Servers: 1100 - 1x300gb Seagate Baracuda (SnapOS Version 3.4.807) 2200 - 2x80gb Maxtor (one dead) (SnapOS 4.0.860) |
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|