Zmanda Forums > Amanda community forums > Operating Systems & Hardware specific issues with Amanda > AIC7xxx detected but no scsi /dev/???
View Full Version : AIC7xxx detected but no scsi /dev/???
Opening tapedev /dev/st0: got error No such device or address.
Try /dev/sg2 - generic scsi device.
Opening tapedev /dev/sg2: got error No such device or address.
Now it is showing that it is not a tape device!!!!!!
You do not have permissions to access the device. amcheck should setuid bit set. or the user should have permission to read tape devices (be part of "disk" group).
Please post your amanda.conf file!
There needs to be another device, the tape drive was not detected by the system. You need to make sure there is not scsi id conflict. Login to the Library control module and figure out what scsi id the tape drive has. If it conflicts with any other scsi devices on the system you will need to change tape scsi id and reboot the changer and the system.
# the actual config file in use at CS.UMD.EDU.
# WARNING: don't use `inf' for tapecycle, it's broken!
etimeout 300 # number of seconds per filesystem for estimates.
#etimeout -600 # total number of seconds for estimates.
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
# amdump, just comment out the definition of tpchanger.
# comment them all out.
# dumps before they are written to tape and are recommended for most sites.
# dumps can be done in parallel (which can dramatically reduce total dump time.
# (with amflush) to tape after an operating system crash or a tape failure.
# they will all be used round-robin.
comment "DEC Differential Digital Linear Tape 2000"
comment "just produced by tapetype program in our own environment"
comment "Exabyte EXB-8500 drive on decent machine"
comment "Exabyte EXB-8200 drive on decent machine"
comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
comment "high-priority root partitions dumped with tar"
comment "The master-host holding disk itself"
2. But this will not work until your system detects your tape device and looking at the /proc/scsi/scsi it has not.
I will check for SCSI ID conflicts. Any other thoughts???
Can you check /var/log/messages for any errors?
SCSI id 7 is typically reserved for the SCSI Controller. I would change the tape scsi id to a different number, reboot the library, reboot the server and check the /proc/scsi/scsi for any new devices.
When you reboot the system you should also have an option to login to the scsi controller utility. By pressing Ctr-D on boot or something along those lines. Once you get in to the utility you can run a scsi scan to see what scsi ids the devices have and make sure you can see both the tape and the changer when you run this scan.
My tapes are AIT-3's which are 100/260Gig tapes. So I tried to run amtapetype to create the tapetype for amanda.conf and this is the error I get.
Opening tapedev /dev/st0: got error Input/output error.
Can you check if you can do dd to the tape?
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
I created the file test and ran dd.
amanda will not be able to use your tape chnager.
I have added these lines into the amanda.conf and this tapetype with these test results.
You cant issue scsi commands to a tape device name. All scsi device name start with "sg" and all tape device name start with "nst". If you want to specify the tape device name you want to write data to you use "nst" if you want to send a scsi command to it you use "sg".
Can you please run "dmesg" and post all the output.
You can also download a tool called "lsscsi" and you can use is to detemine the names for your devices.
agpgart: Detected an Intel i810 E Chipset.
agpgart: detected 4MB dedicated video ram.
eth0: link now 100 mbps, full duplex and up.
How do I configure the tapedev and changerdev????
Weird...what did I do now....????
Check for errors in /var/log/messages.
Oct 30 21:31:33 austin kernel: (scsi0:A:12:0): SCB 7 - Abort Completed.
The device is offline. You will have to reboot the machine for linux to see the device again.
amlabel DailySet1 DailySet1-2 slot 2amlabel: label DailySet1-1 doesn't match labelstr "^DailySet1[0-9][0-9]*$"
did you comment out this line from amanda.conf?
rewinding, writing label DailySet1-1, checking label, done.
also tar up /tmp/amanda directory and e-mail it to me.