Re: Snap Server 4100 Meltdown
 

NO -- ONLY IF YOU DON'T CARE ABOUT WHAT IS ON THE SERVER AND JUST WANT TO REDO THE RAID.

only do a /reinit if you don't care about the currant data.

we had to use the /nocore and format the drive under a specific os so that the starting blocks were correct before shipping the drive out to clients.

Douglas

Re: Snap Server 4100 Meltdown
 

Let's say we just picked up a 4100 off ebay. The Info log shows the miss match in the drives. And the unit shows a drive failure. Would replacing the failed drive cause the system not to build?

Would you recommend reformating all drives to correct the inherit problem while the drives are clean?

Re: Snap Server 4100 Meltdown
 

Ummm...that's kind of a big ass bug for a "falut tolerant" RAID config, but good to know none the less.

I guess I don't totally get it though...why wouldn't replacing the drive with the different start block cure the problem? If a drive is mis-matched, pulled, and replaced with a new one, wouldn't the snap just format the drive with the "current" OS start block and go on it's merry way? Or are you saying that if a snap is set up with a given os, upgraded to a new OS, and the a drive fails, that when the new drive is formatted it won't match because it will be formatted with the "new" OS paramaters, which wouldn't match up with the other 3 drives formatted with the "old" paramaters....

Re: Snap Server 4100 Meltdown
 

Ok, found some more info from my days at snap.

If the snap was originally formated under a 2x version then upgraded to an 3x, and a drive fails -- the replacement drive must be formated under a 2x version.

If snap was original formated under 2x, but after upgrading to 3x the drives were re-formted with the /reinit option then a replacement drive would not need to be formated under 2x first.

The changes between 2x and 3x when it comes to starting block is 16 sectors only.


If the drives were inserted or formated while server was running a 3x version then there is no concern because they all have a 3x starting block location.


If you snap was originally formated under 2x then upgraded to 3x and you have a drive that failed you can remove all drives -- downgrade the server using a 2x version of the .sup file. insert the new drive and format it. Then remove it and re-upgrade server back to a 3x version. reconnect the drives, power up unit and make sure all looks as it did. Then shut down and add the new drive and insert it into raid and all should be ok.

It is ok to have a new drive that is larger than the rest, the starting block will not match the other drives(that can look confusing but is ok - as long as it was formated under the os version as the other drives were originally formated under)

I hope this makes sense. If not--post specific questions and I will try and re-explain.

Douglas snap-tech

Re: Snap Server 4100 Meltdown
 

What about 3x to 4x? Is this required between them as well?

Re: Snap Server 4100 Meltdown
 

NO. There was no change between 3x and 4x for the starting block.

Douglas Snap-Tech

Re: Snap Server 4100 Meltdown
 

Just wanted to update everyone on this snap.

Mike shipped the drive that contained all 4 images of snap drives to me as well as a drive to put data on. I am in process of destriping raid and have 15GB so far. So it will be another successfull recovery from a snap.

Mike will be also posting something later after I give him the list of files recovered.

Douglas Snap-Tech :nod: :nod:

Re: Snap Server 4100 Meltdown
 

I was able to do a full recovery on this 4100 and will be shipping out the recovered data on Monday.

mvastola12 should be posting something this weekend to confirm recovery.

Douglas Snap-Tech

Re: Snap Server 4100 Meltdown
 

Bravo!