Removing drive and moving data from DLink DNS-323 (Alt-F 1.0) to Synology DS213j

[Denis Heraud]

Hi all!

So I'm trying to move the data on my 4TB drives (2x4TB ext4 in Raid1) from a DLink DNS-323 (running Alt-F 1.0) to Synology DS213j (DSM 6.2).

I really don't want to do this over the network as the performance on the DNS-323 is dismal. I was more interested in removing one of the physical hard drives from the DNS-323 and moving the data over USB to the DS213j.

How can this be achieved? I tried failing one of the drives in Alt-F but it wouldn't let me remove it (some error about it being in use?), then I tried mounting the drive in Ubuntu to access the files and I just couldn't get it to mount (probably because I was unable to remove it from the array?).

In any case, is there a way to make at least one of my two mirrored drives readable outside the DNS-323 so that I can transfer my files over?

Thank you!

[Tom Schmidt]

I suggest shutting down your DNS-323, then removing one of its drives.  Then if you have a SATA to USB adapter, you can connect that drive to the USB port of the Synology, mount it, then use rsync to transfer what you want.  Once completed, return the drive to the same bay on your DNS-323 and power it back up.  This way no RAID reconstruction is needed by breaking the mirror.

Tom

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/ef2c0078-f3e3-43a9-89f3-f511dad3879b%40googlegroups.com.

[Denis Heraud]

Thanks for your answer Tom. I've already tried what you are suggesting by removing one of the drives and putting it in a USB enclosure and connecting it to my Mac (running Ubuntu), but I could not get the drive to mount, so I could not access any of the files. Given that I can't use the drive on a computer, what are the odds I could connect it to the DS213j and be able to transfer my files there?

On Wednesday, March 11, 2020 at 3:04:02 PM UTC-4, Tom Schmidt wrote:

I suggest shutting down your DNS-323, then removing one of its drives.  Then if you have a SATA to USB adapter, you can connect that drive to the USB port of the Synology, mount it, then use rsync to transfer what you want.  Once completed, return the drive to the same bay on your DNS-323 and power it back up.  This way no RAID reconstruction is needed by breaking the mirror.

Tom

On Wed, Mar 11, 2020 at 12:55 PM Denis Heraud <dhe...@gmail.com> wrote:

Hi all!

So I'm trying to move the data on my 4TB drives (2x4TB ext4 in Raid1) from a DLink DNS-323 (running Alt-F 1.0) to Synology DS213j (DSM 6.2).

I really don't want to do this over the network as the performance on the DNS-323 is dismal. I was more interested in removing one of the physical hard drives from the DNS-323 and moving the data over USB to the DS213j.

How can this be achieved? I tried failing one of the drives in Alt-F but it wouldn't let me remove it (some error about it being in use?), then I tried mounting the drive in Ubuntu to access the files and I just couldn't get it to mount (probably because I was unable to remove it from the array?).

In any case, is there a way to make at least one of my two mirrored drives readable outside the DNS-323 so that I can transfer my files over?

Thank you!

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.

To unsubscribe from this group and stop receiving emails from it, send an email to al...@googlegroups.com.

[Tom Schmidt]

Since it is a RAID1 disk, you may have to make a md virtual disk for it first.  See  https://blog.sleeplessbeastie.eu/2012/05/08/how-to-mount-software-raid1-member-using-mdadm/ for an example.

Tom

To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/8ec08af6-5431-4a50-92f9-19efbb0b7626%40googlegroups.com.

[Denis Heraud]

Thank you for the link, what is described there is my problem exactly! I will give that a try tonight and report back!

To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/8ec08af6-5431-4a50-92f9-19efbb0b7626%40googlegroups.com.

[Denis Heraud]

So I tried what the blog post suggests, however, I get the following error:

=======================================

~$ sudo cat /proc/mdstat

Personalities : 

md127 : inactive sdd2[0](S)

      3906064080 blocks super 1.0

       

unused devices: <none>

~$ sudo mdadm -A -R /dev/md127 /dev/sdd2

mdadm: /dev/sdd2 is busy - skipping

======================================= 

The HDD is in a USB enclosure, and once connected to my laptop, I get an error after running mdadm that /dev/sdd2 is "busy"...

I've googled that error but nothing seems to help me get past this.

To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/8ec08af6-5431-4a50-92f9-19efbb0b7626%40googlegroups.com.

[Joao Cardoso]

On Thursday, March 12, 2020 at 5:46:19 PM UTC, Denis Heraud wrote:

So I tried what the blog post suggests, however, I get the following error:

=======================================

~$ sudo cat /proc/mdstat

Personalities : 

md127 : inactive sdd2[0](S)

      3906064080 blocks super 1.0

       

unused devices: <none>

It shouldn't even say "inactive"

 

~$ sudo mdadm -A -R /dev/md127 /dev/sdd2

mdadm: /dev/sdd2 is busy - skipping

It thinks that sdd2 is already being used, you must stop the array first. The state that ssd2 is now depends on how the initial array was stopped and/or sdd2 removed from the array.

Use

mdadm --stop /dev/md127

and now 'cat /proc/mdstat' shouldn't print nothing and you can assemble it

mdadm --assemble /dev/md10 /dev/sdd2 # -A == --assemble, -R == --run

I used md10 here, you can use whatever you want, e.g. md0, as long as it does not exists, i.e., it does not appears on 'cat /proc/mdstat' output.

You can (would) now mount /dev/md10.

But the output of 'mdadm --examine /dev/sdd2'  would be useful.

If the array was created by the D-Link fw, the 'mdadm --examine' option would say Version 0.9 (or 0.90?), and if created under Alt-F it would be 1.0.

Both of these md versions put the raid metadata at the end of the partition, so the partition should be recognized as being ext2/3/4 (the 'blkid /dev/sdd2' command would say so) and it should be possible to mount sdd2 directly without assembling the array.

You couldn't do it, so I assume that some other error exists. I assume because you didn't post the sdd2 mount command you used and its the output.

If the md version is 1.1 or 1.2, the md metadata is put at the partition start, so 'blkid' will probably say its part of a raid array and it has to be assembled before for it to be mounted.

[Denis Heraud]

Hi Joao! Thank you for your post.

I ended up getting it to mount (finally!) before reading your post after I came across this post:

https://superuser.com/questions/117824/how-to-get-an-inactive-raid-device-working-again

Thanks for your input!