[kugeln]

NOTE: I have since found out that this procedure does not seem to work on GOS > 4.0, so making a backup ghost image that works will require downgrading to 3.2.019 (where I started) or 3.2.026 (where I ended up trying to fix an issue I was having with ghosting). After the recovery is complete, you can still upgrade to whatever you want. The GRUB boot loader in the 4.x series doesn't seem to like being ghosted. YMMV.


This is the result of a few days of testing. It should probably work on other GuardianOS units as well.

You need:

• One working drive from a GuardianOS unit
  *OR*
• A ghost image of the boot partition. (~5 MB)
• A GuardianOS Image (.gsu) to load onto the new drive
• and of course, four new drives (BLANK!!! If they've been used, I suggest you zero them out with a utility of your choice).

To make the image:
Using a recent version of ghost (I used 8.x) you need to make an image of the boot partition off the original drive. This partition is mirrored across all four drives on the 4500 (and probably other GOS units too) and I believe you can use any of the drives to make the image from.

1. In ghost select Local, Partition, then To Image.
2. Select the disk from the Snap Server. Click OK.
3. Select the first (~15 MB) partition on the Partition selection screen. Click OK.
4. Choose where to save the image and what you want to call it. Click OK.
5. Choose Fast Compression, and yes, you want to proceed with image creation.
6. In about 5-10 seconds, you have your boot image.

To set up the first new drive:

1. In Ghost, again, Choose Local, Disk, From Image.
2. Choose the image you just made. Click OK.
3. Choose the target disk. *be careful and make sure you pick the right one* Click OK.
4. Make sure the new size of the first partition is equal to the old size. Ghost tries to resize the partition to use the rest of your new disk. Change it to match what is shown for "Old Size" (15 in my case). The rest of the space should be indicated as "Free Space". Click OK.
5. At the "Are you sure". Click Yes. In a few seconds you have a new drive, ready to install in your Snap Server.

Getting ready:

1. Install the drive you just ghosted as drive one. Install the remaining drives in the other slots.
2. Power on your Snap.
3. After the boot up process completes it should be in recovery mode.
4. Connect to the snap with your web browser. There's no way of knowing what it'll come up as, so you either have to know how to identify your DHCP clients on your router, or maybe try SSM or Assist (don't know haven't tried either).
5. Now, pick your OS Image you want to load, select the Fresh (full) Install option, and then start your recovery.

After that completes, you should have a fully working GuardianOS Snap Server.

Notes:
I only have a 4500 to test this on. I have *not* tried it with all four drive positions populated--only one. I would recommend *not* using it on your original drives unless they're already blank anyway. I'd suggest trying it on four small (100) gb drives first to make sure it works for you. I assume if all four drives are in place, it will begin building the default RAID5 array immediately after it finishes the recovery and reboots. You may be unable to access it during the rebuild process. Using only one drive seems to keep this from occurring.

I welcome questions and constructive comments. If I got something horribly wrong let me know. If it works for you, let me know.

YMMV, and I'm not responsible if you hose your computer or your Snap. If you do not know how to use Ghost safely, DON'T.

-Levi