Pro/Forums - View Single Post

blue68f100 · 08-01-2007, 07:34 PM

A little more specific detail for me to know what you did.
Did you replace the HD with one that is identical (same mfg, model size & rev) or < > in capacity? There are several procedures scattered all over this site. Which one did you use? Did you remember to change the jumper to master or cs depeding on what you original was.

The rapid flashing is panic mode, System error/crash.

You said you did a bin/img file load. Were you able to do the /init command or did it fail to get that far? And did you do it with 1 drive or 2 installed. The fcb error has to do with the XFS file system. Which makes me wonder if the drive is good/compatiable with your system.

08-01-2007, 07:34 PM	#2
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap 2200 not holding o/s A little more specific detail for me to know what you did. Did you replace the HD with one that is identical (same mfg, model size & rev) or < > in capacity? There are several procedures scattered all over this site. Which one did you use? Did you remember to change the jumper to master or cs depeding on what you original was. The rapid flashing is panic mode, System error/crash. You said you did a bin/img file load. Were you able to do the /init command or did it fail to get that far? And did you do it with 1 drive or 2 installed. The fcb error has to do with the XFS file system. Which makes me wonder if the drive is good/compatiable with your system. __________________ 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