Hi Birgit, thanks for your quick reply. I forgot to mention, that a simple
tar cvf /dev/nst0 <file> and also a tar cvf /dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst <file> is working without any issue. But anyway, here are the answers to your questions: 1) root@192.168.0.254:~# ll /dev/tape/by-id/ total 0 lrwxrwxrwx 1 root root 9 Dez 19 10:26 scsi-1391028290 -> ../../st0 lrwxrwxrwx 1 root root 10 Dez 19 10:26 scsi-1391028290-nst -> ../../nst0 lrwxrwxrwx 1 root root 9 Dez 19 10:26 scsi-1IBM_ULTRIUM-TD1_1391028290 -> ../../st0 lrwxrwxrwx 1 root root 10 Dez 19 10:26 scsi-1IBM_ULTRIUM-TD1_1391028290-nst -> ../../nst0 2) ITDT tool is not installed and as already said, the tar commands directly addressing the LTO tape are working without any issue. The same drive was also working flawless with previous Ubuntu 16.04 and Bareos 19.2. 3) root@192.168.0.254:~# lsscsi -g [7:0:3:0] tape IBM ULTRIUM-TD1 4561 /dev/st0 /dev/sg10 root@192.168.0.254:~# mt -f /dev/st0 status drive type = 114 drive status = 1073742848 sense key error = 0 residue count = 0 file number = 0 block number = 0 root@192.168.0.254:~# /bin/mt -f /dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst eject ejects the tape as expected Hope this helps for further analysis. Many thanks and best regards, Robert Am 18.12.20 um 20:12 schrieb 'DUCARROZ Birgit' via bareos-users:
Hi, what can you see when trying cat /dev/tape/by-id/ ? Do you have ITDT tool installed? Can you try to check the LTO with /opt/ITDT_LINUX/ITDT/itdt U 1 ? What's the output of the following commands: lsscsi -g mt -f /dev/st0 status /bin/mt -f /dev/tape/by-id/scsi-xxxxxxx-nst eject ? Regards, Birgit On 18/12/20 18:35, 'Robert' via bareos-users wrote:Hi everybody, I used previous versions of Bareos on my Ubuntu server (16.04) installation and was quite happy with it. In summer I moved to new Ubuntu 20.04 and was desperately waiting for an appropriate update of Bareos - until yesterday. I installed the fresh Bareos 20 release w/o any issue and migrated my working /etc/bareos setup to my new server but everytime the connected LTO was tried to be accessed I get the following error message: Connecting to Storage daemon LTO at 192.168.0.254:9103 ... stored/dev.cc:245 /dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst has an unknown device type 2 Device "My-LTO" requested by DIR could not be opened or does not exist. 3999 Device My-LTO not found or could not be opened. I checked on equal Name/Device and MediaType settings of the director and the storage daemon. Here's my SD LTO device config: Device { Name = My-LTO DeviceType = Tape MediaType = LTO-1 Archive Device = /dev/tape/by-id/scsi-1IBM_ULTRIUM-TD1_1391028290-nst AutomaticMount = yes AlwaysOpen = yes RemovableMedia = yes RandomAccess = no AutoChanger = no Spool Directory = /srv/data0/backup/spool Maximum Spool Size = 20G } Currently I'm running out of ideas what's going on here and I appreciate any help to solve that issue. Many thanks in advance and best regards, Robert -- 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 <mailto:bareos-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/1981989980.1272466.1608312934143%40mail.yahoo.com <https://groups.google.com/d/msgid/bareos-users/1981989980.1272466.1608312934143%40mail.yahoo.com?utm_medium=email&utm_source=footer>.
-- 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 on the web visit https://groups.google.com/d/msgid/bareos-users/802512b4-3a54-0220-e93f-7c9f13b2db93%40yahoo.de.
