BillyT Posted February 8, 2008 Report Share Posted February 8, 2008 I wanted to ask if there is a diagnostic tool for Mac that would run tests on my system. I would like to run diagnostics on my Mac G4 OS X 10.3.9, SCSI bus, Certance LTO2 drive and Retrospect 6.0.204. I have been getting the dreaded "206 dirty heads, bad media" error with my LTO2 machine and although nothing has changed hardware wise I'm wondering if the problem lies somewhere in the chain and not the machine itself. I have already sent the LTO2 to be professionally cleaned/fixed and it tested fine, but it still won't let me finish a backup (doesn't even finish copying, never get's to verify stage before error) and even get's stuck on trying to verify a previously written tape. Any help will be appreciated. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 8, 2008 Report Share Posted February 8, 2008 Quote: I wanted to ask if there is a diagnostic tool for Mac that would run tests on my system. A good first step would probably be to describe the system hardware, in detail. Makes, models, firmware, drivers, etc etc etc (etc). Dave. Link to comment Share on other sites More sharing options...
BillyT Posted February 8, 2008 Author Report Share Posted February 8, 2008 This is copy and pasting from System Profiler, let me know if you need something else specifically. As of now Retrospect won't even scan the LTO2 to get drive info. I was hoping for some software to verify the SCSI connection and setup. It has worked for several years with this setup and only recently gave the errors. Machine Model: Power Mac G4 CPU Type: PowerPC G4 (3.2) Number Of CPUs: 2 CPU Speed: 1.25 GHz L2 Cache (per CPU): 256 KB L3 Cache (per CPU): 2 MB Memory: 1 GB Bus Speed: 167 MHz Boot ROM Version: 4.4.8f2 ATTO,ExpressPCIProUL3D: Type: scsi-2 Bus: PCI Slot: SLOT-3 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x0007 ROM Revision: 1.6.4f1 Revision ID: 0x0001 ATTO,ExpressPCIProUL3D: Type: scsi-2 Bus: PCI Slot: SLOT-5 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x8007 ROM Revision: 1.6.6f0 Revision ID: 0x0001 CERTANCE ULTRIUM 2: Manufacturer: CERTANCE Model: ULTRIUM 2 Revision: 1581 SCSI LUN: 0 Retrospect6.0: Version: 6.0.204 Last Modified: 1/24/05 11:23 AM Location: /Applications/Retrospect 6.0/Retrospect6.0 ATTOExpressPCIPlus: Version: 2.0.4 Last Modified: 9/18/03 5:08 PM Get Info String: ATTOExpressPCI version 2.0.4f1, Copyright 2001-2003 ATTO Technology, Inc. Location: /System/Library/Extensions/ATTOExpressPCIPlus.kext kext Version: 2.0.4 Loaded: Yes Valid: Yes Authentic: Yes Dependencies: Satisfied Link to comment Share on other sites More sharing options...
rhwalker Posted February 8, 2008 Report Share Posted February 8, 2008 Is there a reason that you are running a version of Retrospect that is almost four years old? The current version is 6.1.138, and the free update is here: http://www.emcinsignia.com/supportupdates/updates/#UPDATETYPE8 What version of Retrospect Driver Update ("RDU") are you running? There are bug fixes in the later RDUs. The complete version history and links to downloads are here: http://kb.dantz.com/article.asp?article=7886&p=2 It appears that you have five SCSI busses, correct? (two on each ATTO UL3D, one on the ATTO Express PCI Plus). I'm concerned that Apple System Profiler isn't showing the two busses for each of the UL3D cards, and that it isn't showing the devices on each of the busses. You should see something like the following: Code: PCI Cards: LSI,523: Name: LSILogic,raid Type: scsi-2 Bus: PCI Slot: SLOT-2 Vendor ID: 0x1000 Device ID: 0x1960 Subsystem Vendor ID: 0x1000 Subsystem ID: 0x4523 Revision ID: 0x0001 ATTO ExpressPCI UL4D: Name: ATTO,ExpressPCIProUL4D Type: scsi-2 Bus: PCI Slot: SLOT-3 Vendor ID: 0x117c Device ID: 0x0030 Subsystem Vendor ID: 0x117c Subsystem ID: 0x8013 ROM Revision: 1.5.2 Revision ID: 0x0008 ATTO ExpressPCI UL4D: Name: ATTO,ExpressPCIProUL4D Type: scsi-2 Bus: PCI Slot: SLOT-3 Vendor ID: 0x117c Device ID: 0x0030 Subsystem Vendor ID: 0x117c Subsystem ID: 0x8013 ROM Revision: 1.5.2 Revision ID: 0x0008 bcom5704: Type: network Bus: PCI Slot: SLOT-4 Vendor ID: 0x14e4 Device ID: 0x1648 Subsystem Vendor ID: 0x106b Subsystem ID: 0x005a Revision ID: 0x0003 bcom5704: Type: network Bus: PCI Slot: SLOT-4 Vendor ID: 0x14e4 Device ID: 0x1648 Subsystem Vendor ID: 0x106b Subsystem ID: 0x005a Revision ID: 0x0003 Parallel SCSI: SCSI Parallel Domain 0: Initiator Identifier: 7 SCSI Target Device @ 16: Manufacturer: MEGARAID Model: Logical Drive 0 Revision: SCSI Target Identifier: 16 SCSI Device Features: Wide, Sync SCSI Initiator/Target Features: Wide, Sync Peripheral Device Type: 0 SCSI Logical Unit @ 0: Capacity: 50 GB Manufacturer: MEGARAID Model: Logical Drive 0 Revision: Removable Media: Yes Detachable Drive: No BSD Name: disk1 OS9 Drivers: No SCSI Logical Unit Identifier: 0 S.M.A.R.T. status: Not Supported SCSI Target Device @ 17: Manufacturer: MEGARAID Model: Logical Drive 1 Revision: SCSI Target Identifier: 17 SCSI Device Features: Wide, Sync SCSI Initiator/Target Features: Wide, Sync Peripheral Device Type: 0 SCSI Logical Unit @ 0: Capacity: 417.42 GB Manufacturer: MEGARAID Model: Logical Drive 1 Revision: Removable Media: Yes Detachable Drive: No BSD Name: disk3 OS9 Drivers: No SCSI Logical Unit Identifier: 0 S.M.A.R.T. status: Not Supported Volumes: disk3s3: Capacity: 417.29 GB Available: 277.69 GB Writable: Yes File System: Journaled HFS+ SCSI Target Device @ 63: Manufacturer: MEGARAID Model: MEGARAIDDUMMYDEV Revision: 1.00 SCSI Target Identifier: 63 SCSI Device Features: Wide, Sync SCSI Initiator/Target Features: Wide, Sync Peripheral Device Type: 31 SCSI Logical Unit @ 0: Manufacturer: MEGARAID Model: MEGARAIDDUMMYDEV Revision: 1.00 SCSI Logical Unit Identifier: 0 SCSI Parallel Domain 1: Initiator Identifier: 7 SCSI Target Device @ 3: Manufacturer: SEAGATE Model: ST373405LW Revision: 0003 SCSI Target Identifier: 3 SCSI Device Features: Wide, Sync, DT SCSI Initiator/Target Features: Wide, Sync, DT Peripheral Device Type: 0 SCSI Logical Unit @ 0: Capacity: 68.37 GB Manufacturer: SEAGATE Model: ST373405LW Revision: 0003 Removable Media: Yes Detachable Drive: No BSD Name: disk0 OS9 Drivers: No SCSI Logical Unit Identifier: 0 S.M.A.R.T. status: Not Supported SCSI Parallel Domain 2: Initiator Identifier: 7 SCSI Target Device @ 0: Manufacturer: EXABYTE Model: VXA 1x10 1U Revision: A110 SCSI Target Identifier: 0 SCSI Device Features: Wide, Sync SCSI Initiator/Target Features: Wide, Sync Peripheral Device Type: 8 SCSI Logical Unit @ 0: Manufacturer: EXABYTE Model: VXA 1x10 1U Revision: A110 SCSI Logical Unit Identifier: 0 SCSI Target Device @ 1: Manufacturer: EXABYTE Model: VXA-2 Revision: 2122 SCSI Target Identifier: 1 SCSI Device Features: Wide, Sync SCSI Initiator/Target Features: Wide, Sync Peripheral Device Type: 1 SCSI Logical Unit @ 0: Manufacturer: EXABYTE Model: VXA-2 Revision: 2122 SCSI Logical Unit Identifier: 0 Where is the LTO2? When you sent it for cleaning and then reinstalled it, did you put it back on the same SCSI bus? Have you tried it on a different SCSI bus? What does ATTO's configuration tool show? That should let you poke about on the SCSI busses. Is there a reason that your two ATTO UL3D cards have different firmware revisions? What ATTO drivers/versions do you have installed as kexts? Doesn't Certance have diagnostics? Most vendors do. Russ Link to comment Share on other sites More sharing options...
BillyT Posted February 11, 2008 Author Report Share Posted February 11, 2008 Thanks for the reply, I updated the firmware so both cards were the latest, and installed the latest Driver Update. Still have the -206 problem. Certance was bought by Quantum and doesn't have a diagnostic program for Mac as far as I can tell. I copied and pasted from within System Profiler so I probably just didn't copy everything, that's why you don't see all the busses. This system has been setup for several years and I've been using it for the last few, but this is the first problems we have had like this. I tried switching out SCSI cards, cables, busses, but still got the -206 error. I shipped the drive back to the repair shop, hopefully they will find the problem. Link to comment Share on other sites More sharing options...
rhwalker Posted February 11, 2008 Report Share Posted February 11, 2008 To ask again (but it doesn't matter because you have sent the drive back): Quote: When you sent it for cleaning and then reinstalled it, did you put it back on the same SCSI bus? Have you tried it on a different SCSI bus? russ Link to comment Share on other sites More sharing options...
BillyT Posted February 29, 2008 Author Report Share Posted February 29, 2008 Sorry it took a while to get back. I got the drive back and used one of the tapes the repair company sent to see if it was my media and it went through till almost the end of comparing and gave the 206 error. I then changed the SCSI ID and started a new back up with new drive and new media. It gave me the 206 error before it could finish copying. Sigh. Link to comment Share on other sites More sharing options...
rhwalker Posted March 1, 2008 Report Share Posted March 1, 2008 Sorry, Billy, I can't help you or suggest something else to try if you aren't going to answer my questions. See my posts above. Link to comment Share on other sites More sharing options...
BillyT Posted March 1, 2008 Author Report Share Posted March 1, 2008 I thought I did answer your question when I said I changed the SCSI ID. I did one backup with the same ID and it went almost to the end of comparing and then changed the ID and it went about 1/3 of the way into coping. Is there a question I'm missing or misinterpreting? Link to comment Share on other sites More sharing options...
CallMeDave Posted March 1, 2008 Report Share Posted March 1, 2008 Is there a question I'm missing or misinterpreting? There are multiple questions Russ asked, which are still right there in his post above. For example, he asked about RDU version loading with Retrospect. And his question about the SCSI bus is not answered by a description of the SCSI ID being used (or changed). Dave Link to comment Share on other sites More sharing options...
BillyT Posted March 1, 2008 Author Report Share Posted March 1, 2008 Is there a reason that you are running a version of Retrospect that is almost four years old? [color:blue]We try to stay at at the same version for a particluar set, in this case LTO2 for as long as we can for consistency.[/color] What version of Retrospect Driver Update ("RDU") are you running? [color:blue]I updated it to Driver Update Version 6.6.101[/color] It appears that you have five SCSI busses, correct? (two on each ATTO UL3D, one on the ATTO Express PCI Plus). [color:blue]I think that's just the way I copied/pasted the system profiler. Here is the PCI/AGP Card info. ATTO ExpressPCI UL3D: Name: ATTO,ExpressPCIProUL3D Type: scsi-2 Bus: PCI Slot: SLOT-3 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x0007 ROM Revision: 1.6.6f0 Revision ID: 0x0001 ATTO ExpressPCI UL3D: Name: ATTO,ExpressPCIProUL3D Type: scsi-2 Bus: PCI Slot: SLOT-3 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x0007 ROM Revision: 1.6.6f0 Revision ID: 0x0001 ATTO ExpressPCI UL3D: Name: ATTO,ExpressPCIProUL3D Type: scsi-2 Bus: PCI Slot: SLOT-5 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x8007 ROM Revision: 1.6.6f0 Revision ID: 0x0001 ATTO ExpressPCI UL3D: Name: ATTO,ExpressPCIProUL3D Type: scsi-2 Bus: PCI Slot: SLOT-5 Vendor ID: 0x1000 Device ID: 0x0020 Subsystem Vendor ID: 0x117c Subsystem ID: 0x8007 ROM Revision: 1.6.6f0 Revision ID: 0x0001 ATY,RV250: Type: display Bus: AGP Slot: SLOT-1 VRAM (Total): 64 MB Vendor: ATI (0x1002) Device ID: 0x4966 Revision ID: 0x0001 ROM Revision: 113-99702-127 Display: Type: display Display Type: CRT VRAM (In Use): 64 MB Resolution: 1024 x 768 @ 75 Hz Depth: 32-bit Color Main Display: Yes Mirror: Off Online: Yes ATY,Pheonix_B: Status: No display connected Display: Type: display Display Type: CRT VRAM (In Use): 64 MB Resolution: 1024 x 768 @ 75 Hz Depth: 32-bit Color Main Display: Yes Mirror: Off Online: Yes ATY,Pheonix_B: Status: No display connected [/color] And the SCSI info. [color:blue]SCSI Bus: SCSI Bus: QUANTUM SDLT320: Manufacturer: QUANTUM Model: SDLT320 Revision: 3737 SCSI LUN: 0 QUANTUM SDLT320: Manufacturer: QUANTUM Model: SDLT320 Revision: 3737 SCSI LUN: 0 SCSI Bus: CERTANCE ULTRIUM 2: Manufacturer: CERTANCE Model: ULTRIUM 2 Revision: 1581 SCSI LUN: 0 CERTANCE ULTRIUM 2: Manufacturer: CERTANCE Model: ULTRIUM 2 Revision: 1581 SCSI LUN: 0 SCSI Bus: [/color] I'm concerned that Apple System Profiler isn't showing the two busses for each of the UL3D cards, and that it isn't showing the devices on each of the busses. You should see something like the following: Code: [color:blue]I took out this info, no need to duplicate in the reply.[/color] Where is the LTO2? When you sent it for cleaning and then reinstalled it, did you put it back on the same SCSI bus? Have you tried it on a different SCSI bus? [color:blue]I have the LTO2 now. I admit I don't know SCSI terminology that well. I changed the SCSI ID on the LTO2. I don't see where to change the bus in the ATTO Configuration Tool. [/color] What does ATTO's configuration tool show? That should let you poke about on the SCSI busses. [color:blue]It shows the LTO2 as Bus: 2 Target: 4 LUN: 0. I'm not sure how to change the bus on the card if that's what you are asking.[/color] Is there a reason that your two ATTO UL3D cards have different firmware revisions? [color:blue]They are now updated and the same firmware version 1.6.6f0.[/color] What ATTO drivers/versions do you have installed as kexts? [color:blue]I'm not sure what you are asking here. In the "Basic Info" on the ATTO configuration tool it says driver version 3.2.1. Not sure if this answers your question.[/color] Doesn't Certance have diagnostics? Most vendors do. [color:blue]That was the first question in my post. I can't find any diagnostic software for the Mac anywhere. They have it for Windows and Linux but not Mac.[/color] Link to comment Share on other sites More sharing options...
rhwalker Posted March 3, 2008 Report Share Posted March 3, 2008 Is there a reason that you are running a version of Retrospect that is almost four years old? We try to stay at at the same version for a particluar set, in this case LTO2 for as long as we can for consistency. Ok, then you are trying to stay with unfixed bugs, too. Retrospect releases for the Mac have rarely added features in the last four or five years; they are mainly for bug fixes and improved compatibility with the OS and with devices (such as SCSI and tape). You deserve what you get on this point. What version of Retrospect Driver Update ("RDU") are you running? I updated it to Driver Update Version 6.6.101 See above about staying with old bugs. I changed the SCSI ID on the LTO2. I don't see where to change the bus in the ATTO Configuration Tool. You plug the device onto a different SCSI bus. Link to comment Share on other sites More sharing options...
BillyT Posted March 6, 2008 Author Report Share Posted March 6, 2008 So if the bus is just a different plug on the SCSI card, then yes I (as I stated above) have tried a different bus as well as a different card. Link to comment Share on other sites More sharing options...
rhwalker Posted March 6, 2008 Report Share Posted March 6, 2008 Ok, that rules out the SCSI interface on the card. Because the cards now have the same firmware, it would seem to point to: (1) the drive (incompatibility with Retrospect's old RDU that you have installed); (2) the ATTO driver (.kext) - no information has ever been provided on this point despite multiple requests - the last/current ATTO driver for your card is version 3.21. (3) the cables; or (4) the firmware. Last/current firmware for the UL3D appears to be dated 7/15/2003, in a flash bundle dated 07/21/2006. Hard to get more data until you update to a current version of Retrospect that might have fixed the bugs, and until you report the ATTO driver version. Russ Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.