Hack a Snap Sever 1000?

[ibecdn]

Help! I have a SNAP 1000 V2 and the HDD died. I did not have an image backup. I have a SNAP 4000 also, Can you get the OS from that server? It is running 3.4.803. Thank you for any helpor if you have and image for 1000 could you email it to me. Thanks again I hope to get this up and running again.

[re3dyb0y]

Mine seems to be playing up again.....

[foglema]

I have a Snap 1100 with a 250 Gb disk that decided to die while I was out of the office. The drive is completely dead and I cannot recover the image so I can setup a new disk. Can someone point me in the direction of an 1100 image. It would be greatly appreciated.

Thank You in advance!

[KWayne]

Greetings:

I have spent the last week reading the entire post on how to upgrade a Snap 1000; impressive at over 500 printed pages. I have the following:

SnapSever Model 2000 Series
S/W 4.0.854(US)
H/W 2.0.0
BIOS 2.0.252
S/N 42872

If I read the articles correctly, several people have been successful by putting the working Server into a Raid 1 mode then remove one drive at a time. It seems too simple, but do you think it would work with my configuration? Also, how do I change the current setup (two drives that look like a single drive) to a Raid 1 configuration?

Thanks in advance for any assistance you may be able to provide.

Wayne

[blue68f100]

2000 Support RAID 0 & 1. Both indicate a single drive to the user. You will need to look at the disk configuration page to see what you currently have. If a raid 0 all data will be lost on the change to raid 1. So backup up all data if you need it.

[nmb]

hi all again,

thx for all the help. 2200 runningo on two new disks.

but I'm having another problem on another 2200.

already tried "config devices fsck 50000 /fix /fixfatal /altsb" and restarted the server.

tests went ok and after that the raid in mirror mode starts resyncing.

after a couple hours the resync fails with error "E File System : Failed to resynchronize logical set 50000, error -1"

I'm trying "config devices resync 50000". let's see how it goes...

[re3dyb0y]

Originally Posted by KWayne

If I read the articles correctly, several people have been successful by putting the working Server into a Raid 1 mode then remove one drive at a time. It seems too simple, but do you think it would work with my configuration? Also, how do I change the current setup (two drives that look like a single drive) to a Raid 1 configuration?

Breaking a RAID config isn't the best idea. Generally most people haven't done this, it does get confusing with all the methods!

I did mine by removing the 2nd drive, and then jacking in a new drive and letting it reformat it and such

Then moving this to primary, and use the 2nd drive and do it again

Or use the drive to do the 2nd drive also, and then just stick them both in after

[re3dyb0y]

Originally Posted by nmb

hi all again,

thx for all the help. 2200 runningo on two new disks.

but I'm having another problem on another 2200.

already tried "config devices fsck 50000 /fix /fixfatal /altsb" and restarted the server.

tests went ok and after that the raid in mirror mode starts resyncing.

after a couple hours the resync fails with error "E File System : Failed to resynchronize logical set 50000, error -1"

I'm trying "config devices resync 50000". let's see how it goes...

It may be easier to break the raid set, and remove it, then rebuild it

[nmb]

Originally Posted by re3dyb0y

It may be easier to break the raid set, and remove it, then rebuild it

but that means backing up all the data right? breaking the raid set erases all data on the drives?

[KWayne]

Originally Posted by re3dyb0y

Breaking a RAID config isn't the best idea. Generally most people haven't done this, it does get confusing with all the methods!

I did mine by removing the 2nd drive, and then jacking in a new drive and letting it reformat it and such

Then moving this to primary, and use the 2nd drive and do it again

Or use the drive to do the 2nd drive also, and then just stick them both in after

So if I understand what you are saying, you simply remove the second drive, insert the new larger drive configures either as Slave or CS depending on what the current second drive is, then power it up. I believe you are saying it will automatically recognize the new second drive, then format it and make it ready for use including putting the OS on it. Then again change out the primary drive, change the Slave to Primary (or CS) and insert the second new drive in and let it again format and copy the OS to it. Do I understand you correctly?

Thanks, Wayne

[blue68f100]

Breaking a raid 1 to JBOD will put all the data on the 10000 drive. If this is the good drive no data will be lost.

If you are dealing with a broken mirror and have installed a new drive, instructions for repairing is in the wiki section.

Other have reported using "co de" instead of config devices works.

Other wise we will need more info on what you are trying to do.

[KWayne]

Originally Posted by blue68f100

Breaking a raid 1 to JBOD will put all the data on the 10000 drive. If this is the good drive no data will be lost.

If you are dealing with a broken mirror and have installed a new drive, instructions for repairing is in the wiki section.

Other have reported using "co de" instead of config devices works.

Other wise we will need more info on what you are trying to do.

Thanks for sticking with me on this. I currently have a:

SnapSever Model 2000 Series
S/W 4.0.854(US)
H/W 2.0.0
BIOS 2.0.252
S/N 42872

that is working quite well with two drives that are combined to look like a single drive, not a Raid 1 environment. I want to replace the existing 2 - 20 Gb drives that work just fine, with 2 - 160 Gb (ATA-100) drives so that I can have more space. Ultimately, I want to configure them as Raid 1 but that can come after the changing of the drives. So I have heard two possible methods, (1), backup any existing data I have, change the existing environment to a Raid 1, then take out one of the drives and replace it with one of the new 160 Gb's. The unit would then copy the OS to the new 160 Gb drive, and when finished, move it to primary, and fail the second one again replacing it with a 160 Gb drive. The (2) method appears to remove the second drive without changing to Raid 1 first, replace it with a new 160 Gb drive, then have it come up after the OS is copied, move this new drive to primary (either Primary or CS) and then remove the second drive which was a 20 GB drive. I am also not clear on what wiki is (I HAVE read all 500 plus pages, but dont remember that term) and would appreciate any help.

Wayne

[nmb]

with this info, is there anyway to know the drive failing to sync?

Logical Device: 10006      Position: 0  JBOD     Size (KB):    32296  Free (KB):    22368  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x182E5A551A568FF1    Mount: /priv      Index: 12  Order: 0
     Partition: 10006  Physical: 10007  FS       Size (KB):    32768  Starting Blk:   515  Private
      Physical: 10007    Drive Slot: 0  IDE      Size (KB): 120627200  Fixed    

Logical Device: 10016      Position: 0  JBOD     Size (KB):    32296  Free (KB):    21528  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x4C6C63AB0B9E06D8    Mount: /pri2      Index: 13  Order: 1
     Partition: 10016  Physical: 10017  FS       Size (KB):    32768  Starting Blk:   515  Private
      Physical: 10017    Drive Slot: 2  IDE      Size (KB): 120627200  Fixed    

Logical Device: 50000      Position: 1  MIRROR_RESYNC Size (KB): 118281312  Free (KB): 23916984  Public   Mounted
  Label:Mirror  Data protection disk
     Unique Id: 0x674BB7006D53A006    Mount: /0         Index: 0  Order: 2
     Partition: 10000  Physical: 10007  M 50000  Size (KB): 119921128  Starting Blk: 88131  Public 
      Physical: 10007    Drive Slot: 0  IDE      Size (KB): 120627200  Fixed    
     Partition: 10010  Physical: 10017  M 50000  Size (KB): 119921128  Starting Blk: 88131  Public 
      Physical: 10017    Drive Slot: 2  IDE      Size (KB): 120627200  Fixed

[blue68f100]

Originally Posted by KWayne

Thanks for sticking with me on this. I currently have a:

SnapSever Model 2000 Series
S/W 4.0.854(US)
H/W 2.0.0
BIOS 2.0.252
S/N 42872

that is working quite well with two drives that are combined to look like a single drive, not a Raid 1 environment. I want to replace the existing 2 - 20 Gb drives that work just fine, with 2 - 160 Gb (ATA-100) drives so that I can have more space. Ultimately, I want to configure them as Raid 1 but that can come after the changing of the drives. So I have heard two possible methods, (1), backup any existing data I have, change the existing environment to a Raid 1, then take out one of the drives and replace it with one of the new 160 Gb's. The unit would then copy the OS to the new 160 Gb drive, and when finished, move it to primary, and fail the second one again replacing it with a 160 Gb drive. The (2) method appears to remove the second drive without changing to Raid 1 first, replace it with a new 160 Gb drive, then have it come up after the OS is copied, move this new drive to primary (either Primary or CS) and then remove the second drive which was a 20 GB drive. I am also not clear on what wiki is (I HAVE read all 500 plus pages, but dont remember that term) and would appreciate any help.

Wayne

It is always better to do a backup, whe you start playing with disks. After you have backed everything up: MARK YOU ORIGINAL HD's AS M/S OR FT/BK. Keep the master as a OS keeper if you like.

Check you drive configuration. Singe disk can be Any raid set, the only indication would be usable space. If you are showing over 20 gig usable you are proably raid 0, Which means there is nothing you can do but to backit up before upgrading. The process I would use would be to break the set to JBOD. reboot the server. Then change the drives to raid 1, reboot and let it build the set. approx 2 hrs.

On a 2000 the drives should be in a master/slave config. By looking at the HW & BIOS you have a version 2. The master is the FT disk, end of cable. So fail the slave, Back drive. Install your new disk and reboot. The snap should format and install the OS on it. Check you drives status from the disk secton. Once the Disk ligh has gone out. You will be ready to fail the master. and do the same process again. Your OS will support hd >137gig. If you end up with a broken mirror, simply change back to JBOD, then back to RAID1.

[blue68f100]

Originally Posted by nmb

with this info, is there anyway to know the drive failing to sync?

Logical Device: 10006      Position: 0  JBOD     Size (KB):    32296  Free (KB):    22368  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x182E5A551A568FF1    Mount: /priv      Index: 12  Order: 0
     Partition: 10006  Physical: 10007  FS       Size (KB):    32768  Starting Blk:   515  Private
      Physical: 10007    Drive Slot: 0  IDE      Size (KB): 120627200  Fixed    

Logical Device: 10016      Position: 0  JBOD     Size (KB):    32296  Free (KB):    21528  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x4C6C63AB0B9E06D8    Mount: /pri2      Index: 13  Order: 1
     Partition: 10016  Physical: 10017  FS       Size (KB):    32768  Starting Blk:   515  Private
      Physical: 10017    Drive Slot: 2  IDE      Size (KB): 120627200  Fixed    

Logical Device: 50000      Position: 1  MIRROR_RESYNC Size (KB): 118281312  Free (KB): 23916984  Public   Mounted
  Label:Mirror  Data protection disk
     Unique Id: 0x674BB7006D53A006    Mount: /0         Index: 0  Order: 2
     Partition: 10000  Physical: 10007  M 50000  Size (KB): 119921128  Starting Blk: 88131  Public 
      Physical: 10007    Drive Slot: 0  IDE      Size (KB): 120627200  Fixed    
     Partition: 10010  Physical: 10017  M 50000  Size (KB): 119921128  Starting Blk: 88131  Public 
      Physical: 10017    Drive Slot: 2  IDE      Size (KB): 120627200  Fixed

It's not telling me which drive is have the problem. Look in the error log and enter "in lo p -1" from the debug screen. You will be looking for errors on 100x0, 100x7 drive/slice markers.

Did you install new drives in this one too?

[KWayne]

Originally Posted by blue68f100

It is always better to do a backup, whe you start playing with disks. After you have backed everything up: MARK YOU ORIGINAL HD's AS M/S OR FT/BK. Keep the master as a OS keeper if you like.

Check you drive configuration. Singe disk can be Any raid set, the only indication would be usable space. If you are showing over 20 gig usable you are proably raid 0, Which means there is nothing you can do but to backit up before upgrading. The process I would use would be to break the set to JBOD. reboot the server. Then change the drives to raid 1, reboot and let it build the set. approx 2 hrs.

On a 2000 the drives should be in a master/slave config. By looking at the HW & BIOS you have a version 2. The master is the FT disk, end of cable. So fail the slave, Back drive. Install your new disk and reboot. The snap should format and install the OS on it. Check you drives status from the disk secton. Once the Disk ligh has gone out. You will be ready to fail the master. and do the same process again. Your OS will support hd >137gig. If you end up with a broken mirror, simply change back to JBOD, then back to RAID1.

OK; here's yet another stupid question.. Whats JBOD? I have found it in many posts dealing with drive statistics, but dont know what it means or how I would change back to it if things get dicey?

Thanks, again, Wayne

Wayne

[re3dyb0y]

JBOD = Just a Bunch Of Disks

Basically, like you would normally use hard drives in a pc

[einsteinagogo]

Can anyone send me a url as to where I can find the SnapOS 4.0 Upgrade. I purchase my Snap 2200 160gb unit, when it was a Quantum 2200, and then it changed hands to Snap, that wanted to charge me for the 4.0 upgrade, and now I see it's been gobbled up by Adaptec, where I cannot even register the device using the serial number and I cannot find 4.0 to download, just the patch!

interested, if I can remove the two 80GB ide drives and replace with larger.

regards

einsteinagogo

[re3dyb0y]

Depending on what OS you are on currently, you may be fine with your current OS

For what reasons do you want/need OS V4?

Do you need 2k3 AD support?

[einsteinagogo]

I've just completed an NT 4.0 to Win2k3 Active Directory upgrade, and I was having problems with my Snap server and authentication. I thought this was an SnapOS issue, but then I found it was SMB signing, and I cannot understand, now I've fixed the registry on the domain controllers, why the DC keep tuirning it back on when I disable it!

From these forums I've also read that the current SnapOS may be better, less overhead etc

What Active Directory features are missing from SnapOS 3.0

[re3dyb0y]

If you are going to 2k3 AD, you will need OS V4 up to date and patched to 4.0.860

This is due to MS security Fixes, and that 2003 Active Directory supposrt is added in V4 of the OS

God knows if you did get it on the AD how you did so without os v4!

[re3dyb0y]

Hmm

While mine was formatting the new 250GB Seagate, it was in 'failure mode' according to the LED patterns.

But then it went back to 'System is running a performing a check operation'

[einsteinagogo]

ah, I've just been prompted by your posting, we've just started migrating to Win2k3 AD from NT 4.0, so were are still running in Mixed-Mode.

So, I'll be needing to upgrade to SnapOS 4.0, where's the download, as I cannot seem to find it on Adaptec site, or find an email to register my Snap Server!

[re3dyb0y]

Like v4.0.860 can be downloaded from Adaptec. But requires a full version to be installed prior to patch.

[diskotech]

Hi all,

I've had a good read through this and the other threads and there's some great info and work been done here.

I've got hold of a Snap Server 1000, it's the later model without the OS on flash. It comes up with the System light flashing and the disk light flashing twice - waiting for software download in broadcast mode I believe. I cannot connect to the device at all, with or without the HD attached. I've gone through the various factory reset options.

I understand the PSU failed (I've obtained a replacement) so the previous owner tried to slave the HD to an XP PC to retrieve the data. I think that in doing so, XP has written something to the drive which has overwritten the SnapOS so the device no longer boots up.

I'm comfortable with using Linux and DD, the missing part of the puzzle is a link to the snap2200.bin file which is what I think I need to resurrect the device. Can anyone on here help? All the FTP sites mentioned here seem to be long dead.

Many thanks!