Snap 14000 Reinstall

[churnd]

I hope this forum's still active... here goes:

I have a SNAP 14000 that I'm trying to reinstall the Guardian OS on. I have the image from Adaptec, and I have the server to where it boots to the recovery console. I select the image, choose Fresh Install, then click Go. The next screen shows the "Fresh Install will erase everything" warning. I click OK. It goes through the process of unzipping the image, and then throws an error saying it can't find the drive to install on. I'm not sure which drive it means, but as far as I know, they're all in there. What's going on?

[churnd]

Here's what's happening:

Installing ...
Using IMAGE target file '/updater/GuardianOSImage' and install script './fullinstall.sh'
-rw-r--r--    1 0        0        115347274 May 31 18:43 GuardianOSImage
./install_tools/
./install_tools/grub/
./install_tools/grub/stage1
./install_tools/grub/grub
./install_tools/grub/stage2
./install_tools/extattrb.fix.sh
./install_tools/checkguest
./install_tools/checkver
./install_tools/dd
./install_tools/raidtab.crippled.adelie
./install_tools/extperm.fix.sh
./install_tools/flashupdate.sh
./install_tools/fstab
./install_tools/fullinstall.sh
./install_tools/fullupgrade.sh
./install_tools/installroot.sh
./install_tools/manufacture.sh
./install_tools/mkboot.sh
./install_tools/mkdir
./install_tools/mkfs.xfs
./install_tools/mknod
./install_tools/mkraid
./install_tools/mkswap
./install_tools/passupd
./install_tools/raidhotadd
./install_tools/raidstart
./install_tools/raidstop
./install_tools/raidtab
./install_tools/raidtab.adelie
./install_tools/raidtab.clipper
./install_tools/raidtab.crippled
./install_tools/updatesnaps
./install_tools/reshare
./install_tools/raidtab.crippled.clipper
./install_tools/raidtab.crippled.emperor
./install_tools/raidtab.crippled.manta
./install_tools/raidtab.crippled.n1000
./install_tools/raidtab.crippled.vmware
./install_tools/raidtab.emperor
./install_tools/raidtab.manta
./install_tools/raidtab.vmware
./install_tools/sfdisk
./install_tools/touch
./install_tools/sfdiskmap
./install_tools/sfdisk.out.developer
./install_tools/pickhintdevice
./install_tools/upgraderoot.sh
./install_tools/partitionize.sh
./install_tools/s2spropmerge.jar
./install_tools/mdctl
CRC ok on image

Platform Bytes of Image File match this machine: 04.01.00


Successfully extracted *.tgz to pipe

Starting ./fullinstall.sh
./fullinstall.sh script
root installation script
requires pwd, sfdisk, mknod, mkraid, mkswap, mkdir, mount, mkfs.xfs
cp and tar

a version of each is located in this directory

Make sure the disks aren't busy...

Install Failed! A drive must be inserted in the first slot.
 Execution of ./fullinstall.sh Failed! 
Fresh Install Failed!

Where does it mean by the "first slot"?

[blue68f100]

Re check all of the jumpers on the drives, Drive 1.
All should be set to MASTER or Single Drive.

The error indicates that drive 1 is not mounting.

If it's not a jumper (drive1) swap the drives with another position. If you have different size drives move the smallest to drive 1.

[churnd]

Where is drive1? If I open the front panel of the server, I can see the 12 hot swappable drives, with a divider before the last 4 (going from left to right) that has the ribbon cable connecting to the front LCD.

Before it started acting up, these drives were in a RAID 5 array, with one drive being a hot spare drive. The RAID 5 array had all the same sized drives I believe, while the hot spare drive was larger.

Is there a drive inside the server that hosts the OS?

[blue68f100]

When you install the OS, only have drive 1 in the 14000. Once the OS has been installed, then hot mount the HD's.

Generally Snap number's their drives from left to right.

I do not know if there is a HD for the OS. Normally it is stored on all HD's, on a seperate partition.

Open the unit up and look. You should find a label marking the drive positions.

[Phoenix32]

Originally Posted by blue68f100

Re check all of the jumpers on the drives, Drive 1.
All should be set to MASTER or Single Drive.

Hmmmm, all of my Guardian units are set as c/s???

Originally Posted by blue68f100

When you install the OS, only have drive 1 in the 14000. Once the OS has been installed, then hot mount the HD's.

Generally Snap number's their drives from left to right.

Open the unit up and look. You should find a label marking the drive positions.

Agreed, boot it with only drive 1 installed, then hot swap the rest in after you get the unit up and running good.

I am not sure 100%, but I believe David is right, drive 1 should be the left most hard disk. There may also be a map of the drives inside the unit on the top cover.

[churnd]

I removed all of the drives, then chose one at random and put it in the leftmost slot. Ran full install again, and it produced the same results. Tried moving the drive to the rightmost slot and tried full install again, but produced the same results.

In my experience with RAID, if a drive is or was a member of a RAID array, getting it available for re-use isn't easy. Could that be the problem here? The possibility of the drives still thinking they should be part of a RAID array? If so, how do I break them up?

[blue68f100]

If your are doing this through the Recovery screen, Keyboard and Monitor or RS232 Terminal. It should not make any difference. Unless it does not like the version of Guardian you are trying to install.

You are correct with the Guardian retaining drive setup. Remove the battery for 10 min to have it clear the drive data stored in the unit. Also try using a drive utility to do a quick format, to anything other than Linux. While you have it open reseat the memory and any card that may be in the unit.

What does the insides of a the 14000 looks like???? If you would please post a picture.

And like Phoeninx said see if it works in Cable Select.

Did you have this working before you tried to do a clean install?

[churnd]

Originally Posted by blue68f100

If your are doing this through the Recovery screen, Keyboard and Monitor or RS232 Terminal. It should not make any difference. Unless it does not like the version of Guardian you are trying to install.

I'm using the recovery screen via web browser. The version is the same as the one that was on it.

You are correct with the Guardian retaining drive setup. Remove the battery for 10 min to have it clear the drive data stored in the unit. Also try using a drive utility to do a quick format, to anything other than Linux. While you have it open reseat the memory and any card that may be in the unit.

I'm trying this now. I also hooked a drive up to my desktop and removed all formatting from it. I will use that one from now on. I also removed the memory modules and reseated the main board, while also leaving the battery out for 10 mins.

What does the insides of a the 14000 looks like???? If you would please post a picture.

I have a picture, but no way to upload it from work. I'd have to wait until I get home.

And like Phoeninx said see if it works in Cable Select.

All of the drives are configured as Master/Single. None had the cable select option. It did work before like this.

Did you have this working before you tried to do a clean install?

Yes. The reason I tried a clean install is because I wanted to revert it back to how it was originally set up so a different person could use it.

[churnd]

OK, I think removing the battery worked because I'm up and running. It may have been a combination of erasing the drive format and removing the battery. I installed the image on that one drive, got the OS up and running, then hot swapped the rest and now it's building a RAID 5 array. Thanks for the help and ideas!!

[Phoenix32]

My bet is on the erasure of the drive...

[churnd]

Originally Posted by Phoenix32

My bet is on the erasure of the drive...

I would like to think so too, but I did try another instance after I had erased the drive, but before I pulled the battery, and it didn't work. So it likely was either the battery pull, memory pull, reseating the motherboard, or possibly all 3. I didn't have the patience to try only one at a time.

[blue68f100]

The bottom line is that every thing is working.

I'm more incline to think it was the battery based on what I have run into my 4500. But if it reconizes a file system it does not clean things either, will retain the data. So it was a combination of a couple of things.

When I tried re-configuring mine, it was remembering all of the HD's that were in place.