Issues running an automatic and unattended clonezilla restore drive

By -

When I try to run an automated and unattended restore via Clonezilla it returns the following error:

Now run "ocs_prerun": mount /dev/sdb2 /mnt...
Mount: /mnt: special device /dev/sdb2 does not exist.
Failed to run: mount /dev/sdb2 /mnt
Press "Enter" to continue......

Then, after hitting Enter it shows the following error:

The directory for this inputted image name does NOT exist: /home/partimag/Amentum_04_21_2022
Program Terminated!!!!
"ocs-sr -kl -e1 auto -e2 -batch -r -j2 -scr -p reboot restoredisk Amentum_04_21_2022 sda" finished with error!

Here is the first entry of my grub.cfg file:

# Since no network setting in the squashfs image, therefore if ip=, the network is disabled.

menuentry "Flysoft RESTORE" {
  search --set -f /live/vmlinuz
  $linux_cmd /live/vmlinuz boot=live union=overlay username=user config components quiet noswap edd=on nomodeset enforcing=0 noprompt ocs_prerun="mount /dev/sdb2 /mnt" ocs_prerun1="mount --bind /mnt/images /home/partimag/" ocs_live_run="ocs-sr -g auto -e1 auto -e2 -r -j2 -k -scr -batch -p reboot restoredisk Amentum_04_21_2022 sda" keyboard-layouts="de" ocs_live_batch="yes" locales=de_DE.UTF-8 vga=788 ip= nosplash net.ifnames=0 splash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1
  $initrd_cmd /live/initrd.img
}

Here is my syslinux.cfg entry for prerun:

label Amentum_04_21_2022
  MENU DEFAULT
  # MENU HIDE
  MENU LABEL Amentum_04_21_2022
  # MENU PASSWD
  kernel /live/vmlinuz
  append initrd=/live/initrd.img boot=live union=overlay username=user config components quiet noswap edd=on nomodeset noeject locales=en_US.UTF-8 keyboard-layouts=NONE ocs_prerun="mount /dev/sdb2 /mnt" ocs_prerun1="mount --bind /mnt /home/partimag" ocs_live_run="ocs-sr -k1 -e1 auto -e2 -batch -r -j2 -scr -p reboot restoredisk Amentum_04_21_2022 sda" ocs_live_extra_param="" ocs_live_batch="no" vga=791 ip= net.ifnames=0  splash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.enable_fbdev=1
  TEXT HELP
  VGA mode 1024x768. OK for most of VGA cards.
  ENDTEXT

I'm not sure why this is happening because I've prepared these drives this way every other time and I feel like I'm missing something.

This is how they show up when viewing them in the file explorer in Windows. It's just two partitions on the same drive:

enter image description here

CZ(D:) would be sdb1 and images(E:) would be sdb2, right? This is what I've put in both the grub.cfg and the syslinux.cfg file and it's telling me sdb2 does not exist. Anyone have any ideas?

Thanks in advance!



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more