Andre Kiss Uber

thank you, João, that metadata "detail" completely slipped my mind. As to using the web wizard, that was my first option, but it did not work, as i reported before, in first post, with error like " All componentes must be different. " please check my first post , i have proposed a possible solution ?? i did create the same (identical) partition scheme, as in first disk, in such way to have swap partition on all disks as for rsync beeing slower, i agree, i will try CP next time thanks again

stage 2: comand to copy from original raid (md0) to new raid (md1), in ssh session rsync -av --exclude lost+found /mnt/md0/ /mnt/md1/ =OK stage 3: poweroff, remove old remaining small disk (sda), from box insert new large disk, in empty slot, turn power on in web interface: - copy partition scheme from sdb to sda =OK - in raid menu, Raid Maintenance - choose COMPONENT "sda2", and OPERATION "add" md1 goes to recovery status and starts to rebuild /dev/md1 = OK job done, the problem that i havent figured...

many KUDOS to João for this fabulous work that is ALT-F currenty experimenting alt-f in dlink dns-320, after many years with default firmware+funplug the aproach above to migrate hdds and grow raid size seems very useful, and i decided to try it after failing sdb from md0, poweroff the box and remove disk = OK insert new, bigger SDB. = OK create partition for swap, like in sda, and raid with remaining space = OK create new raid1 using NONE as component 1, sdb2 as component 2, and NONE as spare =...

many KUDOS to João for this fabulous work that is ALT-F currenty experimenting alt-f in dlink dns-320, after many years with default firmware+funplug the aproach above to migrate hdds and grow raid size seems very useful, and i decided to try it after failing sdb from md0, poweroff the box and remove disk = OK insert new, bigger SDB. = OK create partition for swap, like in sda, and raid with remaining space = OK create new raid1 using NONE as component 1, sdb2 as component 2, and NONE as spare =...