{"id":201,"date":"2017-06-11T15:39:40","date_gmt":"2017-06-11T13:39:40","guid":{"rendered":"http:\/\/www.gadjev.com\/?p=201"},"modified":"2020-04-03T10:17:10","modified_gmt":"2020-04-03T08:17:10","slug":"xpenology-on-vmware-disk-extend","status":"publish","type":"post","link":"https:\/\/www.gadjev.com\/2017\/06\/11\/xpenology-on-vmware-disk-extend\/","title":{"rendered":"Xpenology on VMware – Disk Extend"},"content":{"rendered":"

Recently I run out of free space on one of my XPenology DSM 6 drives and had to run an extend.<\/p>\n

Since it’s running on ESXi, the VMware disk extend was easy. However surprisingly or not the Synology part wasn’t. The GUI does not allow you to increase the size of the RAID Group (in my case Basic without protection – single disk RAID1, Storage Manager–>RAID Group–>Manage the “Expand” option is grayed out)<\/p>\n

So it was obvious manual resize through SSH is necessary.<\/p>\n

After some time spend on googling good articles for doing this, the best one i found was http:\/\/blog.azib.net\/2013\/12\/how-i-upgraded-my-synology-nas-to.html<\/a>. It explains quite well the overall process of manually extend the volume (extend the vmware disk partition, the MD device, the physical, virtual and logical LVM volumes)<\/strong> , however I found Step 1 from the guide as dangerous (the partition recreation with a larger one) so I decided to try the parted partition resize option instead<\/strong>.<\/p>\n

Below are the commands used, but first PLEASE BACKUP YOUR DATA<\/strong> without attempting anything:<\/p>\n

    \n
  1. Extend the Disk in the VMware VM<\/strong> and connect to Synology using SSH <\/strong>(sudo su as needed).<\/li>\n
  2. parted<\/strong> – launch the parted partition editor<\/li>\n
  3. select \/dev\/sdX<\/strong> – chose which drive to work with (in my case \/dev\/sdc)<\/li>\n
  4. unit s<\/strong> – work with sectors instead of GBs (otherwise you might get a message saying you get outside of disk boundaries)<\/li>\n
  5. print free<\/strong> – two reasons for running this – 1. make sure you work with the correct drive; and 2. that you see the free space provisioned from VMwareModel: VMware Virtual disk (scsi)
    \nDisk \/dev\/sdc<\/strong>: 6012954214s
    \nSector size (logical\/physical): 512B\/512B
    \nPartition Table: gpt
    \nDisk Flags:<\/p>\n

    Number Start End Size File system Name Flags
    \n34s 2047s 2014s Free Space
    \n1 2048s 4982527s 4980480s ext4 raid
    \n2 4982528s 9176831s 4194304s linux-swap(v1) raid
    \n9176832s 9437183s 260352s Free Space
    \n3<\/strong><\/em><\/span> 9437184s 5153755935s 5144318752s raid
    \n5153755936s 6012954180s<\/span> 859198245s Free Space      <–the free space is after the last (3rd) partition in the disk<\/strong><\/li>\n

  6. resizepart<\/strong> – run the command to resize the partition\n
      \n
    1. Partition number? 3<\/strong><\/span> <– enter the partition number to edit (replace with 3 with your partition number)<\/li>\n
    2. End?  [5153755935s]? 6012954180s<\/span><\/strong> <–Enter the new last partition sector as seen in the print free command<\/li>\n<\/ol>\n<\/li>\n
    3. quit<\/strong> the parted editor<\/li>\n
    4.  Now it’s time to extend the RAID MD device<\/strong>. To do it first you have to stop any activity on it\n
        \n
      1. lsof | grep volume 3<\/strong> (if lsof is missing – install it from here http:\/\/ipkg.nslu2-linux.org\/feeds\/optware\/syno-i686\/cross\/stable\/) <– check for open files on the volume<\/li>\n
      2. In my case only samba was using the drive and it was stopped by \/usr\/syno\/etc.defaults\/rc.sysv\/S80samba.sh stop <\/strong>.Follow Anton’s guide since it’s more detailed on how to find & stop the service using the drives, especially if you work with the volume where Synology packages are installed – usually volume1.<\/li>\n
      3. lsof | grep volume3<\/strong> <– run it again to ensure nothing remains using the volume.<\/li>\n
      4. umount \/volume3<\/strong> <– unmount the volume (the GUI might start reporting it as crashed – ignore this for the moment)<\/li>\n
      5. vgchange -a n<\/span> vg3<\/strong> <– deactivate the LVM Volume Group. Replace vg3 with your VolumeGroup Name (use vgdisplay -v or vgs commands to identify it)<\/li>\n
      6. Stop and Re-assemble the RAID array
        \nmdadm -S \/dev\/md5<\/span><\/strong> <– replace \/dev\/md5 with your MD device
        \nmdadm -A \/dev\/md5<\/span> -U devicesize \/dev\/sdc3<\/span><\/strong> <–replace \/dev\/md5 with your MD device and \/dev\/sdc3 with your disk partition<\/li>\n
      7. mdadm –grow \/dev\/md5<\/span> -z max<\/strong> <–extend the size of the MD array<\/li>\n
      8. pvresize \/dev\/md5<\/strong> <–extend the LVM Physical Volume and you’ll see the free space in the Physical Volumeroot@Synology:\/usr\/syno\/etc# vgs<\/strong>
        \nVG #PV #LV #SN Attr VSize VFree
        \nvg1 1 2 0 wz–n- 895.40g 0
        \nvg2 1 2 0 wz–n- 415.40g 0
        \nvg3 1 2 0 wz–n- 2.80t 409.70g<\/strong><\/li>\n
      9. vgchange -a y<\/span> vg3<\/strong> <– Activate the LVM volume group<\/li>\n
      10. lvextend -L +409GB \/dev\/vg3\/volume_3<\/strong> <–extend the VLM Logical Volume to the last full GB<\/li>\n
      11. lvextend -L +712MB \/dev\/vg3\/volume_3<\/strong> <–extend it with the remaining MBs as well(use vgs to see how much exact MBs are outstanding)<\/li>\n
      12. root@Synology:\/usr\/syno\/etc# vgs<\/strong> <–run vgs to validate you’ve used all available free space
        \nVG #PV #LV #SN Attr VSize VFree
        \nvg1 1 2 0 wz–n- 895.40g 0
        \nvg2 1 2 0 wz–n- 415.40g 0
        \nvg3 1 2 0 wz–n- 2.80t 0<\/strong><\/li>\n
      13. mount \/volume3<\/strong> <–mount the volume<\/li>\n<\/ol>\n<\/li>\n
      14. At this stage I expected the Synology GUI to reflect the actual RAID group and volume size, but it wasn’t the case.  After a Reboot<\/strong> (which starts the stopped services as well) the RAID group started showing the correct size after the extension<\/strong>. The Volume was still with the old size, but the GUI was handy (Login in Synology–>Storage Manager –>Volume –>select volume 3 –>expand) and the volume was extended<\/strong>, which ended the procedure.<\/li>\n<\/ol>\n

        And REMEMBER”<\/p>\n

        ALWAYS BACKUP YOUR DATA FIRST!<\/strong><\/p><\/blockquote>\n

        Enjoy!<\/p>\n","protected":false},"excerpt":{"rendered":"

        Recently I run out of free space on one of my XPenology DSM 6 drives and had to run an extend. Since it’s running on ESXi, the VMware disk extend was easy. However surprisingly or not the Synology part wasn’t.… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,9],"tags":[],"class_list":["post-201","post","type-post","status-publish","format-standard","hentry","category-articles","category-it"],"_links":{"self":[{"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/posts\/201"}],"collection":[{"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/comments?post=201"}],"version-history":[{"count":4,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/posts\/201\/revisions"}],"predecessor-version":[{"id":216,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/posts\/201\/revisions\/216"}],"wp:attachment":[{"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/media?parent=201"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/categories?post=201"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gadjev.com\/wp-json\/wp\/v2\/tags?post=201"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}