Exaion
Using the Agent

Troubleshooting

What a message or a symptom on the agent means, and what to do about it, from start-up to the end of the session.

Find the message or the symptom you see. Messages are quoted as the agent shows them. A problem with a proof already on the portal (refused, waiting, failed) is covered in Unblock a proof.

The machine does not start from the stick

What you seeWhat it meansWhat to do
The machine starts its usual system, or says no bootable device.The stick was written in a mode that does not start, or with a tool that changes it.Write it again with a supported tool: see Choose a writing tool. With Rufus, use DD Image mode.
After writing, Windows shows the stick as two drives.Normal for a stick written from the ISO.Never format or initialize it. See Write the stick.
An iLO 4 server does not start from the card's virtual USB key.Not supported.Mount the ISO as a virtual DVD instead: see What does not work.
A server tries to start over the network (DHCP, PXE) instead of starting the agent.The management card dropped the virtual DVD: on HPE iLO 4, booting once from it covers a single start.Mount the ISO again, then restart the server: see Start the server.
No menu on the serial console, or each key arrives twice.Wrong serial port, or the BIOS serial redirection is on.See Follow the session from the serial console.
A plain text menu instead of the graphical one.The machine lacks a graphics mode the menu needs.Nothing: the text menu works the same. See Technical details.
Exaion Wipe could not start: nothing is erased. and Write the ISO again from the portal., then the machine switches off after a minute. Or BOOT FAILED!, then the machine halts.The system on the stick could not start.Write the stick again from your ISO: see Write the stick.

The session refuses to start

Nothing is erased in these cases.

What you seeWhat it meansWhat to do
No identity on the boot medium: start from a key written from your ISOThe stick was not written from your organization's ISO.Write it again from your ISO: see What you need.
Base image, with no identity: download your organisation's ISO from the portalThe stick holds the base image, not your organization's ISO.Download your ISO from the portal and write the stick again.
Identity on this key unusable: write the key again from the portal's ISOThe stick's identity cannot be read or used.Download the ISO again from the portal and write the stick again.
This key's system is not its certificate's: write the ISO again from the portalThe system or the identity on the stick is not the one the portal issued: the stick is damaged or was changed.Download the ISO again from the portal and write the stick again.
No reports partition: start from a USB key of the ISO, or plug in a reports keyNo place to save the proof.See Start from a CD or a virtual DVD.
No serial number, asset tag or UUID: set the asset tag in the firmware setupThe machine gives nothing that identifies it.Set an asset tag in the firmware setup, then start again. A value typed at the agent is not accepted.
No operator name or email: set one under [performer] in exawipe.conf, or another message starting with No operator name or emailNon-interactive mode needs the operator's name or email. The message says where the agent looked.Give one there: see When no name or email is found.
Boot medium not identified, nothing erased: start again in interactive modeThe agent cannot tell which disk it started from, and nobody is there to check.Start in interactive mode: see What each mode does.
No disk could be selected, nothing erased: start in interactive mode to see whyNon-interactive mode found no disk it may erase.Check the disks in interactive mode: see Disks the agent never offers.
exawipe.conf, line N: ...A line of the session file is wrong. It never blocks an erasure.See When a line is wrong.

Before and during the erasure

What you seeWhat it meansWhat to do
Warning: boot medium not identified, disks stay excluded. u to liftThe agent cannot tell which disk it started from, so it offers none.Type u to see the reason and lift it if you are sure: see Disks the agent never offers.
A disk marked [-] with a reasonThe agent never erases this disk.See Disks the agent never offers.
Refused, will not be erased: <reason>The disk cannot be erased as it is. The reason says what to do.See Disks refused at confirmation.
Lower guarantee: type a <number>...This disk only gets the lower level of guarantee.Accept it or deselect the disk: see Accept the lower guarantee.
No longer detected: <disks>, or This disk is no longer in the inventory. Refresh and try again.A disk was removed since the list was drawn.Type r to refresh the list, then choose again.
Not enough free space on the reports key: free some or plug in another key, or at the confirmation Not enough space on the reports key: the session will stop before erasing anything unless space is freed or another key is plugged in.A warning: the stick is too full for the proof.See When the stick is full.
Reports key too full, nothing erased: free space on it or plug in another keyNothing erased: the stick has no room for the proof.See When the stick is full.
Reports key not writable: plug in another keyNothing erased: the agent cannot keep room on the stick.Use another stick.
Identifiers not written on the key, nothing erased: check the key, start againNothing erased: the stick was removed or could not be written.Check the stick is plugged in, then start a new session.
A disk shows failedThe erasure or its check did not pass. The other disks go on.See How the result is checked. The reason is in the proof.
A disk shows skippedThe disk was refused at confirmation, was gone or had changed just before its turn, or the session was cancelled.See Disks refused at confirmation.
A disk shows interrupted, not erasedThe agent stopped the session on a defect before this disk was done.See No proof, an agent defect in At the end.
Cancelled: no new disk starts. Wait for the proof; do not power off.You cancelled: the disks already started finish.Wait for the closing screen.
The stick was unplugged.Plugged back in, it is found again.Plug it back in before the end of the session.

On a console

What you seeWhat it meansWhat to do
Last answer came from <console>; you may answer here too.Another console, or the graphical interface, answered last. Nothing is locked.Answer here if you want: see Follow the session from the serial console.
The session changed since your last screen. Read the new state and try again.Another console changed the session before your answer.Read the new screen and answer again.
Connection to the session lost, reconnecting: nothing typed meanwhile is sent.The console lost the session for a moment. It retries every second.Wait, then type again once the screen is back.
Non-interactive mode: no question is asked. Type any line to cancel.Non-interactive mode takes no command from a console: any line typed cancels the session.Type a line only to cancel.
Not available at this step: wait for the next one.The command does not apply now, for example q before the proof is saved.Wait for the next step: see What happens at the end.
Any other refusal of what you typedA typing mistake. The message says what to type.Follow the message.

At the end

What you seeWhat it meansWhat to do
Proof: on the key only, as the portal cannot be reached, <step>No network to the portal: the proof will stay on the stick. The step says where it failed.Check the wired network: see What happens at the end. Or upload the proof later.
The portal was not reached at start: the proof can only be kept on the key.Sending was asked, but the portal was out of reach at start.Upload the proof later: see Deliver a proof kept on the stick.
Proof not stored, do not power off: ... or Proof not written on the reports key, do not power off: ...The proof could not be written: the stick is missing, full or faulty. The agent holds the proof in memory.Plug in a reports key, and do not power off: see Switch off and remove the stick.
Waiting for the portal's answer, up to 20 minutes; the proof is already on the key.The portal is slow or out of reach. The agent tries for up to 20 minutes.Wait, or click Stop waiting for the portal (on a console, type q): see What happens at the end.
Proof not delivered: kept on the key for a later deliveryThe proof did not reach the portal.Upload it.
Proof kept on the key, to deliver to the portal laterThe proof was not sent, by choice or because the portal was out of reach.Upload it.
Proof refused by the portal: <reason>. Keep it on the key.The portal refused the proof. The reason is listed under Portal answers.Keep the proof on the stick. See Unblock a proof.
Proof received by the portal: <status>The portal has the proof.A problem with the status: see Unblock a proof.
Proof lost, the agent stopped before a key took it: erase the disks againThe agent stopped while it held a proof no stick had taken: the proof is lost.Erase the disks again in a new session.
No proof, an agent defect: send support the lone .logs.gz in proofs/, or a photoThe agent could not produce the proof.Contact support.
The agent stopped before any disk was erased: restart the machine.The agent stopped on an error before the session started. The logs for support are written next.Wait for them: see When the agent stops on an error. Then restart the machine. If it comes back, contact support.
Agent stopped after the session: its last screen says what became of the proof.The agent stopped on an error after the session closed. The logs for support are written next.Wait for them: see When the agent stops on an error, then contact support.
The agent stopped on an error. Writing the logs for Exaion support.The agent stopped on an error. The logs for support are written without you asking.Wait for the file's name: see When the agent stops on an error.
Plug in a reports key, then press Enter.The agent stopped on an error and no reports key is plugged in.Plug one in and press Enter: see When the agent stops on an error.
Logs for support written on the reports key: <file>.The logs for support are on the stick.Send that file to support: see Contact support.

Contact support

Get the logs for support

Ask the agent for the logs for support: one file that gathers what support needs to understand the session. Leave the reports key plugged in.

Ask for it

On the screen, click Logs for support at the foot of the left column. It works on every screen, the closing screen included. On a console, in interactive mode, type support.

Wait for the file

The agent shows Writing the logs for support on the reports key., then Logs for support written on the reports key: support/<date>.tar.gz.

Send it

Send support the file from the support/ folder of the stick's WipeReports drive, the proof's file name (proofs/<session>.der, shown on the closing screen) and a photo of the screen.

When the agent stops on an error

When the agent itself stops on an error, the logs for support are written without you asking. The screen shows, in English then in French:

The agent stopped on an error. Writing the logs for Exaion support.
L'agent s'est arrêté sur une erreur. Écriture des logs pour le support Exaion.

then Logs for support written on the reports key: support/<date>.tar.gz. Send that file as above. If no reports key is plugged in, the screen shows Plug in a reports key, then press Enter.: plug one in and press Enter. Do not switch the machine off before the file's name is shown: the system's logs are lost at power-off.

What the file holds

The file is not sent to the portal. It never holds a key, nor the values a person typed (name, email, asset values). It does hold the machine's and the disks' models and serial numbers.

What you seeWhat to do
Logs for support not written: no reports key. Plug one in, then ask again.Plug in a reports key, then ask again.
Logs for support not written: not enough space on the reports key for them and the proofs.Use another reports key: the logs never take the proof's room.
Logs for support not written: the reports key could not be written. Check the key, then ask again.Check the stick, or use another one.
Logs for support are being written: wait for them, then ask again if needed.Wait for the first ones.

When the logs for support could not be written, send what is left:

  • after No proof, an agent defect: the session's logs, the .logs.gz file alone in proofs/ with no .der beside it, and a photo of the screen;
  • otherwise: a photo of the screen. The system's logs are lost when the machine is switched off.

Contents