I made a testing to see if clone then modified something could do some help. Luckily it could and here is the record. <\/p>\n\n\n\n
However, the process is on risk thus it is best to have a backup before proceed. <\/p>\n\n\n\n
For example, if the clone direction is wrong the data on the original disk is gone. Thus, please ask if you have any doubt.<\/p>\n\n\n\n
And this method is ONLY suitable for:<\/p>\n\n\n\n
- \n
- Multi-bays Synology NAS<\/li>\n\n\n\n
- Volume type MUST be\u3010Basic\u3011. Not for SHR Volume of single disk. <\/li>\n<\/ul>\n\n\n\n
This testing is done by DSM7.2 and this may change in the future update. <\/p>\n\n\n\n
STEP0. Stop all apps writing to the volume on the small disk.<\/h2>\n\n\n\nBefore cloning disks, we need to STOP<\/strong> apps<\/strong> ( SMB accessing, Surveillance Station, Virtual Machine Manager…etc ) writing data to the volume related to the source disk. <\/p>\n\n\n\n
If data keeps on writing the volume of the smaller disk, the cloned disk clone will contain inconsistent data.<\/p>\n\n\n\n
In this testing, 1TB disk is used to create a Basic Volume 2: <\/p>\n\n\n\n
![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-10-1024x595.png\")
<\/figure>\n\n\n\nWe are going to upgrade this 1TB volume 2 to bigger one by a 8TB disk. <\/p>\n\n\n\n
STEP1. Know the device id under Synology terminal mode. <\/h2>\n\n\n\nTo use command to control the disk, we need to know the disk id under Linux mode. <\/p>\n\n\n\n
For example here, a DS1618+ has 6 disk slots:
<\/p>\n\n\n\n![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-8.png\")
DS1618+ Drive1 ~ 6 count direction<\/figcaption><\/figure>\n\n\n\n ![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-13.png\")
Drive 1 ~ 6 count direction from HDD\/SDD list <\/figcaption><\/figure>\n\n\n\n Each disk device id is: <\/p>\n\n\n\n
- \n
- Drive 1 \u2192 \/dev\/sda<\/li>\n\n\n\n
- Drive 2 \u2192 \/dev\/sdb<\/li>\n\n\n\n
- Drive 3 \u2192 \/dev\/sdc<\/li>\n\n\n\n
- Drive 4 \u2192 \/dev\/sdd<\/li>\n\n\n\n
- Drive 5 \u2192 \/dev\/sde<\/li>\n\n\n\n
- Drive 6 \u2192 \/dev\/sdf<\/li>\n<\/ul>\n\n\n\n
Similar logic could be applied to other Synology NAS model.<\/p>\n\n\n\n
<\/p>\n\n\n\n
STEP2. Clone the source disk to the bigger disk via Linux command dd<\/h2>\n\n\n\ndd is a basic Linux command used here to clone the sector from 1TB disk to 8TB disk. <\/p>\n\n\n\n
We want to clone the smaller 1TB disk5 ( \/dev\/sde ) to 8TB disk6 ( \/dev\/sdf ).<\/p>\n\n\n\n
![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-12.png\")
Clone direction: Drive 5 to Drive 6<\/figcaption><\/figure>\n\n\n\n Login Synology via SSH<\/a> <\/strong>and Syntax of cloning the whole disk is:<\/p>\n\n\n\n
<\/p>\n\n\n\n
adair@one1618p:~$ sudo -i\nPassword:\nroot@one1618p:~# dd if=\/dev\/sde of=\/dev\/sdf bs=64k<\/code><\/pre>\n\n\n\n- \n
- if = input file. Here is the source disk, disk5: \/dev\/sde.<\/li>\n\n\n\n
- of=output file. It is 8TB disk6, the target bigger disk: \/dev\/sdf.<\/li>\n\n\n\n
- bs is block size. Setting to 64k could get best clone speed in Synology NAS. <\/li>\n<\/ul>\n\n\n\n
Observe the clone speed on Resource Monitor <\/p>\n\n\n\n
![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-9-1024x611.png\")
The command “dd” read Disk5 and write to Disk6<\/em><\/figcaption><\/figure>\n\n\n\n
The average writing speed could be treated about 150MB\/s.<\/p>\n\n\n\nOnce the cloning press is done, ssh terminal will be like this: <\/p>\n\n\n\n
root@one1618plus:~# 15261915+1 records in\n15261915+1 records out\n1000204886016 bytes (1.0 TB, 932 GiB) copied, 6887.13 s, 145 MB\/s<\/code><\/pre>\n\n\n\nCloning 1TB disk to other device means to read 1TB data. <\/p>\n\n\n\n
This will cost about 1.9hrs.<\/p>\n\n\n\n
STEP3. Repartition the bigger disk so it reports its full size<\/h2>\n\n\n\nThe command dd <\/strong>clones the info of every sector of the source disk to target disk, including the partition table.<\/p>\n\n\n\n
The target disk partition table has old resource disk size definition. To correct this, we will need to repartition the bigger target disk for its real size.<\/p>\n\n\n\n
There are many version of Synology disk partition layout after years of development. Thus Synology has a command called synopartition<\/strong> to handle different layout. <\/p>\n\n\n\n
There are 2 parts for this step. <\/p>\n\n\n\n
Part1. Know the partition layout version of old smaller disk<\/h3>\n\n\n\n
This part 1 is to examine the old smaller disk5, 1TB, \/dev\/sde. Here is how to examine the version for disk5, \/dev\/sde. <\/p>\n\n\n\n
It is version 9<\/strong> and its index number is 15<\/strong>. <\/p>\n\n\n\n
root@one1618p:~# synopartition --check \/dev\/sde<\/strong>\n\/dev\/sde: partition layout is version 9, list index is 15.\nroot@one1618p:~# synopartition --list<\/strong>\nIndex Version 1-Bay Size of Root\/Swap\/Reserved Partition\n 1. 1 YES 273042\/ 787185\/ 273042 sectors ( 133\/ 384\/ 133 MB)\n 2. 2 YES 4980087\/ 1044225\/ 257040 sectors ( 2431\/ 509\/ 125 MB)\n 3. 3 YES 530082\/ 787185\/ 16002 sectors ( 258\/ 384\/ 7 MB)\n 4. 5 YES 722862\/ 594405\/ 16002 sectors ( 352\/ 290\/ 7 MB)\n 5. 6 YES 4980087\/ 4192965\/ 257040 sectors ( 2431\/ 2047\/ 125 MB)\n 6. 7 YES 4980480\/ 4194304\/ 262144 sectors ( 2431\/ 2048\/ 128 MB)\n 7. 8 YES 4980480\/ 4194304\/ 260352 sectors ( 2431\/ 2048\/ 127 MB)\n 8. 9 YES 16777216\/ 4194304\/ 262144 sectors ( 8192\/ 2048\/ 128 MB)\n 10. 1 NO 1574307\/ 787185\/ 273105 sectors ( 768\/ 384\/ 133 MB)\n 11. 2 NO 4980087\/ 1044225\/ 257040 sectors ( 2431\/ 509\/ 125 MB)\n 12. 6 NO 4980087\/ 4192965\/ 257040 sectors ( 2431\/ 2047\/ 125 MB)\n 13. 7 NO 4980480\/ 4194304\/ 262144 sectors ( 2431\/ 2048\/ 128 MB)\n 14. 8 NO 4980480\/ 4194304\/ 260352 sectors ( 2431\/ 2048\/ 127 MB)\n 15. 9 NO 16777216\/ 4194304\/ 262144 sectors ( 8192\/ 2048\/ 128 MB)\n <\/strong>19. 100 YES 41943040\/ 4194304\/ 0 sectors (20480\/ 2048\/ 0 MB)\n 20. 100 NO 41943040\/ 4194304\/ 0 sectors (20480\/ 2048\/ 0 MB)<\/code><\/pre>\n\n\n\nPart2. Repartition the bigger new disk<\/h3>\n\n\n\n
Part2 is to partition to the bigger disk, here it is 8TB disk6<\/strong>, \/dev\/sdf<\/strong>. <\/p>\n\n\n\n
And we want to partition it to be verion 9, index 15<\/strong>. Syntax is: <\/p>\n\n\n\n
root@one1618p:~# synopartition --part \/dev\/sdf 15<\/strong>\n\n Device Sectors (Version9: SupportRaid)\n \/dev\/sdf1 16777216 (8192 MB)\n \/dev\/sdf2 4194304 (2048 MB)\nReserved size: 262144 ( 128 MB)\nPrimary data partition will be created.\n\nWARNING: This action will erase all data on '\/dev\/sdf' and repart it, are you sure to continue? [y\/N] y\nCleaning all partitions...\nCreating sys partitions...\nCreating primary data partition...\nPlease remember to mdadm and mkfs new partitions.<\/code><\/pre>\n\n\n\nIt will tell erase all data, but it will not as it does a quick partition only. This does not touch data in the existed volume in this disk.<\/p>\n\n\n\n
To check more details about synopartition, you could google it or type ” synopartition –help<\/strong> ” under SSH terminal. <\/p>\n\n\n\n
root@ad1618:~# synopartition --help\nCopyright (c) 2003-2023 Synology Inc. All rights reserved.\n\nUsage: synopartition (Version )\n--help Show this help.\n--list List the partition layout table.\n--check disk_path(eg.\/dev\/sda)\n Check the partition layout version.\n--remove disk_path [part_no]\n Remove specific partition of disk. Remove all partitions if not specific.\n--part [--force] disk_path index_of_list(1~20) [logical_size_GB ... 0]\n Partition the disk with specific layout.\n--scan-syno-part\n Scan all disk partition which matches syno partition layout.\n If you select layout version less than 6, the logical size will be skip.\n Else you can assign max to 11 logical partitions size with unit GB and end with 0.\n If you don't assign logical size parameters, primary data partition will be created instead.\n\n Please note the index of list may modified in future.\n--log disk_path\n Log start offset and size to file for every partition in the disk_path.<\/code><\/pre>\n\n\n\n<\/p>\n\n\n\n
STEP4. Reboot Synology NAS with the bigger disk<\/h2>\n\n\n\nHere comes the final progress: <\/p>\n\n\n\n
- \n
- Power off Synology NAS<\/li>\n\n\n\n
- Remove the old, smaller disk ( Now it’s our backup ).<\/li>\n\n\n\n
- Power on Synology NAS with the new, bigger disk. <\/li>\n<\/ul>\n\n\n\n
After booting up, the old, smaller size 1TB volume is still there. <\/p>\n\n\n\n
There is a “ expand now<\/span><\/strong> ” link under Storage Manager > Storage Pool. Just click the link:<\/p>\n\n\n\n
![\"\"](\"https:\/\/synopower.club\/wp-content\/uploads\/2024\/04\/image-7-1024x442.png\")
<\/figure>\n\n\n\n1TB volume 2 will be expanded to 8TB volume2. <\/p>\n\n\n\n
<\/p>\n\n\n\n
The above is all. <\/p>\n\n\n\n
From my personal opinion, it is best that Synology directly supports this function on Storage Manager to clone the disk. This feature is useful and convenient. The reasons could be seen in the following posts too: <\/p>\n\n\n\n
- \n
- Replace one drive with bigger basic 1 volume drive<\/a><\/li>\n\n\n\n
- Cloning a disk?<\/a><\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n\n
Upgrading to a Bigger Disk FAQ<\/h2>\n\n\n
\n\n\nWill I lose data moving a Basic volume to a bigger disk?<\/h3>\n
\n\nNot with this method. The clone copies the source disk block for block, so the volume and its data arrive intact. Take a backup first anyway, because a clone that goes wrong halfway leaves you with two unusable disks.<\/p>\n\n<\/div>\n<\/div>\n
\nWhy can a Basic volume not just be expanded in Storage Manager?<\/h3>\n
\n\nA Basic volume sits on one disk with no spare room to grow into. Expanding in place needs either a second disk to convert to SHR or RAID, or a bigger disk with the volume moved onto it, which is what this guide does.<\/p>\n\n<\/div>\n<\/div>\n
\nDo both disks have to be in the NAS at the same time?<\/h3>\n
\n\nYes for the clone step. That is why this only works on a multi-bay unit: the source and the bigger disk both need to be visible to the same running DSM.<\/p>\n\n<\/div>\n<\/div>\n
\nWhy does the partition need to be edited after cloning?<\/h3>\n
\n\nThe clone reproduces the original partition table as well as the data, so the new disk reports the old smaller size. Repartitioning tells the system to use the extra space that the bigger disk actually has.<\/p>\n\n<\/div>\n<\/div>\n
\nIs this supported by Synology?<\/h3>\n
\n\nNo. It uses the DSM shell and standard Linux tools, which is outside what Synology support will help with. Use it when the alternative is rebuilding the volume from backup, and keep that backup until the result is verified.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n
- Cloning a disk?<\/a><\/li>\n<\/ul>\n\n\n\n
- Replace one drive with bigger basic 1 volume drive<\/a><\/li>\n\n\n\n