the forced reboot using ocs_postrun1="/usr/sbin/reboot -f" seems to work
I dont know what issues this could potentially cause.... but for now its a solution that works for what we are doing.
I'm going to test it on multiple machines tonight and tomorrow to be certain
and I will report back here
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"I dont know what issues this could potentially cause" -> Basically in your case I do not think there would be any issue using this soft, forcing reboot. Since this should be OK when you have finished all the deployment using ocs-sr, which runs "sync" to flush the data in the memory to your storage device in the end.
Of course, this is a workaround. It's better you can find the root cause.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a secondary note for you
with the new kernel in 3.1.1-21
it seems to transfer data slightly faster than it did with the previous one
or at least the speed on partclone shows as faster than previous versions
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Scott,
Maybe you can give testing Clonezilla live 3.2.0-3 a try in your case.
Now we have switched to "systemctl -f reboot" when "-p reboot" option is used. Hence I believe you do not need to add "ocs_postrun" parameter again.
If you give that a try, please let us know the results. Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the forced reboot using ocs_postrun1="/usr/sbin/reboot -f" seems to work
I dont know what issues this could potentially cause.... but for now its a solution that works for what we are doing.
I'm going to test it on multiple machines tonight and tomorrow to be certain
and I will report back here
"I dont know what issues this could potentially cause" -> Basically in your case I do not think there would be any issue using this soft, forcing reboot. Since this should be OK when you have finished all the deployment using ocs-sr, which runs "sync" to flush the data in the memory to your storage device in the end.
Of course, this is a workaround. It's better you can find the root cause.
Steven
I'm ok with it not dumping any memory back to the machine... I dont need any of the clonezilla data with the windows based image we are using
Just a secondary note for you
with the new kernel in 3.1.1-21
it seems to transfer data slightly faster than it did with the previous one
or at least the speed on partclone shows as faster than previous versions
@Scott,
Maybe you can give testing Clonezilla live 3.2.0-3 a try in your case.
Now we have switched to "systemctl -f reboot" when "-p reboot" option is used. Hence I believe you do not need to add "ocs_postrun" parameter again.
If you give that a try, please let us know the results. Thanks.
Steven