Pro/Forums - View Single Post

starman7 · 08-06-2006, 01:31 PM

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?

08-06-2006, 01:31 PM	#4
starman7 Cooling Neophyte Join Date: Aug 2006 Location: in the city Posts: 10	Re: dead 2200 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?