SpamMaster50000  Freshman Member

Can i use losetup instead?

Hmm, not good the problem was that my version of mdadm doesn't yet know the data offset option ~ # mdadm --build --assume-clean --level=linear --raid-devices=2 --rounding=64K --data-offset=16 /dev/md2 /dev/sda3 /dev/sdb3 mdadm: unrecognized option '--data-offset=16' Usage: mdadm --help for help

So i guess it's testdisk now... Or do you see something where i made an error?

Ok 2) ~ # mdadm --build --assume-clean --level=linear --raid-devices=2 --rounding=64K --metadata=1.2 /dev/md2 /dev/sda3 /dev/sdb3 mdadm:option --metadata not valid in build mode so i used ~ # mdadm --build --assume-clean --level=linear --raid-devices=2 --rounding=64K /dev/md2 /dev/sda3 /dev/sdb3 mdadm: array /dev/md2 built…

Ok, It's been a while but i managed to get some things done and wanted to sync the next steps with you. First: I managed to get those clones using ssh. Tried it with DEV1 and saw what you described (headers were deleted when i deleted the volume group in the NAS GUI). Then i made copies (5GB) of sda, sda3, sdb and sdb3 of…

Hi, this little "sidequest" was supposed to go fast. Instead i have huge problems getting a file... Tried three methods now... 1) [remote] with putty on windows 2) [remote] on VM Ubuntu 3) [local] on VM Ubuntu where [remote] means i run dd from the remote station - i.e. NAS. [local] means i run dd from the local station -…

what do you think of getting an image of the drives initial data (maybe a gigabyte or so)? I'm experimenting with: dd if=/dev/sda bs=1M count=1000 | ssh admin@192.168.0.XX dd of=cloneofsda.img Another benefit would be a file that i can have a look at. Of course the true purpose is a fallback position in case headers are…

New Sandbox on DEV2 with ~13 TB JBOD Volume ~ # cat /proc/partitions major minor #blocks name 7 0 144384 loop0 31 0 2048 mtdblock0 31 1 2048 mtdblock1 31 2 10240 mtdblock2 31 3 15360 mtdblock3 31 4 108544 mtdblock4 31 5 15360 mtdblock5 31 6 108544 mtdblock6 8 0 13672382464 sda 8 1 1998848 sda1 8 2 1999872 sda2 8 3…

Thank you so much for your patience! I am a little confused about the terminology "Disk Group". From vgscan I learned a bit about LVM, which operates with Physical Volumes (PV), Volume Groups (VG) and Logical Volumes (LV)... I think i understand that concept (sorry so far i was just a user and never bothered to dig into…

Yes, i think i did, because it would be the use case. Ok, we'll see once i try it. As for the other instructions: I'm not sure i understood correctly... Here's what i did ~ # cat /proc/partitionsmajor minor #blocks name 7 0 144384 loop0 31 0 2048 mtdblock0 31 1 2048 mtdblock1 31 2 10240 mtdblock2 31 3 15360 mtdblock3 31 4…

Thanks for the instructions. I used DEV2 as a Sandbox to test everything (no offense). I did the following 1) Create JBOD2) [pre]: Examine with mdadm via SSH "mdadm --examine /dev/sd[ab]3" 3) Copy test data on NAS4) Deleted "Disk Group" in Web Interface5) Rebooted NAS6) checked "mdadm --examine /dev/sd[ab]3" 7) Created new…

Thanks for the instructions. So as a first test i started the whole process on the DEV2 as a sandbox (no offense). I did the following * i created a JBOD (max drive space, all default settings) * got SSH "mdadm --examine /dev/sd[ab]3" info [pre] * Copied some test data on the drive * deleted the whole "Disk Group" *…

You are right, just tried that on DEV2 and as you said it doesn't touch the volumes or Disk Groups Btw, i just noticed that there is a difference between Volume and Disk Group (as long as the "Disk Group" is not deleted the "Create Volume" options are fixed to "Existing Disk Group"). However i seem to have deleted the…

Thank you for the reply Mijzelf. Before i proceed with your idea allow me one question. I may have a configuration backup file (.rom). Could i restore the volume by simply loading this file into the NAS? Can this hurt anything?