Re: [Bacula-users] ERR=Cannot write block. Device is disabled.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hello,

This is the relatively new tape Alert code in Bacula.  The messages are 
for the most part hardware tape errors that Bacula has detected.  You 
can look up tape alert codes, but in general, you will find that they 
tell you the same thing that Bacula has reported.  In this case, after 
the I/O error, Bacula checks the tape alert you configured (or you took 
the default) and it reports tape alert 20.  This particular alert 
generally indicates that the tape media itself is bad, but to keep from 
contaminating the drive, Bacula has automatically disables the drive.  
It also reported that you need to clean your drive.

See your drive manufacturer's manual for how to clean the drive -- 
generally it is cleaned by inserting (or autoloading) a cleaning 
cartridge.  Note, if a drive is particularly dirty it may require 
several cleanings.  Then you can enable the drive with the "enable" 
command in Bacula, and if I am not mistaken, all the old alert status 
codes are cleared on the next "mount" command (even if it is already 
mounted).  This should be documented in the Bacula new features section 
of the document.

By the way, after such an incident (somewhat rare for most people), I 
would recommend to do a btape "test" command as described in the 
manual.  Note: it needs a non-labelled tape and will write on it.

Best regards,
Kern

On 06/16/2018 11:16 PM, Tilman Schmidt wrote:
> My Bacula 9.0.8 installation aborted a job on an LTO-2 drive with a
> pretty spectacular series of error messages, claiming a defective tape
> and asking for a cleaning:
>
> 16-Jun 00:01 xenon-sd JobId 4680: User specified Device spool size
> reached: DevSpoolSize=26,843,596,555 MaxDevSpoolSize=26,843,545,600
> 16-Jun 00:01 xenon-sd JobId 4680: Writing spooled data to Volume.
> Despooling 26,843,596,555 bytes ...
> 16-Jun 00:14 xenon-sd JobId 4680: Error: block.c:293 Write error at
> 15:13078 on device "LTO-2" (/dev/nst0) Vol=Oktober-2. ERR=Input/output
> error.
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Alert: Volume="Oktober-2"
> alert=3: ERR=The operation has stopped because an error has occurred
> while reading or writing data which the drive cannot correct. The drive
> had a hard read or write error
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Alert: Volume="Oktober-2"
> alert=4: ERR=Your data is at risk: Media cannot be written/read, or
> media performance is severely degraded.
>      1. Copy any data you require from the tape.
>      2. Do not use this tape again.
>      3. Restart the operation with a different tape.
> 16-Jun 00:14 xenon-sd JobId 4680: Warning: Disabled Device "LTO-2"
> (/dev/nst0) due to tape alert=20.
> 16-Jun 00:14 xenon-sd JobId 4680: Warning: Disabled Volume "Oktober-2"
> due to tape alert=20.
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Alert: Volume="Oktober-2"
> alert=20: ERR=The tape drive needs cleaning: The drive thinks it has a
> head clog, or needs cleaning.
>      1. If the operation has stopped, eject the tape and clean the drive.
>      2. If the operation has not stopped, wait for it to finish and then
> clean the drive.
>      Check the tape drive users manual for device specific cleaning
> instructions.
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Error creating JobMedia
> records: 1000 OK VolName=Oktober-2 VolJobs=1 VolFiles=15
> VolBlocks=710607 VolBytes=45842743296 VolABytes=0 VolHoleBytes=0
> VolHoles=0 VolMounts=5 VolErrors=2 VolWrites=1590516 MaxVolBytes=0
> VolCapacityBytes=0 VolStatus=Disabled Slot=0 MaxVolJobs=0 MaxVolFiles=0
> InChanger=1 VolReadTime=0 VolWriteTime=4283259819 EndFile=11
> EndBlock=42620 VolType=2 LabelType=0 MediaId=56 ScratchPoolId=0
> VolParts=0 VolCloudParts=0 LastPartBytes=0 Enabled=0
>
> 16-Jun 00:14 xenon-sd JobId 4680: Error: Error writing final EOF to
> tape. Volume Oktober-2 may not be readable.
> tape_dev.c:963 ioctl MTWEOF error on "LTO-2" (/dev/nst0).
> ERR=Input/output error.
> 16-Jun 00:14 xenon-sd JobId 4680: Despooling elapsed time = 00:13:00,
> Transfer rate = 34.41 M Bytes/second
> 16-Jun 00:14 xenon-sd JobId 4680: Elapsed time=01:48:56, Transfer
> rate=16.41 M Bytes/second
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Alert: Volume="Oktober-2"
> alert=3: ERR=The operation has stopped because an error has occurred
> while reading or writing data which the drive cannot correct. The drive
> had a hard read or write error
> 16-Jun 00:14 xenon-sd JobId 4680: Fatal error: Alert: Volume="Oktober-2"
> alert=4: ERR=Your data is at risk: Media cannot be written/read, or
> media performance is severely degraded.
>      1. Copy any data you require from the tape.
>      2. Do not use this tape again.
>      3. Restart the operation with a different tape.
> 16-Jun 00:14 xenon-sd JobId 4680: Warning: Disabled Device "LTO-2"
> (/dev/nst0) due to tape alert=20.
> 16-Jun 00:14 xenon-fd JobId 4680: Error: bsock.c:661 Write error sending
> 65540 bytes to Storage daemon:xenon:9103: ERR=Connection reset by peer
> 16-Jun 00:14 xenon-fd JobId 4680: Fatal error: backup.c:843 Network send
> error to SD. ERR=Connection reset by peer
> 16-Jun 00:14 xenon-fd JobId 4680: Error: bsock.c:549 Socket has errors=1
> on call to Storage daemon:xenon:9103
> 16-Jun 00:14 xenon-dir JobId 4680: Error: bsock.c:661 Write error
> sending 345 bytes to Storage daemon:xenon:9103: ERR=Connection reset by peer
>
> As Bacula had not ejected the tape and was still blocking the drive, I
> had to unmount the drive in bconsole in order to do the cleaning, which
> was successful in clearing the cleaning indicator on the drive itself.
> However when I try to mount the next tape, Bacula still considers the
> device disabled:
>
> *mo LTO-2
> block.c:460 Cannot write block. Device is disabled. dev="LTO-2" (/dev/nst0)
> 3902 Cannot mount Volume on Storage Device ""LTO-2" (/dev/nst0)" because:
> Read label block failed: requested Volume "" on Tape device "LTO-2"
> (/dev/nst0) is not a Bacula labeled Volume, because: ERR=Cannot write
> block. Device is disabled. dev="LTO-2" (/dev/nst0)
> 3905 Device ""LTO-2" (/dev/nst0)" open but no Bacula volume is mounted.
> If this is not a blank tape, try unmounting and remounting the Volume.
>
> How do I clear that condition?
> I didn't find anything on that topic in the documentation, and Google
> also turned up nothing on that message.
>
> aTdHvAaNnKcSe
> Tilman
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Bacula-users mailing list
> Bac...@li...
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>