Add problems with Bacula unable to open tape device

diff --git a/docs/manuals/en/problems/tapetesting.tex b/docs/manuals/en/problems/tapetesting.tex
index 31ad503a59a4b9e6b2c3943e76c8a75f9df11f5f..994204da43c262031d215cfc9bd5fc18dbf64bb4 100644 (file)
--- a/docs/manuals/en/problems/tapetesting.tex
+++ b/docs/manuals/en/problems/tapetesting.tex
@@ -650,8 +650,43 @@ module is being removed because the kernel deems it idle. This is done via
 remove this entry from {\bf crontab}, or you can manually {\bf modprob} your
 driver module (or add it to the local startup script). Thanks to Alan Brown
 for this tip. 
-\label{IncorrectFiles}
 
+\smallskip
+Sometimes the tape handler gets confused.  This can happen if your tape
+drive door is locked (Bacula locks it when writing a tape), and Bacula
+crashes or some other problem occurs.  After this kind of a problem,
+the kernel driver will not recognize that a tape is loaded and you
+may see messages such as:
+
+\footnotesize
+\begin{verbatim}
+19-Sep 16:39 groschat-sd JobId 16072: Warning: mount.c:219 Open of tape
+device "LTO4-Drive" (/dev/tape/by-id/scsi-3500143801403cf22-nst) Volume
+"AAJ372" failed: ERR=tape_dev.c:162 Unable to open device "LTO4-Drive"
+(/dev/tape/by-id/scsi-3500143801403cf22-nst): ERR=No medium found
+
+19-Sep 16:39 groschat-sd JobId 16072: Please mount append Volume "AAJ372"
+or label a new one for:
+    Job:          Rufus.2016-09-19_16.34.22_03
+    Storage:      "LTO4-Drive" (/dev/tape/by-id/scsi-3500143801403cf22-nst)
+    Pool:         Default
+    Media type:   LTO-4
+\end{verbatim}
+\normalsize
+
+in that case, the best thing to do is unload the tape by hand with:
+
+\begin{verbatim}
+(stop Bacula)
+mtx -f /dev/sgx unload
+(restart Bacula)
+\end{verbatim}
+
+where you replace /dev/sgx by your scsi control device name.
+
+
+
+\label{IncorrectFiles}
 \subsection{Incorrect File Number}
 \index[general]{Number!Incorrect File}
 \index[general]{Incorrect File Number}