Prerun mounting error -- Help please!

[Daniel newman]

I have an external hard drive that I set up Clonezilla Live with a 5GB Clonezilla OS partition and a 1TB partition for Images . i'm trying to have CZ automatically prerun and image the machine it's pluggend into and I'm getting the following error when I attempt to do so:

Failed to run: mount /dev/sdb

and then..

the directory for this inputted image name does NOT exist: /home/partimag/Amentum_04_21_2022

Maybe I just don't fully understand how Clonezilla fully operates, but I successfully captured and image to the Images partition (the 1TB one) and there is now a directory with the name Amentum_04_21_2022 on that partition. However, the CZ OS partition has a home/partimag directory in it, but there's nothing in there. Is there supposed to be? I don't recall ever having anything in there when I set this up before.

Here's the syslinux.crg text for prerun and the menu item:

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/sdb /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

Am i missing something here? I have attached a photo of the error screen i'm getting as well as a screenshot of what I see in Windows when in plug that external HD in. sda is my first disk labelled CZ and sdb is the second named Images with the image directory on it. Did i not capture this right?

Thanks very much in advance for the help I really appriciate it!

[Daniel newman]

Okay, so I think I partially figured it out, but now I am getting a different error.

If you look at my photo in my previous post of my external hard drive in the file explorer in Windows, it's clear that the directory that has the image I'm trying to restore exists on sda2, not sdb. Honest mistake.

Changing this in the syslinux.cfg file allows for prerun to initiate and sda2 to be mounted, however, I am now getting an error that says:

/dev/sda is busy. Some partition is mounted

Please see the screenshot for more context. How to do I restore the image directory on sda2 to the target computer I'm plugged into? I feel like I'm missing something important here.

Any help would be greatly appriciated. Thank you!

EDIT: I'm not sure why the image is updside down. It isn't that way on my end. Sorry about that.

[Daniel newman]

Bumping this thread because I still need help I have to give these drives to a client at my job and Clonezilla is not working still.

I also think I relized that my above post was wrong, the drive i'm looking for is in fact, sdb2, but it's still throwing the following errer:

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

sdb2 is the image repository that I saved the image to. Isn't this the one I want to mount? What am I missing here?

Thanks in advance,

[Daniel newman]

I fixed the problem.

If any one is curious as to how I did this, I will post what the fix was, but I feel like i'm shouting into the void here haha!

My issue was not with capturing a Clonezilla image, it was with restoring it and restoring it as an automated and unatteded session. The error I was getting was saying that sdb2 could not be mounted because it doesn't exist, and this ended up being correct, which was very confusing to me at the time.

We switched computer models for this client that i'm working with and I paid closer attention to the drive names when the image was capturing to CZ. They are NVME drives, and linux was labeling it nvme0n1, not sda. The previous computer model we used for this client had SATA drives so linux was reading it as sda and the USB hard drive plugged in as sdb1 (Clonezilla) and sdb2 (Images). So in this new model configuration, linux was seeing the internal hard drive as nvme01n and the eternal USB hard drive as sda since it's the first SATA drive the list, so changeing the command tomount /dev/sda2 /mnt andocs_live_run="ocs-sr -k1 -e1 auto -e2 -batch -r -j2 -scr -p reboot restoredisk Amentum_04_21_2022 nvme0n1 fixed the issue and it's running flawlessly now.

[Steven Shiau]

Great. It's nice to know you have fixed it, and share that with us. Thanks.

Steven