Am 2017-09-20 um 00:27 schrieb Nathan Stratton Treadway: > 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.
correct. > (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.) Yes, been there ... > 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. You run a kernel 2.6 still ? phew ;-) > 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...). The module "st" is not loaded automatically and even when I modprobe it myself I don't get the device file(s), only this line in dmesg: [Die Sep 19 18:22:36 2017] st: Version 20160209, fixed bufsize 32768, s/g segs 256 I am not sure if that means it recognizes the drive at all? According to "man 4 st" there should be something in /sys/class/scsi_tape/ ... it's empty here.
