Ultra 10 & Adaptec SCSI???

I've a little Ultra 10 I need to set up temporarily as a demo box (one in a pair) for live replication. This requires I have a whole lot more disk space than is available all on its own though - and to cater for this I've had an Adaptec AHA 2940UW (Single-Ended) card installed.
I've come across docos on sunsolve mentioning the infeasibility of BOOTING from such a device due to the drivers that need loading at boot-up. Fortunately I don't need to boot from here, unfortunately I can't seem to find drivers for the card (and most Adaptec cards) anywhere!!!
Would anyone here perhaps know better than what I do? Any and all help would be highly appreciated!
Thanks.
~Moi

Hi
Yes, I suspect that the Adaptec drivers for the 29160 and 29160N haven't been re-written for 10.4 or 10.5. When I upgraded to Tiger (10.4.11) on my MDD G4 1.25GHz DP, the Retrospect software would not run at all until I upgraded Retrospect to 6.1.230 from 5.x. Then the backups would run for a time, then freeze up. I'd have to ForceQuit Retrospect. I did no upgrades to the drivers for the Adaptec card. Since the backups would run until a new DDS-3 tape was needed (about 12-14Gb written to the first tape in the backup set), I suspect Retrospect would signal , via communication w/the HP DAT tape drive on the SCSI chain, that a new tape was needed, but due to changes in the headers/structures in Darwin under Tiger, the app would fail and freeze up. If I could get a copy of the APD driver source code, and enough time!, I could probably fix it.
I went the route of getting an ATTO card and all is now well again in backupland.
Here is the KB article from EMC/Dantz on the Adaptec and ATTO cards and Tiger.
As for the "N", I think the hardware difference is the number and type of internal and external SCSI adapters. APD29160 has a single 68-pin LVD SCSI adapter externally, while the APD29160N has a 50-pin SCSI adapter. The number of internal SCSI adapters is also different for the two cards.
Ed

Similar Messages

  • Dell PowerEdge SC1420 with Ultra 320 scsi dirves

    I am having a problem with installing Solaris 10 on the Dell PowerEdge SC1420 with Ultra 320 SCSI drives using PERC 320/DC Controller. The installation hangs at Configuring Devices and gives me some output messages:
    NOTICE: MSG From Adapter: NMI ISR: NMI_BUS_INTERFACE_UNIT_ERROR
    NOTICE: MSG From Adapter: NormPrioCommand was received with Fib StructType = 0xf
    The notices keeps cycling.
    Has anyone experience this issue?
    Any suggestions are appreciated.
    Thank you,
    Brian

    Update:
    I've got the box to install Solaris 10, however, I had to remove 2 sticks of memory. Originally, the box came with 4GB of memory but now I am down to 2GB. Don't know why this is the case but I am able to proceed with the installation without any error or notice messages. Can someone explain to me why this is the case? I will put the memory sticks back in and boot with the OS installed to see what happens and will update my results.
    Thanks,
    Brian

  • Adaptec scsi card 29320A-R

    In this neteware 6.5sp5 server, I have above card installed. Bios recognise
    this card. But when I load adpu32.ham v.3.01.13 6 Aug 2004. system console
    report a error: INVALID OPTION C04020AA 'SLOT' INVALID SLOT NUMBER.
    I have another netware 6.5sp5 server using the identical adaptec scsi card.
    it does not have problem to recognise this card in slot 1.
    The startup file loads the same ADPU320.HAM. The startment in the
    startup.ncf file read as follows:
    ADPU320.HAM SLOT=1
    The only difference between startup.ncf of these 2 servers is:
    The one which recognise the card in slot 1 has a statement to load
    nwtape.cdm and the one which does not recognise the card in slot 1 and
    produce above error has no such statement to load nwtape.cdm
    Any idea. What do I miss out?
    Wai Chu

    > In this neteware 6.5sp5 server, I have above card installed. Bios
    recognise
    > this card. But when I load adpu32.ham v.3.01.13 6 Aug 2004. system
    console
    > report a error: INVALID OPTION C04020AA 'SLOT' INVALID SLOT NUMBER.
    >
    > I have another netware 6.5sp5 server using the identical adaptec scsi
    card.
    > it does not have problem to recognise this card in slot 1.
    >
    > The startup file loads the same ADPU320.HAM. The startment in the
    > startup.ncf file read as follows:
    >
    > ADPU320.HAM SLOT=1
    >
    > The only difference between startup.ncf of these 2 servers is:
    > The one which recognise the card in slot 1 has a statement to load
    > nwtape.cdm and the one which does not recognise the card in slot 1 and
    > produce above error has no such statement to load nwtape.cdm
    >
    >
    > Any idea. What do I miss out?
    >
    the slot number might be influenced by a different bios configuration in
    both servers. this could lead to another slot numbering.
    please try to load the driver without as slot number, like:
    LOAD <path>ADPU320.HAM
    and it will ask for the slot number.

  • No Boot-Up with Adaptec SCSI Card

    Over the weekend I have built a new PC using an MSI  MS6758 875P NEO Motherboard with an MSI FX5600 TD256 Graphics Card.
    The CPU is an Intel 3.0 gig P4
    The system has 2Gb of 400DDR Memory, a Seagate SATA 150 160Gb Hard Drive and a Western Digital 20Gb ATA Hard Drive and an MRI Connexant Modem.
    The system also has a Sony 3.5 Floppy Drive, a Sony DVD Re-Writer and a TDK CD Re-Writer.
    The OS is Windows XP Professional.
    The system as configured above works fine, the problem starts when I attach my Adaptec AHA-2940U2W SCSI Card which has a Hewlett Packard HP C1533 DDS2 Tape Drive attached to it.
    When the card is attached the system goes through the Boot-Up procedure, it finds the Floppy Drive, the Hard Drives, the CD-Rom, and DVD Drive, it then finds the SCSI Card and the Tape Drive, then the SATA Controller and then the Boot-up hangs.  If I remove the SCSI Card it Boots up fine.
    I have altered the IRQ address on the SCSI Card but this made no difference. The default address for the Card is IRQ 7.
    I have configured IRQ 7 on the Motherboard BIOS to ISE/EISA and this made no difference either.
    I have tried the SCSI Card in each of the PCI Slots and still will not Boot.
    I have replaced the Card and Tape Drive back into the system it came out of and it works fine.
    Has anybody had this experience?

    Quote
    Originally posted by valkyrie
    The problem is not MSI, it is Adaptec. I have an Adaptec 2940U2W as well. Same situation when I first installed it. To fix the problem you must go to adaptec.com and download the firmware update:
    http://www.adaptec.com/worldwide/support/driverdetail.html?sess=no&language=English+US&cat=/Product/AHA-2940U2W&filekey=2940u2w_bios_v2572.exe
    The firmware update must be done from MS-DOS (bootable floppy). The firmware update & utility will fit on a bootable floppy. You probably will need to apply the update using a different PC (not MSI Neo2). After you are finished, you will see the Adaptec BIOS shows a date of 2000. Once complete, you can boot from the Adaptec SCSI card and there is no need to disable the SCSI BIOS. I have running (booted from) the machine I'm using to type this.
    Val
    Hi Val,
    Thank you for that, I will carry that out and let you know what happens.
    Regards
    Danny.

  • Adaptec SCSI Drivers (29160) Availability for Windows 7?

    Attempting to "clean" install Windows 7 on SCSI Hard Disks, via Adaptec 29160 controller.
    The install doesn't 'see' the SCSI controller.
    I'm assuming its a driver issue.
    The installation cannot proceed.
    Can the Vista Driver be used? Or do I need a Windows 7 specific SCSI driver?
    If the Vista SCSI driver can be used how does one use the Vista driver with a "Clean" install?
    Thanks in advance...
    Bill -

    If you check the Adaptec Knowledgebase
    http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=13250&p_created=1113325408&p_sid=1u1VcbCj&p_accessibility=0&p_redirect=&p_lva=11119&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PWRmbHQ6MSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTE2LDExNiZwX3Byb2RzPTAmcF9jYXRzPTAmcF9wdj0mcF9jdj0mcF9zZWFyY2hfdHlwZT1hbnN3ZXJzLnNlYXJjaF9ubCZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PXdpbmRvd3MgNw**&p_li=&p_topview=1
    you will find the list of supported parallel scsi cards is very short. I was running an AHA 2940U2W which has served very well for may years only to find no support under Windows 7 and no plans for support in the future, which seems to be the case for almost anything that isn't current. I tried the Vista driver, but that refused to install (Windows actually blocked it), so I have had to upgrade to the only card that supports standard 50pin SCSI2 and 68pin Ultra modes, the ASC29320A-R. Unfortunately, this may be the route you have to take to get things working, but be wary. I have a couple of old CD-ROM drives including a quad speed Toshiba tray loader that I find can read damaged discs that modern fast drives reject. Unfortunately, these old drives are not supported by Windows 7 and cause the SCSI bus to keep resetting virtually stalling the machine when disc access is required. Disabling the drives in device manager helps most of the time, but now and again the bus will go into the reset loop and the only way out is to reboot. So, I'm going am having to replace them with something more modern and put together a second machine using the old hardware for recovering damaged discs. I am deeply unimpressed with the hardware support in modern versions of Windows. Right up to XP virtually any hardware could be used. Now it seems it has to be the most recent or it won't work.

  • Ultra 60 SCSI question

    We have an Ultra 60 running Solaris 8 but we need a LVD capable card. I've gotten my hands on an Adaptec 29160N but it doesn't show up in the "probe-scsi-all" output.
    I guess I'm asking if its compatable at all and if it is what do I have to do to make it work?
    Thanks for any help
    Chris

    If the peripheral must be connected to a LVD card, then the
    375-3057 (X6758a) adapter is qualified for that systemboard.
    Here's the link in the SSH for the E220R system's SCSI cards:
    http://sunsolve.sun.com/handbook_pub/Systems/E220R/components.html#SCSI
    The U-60, the E220R, and the Netra 112x systems all use the same systemboard.
    Adaptec products and Sun SPARC systems just don't function well, together.
    Adaptec doesn't feel there's enough market out there, to include compatibility in their HBA's.

  • Adaptec SCSI controller on Virtual XP mode

    I am trying to get my SCSI HP ScanJet 3C/4C scanners to work on my PC.  I just installed Win 7 64 bits Ultimate with the Virtual PC-XP mode   I cannot get the driver to catch the SCSI controller as it is suposed to be "embedded" in Windows
    XP (according to Adaptec) and thus cannot get separate drivers from Adaptec.  It is an Adaptec AHA-2910C card.
    It shows the card in the hardware manager of Win 7 but has no drivers for it.  If I could at least get the XP mode to see it and install the driver , then I would be in good shape.  Any help would be appreciated.

    Sorry, that's just not possible, XP Mode running in Windows VPC cannot
    see the real hardware of the PC. only virtual devices WVPC provides,
    and pass through SCSI isn't one of the things provided.
    VMWare Workstation may provide what you want, but I'm not sure about
    any of the other VM solutions.
    Bob Comer - Microsoft MVP Virtual Machine

  • Adaptec SCSI card

    I've had a back-up tape drive working (just fine) on a G4 400 running OS X 10.3.9 for a couple of years. I want to move this tape drive to a newer (old) computer, a G4 1.25 now running 10.4.11. I dug around and found the Adaptec driver I apparently installed to enable the SCSI card 2906 on the G4 400. On the newer computer with the newer OS, though, I'm getting kernel attacks.
    I searched the Adaptec site for a newer driver, and there are none. In fact, they indicate "the version 1.1 driver is embedded in Mac OS X 10.2 and later, there is no need to download and install this driver if you are running Mac OS X 10.2 or later."
    I guess my question is, does anyone know if this driver is still embedded in Mac OS 10.4? If so, do you know what it's called - where it's located, so I can make sure it's there. (I actually installed the driver I had from several years ago, so if it wasn't there, it should have been then, but I still had kernel attacks.) Any other ideas on this problem?
    Thanks.
    Ginny

    Thanks, all, for the suggestions. I'm totally flustered with this issue. Been working on it most of the day! According to what BDAqua found, I see that this card may not work with OS 10.4, but kind of hard to believe it wouldn't. (Hope that's just a post that was only current up through the 10.3 era.) The "Ask Adaptec" site Michael found does include 10.4.
    I did find that 1.3 driver, and it is designed for Classic - not OS X (as is the SCSI probe). Fact is, this computer also runs an old (but still good) scanner booted in Classic mode, and everything is working great from that side. (Only use the scanner 4-5 times a year - hate to buy a new one when it still works.)
    I do seem to have all the possible, appropriate extensions in OS X. In fact, I dumped all and reinstalled them through Pacifist. Still have the problem. This tape drive is accessed only through Retrospect, and I'm wondering if something in Retrospect is causing the problem instead of the SCSI connection, but I thought kernel panics were generally hardware related. When I access the drive in Retrospect (like to configure it), even if I don't "use" it, I get a kernel panic when I close Retrospect. If I try to restore a file, as it searches a tape, I get a kernel panic.
    I examined the kernel panic log. Obviously, it doesn't mean much, but the text on every crash ends with:
    com.apple.iokit.SCSITaskUserClienp
    or
    com.apple.iokit.SCSITaskUserClient(1.4.9) . . . and some numbers/letters.
    I also see "SCSI" in a couple of other places in the report, so I do believe it's a SCSI problem, but I'm baffled.
    I might reinstall Retrospect and see if it helps, but I'm not optimistic that it will. Guess I might also try installing 10.3 in a partition that already exists on the drive, boot in 10.3 and see if the SCSI connection starts working. (If it would, guess I'd have to reformat the drive, reinstall everything and stop with the 10.3 install.)
    Any other ideas?
    Thanks,
    Ginny

  • Need a converter between SAS/SA-SCSI and Ultra-160 SCSI

    The Netra-210 machines seem to have the small hard drives with Serial Attached SCSI. The hard drive cloning machine uses the older style SCSI connectors and we have a number of hard drives that are Ultra-160 drives.
    I have not been lucky with my search and have not found a converter so that I can clone the installation from the new SAS drive to the older SCSI drives.
    Does any one have suggestions or has anyone found a converter to be used with such cloning machines?
    thanks!

    Trying to work with the 'dd' command at present. Maybe that will work, but I don't think it can copy the partitions over. If I create Ultra-160 drives with just the partitions in place, "dd" should be sufficient to copy the files/directories over..

  • 845 Ultra + Adaptec Raid 2400a

    [ May be a bit off topic sorry ]
    Hi,
    Motherboard : MSI 845 Ultra Ver 1
    Bios Version : 1.50
    Graphic controler : Generic PCI VGA
    Ram : 2x 256 DDR
    Raid controler : Adaptec 2400a
    ( at the end there should be 2 of those raid controlers with 6 HD connected to it : 2 x 40 Gb IBM ICL series and 4 x 120 Gb Maxtor D540 series )
    I'm having problems entering my raid card bios using this motherboard.
    I type my " ctrl + A " to enter the bios, and the only thing I get is 2 lines with a random text in different color on the top of my screen. I'm able to Ctrl+alt+del to reboot, and able to boot without trying to enter the raid card bios.
    I changed my raid card, and my disks connected to it. I changed the PCI slot.
    Anyone have a Clue for that ? Anyone was able to use that kind of controler on that MB ?
    Regards ...

    The 845 Ultra has bios versions from 3.0 to 3.4 so you either wrote the wrong version or the wrong board.

  • Adaptec SCSI Card Solution (worked for me anyway)

    I know there has been a lot work put into this issue, and even this solution mentioned once before but since it completely worked for me, i figured id post because its inevitable that someone else will ask it soon.
    Like everyone else, once upgrading to Tiger, my Adaptec 2930CU card (supposedly the biggest offender of them all) would kick in kernel panics almost every time I tried to write a DVD-5 DLT and would never get through a DVD-9.
    I took someones advice and deleted the extension for this card in my System/Library/Extensions folder. This completely eradicated the problem and it works as good the old days. I have another machine with a different Adaptec card, not sure which, did the same thing and that solved it.
    Hopefully this will be beneficial to somebody out there as im sure anyone who didn't spend a million dollars on a card a while back probably bought Adaptec

    Thanks for taking the time to come back and let us know - it is valuable to see when a fix has worked for someone.

  • Ultra 320 SCSI card with Snow Leopard Server?

    First off, sorry if this is the wrong place for a thread on Snow Leopard server.
    I have an older Intel Xserve (xserve1,1) with the Apple-branded Ultra320 SCSI PCI-X card. This isn't a third-party card, this is the one from the Apple Store.
    So, are these confirmed to continue to work under 10.6? My server runs 10.4 (I'm skipping 10.5).
    Thanks!

    Hi
    A Beta version is exactly just that. No-one apart from Apple knows for certain what the release version will support. Installing a Beta version of anything on a Production Server would not be a good idea in my view. Although one could risk it if a fully working bootable clone of the current Server was done first prior to installing the Beta (or an update for that matter). Perhaps it's just my cautious nature but I personally would not risk it.
    I've been part of the AppleSeed program for 10.6 Server and Client from the outset and am testing both on my laptop.
    Tony

  • Xserve G5 with Apple Supplied LSI Logic Ultra 320 SCSI Card

    The Xserve G5 has been running 10.4.10 and 10.4.11. It also has the Apple supplied FibreChannel card installed.
    I have tried installing this card into the Xserve and so far have been unable to get it to work, there are two symptoms...
    1) The card is visible in System Profiler, no devices connected to it show. I've tried various combinations of termination, no change.
    2) After a random period of time the Mac goes to 100% processor utilization on both processors and stays there. The Mac can then no longer be accessed remotely and stays that way. This occurs whether or not any cabling is connected.
    This card is the one that Apple lists as a part for the Xserve G5 in GSX. However I've seen a few sites on the web stating that it doesn't really work and you should use a an ATTO ExpressPCI UL4D. Is this the case? Other sites have also said that the LSI card doesn't work with Retrospect, which is a concern to me as that is my objective.
    Any hints would be much appreciated!
    Peter

    Hi Peter
    I don't know about the others but all I've used from the G5 onwards is the range of cards supplied by ATTO. It seems clear from the symptoms you describe that it just does not work and may cause a major problem to your XServe if you persist in trying to use it.
    You may as well take it out and get yourself a relevant ATTO card and never mind too much about what gsx says, it has been 'wrong' before in the past.
    Tony

  • Windows 7 fails to recognize Adaptec 39320 SCSI controller card.

    I recently installed a new Motherboard in an existing system and installed Windows 7 Pro on it instead of Windows XP Pro that I had on the previous motherboard.  The system  included  a Adaptec 39390D SCSI card
    and 4 ultra320 SCSI drives.  I downloaded the drivers for this card from Adaptec, there site says the driver is compatible with Windows 7.  I then went to Device Manager and clicked on, clicked on Storage Controllers, Adaptec 39320-based Ultra 320
    SCSI, and clicked update controller and received driver installed message. 
    Device Manager now shows  "This device is working properly.", but
     the drives do not show up in "Disk Management" were they showed up in previous installations on Windows XP Pro, for Importing.
      The BIOS display during startup shows the controller and the connected drives. 
    This seems to be problem with Windows 7 Professional.  If I made a mistake in installing the Adaptec driver would someone please tell me how to correct the problem.

    Typically, and I could be wrong about this, you want to also update other drivers such as the Chipset (which the SCSI card may be plugged into as on onboard device) which will also be needed in order for the SCSI drives to be seen.
    Did you install Windows 7 using installation media or did you use a deployment mechanism like Microsoft Deployment Toolkit to deploy the OS? If you used MDT, you can pre-package the device drivers (Adaptec drivers included) into the deployment to allow the
    drivers to be installed during the initial install of the OS and not in the OS. This method is recommended to be used for plug-and-play driver installation. 

  • Ultra SCSI devices on MBP?

    IS there a way to hook up external UltraWide SCSI VXA-320 tape drive to MacBookPro?
    Either as ExpressCard? or some kind of an adapter?
    USB?
    Firewire?
    Derek

    The speed of SCSI adapters is very slow.
    I think you're confusing speeds.
    Ignoring the issue of how to interface a SCSI drive to a MBP, anything faster than Ultra 2 Wide SCSI has throughput at 80 MB/s or better - that's megabytes per second, not the 400 megabits per second of FireWire 400. (Remember, MB/s = (Mb/s / 8), so FireWire 400 delivers top throughput of just 50 MB/s.)
    Ultra 3 SCSI or better has a throughput of 160 megabytes per second, faster than even FireWire 800's 800 megabits per second (which would be only 100 MB/s.)
    This is why systems using Fiber Channel are so popular in server farms, as it delivers data at speeds of up to 400 MB/s, or 4x faster than FW800.
    This is also why eSATA is starting to gain traction as a way to attach an external drive, as it communicates with drives at a maximum speed of 2400 Mb/s, or some 3x faster than FW800 (but still slower than Fiber Channel or Ultra SCSI 320.)
    There's a really nice chart outlining this here.
    Just keeping the discussion honest.

Maybe you are looking for