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

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.

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.

Source Code

Booting 'Clonezilla Live'

error: file not found.

error: no such disk.

error: you need to load the kernel first.

Press any key to continue...

Failed to boot both default and fallback entries..

Press any key to continue...

Display All

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,

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

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.

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.