On Wednesday, January 28, 2015 at 12:40:34 PM UTC-2, Marco van Wieringen wrote:
> John Bolt <jobolt6 <at> gmail.com> writes:
>
> >
> > Hello,
> >
> > Please inform the procedure to fix the following backup error after the
> backup:
> >
> > fedora18-sd Elapsed time=01:58:01, Transfer rate=68.49 M Bytes/second
> > fedora18-sd Alert: smartctl 6.2 2013-07-26 r3841
> [x86_64-linux-3.11.10-100.fc18.x86_64] (local build)
> > Alert: Copyright (C) 2002-13, Bruce Allen, Christian Franke,
> www.smartmontools.org
> > Alert:
> > Alert: Smartctl open device: /dev/st0 failed: Device or resource busy
> > 3997 Bad alert command: sh -c 'smartctl -H -l error /dev/st0': ERR=Child
> exited with code 2.
> >
> >
> First of all you should not use /dev/st0 as that is the rewinding tape
> device but /dev/nst0 the non rewinding one for the normal backups.
>
> Your actual problem is that Bareos keeps the device open so you cannot
> run smartctl on either the /dev/st0 or /dev/nst0 but need if you
> really want to use this alert reporting you need to use the SCSI
> generic device. "lsscsi -g" should list the generic device that can
> be used for the specific tape drive. You can either hardcode the device
> name in the alert cmd or set the new "Diagnostic Device" option and use
> the "%D" e.g. "smartctl -H -l error %D" The Alert Command however is
> probably replaced by the tapealert plugin in the future as that captures
> the real alerts and stores them in the database so you can at any time
> see past alerts being reported by the drive. The idea is that such
> functionality will eventually be included in the bareos-webui. We already
> have statistics collection and this tapealert collecting in 14.2 and as
> tapealert is a plugin it can use the same handle bareos has open for the
> taoe device and as such has no need to use the generic SCSI device.
>
> --
> Marco van Wieringen [email protected]
> Bareos GmbH & Co. KG Phone: +49-221-63069389
> http://www.bareos.com
>
> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
> Komplementär: Bareos Verwaltungs-GmbH
> Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
> P. Storz, M. v. Wieringen
I followed your instructions to use the generic driver and smartctl did run,
but bareos still reported an error (See the log bellow).
Exit error 4 is bit 2 in smartctl exit status.
man smartctl shows: "Bit 2: Some SMART or other ATA command to the disk failed,
or there was a checksum error in a SMART data structure (see '-b' option
above)."
smartctl -a /dev/sg5 also shows:
Device does not support Self Test logging
Is there anything to do to fix it?
Shouldn't bareos not report an error since it looks like LTO drives just does
not have selt test loggin and that is not an error?
The bareos log is:
The man also suggests it could be "SMART Self-Test Log Structure" because
Alert: smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.11.10-100.fc18.x86_64]
(local build)
Alert: Copyright (C) 2002-13, Bruce Allen, Christian Franke,
www.smartmontools.org
Alert:
Alert: === START OF READ SMART DATA SECTION ===
Alert: TapeAlert: OK
Alert: Percentage used endurance indicator too short (pl=6)
Alert: Error counter log:
Alert: Errors Corrected by Total Correction
Gigabytes Total
Alert: ECC rereads/ errors algorithm
processed uncorrected
Alert: fast | delayed rewrites corrected invocations [10^9
bytes] errors
Alert: read: 0 0 0 0 0 0.071
0
Alert: write: 0 0 0 0 0 0.000
0
Alert:
Alert: Non-medium error count: 0
Alert:
3997 Bad alert command: sh -c 'smartctl -H -l error /dev/sg5': ERR=Child
exited with code 4.
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
