NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
brettgavin
Feb 12, 2012Tutor
Mount previously created raid via USB
Hi,
Please forgive me if this has already been covered, but I didn't find it.
I set up my Pro6 the other day with one 2TB disk and planned to add my other, smaller disks later. I didn't realize that Xraid2 requires that the smaller disks be the first disks in the volume. So, I offloaded almost 2TB worth of data onto the first disk. I inserted the first of my smaller disks, and the readynas displayed an error about the size of the disk being to small. I pulled the 2TB disk and did a factory reset with one of the small disks in bay 1. I have since recreated the raid with 4 disks (3x500, 1x1000).
Here's what I would like to do:
option A:
either plug the 2TB disk into the Readynas via USB and do a direct file copy from the 2TB to the internal volume;
or
option B:
plug the disk into the computer using ubuntu or knoppix, mount the 2TB, and push it over the network to the readynas.
My questions are:
is option A possible? I don't want it to erase the disk and create a new partition.
if option A isn't going to work, what is the best procedure for accomplishing option B?
Thanks in advance,
Brett
Please forgive me if this has already been covered, but I didn't find it.
I set up my Pro6 the other day with one 2TB disk and planned to add my other, smaller disks later. I didn't realize that Xraid2 requires that the smaller disks be the first disks in the volume. So, I offloaded almost 2TB worth of data onto the first disk. I inserted the first of my smaller disks, and the readynas displayed an error about the size of the disk being to small. I pulled the 2TB disk and did a factory reset with one of the small disks in bay 1. I have since recreated the raid with 4 disks (3x500, 1x1000).
Here's what I would like to do:
option A:
either plug the 2TB disk into the Readynas via USB and do a direct file copy from the 2TB to the internal volume;
or
option B:
plug the disk into the computer using ubuntu or knoppix, mount the 2TB, and push it over the network to the readynas.
My questions are:
is option A possible? I don't want it to erase the disk and create a new partition.
if option A isn't going to work, what is the best procedure for accomplishing option B?
Thanks in advance,
Brett
51 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredThe problem is you have a volume with the same name using devices with the same names as the internal disks in the NAS. You'd need to rename some stuff and then use SSH to mount it. Not easy but doable.
You'd need to unmount the volume, do
umount /dev/c/c
lvchange -an /dev/c/c"
lvrename /dev/c/c /dev/oldvol/oldvol
You'll also need to do
mdadm --stop -scan
and then assemble replacements for /dev/md0 /dev/md1 and /dev/md2 using mdadm.
This is in order not to conflict with what's used by the internal disks in the NAS.
You'd also need to have SSH access to be able to mount your old volume when the disk is connected to the NAS via USB. - Great, thanks for the help.
am i supposed to run the lvrename cmd on the readynas via ssh or on ubuntu? when i run it on ubuntu, it won't let me rename it to /dev/oldvol/oldvol, it says the old and new must have the same volume group. i did rename it to /dev/c/oldvol, will that be enough?
root@ubuntu:/dev/c# lvrename /dev/c/oldvol /dev/oldvol/oldvol
Logical volume names must have the same volume group ("c" or "oldvol")
Run `lvrename --help' for more information. - mdgm-ntgrNETGEAR Employee RetiredI think /dev/c/oldvol should be enough.
However you will need to get new names for the md stuff as well.
You'll need to do this using Ubuntu so that the names aren't conflicting when you connect the disk back to the ReadyNAS again. - I'm sorry to ask so may questions. I know enough to get around linux, but am by no means proficient.
I re-ran
vgscan and mdadm --assemble --scan
I don't see /dev/md0 or md1. /dev/md2 is present.
Was I correct in running those commands? Am I missing something? - mdgm-ntgrNETGEAR Employee RetiredWell I guess the data volume on /dev/md2 is what you care about. You will need to assemble it under a different name to avoid conflicting with the name of the one internally in the ReadyNAS.
- Based on what I've read about mdadm, the command to accomplish this should be something like this:
mdadm --assemble --name=brett
Correct?
I do have a folder at /dev/md
Its contents are:
root@ubuntu:/dev/md# ls
001F33EAE093:0 001F33EAE093:1 2
Are these the md0 and md1 you referenced earlier? - ok. I see that --name is for specifying the name of the existing array, not to set a new name. --update doesn't seem to have the right options either. Do you have any suggestions?
- mdgm-ntgrNETGEAR Employee RetiredI'm not sure as I haven't done it myself. You can give it a try.
- ok. i think i've got it!
i used these instructions:
http://serverfault.com/questions/267480 ... raid-array
and renamed the three partitions to md111 md222 and md333
should i be able to plug this into the readynas without conflict now? - mdgm-ntgrNETGEAR Employee RetiredYou should be able to connect the disk via USB now.
You'll need to use SSH access to be able to mount the volume on the external drive though.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!