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

It'll be interesting to see what happens - in a hardware RAID environment, if you replaced a 200GB disk with a 750GB one, you would typically lose the remaining 550GB of space, although I believe some of the newer RAID controllers do allow the "container" to be expanded as a separate operation once all of the original members have been replaced with the larger ones.

Apart from the situation described above - which could force you to reformat to recover the missing space - it should work.  I have done something similar with an IBM xSeries server, replacing three drives in a RAID5 array, one by one, each time waiting for the rebuild to complete, before replacing the next drive - the purpose of the exercise in this case was the "pre-emptive" replacement of a suspected defective drives - we had had an unusually high number of failures and the decision was made to replace all the drives of a particular part number.

There should be no need to swap the 750 from left to right (step #6), as the unit should rebuild from either bay - also - if you look at steps 3 & 4 - you're apparently inserting a 750 GB drive with the power on - I suspect this is an error in the sequence, rather than the actual plan, but I will tell you - in my experience, the unit will not detect a "hot inserted" drive - yes - I did test that

A 250GB drive takes a few hours to resync - I don't recall exactly, but not more than 3 at the most 4 hours.

Last edited by fordem (2008-01-31 00:32:04)

the issue i will have is that the contents of the old HD (to be replaced) have really LOOOOOOOONG file names and a HUMUNGUS folder structure at least 16 tiers down. this causes issues in respect to file copy as i get errors like .. . cannot copy file / folder

can someone advise a way around that long file name / folder issue?

standard windows copy

fickle wrote:

the issue i will have is that the contents of the old HD (to be replaced) have really LOOOOOOOONG file names and a HUMUNGUS folder structure at least 16 tiers down. this causes issues in respect to file copy as i get errors like .. . cannot copy file / folder

can someone advise a way around that long file name / folder issue?

I've come across a related problem using Windows and the DNS-323 built-in samba.  When I tried deleting files (from Windows Explorer), it wouldn't delete anything with a pathname (complete directory names plus filename) longer than 256 characters.  I'm guessing this would be true for a copy also.

Your alternatives are to copy using telnet on the DNS-323, or you might get away with a Windows command-line tool like robocopy (http://en.wikipedia.org/wiki/Robocopy).  It might also occur (from googling quickly about it) if you haven't mapped a drive letter to the DNS-323 shared folder.  This is true in my case--I was just using the UNC path (\\192.168.1.200\Volume_1\...) in Windows Explorer when I came across the problem.

From quickly browsing Google I couldn't tell if this is a Samba problem, a Windows problem, or an Explorer problem.  In any case, telnetting into box allowed me to easily delete the affected files.

If you're really stuck and nothing above helps, and you're trying to copy from the DNS-323 to a Windows PC, you could use SCP (basically a secure version of FTP, but using SSH).  To do that, setup the SSH server (called dropbear) from fonz' fun_plug on the DNS-323.  Then download WinSCP for Windows to connect.  Just post if you need more help.

Last edited by blbrown (2008-01-31 04:17:35)

Use telnet and cp or mv commands. Mount your old disk via usb on the DNS-323 and it is as simple as doing:

cp -pr /mnt/USB/dir /mnt/HD_a1/dir

oh, btw, i was advised on the dlink forum site that an upgrade of HD's via the method i posted above will not provide full capacity of the additional space. that additional space will be created via JBOD, but id rather do RAID1.. so it seems copy first, then insert, format, copy back