Posts by Stramm

    What if the user doesn't have a non-btrfs filesystem? Putting the iso in /boot is the best place because initrd is there and the system won't be accessible if /boot isn't working. People who want btrfs for a root filesystem will just have to put /boot on ext4 or something other than btrfs.

    Yep, that sounds somehow quite logical. I'll try to create a boot partition, add it to fstab and see what happens. Hope I do not mess things up :)

    The plugin doesn't touch initrd. It creates a grub entry in /etc/grub.d/ and runs update-grub. If your system is booting from btrfs for root, then the btrfs module is in the initrd. If someone wants to look into booting an iso from grub on btrfs and point me at the info, I will see what I can do. But I'm really busy trying to get the plugins ported to OMV 6.x and don't have time to dig into this.

    After some googling this sounds like a problem with no perfect solution. A workouround could be the possiblility to chose the download location of the iso (that should be used in grub.d, too). If that path is on a non btrfs, xfs partition booting should work.

    But I won't ask you to implement that. You already have lots to do with porting all the plugins to omv 6. And thanks again for looking into this.

    This is your problem. The way the plugin sets up grub for the ISO is probably completely wrong for btrfs. I don't even know if grub can boot an iso from btrfs. The plugin can only support so many things.

    Thanks for the info. And very understandable that not everything can be supported. Still a pity for me ;)

    Then I'll try with btrfs snapshots to remote hds.... Clonezilla is just so convenient.

    After the friendly hints where to find Clonezilla I tried to boot into it but got some problems. The bootloader is telling me, that it is not able to find the iso.

    error: file '/boot/clonzilla-live-2.6.0-37-amd64.iso' not found


    I have installed the kernel plugin, then inside the plugin downloaded the clonezilla image, chosen to boot once into the image and finally rebooted.


    A look into grub config:

    Code
    ### BEGIN /etc/grub.d/42_clonezilla ###
    menuentry 'Clonezilla Live' {
    set isofile="/boot/clonezilla-live-2.6.0-37-amd64.iso"
    loopback loop $isofile
    linux (loop)/live/vmlinuz boot=live live-config noswap edd=on nomodeset ocs_prerun="dhclient" ocs_live_run="ocs-live-general" ocs_live_extra_param="" keyboard-layouts=NONE ocs_live_batch="no" locales="en_US.UTF-8" ocs_daemonon="ssh" vga=788 nosplash toram=filesystem.squashfs findiso=$isofile
    initrd (loop)/live/initrd.img
    }
    ### END /etc/grub.d/42_clonezilla ###


    /boot


    The disks are btrfs. I first installed debian and on top OMV.

    filesystem:

    Any ideas what might go wrong here?

    Yep. This was separated into a second plugin because I couldn't figure out how to dynamically hide this tab on OMV 6.x for arm board which are not supported. So, this plugin is only available to i386 and amd64 systems. I know it doesn't make much sense but it was the best option I could find.

    Haven't installed the kernel plugin as the description just mentions the 'Proxmo' kernel. Maybe you want to correct the spelling and add the other helpful features to the description, too?

    My problem was that docker started before all my disks were mounted. So a lot of my containers didn't work properly. So I added (OMV 6) an override file /etc/systemd/system/docker.service.d/override.conf and added my disks there with the commands




    [Unit]

    Requires=srv-dev\x2ddisk\x2dby\x2duuid\x2d025fdf48\x2dd69c\x2d480d\x2db9b0\x2dd407189a9a2b.mount

    After=srv-dev\x2ddisk\x2dby\x2duuid\x2d025fdf48\x2dd69c\x2d480d\x2db9b0\x2dd407189a9a2b.mount



    to find the mounts you can use:

    systemctl list-unit-files | grep ".mount"


    btw. in OMV4 the config file was

    /etc/systemd/system/docker.service.d/openmediavault.conf