RPI4 OMV - can it be this easy to boot from SSD?

    • Official Post

    I will attempt to do a clean install of OMV on the SSD

    If you are going to do a new installation you have another safer option. Do the Debian 11 installation and during the installation you can create the partitions you need. Then install OMV with the script. You avoid all the gparted hassle.

    Even if you want to restore an OMV backup to the installed debian partition you can do that too and it will still work, I have done it before with fsarchiver and it works.

  • Thanks guys. Appreciate all the help.


    Soma are you suggesting to resize the rootfs partition to use the unallocated space?


    I actually wanted to create a new partition to keep my docker data separate from rootfs.


    Either option is fine I guess.


    I’m just determined to work out why I can’t add a new partition (yet)

    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

  • I actually wanted to create a new partition to keep my docker data separate from rootfs.

    TLDR, only read that you wanted to increase the size of the partition.


    If you want to make a new partition on the rest of the space:

    fdisk /dev/sdX where X is the letter that is assigned to the SSD.

    p will "print" the details of the partiton table and what is done

    Take note of the END SECTOR of partition 2

    n will make a new partition and it should show the END SECTOR+1 of partition 2.


    See this example (your will show different)(imagine that it was your 32Gb SD card and now this is the SSD)

    When using n, the first sector for the new partition had to be 61071359+1 = 61071360

    Then just use accept the numbers that show automatic.



    If you're 100% sure you made the correct procedure:

    w will write the partition table with the rest of the drive on a new partition.

    q to exit the fdisk


    Run sync on the CLI and you should see a new partition that you can create a FS on OMV GUI.

    Or you can also do it on the CLI.


    I can guide you, if you want.


    Just post the output of:

    sudo fdisk -l /dev/sdX replace X with your drive letter

  • OK so I created the new partition (90gb) and looks fine using fdisk


    Code
    Device     Boot    Start       End   Sectors  Size Id Type
    /dev/sda1           8192    532479    524288  256M  c W95 FAT32 (LBA)
    /dev/sda2         532480  62333951  61801472 29.5G 83 Linux
    /dev/sda3       62333952 250880802 188546851 89.9G 83 Linux

    but it was not visible to format in the OMV GUI. Not sure why this is the case. I did sync and restarted the pi but no luck


    So I used mkfs to format it at the cli


    Code
    mkfs.ext4 /dev/sda3

    After this it is available to mount in OMV but this is what I see in OMV after mounting it. After a reboot, it shows as unmounted and nothing is written to /etc/fstab


    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

  • I think I have found a clue. When I make changes in OMV I do not get the yellow apply changes dialog at all on this system. This is probably why the disk is not being mounted.


    Done some testing and no matter what I do, the apply changes dialog does not appear. Might be something strange is going on as the starting point for this installation is a clone of my sd card...

  • cleared browser cache and refreshed page and it's working! Now the yellow dialog appears and saves the config correctly.


    Not sure what was going on here but looks ok now

    OMV 7 (latest) on N100 Minipc (16GB) and RPI5 (8GB). OS on SD card. System ext4 on SSD. Data BTRFS on HDDs

Participate now!

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