dead 2200

[starman7]

i think it started w/ a bad power supply (blinking green light, fading in and out)

when i could attach to its webserver, it would say unavailable: checking disks...

i moved the drives to an earlier snap 2200 - but it said no drives present.
the original drives in it had jumpers, but my broken snap's drives didn't. so i didn't use any when trading places into the older enclosure.

one symptom is the disk light rarely comes on. the server is only very rarely pingable it seems to fade in, but is mostly out.

this trait exhibited itself when i moved the bad drives to the older enclosure.

switching everything back, the old snap still works correctly.

but i am still having major difficulty with the newer one.

i tried attaching one of the bad dirves to an xp machine (attached a jumper to make it slave) but it was not recognized (though the machine saw it as unformated 160gb i think)


did putting it in another earlier snap server, or in winxp pro machine mess it up?

update: i should mention i put the top drive into the winxp machine before putting both into the older enclosure ...

the little power button doesn't seem to turn it off. is it worth trying to do a reset?

my backups are pretty old. this was a mirrored configuration.

might both enclosures be good, but something is bad on the drive(s)

how might i mount either of them to backup to new media?

thanks for any hints!!!


update: when i replaced the bad drives in their enclosure, and for the fleeting moment when i could attach to its webserver, it as it did in the older enclosure said drive was missing or offline ...

s7

[re3dyb0y]

Well, as long as you didnt attempt to fromat it in the XP machine, the drive 'should' be ok

[starman7]

Thanks for the reply. Any idea why now the webserver says 'disk missing or offline'?

Also -any theories why the webserver is only momentarily available?

Could this be because it is being served from the bad disk (i would think the ws is embedded)?
But why would a ping also only work when the webserver is up?
And, this is the case when the 'bad' drives are in the good enclosure as well.

How might I proceed?

I believe I put the top disk in the WinXP machine. Does it matter?

That Windows XP saw it (as empty) in its disk manager, would this indicate it was the working disk? If one still works ...

This is a 2x160gb device. It was configured for 'redundancy' - which halfed it's total. How does this redundancy work?

If I am unable to figure out, has anyone used a service that was successful in recovery of data? How expensive? What do they charge if unsuccessful?

What might I expect calling Adaptec for a $199 support incident?

update: actually, when i went to their site, even paid support is no longer offered after a certain time, which for me has passed.

Thanks,
s7

[starman7]

thanks to help from blue68f100

lucky for me i was smart enough to have it in RAID1.
i simply disconnected the dead drive. and let the good drive check itself.
after 30 or so minutes and a reboot, i could mount my data again!

which is being backed-up now!! i am a much happier camper. But still quite nervous! this is a work file server. So my ass was not looking good (with my backup being a year old). What is the best/fastest way to backup 160+ GB? It's always been so slow to do, which is why I had it in RAID1. I am copying right now to a lacie 250gb firewire device, w/ the snap on the same 10/100 switch as the machine hosting the firewire drive. Though I am not very confident in the lacie, given my current experience, and that it is not RAID capable.

hope the good drives last long enough for the backup (and restore if necessary) and then to re-mirror.

is re-mirroring easily done through the admin pages? or does it happen automatically? Or must I issue some commands?

where can i find a suitable replacement drive. i have read here it must be IDE, but some drives are specd at IDE/EIDE -would that work as in:

http://www.buy.com/prod/Western_Digi...ml#description

the snap did not seem to want to come up with the bad drive connected (e.g. very intermittent almost impossible access and non responsive pings, almost no disk light activity), even though there was also a good drive in there.

so for me, it seemed to have been necessary to disconnect the bad drive. As having it in, i could not access the admin pages, or ping.

if my backup is successful, would you put the snap back into commission - 30 or so users, hitting it sort of hard sometimes (large files, lots of NFS) w/o having a replacement drive yet? They really depend on it for work. Will re-mirroring be quicker than the copy I am doing now to backup?

[re3dyb0y]

EIDE can work

But IDE is better

IDE/EIDE means it is EIDE, but if it aint supported, it will use IDE


Also, ATA100 is better to get than 133, as some 133 drives cause problems



Seagate make better drives, well, as most snap servers are concerned (less overall reported problems with them)

http://www.buy.com/prod/Seagate_Barr...202153080.html

And Seagate have a 5 year warranty, over WD's 3

Or 160GB

http://www.buy.com/prod/Seagate_Barr...201949355.html

[starman7]

my 1 remaining drive is a WD 160GB -could i put in a 160GB seagate, and re-mirror to it. I was under the impression the drives had to be same make and model???

thanks,
s7

[blue68f100]

In most cases it is prefered to be the same size, make and model. Snap says if it's with in 2% it should work. As long as the smallest actual capacity drive is in position 10000, it should work. The mirror is built off of the 10000 drive.

[starman7]

are there instructions for putting 2 new size disks in a 2200.

i'm considering going to 2x300gb or 2x500 gb from the current 2x160.
any recommendations on which drives to buy?

do i need some image file? can i get this off of the 1 currently working 160gb disk (in position 1)?

thanks,
s7

[blue68f100]

There are instructions for coping the boot/OS tracks from 1 drive to another drive ( or to file) in the wiki section.

If you are needing data off there is a simplier way of doing it. If you were in a RAID 1 when you had a drive failure.

Install the new drive in the 10000 position Top, with the working drive in 10010 bottom. The unit should boot from 10010, then initilize and add the os to the new drive. The snap should report the raid as broken, with a Orphin Drive. Copy the data from 10010 (old) to the new drive. Shutdown and remove the 10010 drive and re-boot to see if it will boot. If so you will need to change the drive config to JBOD. Shutdown and install the new drive into 10010 position. power back up an let the snap do its thing. Once the init has been completed you can change the disk config back to RAID1.

NOTE: If your failed drive was 10010 (bottom), you do not need to swap drives when you replace the failed drive. The snap will reconize it, init and copy the OS over. Copy the data over, power down and install then new drive. It should boot and init the new drive. If it is reporting a broken raid, Break the raid set to JBOD. Then change the drive config back to raid 1. ALL DATA ON DRIVE 1 (top, 10000) WILL BE COPIED TO DRVIE 2 (bot, 10010).

As for drives, I think the last user working on a 2200 installed 2 x 500gig. New Seagates 7200.10 drives. I have 300 in mine.

[starman7]

thanks -is it necessary to copy the boot/os tracks over to the bigger drive to upgrade?

could i just put the bigger drive in the bottom (if the original top drive still works)? would it do it automatically? or is there a debug command that would do it (assuming it would even come up with 2 different drives installed)...

[starman7]

thanks -is it necessary to copy the boot/os tracks over to the bigger drive to upgrade?

could i just put the bigger drive in the bottom (if the original top drive still works)? would it do it automatically? or is there a debug command that would do it (assuming it would even come up with 2 different drives installed)...

[blue68f100]

It will format and install the OS if it was in RAID 1 prior to failure.

It will not Re-Mirror, requires a cmd line from debug. No data will be transfered to the new drive. So if you want the data on the new drive you will need to manually copy it over.