I am trying to create a custom live image using the custom-ocs script feature on our clonezilla-servers. I realized that the last time I did this we were running Ubuntu-Intrepid. We now have Servers running Wheezy and Jessie.
When I try creating custom-ocs the vivid version is downloaded and an iso is created called debian-live-for-ocs and one called clonezilla-live-20150617. The debian image gives a stock clonezilla live menu. The other iso boots to black screen with white block mouse cursor.
I assume that I am missing something.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried new script. I modified source and destination to sdb2 and sdb3 for running from usb. It still comes up with black screen and blinking cursor instead of backup and restore menu.
Hi rick
I have used the custom-ocs and modified it for my uses. I do a complete backup of all partitions (using a CD Clonezilla), not individual partitions. As such I use sda as the Operating System disk and sdb for the Repository for my Images. I have recently attempted to use a USB Live Clonezilla and I am making adjustments currently to my scripts.
I believe that the Operating System drive is always sda ( I make sure that the OS containing SATA drive is connected to the lowest number SATA connector on the Motherboard). The Repository (where the Image stuff is kept) is always on sdb when I use a CD Clonezilla. (This might change when I use a USB Thumb Drive for Clonezilla)
So I believe, based on this, that your "source" should be sda1 and not sdb2. You should not use sdb2 as it most probably is your USB Clonezilla Live (if I understand your post). Chances are that your Repository would be either a secondary partition (a backup on the same spindle is not very wise) on sda (such as sda2) or more appropriately a sdc1 which would be your Repository for Images and another drive altogether.
Cloning partitions I found to be to problematic so I always do a Full Disk Backup each time. This has saved me some headaches, I believe.
Note when doing a semi automated backup make sure that only the peripherals (the drives needed to carry out the Backup) you want are connected. Such items as MP3 players, etc could mess up your Drive order, so they should be removed before backing up any unit.
Last edit: Robert Weir 2015-06-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Rick
I believe that since you are using an USB stick to boot clonezilla from, that you need to use sdc as your target disk. I have not actually done this as yet but that is what I expect to have to do. I believe that the USB Bootable Clonezilla uses sdb as its Disk Identifier.
If the bootable Clonezilla was on a CD sdb would be fine. I believe however that you are booting from a USB stick which is seen as another block device. The USB stick reads from the syslinux directory and not from the isolinux directory, so you must put your code in that directory when you are recreating your iso image (syslinux.cfg instead of isolinux.cfg). I use ISO Master to make changes to my iso files.
Give that a try and post back.
Last edit: Robert Weir 2015-07-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to create a custom live image using the custom-ocs script feature on our clonezilla-servers. I realized that the last time I did this we were running Ubuntu-Intrepid. We now have Servers running Wheezy and Jessie.
When I try creating custom-ocs the vivid version is downloaded and an iso is created called debian-live-for-ocs and one called clonezilla-live-20150617. The debian image gives a stock clonezilla live menu. The other iso boots to black screen with white block mouse cursor.
I assume that I am missing something.
Please describe how you customized that in detail. It would be easier for us to understand where went wrong.
Steven.
I think part of my problem is I was using your old script. I found newer ones on Github and will try starting again with those for base.
I tried new script. I modified source and destination to sdb2 and sdb3 for running from usb. It still comes up with black screen and blinking cursor instead of backup and restore menu.
Hi rick
I have used the custom-ocs and modified it for my uses. I do a complete backup of all partitions (using a CD Clonezilla), not individual partitions. As such I use sda as the Operating System disk and sdb for the Repository for my Images. I have recently attempted to use a USB Live Clonezilla and I am making adjustments currently to my scripts.
I believe that the Operating System drive is always sda ( I make sure that the OS containing SATA drive is connected to the lowest number SATA connector on the Motherboard). The Repository (where the Image stuff is kept) is always on sdb when I use a CD Clonezilla. (This might change when I use a USB Thumb Drive for Clonezilla)
So I believe, based on this, that your "source" should be sda1 and not sdb2. You should not use sdb2 as it most probably is your USB Clonezilla Live (if I understand your post). Chances are that your Repository would be either a secondary partition (a backup on the same spindle is not very wise) on sda (such as sda2) or more appropriately a sdc1 which would be your Repository for Images and another drive altogether.
Cloning partitions I found to be to problematic so I always do a Full Disk Backup each time. This has saved me some headaches, I believe.
Note when doing a semi automated backup make sure that only the peripherals (the drives needed to carry out the Backup) you want are connected. Such items as MP3 players, etc could mess up your Drive order, so they should be removed before backing up any unit.
Last edit: Robert Weir 2015-06-25
I keep trying but I either get bog standard clonezilla (using sda) or black screen (sdb). Not getting custom menu at all.
Hi Rick
I believe that since you are using an USB stick to boot clonezilla from, that you need to use sdc as your target disk. I have not actually done this as yet but that is what I expect to have to do. I believe that the USB Bootable Clonezilla uses sdb as its Disk Identifier.
If the bootable Clonezilla was on a CD sdb would be fine. I believe however that you are booting from a USB stick which is seen as another block device. The USB stick reads from the syslinux directory and not from the isolinux directory, so you must put your code in that directory when you are recreating your iso image (syslinux.cfg instead of isolinux.cfg). I use ISO Master to make changes to my iso files.
Give that a try and post back.
Last edit: Robert Weir 2015-07-01