OCS Live stopped outputting file last week

[Roger H]

Hi All,

I've been running a custom config for a couple years now, which writes out the image "automagically" from the start menu.

Last week I started getting this error:
"The input device [tpl-w10-2004.mshome.net-2021-03-18-1601-img] does NOT exist in this machine!"
"We will not save this device [tpl-w10-2004.mshome.net-2021-03-18-1601-img] !"

The command being issued and the error:
"ocs-sr -q2 -j2 -z9p -i 4096 -sfsck -senc -p choose savedisk autohostname sda" finished with error!

I tried running that command by hand at the command prompt, no luck, same error, the time keeps changing on the filename, but that's about it.

As additional troubleshooting, doing "sudo clonezilla"
device-image
use existing mount (skip)
savedisk
accept default name
select sda (the only drive that appears)
select all the same options

and it ran just fine.

The only thing I can see that's any different is that previously the machine was showing up as localhost.localdomain.mshome.net, but now we're seeing this tpl-w10-2004 instead...

The source machine is a Hyper-V VM

Are there any other macros that would be available in the machine name? could I put something in like baseimage_%DATE%%TIME% ?

[Roger H]

Well.. not sure what exactly happened in there, but after I rebuilt the source image with the new Ubuntu based image, my autoclone is behaving nicely again.

[Roger H]

The autoclone is back to writing localhost.localdomain.mshome.net too.. weird

[Steven Shiau]

So there is no any issue? Or?

Steven

[Roger H]

Might have just been timing... my suspicion, and I need to poke around some more to confirm, is that the name is pulling from the dns cache somehow.

What mechanism do you use for autohostname??

[Roger H]

Switching over to the new autoname-wpfx= seems to work just fine, so.. there's a viable workaround :)

[Steven Shiau]

Thanks for sharing that.

Steven