Pro/Forums - View Single Post

fisherscpa · 08-02-2007, 06:37 AM

A drive on the Mirrored unit failed. I did not know the anatomy of the unit but it turns out it was the 1st or main drive. The error on the debug page read something like "broken mirror". Following the instruction on replacing a dead drive on the unit did not work initially. Fortunately, I did have an image copy of the o/s and the information on the original drive was already backed-up on another drive. My attempts to reint the original drive failed as the debug page still listed the original (and remaining drive) as drive 50000 not 10000.

I reformatted the drive in a in windows system and copied the image file over to the drive using dd.

Once the drive is installed it reformats and initialized fine. It is not until a second (identical drive) is installed, reformated and initializes that I have an issue. Sometimes the issue is immediate. Sometimes it takes a few hours with the system running normally before the rapid system light (panic) occurs. I have not tried to mirror the drives or set as striping. The drives are just 2 independent drives in the unit. Each with a different share name. I have even tried copying the original good drive (the entire drive) to the replacement drive using dd. Again its OK for a while (hours) then the panic error occurs. Sometimes I can merely reboot the system and it remains stable for a couple of hours but eventually I get back to the panic error and unit will fail to reboot correctly.

To answer your questions...
1) Did you replace the HD with one that is identical (same mfg, model size & rev) or < > in capacity?= YES
2) There are several procedures scattered all over this site. Which one did you use? ALL OF THEM EVENTUALLY. I DON'T KNOW WHICH ONE FIRST.
3) Did you remember to change the jumper to master or cs depeding on what you original was. ORIGINAL WAS MASTER BUT THE SYSTEM WILL NOT RECOGNIZE THE 2ND DRIVE UNLESS IT'S JUMPER IS SET AT SLAVE FOR SOME REASON.
4) 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? YES (SEE ABOVE)
5) And did you do it with 1 drive or 2 installed. I HAVE TRIED ALMOST ALL THE COMBINATIONS AVAILABLE. I HAVE TRIED INITIALIZING THE DRIVES INDEPENDENTLY THEN PUTTING BOTH DRIVES IN THE UNIT AT THE SAME TIME- NO SUCCESS.
6) The fcb error has to do with the XFS file system. Which makes me wonder if the drive is good/compatiable with your system. THE REPLACEMENT DRIVE IS IDENTICAL TO THE ORIGINAL AND MIRROR. I HAVE ALSO TRIED OTHER DRIVES. ALL WITHOUT SUCCESS.

I have also tried to upgrade the o/s once the drive was operating correctly. The upgrades are reported to have taken place but the system doesn't show the new s/w version which I get a specs page.

Thanks,

Jeff

08-02-2007, 06:37 AM	#3
fisherscpa Cooling Neophyte Join Date: Oct 2005 Location: Indianapolis Posts: 11	Re: Snap 2200 not holding o/s A drive on the Mirrored unit failed. I did not know the anatomy of the unit but it turns out it was the 1st or main drive. The error on the debug page read something like "broken mirror". Following the instruction on replacing a dead drive on the unit did not work initially. Fortunately, I did have an image copy of the o/s and the information on the original drive was already backed-up on another drive. My attempts to reint the original drive failed as the debug page still listed the original (and remaining drive) as drive 50000 not 10000. I reformatted the drive in a in windows system and copied the image file over to the drive using dd. Once the drive is installed it reformats and initialized fine. It is not until a second (identical drive) is installed, reformated and initializes that I have an issue. Sometimes the issue is immediate. Sometimes it takes a few hours with the system running normally before the rapid system light (panic) occurs. I have not tried to mirror the drives or set as striping. The drives are just 2 independent drives in the unit. Each with a different share name. I have even tried copying the original good drive (the entire drive) to the replacement drive using dd. Again its OK for a while (hours) then the panic error occurs. Sometimes I can merely reboot the system and it remains stable for a couple of hours but eventually I get back to the panic error and unit will fail to reboot correctly. To answer your questions... 1) Did you replace the HD with one that is identical (same mfg, model size & rev) or < > in capacity?= YES 2) There are several procedures scattered all over this site. Which one did you use? ALL OF THEM EVENTUALLY. I DON'T KNOW WHICH ONE FIRST. 3) Did you remember to change the jumper to master or cs depeding on what you original was. ORIGINAL WAS MASTER BUT THE SYSTEM WILL NOT RECOGNIZE THE 2ND DRIVE UNLESS IT'S JUMPER IS SET AT SLAVE FOR SOME REASON. 4) 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? YES (SEE ABOVE) 5) And did you do it with 1 drive or 2 installed. I HAVE TRIED ALMOST ALL THE COMBINATIONS AVAILABLE. I HAVE TRIED INITIALIZING THE DRIVES INDEPENDENTLY THEN PUTTING BOTH DRIVES IN THE UNIT AT THE SAME TIME- NO SUCCESS. 6) The fcb error has to do with the XFS file system. Which makes me wonder if the drive is good/compatiable with your system. THE REPLACEMENT DRIVE IS IDENTICAL TO THE ORIGINAL AND MIRROR. I HAVE ALSO TRIED OTHER DRIVES. ALL WITHOUT SUCCESS. I have also tried to upgrade the o/s once the drive was operating correctly. The upgrades are reported to have taken place but the system doesn't show the new s/w version which I get a specs page. Thanks, Jeff