DSM-G600, DNS-3xx and NSA-220 Hack Forum

Well that took a few days of beating my head against the wall and reading ALOT on drive recovery, but after dlink RMAd my box, i sorted out a way to make it work!

basically, i cloned the offending drive with the assistance of a cute little script entitled "dd_rhelp"

it took 20 hours, and was almost 4 times as fast as dd.
average transfer rate over USB of
took duplicate, dropped it in my 343, and proceeded to power up.
before i could even get into the web interface it sent me prowl notifications.

now i have a few questions in with the engineer at dlink.. like:

if its behaving PROPERLY
will it boot and access data with the bottom 3 bays still loaded, of course assuming raid 5 was configured on all 4...?

and  if i decide to start populating this thing with 2TB drives, will i be able to swap them out one at a time, let them rebuild and move to the next one, eventually with the last drive in place have 6T operational storage?

hopefully i will have an answer tuesday.

exchange as follows:
-------------------
On Fri, May 28, 2010 at 6:08 PM, JD wrote:
dunno if you recall- we spoke on the phone the other day, and we decided to RMS the device..

had a question for you..
if its behaving PROPERLY
will it boot and access data with the bottom 3 bays still loaded, of course assuming raid 5 was configured on all 4...?

and my next question is if i decide to start populating this thing with 2TB drives, will i be able to swap them out one at a time, let them rebuild and move to the next one, eventually with the last drive in place have 6T operational storage?
--------------------------------
JD,

Yes it will as long as there wasn't an issue on one of the remaining to cause this in the first place as well as the failed drive.

If you want to crate a larger RAID5 volume you will need to backup your data and reformat selecting a larger Volume size once all larger drives are present.
-------------------------------------------------------------





So how did it end?

Dropping in a new drive made it want to force a format. Part of said format, if you choose raid5, will WIPE your data.. on ALL drives!

I ended up dropping the new drive in a 2 drive bay with the old drive, which was having SMART errors, and running a command using:
http://www.kalysto.org/utilities/dd_rhelp/index.en.html
(yup, i'm a linux guy)

dd_rhelp if=/dev/sdb of=/dev/sdc notrunc
tho you can try :
dd_rhelp if=/dev/sdb1 of=/dev/sdc1 notrunc
and count up as you go..
me- im a set it and forget it kinda guy.

it makes a complete scan of the source drive and even sets up file format and partitions exactly on the new drive..
stripped all the drives, updated to the beta software (1.04b03) to keep it from crashing during rebuild, set it to auto rebuiild, powered it off,
populated the drives in their appropriate slots, powered it up, then let her rip.
a few hours later it finished rebulid.
(tho its preformance during rebuild is kinda lousy, IMHO, but once its done its working like a champ, as in i havnt restarted this bloody thing since early June)
i just wish i could figure out how to fix the uptime bug!