Unable to see sda in non interactive

[Clay]

When I set the Client with this command Its fails with unable to find sda.

drbl-ocs -g auto -e1 auto -e2 -r -x -j2 -sc0 -p reboot --clients-to-wait 1 --max-time-to-wait 300 -h ” 192.168.100.22" -l en_US.UTF-8 startdisk multicast_restore 2020-10-02-17-imgG40 sda

I have attached a picture of the error. I checked the status of the service and its showing as failed. Not sure that is helpful or not.

root@clone-192-168-100-22:/etc/systemd/system# systemctl status ocsd-run.service
● ocsd-run.service - OCS-run service via Clonezilla
Loaded: loaded (/etc/systemd/system/ocsd-run.service; static; vendor preset: enabled)
Active: inactive (dead) since Sat 2020-10-03 15:45:54 PDT; 19min ago
Process: 4318 ExecStart=/etc/init.d/ocs-run start (code=exited, status=0/SUCCESS)
Process: 4314 ExecStartPre=/bin/plymouth quit (code=exited, status=1/FAILURE)
Main PID: 4318 (code=exited, status=0/SUCCESS)
Oct 03 15:41:16 clone-192-168-100-22 systemd[1]: Starting OCS-run service via Clonezilla...
Oct 03 15:45:54 clone-192-168-100-22 systemd[1]: Started OCS-run service via Clonezilla.
root@clone-192-168-100-22:/etc/systemd/system# systemctl list-dependencies ocsd-run.service
ocsd-run.service

When I run the Client setup in Interactive mode it see the disks and the Restore works perfectly. I have included a picture of that as well.

drbl-ocs -b -h ” 192.168.100.22" -l en_US.UTF-8 -y1 -p reboot select_in_client

When it fails and I drop to a prompt and I can run the command it shows in the Client windows it now works perfectly.

/usr/sbin/ocs-sr -g auto -e1 auto -e2 -r -j2 -c -scr -p reboot restoredisk 2020-10-02-17-imgG40 sda

I am running Clonezilla SE version 3.39.14 and was just pulled down and installed a few days ago.

Any help would be appreciated.

Clay

[Clay]

I wanted to add the sda is a Hardware RAID 5 volume.

Clay

[Clay]

I was able to work around this issue by adding a delay.

# 3 modes, proc-cmdline, ocs-run.param, and both. If both, the ocs_opt are the same in proc-cmdline and ocs-run.param. We choose to use proc-cmdline if it's both so that we can always put "ocs_client_trig_type=both" in drbl-ocs.conf. If we want to interactively debug, use ocs-run -p.
  case "$ocs_client_trig_type" in
    proc-cmdline|both)
      echo "Reading ocs_opt from /proc/cmdline..."
      # Following is a fix for sda not coming on line before
      # restore is started.  quality@sambanovasystems.com
   ***->   echo "Waiting 10 secs to allow all disks to be probed..."
     ->/bin/sleep 10*
      parse_cmdline_option ocs_opt # ocs_opt is now got from /proc/cmdline
      [ -z "$ocs_opt" ] && wait_for_press_enter_then_abort "No clonezilla param in /proc/cmdline!"
      case "$ocs_opt" in
       *select_in_client*)
         # For Ubuntu < 13.10, the plymouthd might be running even we force to disable it in /etc/init/plymouth.conf.

[Steven Shiau]

OK, thanks for sharing that. Apparently it needs more time to be enabled after system is booted.
Newer Linux kernel might fix this issue in the future.

Steven