Replies: 1 comment 1 reply
-
|
Control C will abort nwipe without it producing any pdfs. When the wipes complete, I believe it says press the spacebar or return key. Doing so, should then allow nwipe to generate the pdf's and exit. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm new to ShredOS and I'm trying to get the following configuration working. The ShredOS bzImage is hosted on a Linux Server (Ubuntu) which also acts as a DHCP server. I would like to connect several 'erasers' (old PCs with disks to be wiped) to a local network via a simple switch. These erasers should load ShredOS via TFTP and then push the certificate.pdf back to the server.
Since the PCs are quite old, they only support legacy PXE. My current directory structure is:
Currently, the erasers boot successfully, load the ShredOS image, and start the process. However, I am having trouble with the PDF saving feature.
When I interrupt the process with a CTRL+C, I expect a .pdf file (containing either the report or error logs) to be saved back to the server. I created a folder at
/srv/tftp/PDF/, but I haven't been able to get the upload to work yet.Here the content of my default file:
I copied the shredos_output parameter from a previous post which reports almost the same hardware configuration. Below a picture of the error screen I get every time.

Should I expect the erasing process to end? No PDF file or report is even created if the process is interrupted with CRTL+C.
Any advice would be useful.
Thanks in advance.
Paolo
Beta Was this translation helpful? Give feedback.
All reactions