OMV image on Libre Renegade did not expand FS

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • OMV image on Libre Renegade did not expand FS

      I install an OMV image on a Libre Renegade board using a 64GB MicroSD card but I am unable to get it to expand the file system.
      Here is my outupt of armbianmonitor -u
      ix.io/1m05

      How can I get it to expand?

      more info if needed as follows:


      root@renegade:~# fdisk -l
      Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      Disk /dev/mmcblk1: 59.5 GiB, 63864569856 bytes, 124735488 sectors
      Units: sectors of 1 * 512 = 512 bytes
      Sector size (logical/physical): 512 bytes / 512 bytes
      I/O size (minimum/optimal): 512 bytes / 512 bytes
      Disklabel type: dos
      Disk identifier: 0x811771fc

      Device Boot Start End Sectors Size Id Type
      /dev/mmcblk1p1 32768 163839 131072 64M 83 Linux
      /dev/mmcblk1p2 163840 15500000 15336161 7.3G 83 Linux
      /dev/mmcblk1p3 15500001 123488127 107988127 51.5G 83 Linux


      Disk /dev/zram0: 50 MiB, 52428800 bytes, 12800 sectors
      Units: sectors of 1 * 4096 = 4096 bytes
      Sector size (logical/physical): 4096 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      Disk /dev/zram1: 490.5 MiB, 514355200 bytes, 125575 sectors
      Units: sectors of 1 * 4096 = 4096 bytes
      Sector size (logical/physical): 4096 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      Disk /dev/zram2: 490.5 MiB, 514355200 bytes, 125575 sectors
      Units: sectors of 1 * 4096 = 4096 bytes
      Sector size (logical/physical): 4096 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      Disk /dev/zram3: 490.5 MiB, 514355200 bytes, 125575 sectors
      Units: sectors of 1 * 4096 = 4096 bytes
      Sector size (logical/physical): 4096 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      Disk /dev/zram4: 490.5 MiB, 514355200 bytes, 125575 sectors
      Units: sectors of 1 * 4096 = 4096 bytes
      Sector size (logical/physical): 4096 bytes / 4096 bytes
      I/O size (minimum/optimal): 4096 bytes / 4096 bytes


      root@renegade:~# df -h /dev/mmcblk1
      Filesystem Size Used Avail Use% Mounted on
      udev 2.0G 0 2.0G 0% /dev
    • stevelloyd wrote:

      Device Boot Start End Sectors Size Id Type
      /dev/mmcblk1p1 32768 163839 131072 64M 83 Linux
      /dev/mmcblk1p2 163840 15500000 15336161 7.3G 83 Linux
      /dev/mmcblk1p3 15500001 123488127 107988127 51.5G 83 Linux
      This is how it should look like. The rootfs is expanded to a reasonable size and the rest is available as 3rd partition you can put a filesystem and an OMV share on. In the past we used 4 GB since OMV will not need more space on the rootfs anyway (unless you use plex or other stuff putting databases on the rootfs) and all the automatically assigned space is 'lost'. Using 8GB is just some safety headroom.

      If you don't like this and know what you do you can delete the 3rd partition and then resize the 2nd one manually. Most simple way is to start from scratch, this time deleting /root/.rootfs_resize prior to first boot (the resize rule is defined here).
    • stevelloyd wrote:

      I will be using plex so how do I resize it to fit the entire MicroSD after the first boot? If I remove the /root/.rootfs_resize and reboot, will that work?
      GParted.
      I'm not an expert. I'm just a tourist here.

      - ODROID-HC1 (Samsung Exynos5422, 2GB LPDDR3 RAM, Gigabit Ethernet)
      - Sandisk Ultra 16GB A1 "SDSQUAR-016G-GN6" (btrfs)
      - Samsung SpinPoint M8 1TB (ext4)
      - OMV 4.1.11 / ARMBIAN 5.60 + Kernel 4.14.69
    • Don't place your Plex Metadata Library on a small OMV OS drive. If you run dockers, don't place the containers there either.

      What's going on here:

      Dockers consume 5.5GB

      Plex Metadata consumes 260GB

      OMV OS SSD drive size 16GB
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380

      The post was edited 1 time, last by gderf ().

    • stevelloyd wrote:

      I will be using plex so how do I resize it to fit the entire MicroSD after the first boot? If I remove the /root/.rootfs_resize and reboot, will that work?

      This is an Armbian mechanism so not directly related to OMV or Debian in general. With Armbian it's removing the resize rule as above and then starting the resize service again: forum.armbian.com/topic/3783-o…ab=comments#comment-27487

      We renamed the service in the meantime so maybe it's already this on the Renegade image:

      Source Code

      1. systemctl enable armbian-resize-filesystem && reboot

      Depending on how large your media library is 64 GB might be too small so ensure that you keep an eye on disk utilization.
    • When I run your command I get

      Source Code

      1. root@renegade:~# systemctl enable armbian-resize-filesystem
      2. Created symlink /etc/systemd/system/basic.target.wants/armbian-resize-filesystem.service â /lib/systemd/system/armbian-resize-filesystem.service.
      3. root@renegade:~#

      but when it reboots it looks the same

      Source Code

      1. root@renegade:~# df -h
      2. Filesystem Size Used Avail Use% Mounted on
      3. udev 2.0G 0 2.0G 0% /dev
      4. tmpfs 393M 5.5M 387M 2% /run
      5. /dev/mmcblk1p2 7.4G 1.6G 5.3G 23% /
      6. tmpfs 2.0G 8.0K 2.0G 1% /dev/shm
      7. tmpfs 5.0M 4.0K 5.0M 1% /run/lock
      8. tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
      9. tmpfs 2.0G 4.0K 2.0G 1% /tmp
      10. /dev/mmcblk1p1 58M 41M 15M 74% /boot
      11. /dev/zram0 49M 12M 34M 26% /var/log
      12. tmpfs 393M 0 393M 0% /run/user/0
      Display All
    • stevelloyd wrote:

      when it reboots it looks the same

      I guess you didn't remove the 3rd partition manually before? Again: only real advice is:

      tkaiser wrote:

      If you don't like this and know what you do you can delete the 3rd partition and then resize the 2nd one manually. Most simple way is to start from scratch, this time deleting /root/.rootfs_resize prior to first boot
      If it's only about Plex using the 3rd partition for Plex and pointing to it in the configuration might be the better idea since then a growing Plex database can't completely fill the rootfs partition.
    • Thanks for your patience as I am trying to understand. I tried deleting /root/.rootfs_resize before running that command and it did nothing.

      My objective is to expand the second partition so that I do not need a third one. I will be using a USB drive for the plex movies so I am not worried about filling up the sd card.

      how do I "delete the 3rd partition and then resize the 2nd one manually"?

      Thanks
    • stevelloyd wrote:

      how do I "delete the 3rd partition and then resize the 2nd one manually"?

      OMV is based on plain Debian. So if you're not that familiar with Linux/Debian in general it might be a better idea to follow the advice to start from scratch. Otherwise see the other answers and use some Google-Fu.

      If you don't put the Plex database on your rootfs expanding the partition is completely useless anyway.