Separately, and I'm used to this getting swatted over to Deadline and ultimately my problem to solve is a problem on Linux.
Deadline sniffs out paths to convert from X:/ to /mnt to accommodate cross-platforms however fails to detect the Deep Image path - I don't know why, not sure how Octane presents paths or how Deadline needs to find those paths - it can detect/convert RGBTextures etc and all other Houdini paths I'm using (so it's already 99% Octane compatible) and only fails on this Deep Image.
As I mentioned, I'm used to these errors being left in the ether however, last time the Otoy Houdini developer was found guilty of making inconvenient changes and the community made him change the Octane behaviour back (lol!)
2024-03-28 12:13:35: 0: STDOUT: 12:13:35 INFOR: [save image] -------- Saving the EXR "/mnt/Projects/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: [Octane] 12:13:35 INFOR: [save image] -------- Saving the EXR "/mnt/Projects/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: 12:13:35 INFOR: [save image] -------- Saving the EXR deep image to the "X:/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: [Octane] 12:13:35 INFOR: [save image] -------- Saving the EXR deep image to the "X:/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr" file
2024-03-28 12:13:35: 0: STDOUT: *** OCTANE API ERROR: can't open '/ElectricLensCo/SPS/JT24/Houdini/render/Shot_04/v1/Shot_04_v1_Deep.0061.exr' for writing.
2024-03-28 12:13:35: 0: STDOUT: *** OCTANE API INFO: ERROR: failed to export the deep image file