openmediavault-backup install clonezilla fails

    • OMV 1.0
    • 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

      Source Code

      1. df -h
      2. Filesystem Size Used Avail Use% Mounted on
      3. rootfs 113G 12G 96G 11% /
      4. udev 10M 0 10M 0% /dev
      5. tmpfs 3.2G 3.1M 3.2G 1% /run
      6. /dev/mapper/omv-root 113G 12G 96G 11% /
      7. tmpfs 5.0M 0 5.0M 0% /run/lock
      8. tmpfs 6.3G 148K 6.3G 1% /run/shm
      9. /dev/sdc1 228M 228M 0 100% /boot
      10. /dev/sda1 15T 3.8T 11T 26% /media/c615b345-5b9c-498d-84b8-610b1fce3cfe
      11. /dev/sda2 3.6T 933G 2.5T 27% /media/6920b979-8dd4-4500-85eb-8d06766e1af6
      12. /dev/sdb1 5.5T 3.3T 2.0T 63% /mnt/amanda/vtape
      13. tmpfs 16G 112K 16G 1% /tmp
      14. /dev/sdd1 117G 188M 111G 1% /mnt/backupsys
      Display All
    • 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 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      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

      Source Code

      1. fdisk -l
      2. WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
      3. Disk /dev/sdb: 6000.6 GB, 6000606183424 bytes
      4. 255 heads, 63 sectors/track, 729532 cylinders, total 11719933952 sectors
      5. Units = sectors of 1 * 512 = 512 bytes
      6. Sector size (logical/physical): 512 bytes / 4096 bytes
      7. I/O size (minimum/optimal): 4096 bytes / 4096 bytes
      8. Disk identifier: 0x00000000
      9. Device Boot Start End Blocks Id System
      10. /dev/sdb1 1 4294967295 2147483647+ ee GPT
      11. Partition 1 does not start on physical sector boundary.
      12. WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
      13. Disk /dev/sda: 24000.3 GB, 24000277250048 bytes
      14. 255 heads, 63 sectors/track, 2917867 cylinders, total 46875541504 sectors
      15. Units = sectors of 1 * 512 = 512 bytes
      16. Sector size (logical/physical): 512 bytes / 512 bytes
      17. I/O size (minimum/optimal): 512 bytes / 512 bytes
      18. Disk identifier: 0x00000000
      19. Device Boot Start End Blocks Id System
      20. /dev/sda1 1 4294967295 2147483647+ ee GPT
      21. Disk /dev/sdc: 128.0 GB, 128035676160 bytes
      22. 255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
      23. Units = sectors of 1 * 512 = 512 bytes
      24. Sector size (logical/physical): 512 bytes / 512 bytes
      25. I/O size (minimum/optimal): 512 bytes / 512 bytes
      26. Disk identifier: 0x000557b1
      27. Device Boot Start End Blocks Id System
      28. /dev/sdc1 * 2048 499711 248832 83 Linux
      29. /dev/sdc2 501758 250068991 124783617 5 Extended
      30. /dev/sdc5 501760 250068991 124783616 8e Linux LVM
      31. Disk /dev/mapper/omv-root: 122.6 GB, 122553368576 bytes
      32. 255 heads, 63 sectors/track, 14899 cylinders, total 239362048 sectors
      33. Units = sectors of 1 * 512 = 512 bytes
      34. Sector size (logical/physical): 512 bytes / 512 bytes
      35. I/O size (minimum/optimal): 512 bytes / 512 bytes
      36. Disk identifier: 0x00000000
      37. Disk /dev/mapper/omv-root doesn't contain a valid partition table
      38. Disk /dev/mapper/omv-swap_1: 5221 MB, 5221908480 bytes
      39. 255 heads, 63 sectors/track, 634 cylinders, total 10199040 sectors
      40. Units = sectors of 1 * 512 = 512 bytes
      41. Sector size (logical/physical): 512 bytes / 512 bytes
      42. I/O size (minimum/optimal): 512 bytes / 512 bytes
      43. Disk identifier: 0x00000000
      44. Disk /dev/mapper/omv-swap_1 doesn't contain a valid partition table
      45. WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
      46. Disk /dev/sdd: 127.5 GB, 127473287168 bytes
      47. 255 heads, 63 sectors/track, 15497 cylinders, total 248971264 sectors
      48. Units = sectors of 1 * 512 = 512 bytes
      49. Sector size (logical/physical): 512 bytes / 512 bytes
      50. I/O size (minimum/optimal): 512 bytes / 512 bytes
      51. Disk identifier: 0x00000000
      52. Device Boot Start End Blocks Id System
      53. /dev/sdd1 1 248971263 124485631+ ee GPT
      54. root@omv:~# parted -l
      55. Model: LSI MR9271-8i (scsi)
      56. Disk /dev/sda: 24.0TB
      57. Sector size (logical/physical): 512B/512B
      58. Partition Table: gpt
      59. Number Start End Size File system Name Flags
      60. 1 1049kB 17.6TB 17.6TB ext4 primary
      61. 2 17.6TB 21.6TB 4008GB ext4 timelair
      62. Model: LSI MR9271-8i (scsi)
      63. Disk /dev/sdb: 6001GB
      64. Sector size (logical/physical): 512B/4096B
      65. Partition Table: gpt
      66. Number Start End Size File system Name Flags
      67. 1 1049kB 6001GB 6001GB ext4 primary
      68. Model: ATA SAMSUNG SSD 830 (scsi)
      69. Disk /dev/sdc: 128GB
      70. Sector size (logical/physical): 512B/512B
      71. Partition Table: msdos
      72. Number Start End Size Type File system Flags
      73. 1 1049kB 256MB 255MB primary ext2 boot
      74. 2 257MB 128GB 128GB extended
      75. 5 257MB 128GB 128GB logical lvm
      76. Model: LSI MR9271-8i (scsi)
      77. Disk /dev/sdd: 127GB
      78. Sector size (logical/physical): 512B/512B
      79. Partition Table: gpt
      80. Number Start End Size File system Name Flags
      81. 1 1049kB 127GB 127GB ext4 primary
      82. Model: Linux device-mapper (linear) (dm)
      83. Disk /dev/mapper/omv-swap_1: 5222MB
      84. Sector size (logical/physical): 512B/512B
      85. Partition Table: loop
      86. Number Start End Size File system Flags
      87. 1 0.00B 5222MB 5222MB linux-swap(v1)
      88. Model: Linux device-mapper (linear) (dm)
      89. Disk /dev/mapper/omv-root: 123GB
      90. Sector size (logical/physical): 512B/512B
      91. Partition Table: loop
      92. Number Start End Size File system Flags
      93. 1 0.00B 123GB 123GB ext4
      Display All
    • 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.

      Source Code

      1. Booting 'Clonezilla Live'
      2. error: file not found.
      3. error: no such disk.
      4. error: you need to load the kernel first.
      5. Press any key to continue...
      6. Failed to boot both default and fallback entries..
      7. 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

      1. Found linux image: /boot/vmlinuz-3.2.0-4-amd64
      2. Found initrd image: /boot/initrd.img-3.2.0-4-amd64
      3. done
      4. 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.
    • 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 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      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.
    • 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 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!