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. Greetings Jens [email protected] schrieb am Montag, 2. Juni 2025 um 14:44:52 UTC+2: > Hello folks, > > since 2025-05-26 I'm experiencing errors when writing backups from disk to > tape. Here's the first of several error messages in the log: > > 26-Mai 23:16 bareos-sd JobId 61405: Error: stored/block.cc:750 Write error > at 30:8296 on device "IBM-Drive-0" (/dev/nst0). ERR=Eingabe-/Ausgabefehler. > 26-Mai 23:16 bareos-sd JobId 61405: Error: stored/block.cc:768 Write error > on fd=5 at file:blk 30:8296 on device "IBM-Drive-0" (/dev/nst0). > ERR=Eingabe-/Ausgabefehler. > 26-Mai 23:17 bareos-sd JobId 61405: Error: Re-read of last block OK, but > block numbers differ. Read block=8294 Want block=8295. > 26-Mai 23:17 bareos-sd JobId 61405: End of medium on Volume "WOC4-1L78" > Bytes=1,155,880,771,584 Blocks=275,597 at 26-Mai-2025 23:17. > 26-Mai 23:17 bareos-sd JobId 61405: 3307 Issuing autochanger "unload slot > 1, drive 0" command. > 26-Mai 23:19 bareos-dir JobId 61405: Using Volume "WOC1-4L78" from > 'Scratch' pool. > > I'm using bareos 24.0.4~pre0.1014be830-74 (community repo) on an > up-to-date Debian 12.11. The one thing that has happened when the first > error occurred was a kernel upgrade on the computer from version > 6.1.0-35-amd64 to 6.1.0-37-amd64. I rebooted the computer after the upgrade. > > What I've tried so far: > > - I thought this was a problem with an old tape so in the meantime I > tried with 5 different tapes which produce the same error. > - I ran some drive check in the storage loader's Web-UI but no > problems or errors are shown. > - I've booted into the old kernel and I'm running the backup again. > The backup is currently running for more than an hour without errors. > > I would now wait for the backup to finish and then try again with the > newer kernel to see if the problem persists. > > Has anyone experienced similar problems after the kernel upgrade? > > Greetings, Jens > -- 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 view this discussion visit https://groups.google.com/d/msgid/bareos-users/99c829c0-a6c8-436f-bcf6-dffb116cf4c0n%40googlegroups.com.
