LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Debian Tape Drive not detected (lsmod shows st)? (https://www.linuxquestions.org/questions/linux-hardware-18/debian-tape-drive-not-detected-lsmod-shows-st-443522/)

gecon 05-10-2006 01:00 PM

Debian Tape Drive not detected (lsmod shows st)?
 
Hello all,

It is the first time trying to use a DAT (on SCSI a controller) tape drive on linux.
Unfortunatelly, the tape drive is not available.
Here are some info:

Code:

# uname -r
2.6.8-3-686

Code:

# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW      Rev: DS09
  Type:  Direct-Access                    ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: SEAGATE  Model: ST336607LW      Rev: DS09
  Type:  Direct-Access                    ANSI SCSI revision: 03


Code:

# lsmod
Module                  Size  Used by
st                    40316  0
af_packet              22568  0
ipv6                  264836  12
pcspkr                  3592  0
tsdev                  7392  0
mousedev              10476  0
evdev                  9600  0
psmouse                20360  0
floppy                61200  0
parport_pc            36900  0
parport                41800  1 parport_pc
aic79xx              308572  0
uhci_hcd              33136  0
shpchp                101900  0
pciehp                99020  0
pci_hotplug            34640  2 shpchp,pciehp
intel_agp              22816  1
intel_mch_agp          10608  0
agpgart                34664  2 intel_agp,intel_mch_agp
ehci_hcd              32004  0
usbcore              119044  4 uhci_hcd,ehci_hcd
ata_piix                8132  0
libata                41700  1 ata_piix
e100                  32608  0
mii                    5120  1 e100
e1000                  85828  0
capability              4520  0
commoncap              7232  1 capability
ide_cd                42656  0
ide_core              139940  1 ide_cd
cdrom                  40732  1 ide_cd
genrtc                  9588  0
ext3                  127240  7
jbd                    62616  1 ext3
mbcache                9348  1 ext3
sd_mod                21728  10
aic7xxx              206392  8
scsi_mod              125228  5 st,aic79xx,libata,sd_mod,aic7xxx
unix                  28756  38
font                    8320  0
vesafb                  6656  0
cfbcopyarea            3872  1 vesafb
cfbimgblt              3040  1 vesafb
cfbfillrect            3776  1 vesafb

Code:

# mt -f /dev/st0 status
/dev/st0: No such device or address

Part from /var/log/messages:
Code:

SCSI subsystem initialized
ACPI: PCI interrupt 0000:02:01.0[A] -> GSI 24 (level, low) -> IRQ 201
ACPI: PCI interrupt 0000:02:01.1[B] -> GSI 25 (level, low) -> IRQ 209
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 3960D Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Using anticipatory io scheduler
(scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
(scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit)
  Vendor: SEAGATE  Model: ST336607LW        Rev: DS09
  Type:  Direct-Access                      ANSI SCSI revision: 03
scsi0:A:0:0: Tagged Queuing enabled.  Depth 8
  Vendor: SEAGATE  Model: ST336607LW        Rev: DS09
  Type:  Direct-Access                      ANSI SCSI revision: 03
scsi0:A:1:0: Tagged Queuing enabled.  Depth 8
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 3960D Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs

SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB)
SCSI device sda: drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 > p3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 71132959 512-byte hdwr sectors (36420 MB)
SCSI device sdb: drive cache: write through
 /dev/scsi/host0/bus0/target1/lun0: p1 p2 < p5 p6 >
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Adding 498004k swap on /dev/sda3.  Priority:-1 extents:1
EXT3 FS on sda1, internal journal
Generic RTC Driver v1.07
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Capability LSM initialized
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sdb6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
e1000: Ignoring new-style parameters in presence of obsolete ones
Intel(R) PRO/1000 Network Driver - version 5.2.52-k4

Please, can you provide any suggestions?

And in case this is fixed (don't know how right now), since it is my first time with DAT, is there any nice open source tool that is well known today to handle full/incremental backups and restores on DAT from the console (not GUI)?
I mean a tool providing the user a more friendly interface than tar to be use for restore by the operators and be able to work as a daily cron job, too.

TIA.

Regards,
G.

michaelk 05-11-2006 07:29 AM

I do not see the drive being recognized by the OS.
Does the SCSI controller BIOS detect the tape drive during POST?
Is the SCSI chain terminated correctly?
Make sure the tape drive ID is not set as either of the hard drives.
What is the make/model of the tape drive?

gecon 05-11-2006 09:32 AM

Quote:

Originally Posted by michaelk
I do not see the drive being recognized by the OS.
Does the SCSI controller BIOS detect the tape drive during POST?
Is the SCSI chain terminated correctly?
Make sure the tape drive ID is not set as either of the hard drives.
What is the make/model of the tape drive?


Not recognized by the system is also what I understand from the above. I do not have physical access to the system to see BIOS messages. I will visit the computer room hosting the PC, soon and will post those info.

Thank you...


All times are GMT -5. The time now is 06:32 AM.