SCSI auto sense failure when SCSI tape drives are present

I've got a driver based on Sun's old SCSI Solaris 8 bst.c sample that worked fine up until the latest Solaris 10. Now I get a "Check condition with Auto Sensing" failure on all SCSI targets using this driver whenever a SCSI tape drive is present.
Is there a document that describes SCSI driver changes with the latest Solaris 10?

When a failure occurs pkt_r is 0 (command complete), pkt_state has flags 0x17 (which mean xfer didn't happen and STATE_ARQ_DONE didn't happen), but the sts_chk bit is true indicating a check condition.
rqsense option is set, so the driver doesn't attempt to manually retrieve sense data. Should it?
Anyone at Sun want to advise on an OS behavior change that might be linked to this?

Similar Messages

SCSI Tape Drive 599-2081-01: What tapes?

I can find no documentation whatsoever on sun.com for the SCSI Tape Drive 599-2081-01. I'm thinking of buying this tape drive from a friend, but he doesn't know what tapes will work on it.
Will Exabyte 8mm 112metre tapes work, for instance? I already have some of them.
This is to work with an Ultra 10. I doubt an my old Adaptec 2940UW card will work with it... I'll have to get a PCI card that's suitable for Solaris 8.
Thanks!

I have one of these drives and currently use Exabyte 170m (Mammoth) tapes... they run about 50 bucks
and their part number is 312629...

Sony SDT-9000 scsi tape drive under udev

I've installed Arch .7 and have updated the system with pacman. I set up the system to use udev.
I have an Adaptec AHA-7850 scsi card with a Sony SDT-9000 tape drive attached as the only scsi device.
When I check out /dev, there is an sg0 device, but no tape, st0, nst0, etc. dmesg shows the tape drive identified at boot, and cat /proc/scsi/scsi also shows it.
I can't use mt on the sg0 device, and I'm not sure if that is my controller or my tape drive, and if the tape drive, how I gain access to it.
Thanks in advance.

Ok, I figured it out. I was using kernel26-scsi, but didn't realize I still needed to load the scsi tape module (st) into rc.conf. Did that, now it works.

How to add SCSI tape drive card to Hyper -v 2012

Hi,
It is possible to add HP LTO tape drive through SCSI connector in Windows server 2012 core installation standard edition.
Regards,
Shahul Hameed

Are you referring to Windows Server 2012 or Hyper-V 2012? Big difference.
With Hyper-V 2012, you only have the Hyper-V role, no other roles. With Windows Server 2012 you should be able to do it, if the HP drivers allow you to install without a GUI, or you may want to install the tape drivers with the GUI and then remove the GUI
to go back to a "core" install.
You cannot connect or pass-through a tape drive to a Hyper-V VM, regardless of the host.

Drivers for scsi tape drive

morning, mr
i have a SUN blade 1500, solaris 9, i attached Fujitsu tape drive 3480/90 M2488C, in adaptec scsi (se) card, but i don see the drive in solaris, the scsi card is good (tested) and Fujitsu tape drive is good (tested).
Please, what i need to do?, what command, patches? i don know wath to do
thank you
victor Rodriguez

Consider using a SCSI card that has been qualified to work in a SPARC-based system.
http://sunsolve.sun.com/handbook_pub/Systems/SunBlade1500/components.html#SCSI
Adaptec brand cards do not work in that architecture.
They work in PeeCee's.

What external tape drives are compatible with sunblade 100s?

hi,
please, can anybody tell me:
1. where i can find out whether or not a particular tape drive is compatible with my sunblade 100 workstation running solaris 9?
2. do external tape drives usually connect to the workstation's serial port?
3. what kind of specs/features should i be looking out for?
thanks in advance for your replies.
Message was edited by:
sun-certified

I would imagine you could use any tape drive with your sun blade... most are connected by either scsi or fiber channel... there could be some that are network controlled... not aware of any that are controlled by serial port...
GOOGLE is a wonderful thing... try it, you will like it...
compatibility is more concerned with which OS and program you want to use with the tape drive...
specs depend on what you are backing up... a single user would most likely only need a single drive... if you were a multi-national corp, then maybe you might contact Sun Sales...
maybe you should to some research yourself...
haroldkarl

How do i find out what drives are present in a particular system

Hi,
How do i find out what drives are available in a particular system either by giving the systems ipaddress or the systems name...

You can't do that. That would be a real security risc.
/KAj

IPAD 3 wont connect to MIFI 4620L when other wifi signals are present

I work in a large building with multiple wifi signals bouncing around. My MIFI 4620L works perfectly with all my devices everywhere except in the building in which I work (where it is most needed). Jetpack reception is good. IPAD recognizes the jetpack, but when I try to connect it either simply wont connect or it connects and disconnects in a fast repetitive cycle. Any Ideas?

Hi knox99,
It's a bummer when you are having trouble using your device in the place you need it most! I'm here to work with you and get to the root cause of the issue. Please try the steps below for some troubleshooting.
Connect to any device and then navigate to 192.168.1.1 . Then, login using the password on the Mifi label. Once completed, please click on Advanced and then Settings and change the available Wi-fi Connects to one. At this point, please retest at your work location. Please let me know if you need additional assistance, thank you!
Christina B
VZW Support
Follow us on Twitter @VZWSupport

External tape drive DAT 72 problem

Hi all,
I have solaris 10 sparc running and working very well
but i have problem with external SCSI tape drive DAT 72 problem
it seems to me the tape drive is manufactured by SUN microsystems
when i ran ls -l /dev/rmt/0
it reveals the following output
bash-3.00# mt -f /dev/rmt/0 status
/dev/rmt/0: No such file or directorywhen i ran ls -l
it reveals the following output
ls -l /dev/rmt/0
lrwxrwxrwx   1 root     root          43 Sep 20 2006 /dev/rmt/0 -> ../../devices/pci@8,600000/scsi@1,1/st@3,0:it seems to me everything is okay
SCSI cable is connected properly to Tape device and to server as well
the tape has SCSI termination dongle as well and connected properly to Tape device as well
any ideas would be a great assist
Thanks in advance
Edit/Delete Message

first of all thanks for your reply
it's not newly installed and i'm not sure if it was working or not because i'm successor for an administrator who left job to new
by the way i rebooted to OBP multiple in hope that Solaris search for new peripherals and configure the one's it recognises.
times with no luck
anyways i ran prtconf bash-3.00# prtconf
System Configuration: Sun Microsystems sun4u
Memory size: 8192 Megabytes
System Peripherals (Software Nodes):
SUNW,Sun-Fire-280R
    scsi_vhci, instance #0
    packages (driver not attached)
        SUNW,builtin-drivers (driver not attached)
        deblocker (driver not attached)
        disk-label (driver not attached)
        terminal-emulator (driver not attached)
        SUNW,debug (driver not attached)
        dropins (driver not attached)
        kbd-translator (driver not attached)
        obp-tftp (driver not attached)
        SUNW,i2c-ram-device (driver not attached)
        SUNW,fru-device (driver not attached)
        ufs-file-system (driver not attached)
        hsfs-file-system (driver not attached)
    chosen (driver not attached)
    openprom (driver not attached)
        client-services (driver not attached)
    options, instance #0
    aliases (driver not attached)
    memory (driver not attached)
    virtual-memory (driver not attached)
    SUNW,UltraSPARC-III+ (driver not attached)
    memory-controller, instance #0
    SUNW,UltraSPARC-III+ (driver not attached)
    memory-controller, instance #1
    pci, instance #0
        ebus, instance #0
            flashprom (driver not attached)
            i2c, instance #0
                nvram, instance #0
                idprom (driver not attached)
                dimm-fru, instance #1
                dimm-fru, instance #2
                dimm-fru, instance #3
                dimm-fru, instance #4
                dimm-fru, instance #5
                dimm-fru, instance #6
                dimm-fru, instance #7
                dimm-fru, instance #8
            bbc (driver not attached)
            power (driver not attached)
            i2c, instance #1
                cpu-fru, instance #9
                temperature, instance #0
                cpu-fru, instance #10
                temperature, instance #1
                fan-control, instance #0
                motherboard-fru, instance #11
                ioexp, instance #0
                ioexp, instance #1
                ioexp, instance #2
                fcal-backplane, instance #12
                remote-system-console, instance #13
                power-distribution-board, instance #14
                power-supply, instance #15
                power-supply, instance #16
                rscrtc (driver not attached)
            beep, instance #0
            rtc, instance #0
            gpio, instance #0
            pmc, instance #0
            parallel, instance #0
            rsc-control, instance #0
            rsc-console, instance #1
            serial, instance #0
        network, instance #0
        usb, instance #0
            mouse, instance #3
            keyboard, instance #2
        scsi, instance #0
            disk (driver not attached)
            tape (driver not attached)
            sd, instance #6
        scsi, instance #1
            disk (driver not attached)
            tape (driver not attached)
        SUNW,XVR-100, instance #0
    pci, instance #1
        SUNW,qlc, instance #0
            fp (driver not attached)
                disk (driver not attached)
            fp, instance #1
                ssd, instance #1
                ssd, instance #0
        scsi, instance #2
            disk (driver not attached)
            tape (driver not attached)
            st, instance #18
        scsi, instance #3
            disk (driver not attached)
            tape (driver not attached)
            sd, instance #1 (driver not attached)
            sd, instance #2 (driver not attached)
            sd, instance #3 (driver not attached)
            sd, instance #4 (driver not attached)
            sd, instance #5 (driver not attached)
            sd, instance #7 (driver not attached)
            sd, instance #8 (driver not attached)
            sd, instance #9 (driver not attached)
            sd, instance #10 (driver not attached)
            sd, instance #11 (driver not attached)
            sd, instance #12 (driver not attached)
            sd, instance #13 (driver not attached)
            sd, instance #14 (driver not attached)
            sd, instance #15 (driver not attached)
            sd, instance #16 (driver not attached)
            st, instance #0 (driver not attached)
            st, instance #1 (driver not attached)
            st, instance #2 (driver not attached)
            st, instance #3 (driver not attached)
            st, instance #4 (driver not attached)
            st, instance #5 (driver not attached)
            ses, instance #0 (driver not attached)
            ses, instance #1 (driver not attached)
            ses, instance #2 (driver not attached)
            ses, instance #3 (driver not attached)
            ses, instance #4 (driver not attached)
            ses, instance #5 (driver not attached)
            ses, instance #6 (driver not attached)
            ses, instance #7 (driver not attached)
            ses, instance #8 (driver not attached)
            ses, instance #9 (driver not attached)
            ses, instance #10 (driver not attached)
            ses, instance #11 (driver not attached)
            ses, instance #12 (driver not attached)
            ses, instance #13 (driver not attached)
            ses, instance #14 (driver not attached)
            ses, instance #15 (driver not attached)
    ramdisk-root, instance #0
    os-io (driver not attached)
    iscsi, instance #0
    pseudo, instance #0
bash-3.00#any further idea

Solaris FC Tape Drive

Hi Folks,
We have the following scenario:
- SunFire v490 server
- DAT 72 tape, SCSI
- LTO4 tape, FC (via qlogic HBA)
- Solaris 9 + updated patches
We need some help regarding the FC tape configuration. *"cfgadm -al"* shows the FC tape as:
c4::500110a0008a18eb tape connected configured unknownand *"ls -l shows"* :
lrwxrwxrwx 1 root root 68 Jan 31 14:16 /dev/rmt/1 -> ../../devices/pci@8,600000/SUNW,qlc@1/fp@0,0/st@w500110a0008a18eb,0:Wich is the tape's WWN. But when the tape drive status is invoked via "*mt -f /dev/rmt/1 status"* , it shows
/dev/rmt/1: No such device or addressWhat are we missing here?
Any suggestions will be greatly appreciated, thanks in advance,
SEC

Hi,
Thanks for your responses, after installing the suggested patch in single user mode, performing reconfiguration reboot did not help.
The FC HBA is already configured and working, but qhe we try to reconfigure the drive it shows:
root@host1 # cfgadm -c configure c4::500110a0008a18eb
cfgadm: Library error: failed to create device node: 500110a0008a18eb: Invalid argumentAny help will be very appreciated,
SEC

Sys-suspend fails on Solaris 9 with tape drive present

I ran across a post by T. Kloeber (http://forum.java.sun.com/thread.jspa?threadID=5109999&messageID=9374786) on the Sun developer forum on this.
I replaced my Solaris 7 SS5 with an Ultra 2 and installed Solaris 9 fresh. The external disks and tape drive are unchanged. The SS5 used to suspend properly about 95% of the time, but now the machine refuses to suspend with the tape drive connected. Log messages are:
Mar 21 16:20:13 madera cpr: [ID 535284 kern.notice] System is being suspended
Mar 21 16:20:24 madera cpr: [ID 122848 kern.warning] WARNING: Unable to suspend device st@4,0.
Mar 21 16:20:24 madera cpr: [ID 537702 kern.warning] WARNING: Device is busy or does not support suspend/resume.
Mar 21 16:20:30 madera cpr: [ID 457896 kern.notice] NOTICE: Suspend operation failed.
Mar 21 16:20:30 madera cpr: [ID 583038 kern.notice] System has been resumed.
and the system is not suspended. Is there anything i am missing on Solaris 9?
I am able to modunload the st driver, then when I attempt to suspend, the driver gets reloaded, and I get the failure above.
I ran across an E10000 service manual from 2.6 days that said that tape devices were not suspendable. They must have rethought that by Solaris 7. No idea why 9 should refuse this. I have the latest recommended patches.
TIA for any information!
TW

I ran across a post by T. Kloeber (http://forum.java.sun.com/thread.jspa?threadID=5109999&messageID=9374786) on the Sun developer forum on this.
I replaced my Solaris 7 SS5 with an Ultra 2 and installed Solaris 9 fresh. The external disks and tape drive are unchanged. The SS5 used to suspend properly about 95% of the time, but now the machine refuses to suspend with the tape drive connected. Log messages are:
Mar 21 16:20:13 madera cpr: [ID 535284 kern.notice] System is being suspended
Mar 21 16:20:24 madera cpr: [ID 122848 kern.warning] WARNING: Unable to suspend device st@4,0.
Mar 21 16:20:24 madera cpr: [ID 537702 kern.warning] WARNING: Device is busy or does not support suspend/resume.
Mar 21 16:20:30 madera cpr: [ID 457896 kern.notice] NOTICE: Suspend operation failed.
Mar 21 16:20:30 madera cpr: [ID 583038 kern.notice] System has been resumed.
and the system is not suspended. Is there anything i am missing on Solaris 9?
I am able to modunload the st driver, then when I attempt to suspend, the driver gets reloaded, and I get the failure above.
I ran across an E10000 service manual from 2.6 days that said that tape devices were not suspendable. They must have rethought that by Solaris 7. No idea why 9 should refuse this. I have the latest recommended patches.
TIA for any information!
TW

Tape drives disappears intermittently

Hi,
We have a scalar-1500 library attached to SunFire V440 system with Solaris9/05. The problem is that some of the tape drives are disappearing to the OS intermittently. We do remove and re-fix the failed drives to resolve the issue. Anybody can advice me on this? Is this a problem with the tape library? or with the OS or with the SAN switches?
c9::500308c09b7c3011 tape connected configured unknown
c9::500308c09b7c3019 tape connected configured unknown
c13 fc-fabric connected configured unknown
c13::500308c09b7c3001 tape connected configured failed
c13::500308c09b7c3091 tape connected configured unknown
c13::500308c09b7c3099 tape connected configured unknown
c14 fc-fabric connected configured unknown
c14::500308c09b7c3005 tape connected configured unknown
c14::500308c09b7c3095 tape connected configured unknown
c14::500308c09b7c309d tape connected configured unknown
Nov 19 08:21:06 server1 transport rejected
Nov 19 08:21:16 server1 scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/SUNW,qlc@4/fp@0,0/st@w500308c09b7c3001,0 (st331):
Nov 19 08:21:16 server1 transport rejected
Nov 19 08:21:16 server1 avrd[5067]: [ID 459058 daemon.error] ioctl error on IBM.ULTRIUM-TD3.005 (device 6, /devices/pci@1e,600000/SUNW,qlc@4/fp@0,0/sg@w500308c09b7c3001,0:raw) thru sg driver, I/O error
Nov 19 08:21:26 server1 scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/SUNW,qlc@4/fp@0,0/st@w500308c09b7c3001,0 (st331):
kapsi

try to force load sg driver using /etc/system, so that the driver doesn't get unloaded if the drives are not used
Hope this helps
Rgeards
Ushas Symon

MacBook Doesn't Wake Up (when External FireWire Drives attached)

Anybody else notice their MacBook not waking up from sleep when Fire Wire drives are attached, specifically through the FW port or the Express Card port.
Granted, the MacBook wakes up 50% of the time in general with nothing attached...kind of a crap shoot.

Hi, I have a macbook air for some time now. It works fine, starts reasonable fast and with one exception I'm pleased with it.If I closed the LID or press the on-off button the system sleeps. When I open the lid the next day (8 -12 hrs later) the system doesn't wake up. The log file which I presume is send to Apple did lead to a patch. I saw on the support site various conversations in respect to this issue with various results.
I see that the problem of James even returned and was not reported to be resolved until now.
In my log I have the following messages, "Sleep failure" of last few days. What should I do to resolve this, or is Apple delivering a patch for this?
<Start log copy>
17-09-14 03:14:01,755 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Capability Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
17-09-14 09:24:37,960 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Platform Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
20-09-14 03:31:14,288 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Capability Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
20-09-14 09:56:41,453 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Platform Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
<end log copy>
regards, Roderick.

HD file storage to tape drive

We are soon going to be shooting everything in HD (moving up from 4:3 SD)
What are the best options you have found to work for storing data long-term?
Going to HD tape is NOT an option, so I figured that tape drives are the best solution. Cost is an issue, so I'm looking for a reasonably priced product.
Are there some that are better than others?
THX

HI Paul, I recently have had some great success with Ultrium LTO4 tape drives in a P2 workflow on native OSX. I use TOLISGROUPS BRU-PE (beta), HP AND QUantum tape drives with both ATTOTECH expressas and LSI SA HBAs in a MACPRO.
For all the detail and comments look at:
http://www.reduser.net/forum/showthread.php?t=21284&page=6
and
http://discussions.apple.com/thread.jspa?messageID=8457828&#8457828
I very happy with this workflow and its not that expensive.
w
HK

SL5000 tape drives not detected

Hello Folks,
Hope all are fine.
We have connected SL 500 drives and a robot to the switch A ( Brocade silkworm )where the backup server is connected. The back server is also connected to the Switch B to keep redundancy.
The following are the zone details
Swich A
Zone name: bkpzone
Switch ports: 1( bkpserver), 2( SL500 tape drive 1), 3(Robot)
Swich B
Zone name: bkpzone
Swich ports: 1( bkpserver), 2( SL500 tape drive 2)
Once connected, the backup server is rebooted by using reboot -- -rv to detect the tape drives and robot. Unfortunately the two tape drives are not present in /dev/rmt and it rmt seems to be empty. But the Robot is detected.
The OS version is SunOS prdbw 5.9 Generic_122300-19 sun4u sparc SUNW,Sun-Fire-V490.
Do I need to changing anything on the server to get the tape drives detected.
Thanks in advance,
Sal.

sgscan is showing below output. I don't know why it is showing ??? for tapes
bash-3.00# /usr/openv/volmgr/bin/sgscan
/dev/sg/c0t0l0: Changer: "ATL 1500"
/dev/sg/c0t1l0: Tape (???): ""
/dev/sg/c0t2l0: Tape (???): ""
/dev/sg/c2t0l0: Disk (/dev/rdsk/c0t0d0): "SEAGATE ST336605LSUN36G"
/dev/sg/c2t1l0: Disk (/dev/rdsk/c0t1d0): "SEAGATE ST336607LSUN36G"
/dev/sg/c2t2l0: Disk (/dev/rdsk/c0t2d0): "SEAGATE ST373207LSUN72G"
/dev/sg/c2t3l0: Disk (/dev/rdsk/c0t3d0): "SEAGATE ST373207LSUN72G"
----------------------------

SCSI auto sense failure when SCSI tape drives are present

Similar Messages

Maybe you are looking for