openmediavault-backup install clonezilla fails

  • Hello,
    I installed openmediavault-backup 1.0.6 for the first time, which went fine, then clicked install on the clonezilla tab which failed at ~80% ( lost the log sorry ) with a message that it ran out of boot space. It made a /boot partition on my system disk, but apparently too small. I have lots of room, perhaps configured oddly as this is omv on top of a debian install. Any hints on how/where to give it the space it wants?
    I want to backup to /dev/sdd which is a twin of my system drive but in a hotswap raid slot. /dev/sdb1 is for backing up data if it matters


    • Offizieller Beitrag

    The plugin does not create the /boot directory or partition. All it does is download the clonezilla ISO to the /boot directory. You seem to have a non-standard install. What is the output of: fdisk -l

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • thanks, i'd *just* finally realized it didn't create the /boot. It is a non-standard install, lenny originally which picked my partition sizes though knowing myself I probably tweaked them. then upgraded to wheezy then upgraded omv from 0.5x to 1.x.


    I added parted -l after the fdisk -l


  • I think i'm good to go with this plan


    remove broken clonezilla download in /boot, purge old kernels with dpgk and I should have enough space.


    re-try omv-backup install, backup, test restore, reboot from usb iso and resize /boot to be a bit bigger.


    ls -ls /boot/
    total 228875
    135874 -rw-r--r-- 1 root root 138588888 Nov 15 20:18 clonezilla-live-2.2.4-12-i686-pae.iso
    105 -rw-r--r-- 1 root root 106193 May 13 2014 config-2.6.32-5-amd64
    128 -rw-r--r-- 1 root root 129206 Jun 6 09:51 config-3.2.0-0.bpo.4-amd64
    128 -rw-r--r-- 1 root root 129281 Oct 30 05:44 config-3.2.0-4-amd64
    5 drwxr-xr-x 3 root root 5120 Nov 1 20:42 grub
    10575 -rw-r--r-- 1 root root 10784185 Nov 11 18:19 initrd.img-2.6.32-5-amd64
    10079 -rw-r--r-- 1 root root 10278495 Oct 26 18:49 initrd.img-2.6.32-5-amd64.old-dkms
    3069 -rw-r--r-- 1 root root 3128727 Nov 11 18:19 initrd.img-2.6.32-5-openvz-amd64
    3069 -rw-r--r-- 1 root root 3128648 Nov 11 18:19 initrd.img-2.6.32-5-vserver-amd64
    3069 -rw-r--r-- 1 root root 3128721 Nov 11 18:19 initrd.img-2.6.32-5-xen-amd64
    11527 -rw-r--r-- 1 root root 11756000 Nov 11 18:19 initrd.img-3.2.0-0.bpo.4-amd64
    10873 -rw-r--r-- 1 root root 11088603 Oct 26 18:49 initrd.img-3.2.0-0.bpo.4-amd64.old-dkms
    3069 -rw-r--r-- 1 root root 3128743 Nov 11 18:19 initrd.img-3.2.0-0.bpo.4-rt-amd64
    12047 -rw-r--r-- 1 root root 12286093 Nov 11 18:19 initrd.img-3.2.0-4-amd64
    11557 -rw-r--r-- 1 root root 11786465 Oct 26 18:54 initrd.img-3.2.0-4-amd64.old-dkms
    12 drwxr-xr-x 2 root root 12288 Jan 9 2014 lost+found
    1637 -rw-r--r-- 1 root root 1668057 May 13 2014 System.map-2.6.32-5-amd64
    1991 -rw-r--r-- 1 root root 2029390 Jun 6 09:51 System.map-3.2.0-0.bpo.4-amd64
    2075 -rw-r--r-- 1 root root 2113839 Oct 30 05:44 System.map-3.2.0-4-amd64
    2381 -rw-r--r-- 1 root root 2426656 May 13 2014 vmlinuz-2.6.32-5-amd64
    2817 -rw-r--r-- 1 root root 2871344 Jun 6 09:45 vmlinuz-3.2.0-0.bpo.4-amd64
    2788 -rw-r--r-- 1 root root 2842464 Oct 30 05:42 vmlinuz-3.2.0-4-amd64

  • 2 problems solved, 2 new problems. balance is preserved at least.


    new problem 1) might be of interest to you. pressed the boot once from clonezilla then the reboot button. but headless server failed to come back up. attaching screen & keyboard and retrying i caught it saying this before pausing at the grub select menu.


    so, put clonezilla on a usb key and tried manually, noticed that my boot /dev/sdcX disk become /dev/sdd and my target backup on the raid adapter (/dev/sdd ) becomes /dev/sdc. perhaps the trouble? target ssd is on hotswap port of megaraid as 'raid0'( standard weird way to have one disk on megaraid)
    the log from 'boot once from clonezilla' seemed happy,

    Code
    Found linux image: /boot/vmlinuz-3.2.0-4-amd64
    Found initrd image: /boot/initrd.img-3.2.0-4-amd64
    done
    Done...


    new problem 2) my second ssd is seen as 1gb smaller than the first, no idea why. they're identical, except the target was used for a bit as a cachecade disk and resides on a hotswap port of the raid card as 'raid 0' so clonezilla won't clone to it in disk to disk mode.


    q: will imaging option work with the omv restore plugins?



    solved problems 1. hadn't appreciated the note on the plugin page saying clonezilla iso was 130 mb, i now understand that's something to pay attention to. maybe a df check before download?


    solved problems 2. dpkg --purge to remove old kernels freed up some space. mostly it was the /boot/*old-dkms files though. these were from dkms install of 10gbe solarflare drivers and upgrade drivers, appears one has to clear them by hand 'rm /boot/*.old-dkms' after that had 40mb at least left over after the clonezilla iso download.

    • Offizieller Beitrag

    I don't do a df check because most people don't have separate boot partition and space shouldn't be an issue. I will see about adding it.


    If your other ssd is smaller, use the advanced option in clonezilla and check the -icds option. With only 1 gb difference, it shouldn't have a problem.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I have a dumb question that googling isn't helping with, is the idea to clone then remove the target drive from the system?


    Asking because after cloning ( had managed to clone mbr, I think it was ), both drives have the same uuid and I was trying to figure out if not finding images on reboot problem was uuid related. maybe grub with labels will work for me.

    • Offizieller Beitrag

    That is not a dumb question :) Yes, I typically would remove the drive. It would be difficult to know which drive you are truly using if they have the same uuid.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!