SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
command to see what has been detected. On my system I see this:
Attached scsi tape st0 at scsi2, channel 0, id 0, lun 0
Once you have your drive working it is worth noting that if your drive is shoeshining i.e. moving the tape back and forth a lot this is caused by the kernel only allocating a 32k tape buffer by default.
This can be changed either as a parameter to the kernel or as a parameter to modprobe when you load the st module.
in grub.conf add the following to the line starting kernel
If you reboot after loading a module it would be useless since it won't load again automatically. modprobe st to load the module and see if you tape is recognized, or if you want to "feel safe" with a reboot, add the modprobe st line to /etc/rc.d/rc.modules
It would be useful to see the output from the kernel boot (you can do this using dmesg), specifically the section where your scsi card detects the tape drive. Can you post this section onto the forum (not the whole dmesg output).
Hi, sorry for interrupting but I seem to have a very similar if not the same problem. I have a tape drive installed in my Slack 10.1 box and the Adaptec card recognises the drive before Linux starts to boot.
I tried "modprobe st buffers_kbs=128" and now I can see it when I do lsmod:
Module Size Used by Not tainted
st 27832 0 (unused)
Does that mean I should be able to mount it now? I have tried this so far:
root@mail:~# mount /dev/sda1 /mnt/tape
mount: mount point /mnt/tape does not exist
root@mail:~# ls /mnt
cdrom/ floppy/ hd/
root@mail:~# mkdir /mnt/tape
root@mail:~# mount /dev/sda1 /mnt/tape
mount: /dev/sda1 is not a valid block device
root@mail:~# mount /dev/sda /mnt/tape
mount: /dev/sda is not a valid block device
root@mail:~# mount /dev/sdb /mnt/tape
mount: /dev/sdb is not a valid block device
root@mail:~# mount /dev/sg0 /mnt/tape
mount: /dev/sg0 is not a block device
What to try next?
Hope you don't mind me hijacking this thread .. it seemed relevant and may help all of us.
Your problem is that your scsi card has not been correctly configured and the module has not loaded. Because of this the system knows nothing about the scsi devices attached to your scsi controller.
The st module has loaded correctly but because no scsi devices have been detected the module has nothing to do.
Finally tapes can not be mounted like a file system, you can use the command mt to control the tape drive once you have it correctly detected and you can read and write to the tape using programs such as tar but you can't mount it like a filesystem.
If you let me know what scsi card your using we should be able to locate the appropriate module for it.
Now I can control the tape drive using the "mt" command.
I have one final question for ya as you've resurrected this thread! I've been looking for a graphical front end for "mt" since setting this up as I'm used to using programs like Backup Exec in windows, rather than tar and gzip. I tried using KDAT which comes with KDE but it doesn't seem to be capable of mounting my tape drive. I think it's because I have to use mt to send commands to it. Any ideas?
There are a number of open source backup tools available although no GUI to mt that I know of.
I have been trialing bacula http://www.bacula.org/ which allows you to have managed drives, there is also a free version of arkeia available which is a comercial package but will support a single tape drive and should do what you want. have a look at
I know this is an old thread, but I just realized this. When trying to initialize this section of the code, it is telling me that buffers_kbs is not a valid parameter. Any other ideas to change the buffer size?