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
    http://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

  • 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).

  • 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

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

    Edited once, last by gderf ().

  • 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: https://forum.armbian.com/topi…ab=comments#comment-27487


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


    Code
    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

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


    but when it reboots it looks the same

  • when it reboots it looks the same


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

    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

  • 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.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!