On Tue, Sep 19, 2017 at 18:44:35 +0200, Stefan G. Weichinger wrote:
> Problem:
>
> even after installing mt-st, scsiutils etc and repeated reboots I
> don't get any device files (/dev/nst? /dev/st? /dev/tape* etc)
>
> Even a mknod or modprobe st does not help:
>
> # mknod /dev/st0 c 9 0
>
> # mt -f /dev/st0 status
> /dev/st0: No such device or address
>
> Any advice?
>
I don't know the specifics for a SAS-based tape drive, but in general my
impression is that (on modern Debian Linux systems) all device files
should be aotmatically created (via udev) when the related kernel module
is loaded.
(See /lib/udev/rules.d/60-persistent-storage-tape.rules for a little
more information, though that mostly just shows how the /dev/tape/by-id
and by-path symlinks get created pointing to the kernel-module-default
/dev/st* device files.)
For a "plain" SCSI tape drive we have, the kernel module in question (on
an old server running linux 2.6) is just "st.ko" . So, there is a
module for the SCSI card that gets loaded (by the PCI-bus scanning
process), then the st.ko module gets loaded when the tape drive is
detected on the SCSI bus.
Sounds like your SAS card driver is being detected by the PCI scan, but
I'm not sure which module is supposed to handle the tape drive in your
case... (or the answer to your question about firmware...).
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
