What's the easiest way to resize the system drive?

    • OMV 2.x
    • What's the easiest way to resize the system drive?

      I was originally running my OMV off of a 2GB USB drive. I recently picked up two new 4GB USB drives and used dd to clone my 2GB drive onto one of them. However, the cloned drive is still only using a 2GB partition. Strangely, the resize button in the OMV web interface is grayed out for that partition. What's the easiest way to resize the system drive to the full 4GB size?
    • Boot gparted-live on that system. You can install it to grub with no need for a usb stick with the openmediavault-backup plugin. Use systemrescuecd if they box is headless.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • That actually may be a better method since your 2 gb usb stick might not have enough room for the gparted ISO file.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I ended up doing this entirely with GParted on another system (my OMV is headless). Put GParted on a USB drive, and booted my other system. I used dd to make a backup on my OMV system USB drive, and then first resized the logical partition containing the swap partition to take up all free space at the end of the drive, and then moved the swap partition to the end of the logical partition, before resizing the logical partition back down be just big enough to hold the swap. Then I resized my system partition to take all the free space.

      Seems to have gone off without a hitch, boots and runs fine.
    • tinh_x7 wrote:

      Ok, this is my first time using gpart.
      When you said move the swap partition to the end of the drive, you mean move to the the right end or the bottom end of the logical partition?

      technikaffe.de/anleitung-322-o…rung_der_systemfestplatte
      Well, in my case, I had a lot of unallocated space at the end of the drive, and my objective was to expand the system partition to take up all of that space. My swap partition was contained in a logical partition and was between my system partition and the unallocated space, I believe this is standard.

      So, in order to get my system partition to fill up the unallocated space, I needed to first push the swap partition and the logical partition containing it to the end of the drive (the right), so that the unallocated space would be next to the system partition.
    • I would like to suggest to build a process to allow re-sizing of system drive within OMV - may be in version 3.0. I was using an SSD as a boot drive and OMV takes over the entire space after install. I was told to use gparted to re-size the system drive and free up space for data use. It works essentially but just extra steps one has to mindful. A friend of mine runs Unraid which runs fully off an USB drive and there are no data written to disk once system has booted. So, there are no concerns for frequent failures for USB drive as the case with OMV. But I really like OMV so far and going to keep it.
    • I need some help here guys.

      I gparted wrong size.

      Here's the scenario:

      1. Old hard drive is 1TB.
      2. New SSD is 120GB
      3. I gparted the old hdd logical partition to 118GB, and left the swap partition untouched, and the unallocated space is also not formatted.
      4. Next, I then used Clonezilla to clone the image from device to image.
      5. When I tried to restore from the image, it's tried to restore 1TB, instead 118GB. Therefore, it couldn't be restore.
      6. I then used GPart, and went back to clone the disk parts (individual partitions), when I tried to restore, it said no partition is found. In reality, the partitions are in my backup folder.
      7. I came back and tried a few method, and now, my OMV partition is 140GB used instead a few gig space used.

      Any advice?
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10
    • If you resized the OS partition to 118GB, the swap would have still been at the end of the disk. I would resize the OS partition to much smaller (unless you need it) and then move the swap to come right after the OS partition. When you use clonezilla, make sure to use ICDS in advanced options.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • The problem is that the size in GPart unit count is different compare to Clonezilla.
      It's display as 118GB in GPart, but in Clonezilla, it's 127GB.
      Not only that, but when I clone, it's clone the un-allocated space too, which is about 700GB.
      I tried clone from device to image, it's clone the entire hdd, 1TB, but if I clone just the parttiions & try to restore it, then it's said there is no partition in my backup folder.
      Maybe I get some screenshots tonight, for better explanation.
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10
    • You are probably running into the difference between GiB and GB. I would make the OS partition smaller. You can always increase it after the clone.

      It clones the un-allocated space because it is in the middle. Screenshots would most likely help as well :)
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • You're correct, I wish I know this GiB and GB before I use GPart.
      I'll get some screenshots tonight.

      How do I move the un-allocated partition out of the way?

      Edit: see the attachment.
      OMV OS displaying 117GB is used it's incorrect b/c I use GParted to be 128GiB, but it's ended up as 130GB.

      Thanks in advance.
      Images
      • GParted_hdd_alt.png

        909.61 kB, 957×465, viewed 429 times
      • hdd_old.png

        20.73 kB, 903×146, viewed 402 times
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10

      The post was edited 4 times, last by tinh_x7 ().

    • I've tried with option -icds in Clonezilla with device-to-device image, and part-to-local part, but it didn't work.
      I don't want to re-install this; it's too much work.

      update: I got this error when I used -icds with -k1 argument
      Images
      • boot error.png

        660.98 kB, 982×477, viewed 431 times
      OMV v4.0
      Asus Z97-A/3.1; i3-4370
      32GB RAM Corsair Vengeance Pro
      4x3TB RAID10

      The post was edited 3 times, last by tinh_x7 ().