V240 scsi problems w/dlt4000

Hi
I have a legacy dlt4000 drive inside a library. When I connect the drive to any of my v240/v210/T1 hosts, SCSI bus fails (orange service light turns on).
dlt is SCSI2-SE, multiple cables and terminators was used, I tried it at Solaris 9, Solaris 10 and Solaris 11
SCSI error comes also with drive disconnected from power and removed from library
Drive is working ok (it comes from technical service and all test was ok), it's a Quantum DLT4000, model TH5XA, and it's supposed to work with Solaris. I change all modifiable jumpers without success.
All my SCSI hba are SE/LVD (dual)
Configuring /kernel/drv/glm.conf with
scsi-options=0x78;
or
scsi-options=0x178;
gives the same problem.
messages are:
Apr 17 16:57:39 pampa scsi: [ID 107833 kern.warning] WARNING: /pci@1c,600000/scsi@2,1 (glm1):
Apr 17 16:57:39 pampa timeout on bus reset interrupt
Apr 17 16:57:39 pampa genunix: [ID 408789 kern.warning] WARNING: glm1: fault detected in device; service unavailable
Apr 17 16:57:39 pampa genunix: [ID 451854 kern.warning] WARNING: glm1: timeout on bus reset interrupt
Apr 17 16:57:43 pampa rmclomv: [ID 218314 kern.error] FAULT_SENSOR @ MB.FF_SCSI has FAILED.
Apr 17 16:57:52 pampa pcisch: [ID 569400 kern.warning] WARNING: pcisch2: ino 0x28 blocked
Apr 17 16:57:52 pampa pcisch: [ID 548919 kern.info] glm-1#0
Apr 17 16:57:52 pampa pcisch: [ID 100033 kern.info]
Apr 17 16:58:16 pampa rmclomv: [ID 218314 kern.error] FAULT_SENSOR @ MB.FF_SCSI has FAILED.
Apr 17 16:58:56 pampa last message repeated 1 time

What are the part numbers and where did you get the disks?

Similar Messages

IDE/SCSI Problems with Neo 4 Platinum/Sli

I am routinely getting Event 11 and Event 9 errors in my event viewer which are basically "The controller detected an error on device " then lists a controller and a harddrive. I never got errors like this on my old rig (an Asus A7Pro Motherboard) and I'm using many of the same components. I get controller errors on my Adaptec Card/HDD which is very odd since I'd imagine they were totally separate from the nVidia or Silicon Image SATA/IDE on the board.
New Rig:
MSI Neo4 Platinum/SLI
Athlon 64 3500+
Thermaltake K8 SilentOrb
1 GB (Dual Channel 512MB DDR) Kingson Hyper-X
1 BFG 6800GT OC (PCI-E) (with an Artic Cooling NVSilencer rev2)
Turtle Beach Santa Cruz (although I may change to the onboard 24bit SB Live)
Adaptec 29160 PCI Ultra 160 Controller
Belkin 54G Wireless Adapter
Pioneer SCSI II slot load DVD-ROM drive
Toshiba SCSI II CD-R/CD-RW drive
500+ Watts Vantec Stealth PSU (with good voltages on all rails)
74GB Western Digital Raptor (SATA connected to Slot 4 - nVidia SATA channel, no RAID)
80GB Western Digital 8MB RAM, Special Edition UDMA 4 IDE HDD
36GB Seagate Ultra2 Cheetah
Old Rig had the WD IDE drive, the SCSI card and dvd/cd drives, the sound card, and the wireless card.
I originally had a 40GB IDE Maxtor drive (which I replaced with the Digital Raptor) but it had all sorts of event 11 and 9 errors and exhibited slow IDE performance and even created conflicts with the WD IDE Drive outside of windows. I had problems running the WD diagnostsics software (runs in DOS) when the Maxtor drive was set to primary master on either of the two IDE channels.
What I'm wondering is if there is a BIOS upgrade or Driver release or anything that fixes these problems for people. I'm using BIOS 3.1 (when I upgraded to Bios 3.4, my computer would BSOD in normal and safe modes, and I didn't feel like reinstalling Windows, so I downgraded back to 3.1) The nVidia IDE drivers (6.53) caused massive problems with my drives (event 11 and 9 and endless lockups with the IDE light remaining on, requiring cold boots) so I ditched them for the windows default drivers.
I'm curious if people have checked out their own event viewer (Control Panel->Administrative Tools->Event Viewer->System for all you non-power users) and checked out the errors listed there.
The only other stability problem sI've noticed is when playing Half Life 2 in 1280X1024 resolution (1024X768 didn't have the problem) would cause complete crash of the machine. Monitor would lose signal and a cold boot was required... reset button didn't fix the problem. I figured this might be a cooling issue so I checked temps and they were fine. Then I figured it may be a power problem so I upgraded to the Vantec Stealth PSU (from my Antec 380W SilentPower) I haven't tested HL2 extensively since, so I'm not sure if this problem has gone away. The other problem occurs when trying to rip a CD in iTunes with "cd error checking on" System totally stalls out and a cold boot is required to get the SCSI happy again. If I rip using error checking off, things seem to work, however I get a problem sometimes where a track will suddenly squeel and crack in the middle and then the remainder of the song will be the first track on the album. The next track in the sequence will have a half second blip of the previous track on it, essentially meaning that two tracks are "broken rips" Ripping in AudioGrabber with ASPI doesn't seem to exhibit these problems.
Any similar experiences or sollutions/advice would be greatly appreciated.

It's been fixed for the Neo2. I am using a modded version called 1C3 EasyBios [rev.2]. I think it is based on the latest version or new beta of the official 1.B. Read all about it:
https://forum-en.msi.com/index.php?topic=88384.0
https://forum-en.msi.com/index.php?topic=59711.msg622296#msg622296

Crazy tiger, classic and 2906 scsi problem

Sorry, long post to follow.
A list seems the best way to describe this problem
1) I found an old scsi drive that had os 9.22 on it and wanted to run it in classic on os 10.4.11
2) I installed the old adaptec 2906 card in a G4 Digital Audio connected the drive and booted into tiger.
3) The harddrive was visible in the finder and under the "classic" preferences.
4) I started classic off of the scsi drive and everything was fine. I opened a couple of programs and all was good.
5) I rebooted for some reason (without stopping classic).
6) Tiger would not reboot. Nothing I tried would boot the computer. I would get the grey bootup screen with the apple but the spinning wheel would not show up. I waited up to 30 minutes at one point for something to happen.
7) I removed the drive (unplugged it from power and the bus) and still no boot.
8) I removed the scsi card and still no boot.
9) restarted from CD and repaired the drive.
10) Yeah, Tiger boots up.
11) I think all is fixed and reconnect everything.
12) No boot again!!!
What could have happened after that first bootup? The drive seems to fire up as it did the first time (it is loud and hard to miss).
Could the scsi card be dead after the one reboot?
If I added an extension to the os 9 drive would that have an effect on Tiger booting (I find this unlikely but thought i would ask)?
One other thing and this may be Important. I also have an IDE controller card Acard AEC-62800M installed which seems to show up as a scsi card.
Any Ideas would be great.

I also have an IDE controller card Acard AEC-62800M installed which seems to show up as a scsi card.
I've seen that with several PCI/IDE cards and would consider it normal.
Have you tried PRAM/NVRAM/PMU resets...
Does it boot into Open Firmware with CMDOption+of ?
http://docs.info.apple.com/article.html?artnum=42642
Have you done a PRAM reset...
http://docs.info.apple.com/article.html?artnum=2238
Tried resetting the PMU?
http://docs.info.apple.com/article.html?artnum=14449

Oracle VM - scsi problem

Hello,
We have just installed Oracle VM from the 2.1.1 iso image and the install went fine but now when we try to ftp files to the server we get serious I/O errors starting with "SCSI offset overrun detected resetting bus". After this we get a bunch of dump card state start end ends and the server becomes unusable.
This is running on a dell poweredge sc420 server with an Adaptec (Dell OEM) 39320 Ultra 320 controller - and two seagate ST373307CW hard drives (not raided). Currently we are only using the first drive of the pair.
Is it possible to run the OracleVM on this machine?
Thanks,
Adam

Found out our wonderful network admins put a firewall between each rack without telling us. Nice. Problem solved.

SCSI problem

I am trying to install Solaris 8 x86 edition (10/01) on a single processor board (VMEbus SBC) using the Intel 815e chipset. It has an onboard LSILogic U160 SCSI controller and an integrated Intel 82559 Fast Ethernet LAN controller. It currently has PIII 700 CPU and 256 MB PC133 SDRAM.
The problem I have appears to be the driver for the U160 controller. Booting with the 10/01 DCA diskette or CD-rom (1/2) proceeds normally, including the scan for devices. At this point I press F4 to indicate supplementary drivers are to be provided, then I mount the SYMBIOS ITU diskette for the Solaris 8 driver, and it appears to be read properly. I then proceed with the device scan, and the LSILogic 53C1010 SCSI controller is detected as it should. Then, after choosing "Solaris Interactive" for the type of install, the kernel load (apparently) stops with a cursor at the top of the blank gray page (it starts rotating at this point if you forego the driver installation, as I have done several times, with successful installations).

Do you need the SCSI controller for any part of the installation?
You can always add the drivers for the SCSI controller after installation is complete using the pkgadd command.
If the controller gets in the way during installation try disabling it under your BIOS setup.
Hope this helps and revert back with other questions.
Allen
Sun Developer Technical Support

MS-9121 E7505 Master-LS SCSI problem

hi
I've got a MS-9121 mainboard with a SCSI 320MB controller onboard.
I bought me now a Maxtor Atlas 10k IV 146GB and connected it on the original MSI SCSI cabel which was delivered with the mainboard.
The problem is now, the controller recognizes and syncronizes the drive only with 40MB/s instead of the full 160MB/s or even 320MB/s.
The cable is terminated on the last plug with the original terminator.
As the drive has an SCA bus, I've attached to it a SCA --> LVD adapter.
I've also tried a new IBM 146GB drive which should provide 160MB/s or even 320MB/s, but even this drive is only synced with 40MB/s.
I also have an older 36GB IBM SCSI drive, which is correctly synced with 160MB/s, as long as I've none of the above mentioned drives connected.
I haven't yet replaced the cable, as I don't have a spare one.
I've even upgraded the firmware of the Maxtor drive, in the hope that the problem will be solved, but no. (that was before I had the other 146B IBM SCSI drive)
I'm suspecting now the firmware of the controller, which currently has release 5.02.00. Bios release of the motherboard is version 1.1.
I hope I get here some answers, as I never got one from the emailsupport :(
thanks for help,
pato

Hi Pato,
OK, you have 80-pin drive and converting to 68 pin.
I would suggest you 68 to 68..........you will gain to 160 status.......
If you really wish to go FULL 320 you will have to buy a 80 pin 320 controller card........
I am 99% sure this is reason for SLOW down.......
It is like: (For other readers) Putting a 40pin IDE cable on ATA100 hard drive......
Del

Sparc Station 10 external SCSI Problems

Hi folks,
i have installed Solaris 8 (10/01) on a Sparc Station 10.
All worked fine, except, that only 2 drives from the external SCSI-Array (4 drives ) are recognized by the system.
The format-command hangs for more than 5 Minutes after starting it and then displays ALL drives, but 2 of the
ext. are shown as unknown drivetype.
In the diag probe-scsi-all, all drives are showed correctly.
The SCSI configuration: 3 SCSI Controllers .
2 internal HD's (1.0 GB) and (i hope for the future) 4
external. CDROM is attach one the external connector
from the internal drivecontroller.
Any ideas... ?
Thx in adavance.
Peter
[email protected]

hi,
usually when you see 'drive type unknown' it means that the system does not recognise what type of disk it is. you could try selecting the disk, reformat it or give it a 'type'. failing this, it is a new disk required..
hope this helps
M

G4 Mac Server Booting Problems (?)

Computer: PowerMac G4 AGP PowerPC G4 400 MHz, 768 MB Ram, OS 9.04, Server software AppleShare IP 6.3.1.
The server froze when I ran Retrospect mirror backup copying the server drive to an external Firewire drive.
Now almost every time that I reboot, the server freezes with (at) an arrow mouse icon in the upper left screen. The server will fully reboot about once for every ten reboots.
The computer will boot (randomly) from a boot CD with Norton Utilities. Norton says there are no problems.
I ran Disk First Aid and I get a couple of error messages: "MountCheck found minor errors" and "Volume Bit Map needs minor repair".
I ran Repair (Disk First Aid) and it said Problems Fixed.
The problem is, the computer still freezes (randomly) when booting at the arrow mouse icon in the upper left screen.
I have done all the usual fix routines (reset PRAM, rebuild desktop, reset CUDA, etc.); nothing helped.
What is the problem??? How do I fix it? Thanks.
PowerMac G4 AGP PowerPC G4 - SERVER Mac OS 9.0.x 400 MHz, 768 MB Ram, OS 9.04, Server software AppleShare IP 6.3.1.

So here's what I've done so far:
I copied a backup System folder from June this year to the second hard drive on the server. I set the boot disk control panel to Drive2 and re-booted. Froze.
I put a boot CD in the tray and re-booted while holding down the "C" key. The computer booted to Drive2 (what I had previously set it to). I did a re-boot to test (ejecting the CD) and the computer froze.
I rebooted again this time hitting the keyboard's Return key and moving the mouse - reboot ok.
Leaving the computer up (running the June System on Drive2) I tested some functions. The printer still does not work (connected to Apple Share IP print server). The server still does not show up in the Chooser of the users, but they can connect if they have an alias already set up.
I noticed that the Extensions Manager freezes the computer when I click on it. And sometimes I'm getting an Open Transport error message.
So..... We're looking at a SCSI problem or clock battery problem?

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

No Operating System - v1.6.2 uses 'Paravirtual' scsi hba

Hi,
I finally got the v1.6.2 ova to deploy by using the WebClient instead of the NativeClient, however I went to boot it up and it will not boot. The error message is "No operating system found" and the vm's settings indicate that it is using the paravirtual scsi hba. I tried changing to the LSI Logic Parallel but that got the same result. Can anyone confirm what it should be? And has anyone been successful with v1.6.2?
Addendum : the deployment seems flawed. During the deployment wizard it states that two hard disks will be deployed - an 8GB Thin and a 16GB Thick/Lazy. However after deployment has completed there is a hard disk 1 - 16GB Thick and a hard disk 2 - 100MB Thick. I did choose Thick Eager for the disks during deployment but did not (could not) modify disk sizes. So far not having much luck with this fling...
Cheers,
Ron

Hi Ron,
I don't think it's paravirtual SCSI problem. More likely the deployment is not successful. Can you try a fresh deployment, have disks think eager zeroed, and do not power on after deployment? Once it's done, please verify the VMDKs. Here's what I have on my vSphere host:
# cd to VM installation directory first.
$> ls -l *-flat.vmdk
-rw------- 1 root root 17179869184 Apr 8 16:50 <VM_NAME>-flat.vmdk
-rw------- 1 root root 104857600 Apr 8 16:50 <VM_NAME>_1-flat.vmdk
$> md5sum *-flat.vmdk
a4c310c3bd78d40a326b38c9b46abd5d <VM_NAME>-flat.vmdk
f67870ca1e0eed6c79b293ec3c54960f <VM_NAME>_1-flat.vmdk
You might also want to use vmkfstools to check if there is error (vmkfstools --fix check <VM_NAME>-flat.vmdk).
If any of the above doesn't match, you should check /var/log/vmkernel.log and the vmware.log file locates with your VMDK's and see if there is error during deployment (vmware.log will be generated only after first boot).
Thanks,
Chien-Chia

P965 Neo-F memory problems - bad mobo or something I missed?

I bought a new system the other day, and chose the P965 Neo-F as my motherboard. However, it seems I either have a broken unit or missed something crucial.
The machine originally shipped with a G-Skill 800MHz 2 gig set of the NB series. I spent my first night trying to get Windows installed, only to have it crash repeatedly as it tried to copy kodak_dc.icm and various other files. Always the same ones. I thought my CD was bad, so I dug out a copy of Vista's Beta 2. It also failed on a generic "Failed to copy files" error. I then did what I probably should've done immediately and ran Memtest86+.
Within the first 5% I had about 200 errors, so I figured my RAM was bad. I experimented with various slot combinations, dual channel and otherwise. I discovered that the first stick in the first slot would run Memtest86+ until the cows came home with no problems, everything else caused a huge number of errors sooner or later. Interestingly the other stick on its own in slot one would cause massive amounts of errors within seconds. Sometimes these errors would occur within the first few percentages of the first pass, sometimes at the very end. I experimented by upping the voltage in increments from 1.80 to 2.00 and then lowering the RAM speed to 667MHz. No effect.
I exchanged the RAM at the store, but since they were out of G-Skill I got two sticks of generic TwinMOS 667MHz DDRII. The problems continued. One stick in slot 1 will run all day, Windows installs and runs fine. Any other combination causes huge amounts of errors (my record was 7200 errors at the 67% mark with sticks in slots 1 and 4) and data corruption in Windows.
I just rang up the guys at the store and we agreed that since the system is running fine on one stick, I'll try to debug this thing over the weekend. If I can't come up with anything I'll go and have the motherboard swapped on Monday. So, any ideas on things I could try?

Quote from: soralapio on 08-December-06, 16:33:31
I bought a new system the other day, and chose the P965 Neo-F as my motherboard. However, it seems I either have a broken unit or missed something crucial.
The machine originally shipped with a G-Skill 800MHz 2 gig set of the NB series. I spent my first night trying to get Windows installed, only to have it crash repeatedly as it tried to copy kodak_dc.icm and various other files. Always the same ones. I thought my CD was bad, so I dug out a copy of Vista's Beta 2. It also failed on a generic "Failed to copy files" error. I then did what I probably should've done immediately and ran Memtest86+.
Within the first 5% I had about 200 errors, so I figured my RAM was bad. I experimented with various slot combinations, dual channel and otherwise. I discovered that the first stick in the first slot would run Memtest86+ until the cows came home with no problems, everything else caused a huge number of errors sooner or later. Interestingly the other stick on its own in slot one would cause massive amounts of errors within seconds. Sometimes these errors would occur within the first few percentages of the first pass, sometimes at the very end. I experimented by upping the voltage in increments from 1.80 to 2.00 and then lowering the RAM speed to 667MHz. No effect.
I exchanged the RAM at the store, but since they were out of G-Skill I got two sticks of generic TwinMOS 667MHz DDRII. The problems continued. One stick in slot 1 will run all day, Windows installs and runs fine. Any other combination causes huge amounts of errors (my record was 7200 errors at the 67% mark with sticks in slots 1 and 4) and data corruption in Windows.
I just rang up the guys at the store and we agreed that since the system is running fine on one stick, I'll try to debug this thing over the weekend. If I can't come up with anything I'll go and have the motherboard swapped on Monday. So, any ideas on things I could try?
I think at least using ddr2 800mhz had some restrictions on size or something.
Im my self running 2x1gb Kingston Valueram 667mhz no probs. So I would suggest mobo is bad, or you need to get newer bios. My original was 1.5, im using 1.6B9 because of my scsi problems. 1.5 was fine with my memory in dual channel mode.
But to the quality of mobo i think its not ready for shipment yet. I have 3 scsi controllers, where 2 raid controllers isnt working/booting propebly and have performance issues on this mobo, while they work ok with my old a64 system, or my yet older p3 system.

Raid Level 5+6 under 10.5.6 ?

we couldn't use our SCSI RAID Level 6 under 10.52/10.53/10.54/10.5/5
heavy CPU load after a while and crash of the AFP
now the RAID is for sale !
Murphy's low, seems that Apple has fixed some kinds of problems with RAID
http://support.apple.com/kb/HT3192
any body has already Experience with the 10.5.6 and the use of RAID Level 5 or Level 6 on a Server?
any information would help
thanks

No version of Mac OS X supports RAID5 or 6. Theses RAID levels are always implemented in hardware and therefore not subject to the whims of the OS. In reality the RAID is shrouded by the controller and OS has no idea of the underlying array format and there there is nothing to fix in the OS.
I think the pertinent part of your post, though is the 'SCSI' element. I expect that ant problems you have relate to the SCSI card you're using and not the OS. Since there are no specific SCSI fixes in 10.5.6 I doubt anything has changed (but Apple are notorious for not detailing all the low-level changes they make, so you might be lucky.
You'd have a better chance, though, of looking at the SCSI card you're using (what make/model is it?) and checking the drivers provided by the vendor. Most SCSI problems in my experience have come down to card and drivers, not necessarily the OS.

Cldg switch command hangs for long time

Hello Experts ,
We have renamed the veritas volumes vol1 and vol2 of disk group "dg", which is under cluster control.
The renaming of volumes are successfully completed and modification updated in Cluster CCR (cldg sync dg) and volumes are mounted successfully in node002.
We have switch over the disk group "dg" from node002 to node004. The disk group switch over to the node node004 successfully and able to mount the volumes.
Again, we have switch over the disk group "dg" from node004 to node002, but the switch command is not successful and hanged for long time. When we check the /var/adm/messages in node002, the below messages appeared
Oct 22 11:49:39 node002 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/scsi@1 (mpt0):
Oct 22 11:49:39 node002 Disconnected command timeout for Target 0
Oct 22 11:50:49 node002 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/scsi@1 (mpt0):
Action plan followed for renaming the volume:*
node002:/var/tmp/bak# umount /local/mqm/log/mq_log
node002:/var/tmp/bak# umount /local/mqm/qmgrs/mq_qmgr
node002:/var/tmp/bak# vxvol -g dg stop vol1
node002:/var/tmp/bak# vxvol -g dg stop vol2
node002:/var/tmp/bak# vxedit -g dg rename vol1 vol1_log
node002:/var/tmp/bak# vxedit -g dg rename vol2 vol2_qmgf
node002:/var/tmp/bak# vxvol -g dg start vol1_log
node002:/var/tmp/bak# vxvol -g dg start vol2_qmgf
node002:/var/tmp/bak# cldg sync dg
Please advice on this error and how to resolve this.
Regards,
R. Rajesh Kannan

But what is device mtp0? It doesn't sound like a disk name. It is having SCSI problems. I don't know if these messages are relevant though.
I don't use VxVM as a rule, but your procedure seems reasonable to me.
Tim
---

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR

My Power Mac G4 Dual 1GB Quicksilver Server running 10.4.6 Server is crashing almost every night during backup using Retrospect 6.1 to an Ecrix (Exabyte) VXA-1 Firewire tape drive. I have both a Firewire and Ultra SCSI drive and first thought it was a SCSI problem, so I shut down that drive and even pulled the SCSI card, but still have the problem. I had an external Firewire drive going bad and hoped that replacing it would solve the problem, but didn't. I haven't yet tried taking the Firewire drive down and only backing up to the SCSI. I found a thread from last December where someone said they had talked to an Apple Engineer and said that there was known problem with AFP getting busy and causing a very similar error.
Below is the text of the crash report. Can someone give me suggestions based on my description and the crash report?
Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000073 PC=0x00000000000343CC
Latest crash info for cpu 0:
Exception state (sv=0x44CB6000)
PC=0x000343CC; MSR=0x00001030; DAR=0x00000073; DSISR=0x40000000; LR=0x0003451C; R1=0x21CC3D50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x022E2C60 0x0003451C 0x00034280 0x000A9894
Proceeding back via exception chain:
Exception state (sv=0x44CB6000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x00A19000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x44CB6000)
PC=0x000343CC; MSR=0x00001030; DAR=0x00000073; DSISR=0x40000000; LR=0x0003451C; R1=0x21CC3D50; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x022E2C60 0x0003451C 0x00034280 0x000A9894
Exception state (sv=0x00A19000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)
Kernel version:
Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPCModel: PowerMac3,5, BootROM 4.3.3f2, 2 processors, PowerPC G4 (2.1), 1 GHz, 1.5 GB
Graphics: ATI Radeon 7500, ATY,RV200, AGP, 32 MB
Memory Module: DIMM0/J21, 512 MB, SDRAM, PC133-333
Memory Module: DIMM1/J22, 512 MB, SDRAM, PC133-333
Memory Module: DIMM2/J23, 512 MB, SDRAM, PC133-333
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: pci9004,7850, sppciscsibus, SLOT-3
Parallel ATA Device: ST380021A, 74.53 GB
Parallel ATA Device: HDS722525VLAT80, 232.89 GB
Parallel ATA Device: PIONEER DVD-RW DVR-104,
Parallel ATA Device: IOMEGA ZIP 250 ATAPI,
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Logitech, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
FireWire Device: (1394 ATAPI,Rev 1.00), Prolific PL3507 Combo Device, Up to 400 Mb/sec
FireWire Device: LaCie FW800 Disk drive LUN 0, LaCie Group SA, Up to 400 Mb/sec
FireWire Device: LaCie 1394 Disk drive LUN 0, LaCie Group SA, Up to 400 Mb/sec
FireWire Device: VXA-1 1100, ECRIX, Up to 200 Mb/sec
FireWire Device: unknown_device, unknown_value, Up to 400 Mb/sec
Power Mac G4 Dual 1GB Quickilver Mac OS X (10.4.6) Power Mac G4 Dual 1GB Quicksilver (Server)

Same problem here (kernel trap=restart) during the Retrospect 6.0.212 backup to a SCSI tape drive.
With 10.4.5 we didn't have this issue, now it happens every couple of days...
Xserve DP-G4 1.0Ghz, OS 10.4.6

Tape Drive Recognization

Some time after reboot my system doesn't recognize attached tape drive means cat /proc/scsi/scsi shows nothing and I have no clue what to do in this case and why it happens. Also after reboot the permission of /dev/sg0 get changed and I have to again set it accordingly so that oracle user can access the tape drive. I am planning to put that chmod command in system startup script but is it the right way to fix it?
And still dont have any solution for /proc/scsi/scsi problem.
I am using SUSE 9 (64 bit) and OSB 10.1.0 with HP DAT 72 tape drive
I will appreciate if someone can explore the solution.
Thanks
Daljit Singh

Hi Ketan,
>> unable to initialize ASPI manager
Check SCSI id on your tape device. Try to use different SCSI number or try install correct device driver of the tape device.
Best regards,
Orkun Gedik

V240 scsi problems w/dlt4000

Similar Messages

Maybe you are looking for