Quote:
Originally Posted by blue68f100
I did some extensive testing when I got my 4500. I was pulling the power in the middle of large data transfers (writes) to try to crash the unit. As long as the watchdog was active, snapshots and diaster recovery active it was always able to recover. But soon as you took the diaster recovery away you were asking for trouble. In most cases if the Main HD boot failed you need to allow plenty of time for watchdog to attempt the next HD. This can be a long time considering the std boot takes anywhere from 5-10 min depending on model. One thing you can do is setup the null modem cable and your terminal program. This is active during the boot process so you can see where the problems are accouring.
If you must have the data, I would contact Snaptech. If only the OS was damaged preventing if from booting, extraction of the data will be quick and easy. And should not cost an arm and a leg.
One thing I do and Phoenix too is run SpinRite on ALL of our HD's. This at times will repair a HD and it will boot up. It also builds the bad sector table so the SMART does not have to do it during a transfer if a bad sector is found. This way will keep the HD's (RAID5) in sync.
You can SSH into the shell using a terminal program or putty on MS Windows if the gui is not working.
|
I may try the null modem cable to see what it spews if anything, but do know that i CANT ssh at this time (i do use putty), as i get a connection refused. I also CANT get into the gui. The data's not so important that i'd need to spend money to fix it, but i would like to muck around with it myself.
I've heard this spinrite mentioned a few times, do you have a favorite place to download it from or purchase it from if it's not a freebie? Also i assume it's windows based so i'd have to take the dead drive out of the snapserver to have spinrite scan it, or is that incorrect?