Hello again, the latest backup have been running smoothly without any errors so the issue can be closed.
Greetings, Jens jens.gr...@gmail.com schrieb am Mittwoch, 4. Juni 2025 um 17:04:40 UTC+2: > Hi Andreas, > > thank you for the tip. I've looked into the kernel.log and found these > entries: > > 2025-05-26T23:16:43.264361+02:00 gandalf kernel: [49612.006103] > mpt3sas_cm0: log_info(0x31120439): originator(PL), code(0x12), > sub_code(0x0439) > 2025-05-26T23:16:43.264389+02:00 gandalf kernel: [49612.006153] st > 1:0:0:0: [st0] Error b0000 (driver bt 0, host bt 0xb). > … > 2025-05-27T23:09:14.578491+02:00 gandalf kernel: [135560.892293] > mpt3sas_cm0: log_info(0x31120439): originator(PL), code(0x12), > sub_code(0x0439) > 2025-05-27T23:09:14.578508+02:00 gandalf kernel: [135560.892324] st > 1:0:0:0: [st0] Error b0000 (driver bt 0, host bt 0xb). > > I'm not sure what that exactly means, but some research and ChatGPT make > me think that this may indicate a medium error, a hardware issue, or a > cable/SAS connection problem. > > I've tested different tapes with the same error so i would rule out the > medium error. The tape drive was replaced in November 2024 so I would rule > that out too. Maybe a cable/SAS connection problem which has been magically > resolved by the reboot. > > As I wrote I will have an eye on the next few backups hoping I can close > this issue. > > Greetings, Jens > > Andreas Rogge schrieb am Mittwoch, 4. Juni 2025 um 14:50:05 UTC+2: > >> Hi Jens, >> >> Am 03.06.25 um 10:11 schrieb jens.gr...@gmail.com: >> > The backup finished with the old kernel without any errors. >> > >> > After that I rebooted into the new kernel and started another (smaller) >> > backup job which also ran without errors. >> > >> > So maybe it was just a weird coincidence. I will let some more backups >> > run with the new kernel and report if the errors occur. >> >> It usually makes sense to look at the kernel-log (i.e. dmesg) after >> things like that happen. >> While the tape driver's API is pretty terse and doesn't usually report >> anything beyond "IO Error" the kernel log is usually a lot more chatty. >> >> Best Regards, >> Andreas >> -- >> Andreas Rogge andrea...@bareos.com >> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386> >> 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, Jörg Steffens, Philipp Storz >> >> -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bareos-users/a6beca82-0eac-4b35-970a-5128a4823930n%40googlegroups.com.
