Solaris 10 01/06 hard crash with firewire drive attached

I have Solaris 10 01/06 installed on a Sun W2100z workstation (BIOS is most recent available when last I checked in March). I have applied all publically available Solaris 10 patches that one can get without having a support contract.
I have an external firewire hard drive attached to the system but it's not powered on.
If I halt the workstation, power on the firewire drive, and then attempt to boot the workstation, Solaris will begin to load and then I get a kernel panic and crash dump. This happens every time.
My "mdb" skills are lacking, but if I issue:
cd /var/crash/hostname
mdb unix.1 vmcore.1
I get:
Loading modules: [ unix krtld genunix specfs ufs ip sctp usba uhci s1394 nca random fcp fctl emlxs lofs nfs audiosup sppp crypto ]
$cscsa1394_cmd_fill_cdb_rbc+0x332()
scsa1394_cmd_fill_cdb+0x6f()
scsa1394_scsi_start+0xe4()
scsi_transport+0x60()
scsi_watch_thread+0x2fa()
Anyone else having repeatable crashes on Solaris 10 01/06 x86_64 with firewire hardware attached?
Thanks,
Tim

Hi Asgorath,
Unfortunately I do not have an answer for you but I
am experiencing the identical problem on a HP
Proliant BL25p Blade Server. Here is my hardware
config:
CPU - Dual Opteron 2.6 Single Core
Memory - 16gb
Controller - HP Smart Array 6i
Logical drives - 1 (2x72gb RAID1+0)
I have tried the same things as you and I still get
intermittant boots. Power on and off does not always
work as the system still hangs. It's totally hit or
miss. Once it soes boot it seems to work fine. I have
also installed the latest Solaris 10 for x86 Patch
Cluster in hopes that some of the kernal patches
would fix the problem. So far no luck as the system
continues to hang...HARD!! HP was out to my site
today and the Eng. is going back to the group that
qualified Solaris10 on the HP Blades and see if they
have any input. If I receive anything back I will
post it here. I know this post is late and if you
have resolved please post your fix.Hi doc42755,
I have not come up with a solution as of yet, if I do come up with a solution i will most certainly post it here.
However, if you find the solution could you let us know in this thread aswell.
Thanks
Asgaroth

Similar Messages

IMac won't boot with SATA external firewire drive attached

I have an 1T Hitachi SATA drive enclosed in a Macally firewire enclosure. If it is attached either in series with other IDE firewire drives or directly, my iMac will boot only to the Apple icon and will not engage the gear icon. If I disconnect the drive the iMac will boot normally with all the other IDE firewire drives attached. I've troubleshot with both Macally and Hitachi, received a replacement enclosure and have an RMA from Hitachi. Before I send the Hitachi back with the possibility of a replacement not fixing the problem, I am asking whether there is a known problem with external SATA drives in particular. TIA. -Dave

I have the same problem exactly but with two firewire 800 drives attached. Both are LaCie d2 500 gb drives. I have tried each one as the first in the series with no luck. I have not tried to connect with any other type of cable.

Can I change hard disk with SSD drive in Toshiba NB100?

Can I change hard disk with SSD drive in Toshiba NB100 ?
The Hard disc in this model is same size as SSD 2.5" drive?

Hi
As mentioned above: the SATA controller is supported so you will need to use a SATA SSD drive usually it should not be a big problem to upgrade the notebook with an SSD drive in some cases it could be possible that the SSD firmware needs to be updated but this depends on the SSD drive manufacturer
However, the SSD drive is much faster than a common HDD. Therefore you should notice a faster performance

10g RAC on SLES 9 with Firewire drive

Hello,
Is there documents/guides to setting up 10g RAC with firewire drive on SLES 9. Thank you.

Mike:
Yes! I resolved the problem by applying the 9.2.0.3 patch. However, ocfs is not working properly. Sometime I got I/O problem or used one node to create tablespace but the other node can not see it right away. May be is because I use version 1.0 of ocfs.o. I am trying to find newer version of ocfs.o. If you know where to get it please let me know.

IMac won't boot with external drives attached

I am using iMac 27" Late 2013 model upgraded to mavericks 10.9.4. Two external drives are always attached with it, one is segate 3.5" 2TB USB 3.0 drive and another one is 2.5" usb 2.0 drive.
when i start my imac with external drives attached it won't boot up. Stuck at plain white screen after a startup chime, not even any apple logo or any progress circle appears. And i have to detach all of my drives to make it boot.
This problem arises after upgrading to mavericks. Already tried resetting PRAM, SMC and checked Startup disk and verify disk with disk utility.

Raja,
Do a SMC reset perhaps even a couple of times and see if that helps. Also in System Preferences + Startup Disk make sure the internal HD is selected.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
Roger

Will external hard disk with firewire help me to back up my laptop using time machine?

Hi,
I have macbook pro from 2011 with 750GB hard disk and I try to back up my hard disk using time machine for the first time.
I used time machine before in the previous OSX versions but I had to format the external disk.
I have an external Western Digital hard disk with 3TB space. It has only usb connection.
When I try to backup all my data (650GB) the speed is 25GB per day, so it will take me about a month to backup my disk.
It's my work laptop, so I can't leave it for backup for more than 2-3 days.
I read a lot of forums and tried to see if the small speed is only at the beginning of the back up.
I also tried all the tricks with turning off the spotlight indexing and so on.
Nothing really helps, so my question is:
Is it going to help, if I buy an external disk with a firewire connection? Will I be able to backup my data in 2-3 days?
Thanks,
Arshavski Alexander

A Firewire drive would only be about twice as fast as USB 2, so you're still looking at 15 days. Something isn't right. I'm usinge FW800, and my my 1TB backs up overnight.
Take a look here and see if anything helps: http://pondini.org/TM/D2.html

Can't get X11 to load, hard crashes with Geforce 8200M

I can't get Xwindows to load on a new laptop I recently got. Ubuntu Live 64bit works fine, even can install the NVIDIA drivers and get 3D support on it (tested this before I purchased the laptop). So in Arch Linux (64bit) I downloaded the main NVIDIA driver package, module loads fine. When I try to start Xwindows, I get a "bus error" as regular user. When I try root, my machine crashes hard (can't even toggle CAPS lock). I can't even load Xwindows with the VESA driver, it complains about MTRR not matching correctly.
Specs on the machine can be found here: http://h10025.www1.hp.com/ewfrf/wc/docu … ct=3860070
Any help would be greatly appreciated. I also tried the 190 beta drivers, same problems occur. I can get any log files if needed later, I don't have immediate access to the machine.
Thank you in advance,

scriptmunkee wrote:Not sure if my issue is the same as yours, but I updated to night and had version 185.18.31-1 installed with kernel 2.6.30.4-1. That combination didn't allow Xorg to start properly. I don't get an error at all. I get a failure or a halt when the Nvidia driver attempts to replace the ACPI hotkey events
Are you able to load it properly using vesa of nv drivers? I can't seem to get mine to load with any driver- it always crashes hard.

Crashes when Firewire Drives are mounted

For some reason now Logic crashes (hangs...not responding) when i boot Logic with my one firewire drive mounted. When i unmount the drive and then boot Logic it works fine. THen i re mount it and open my project.
Is there a fix for this?

Here's what I think is going on...
You wrote:
If i boot logic and then mount the drive it works fine.
Logic keeps a file (somewhere) that remembers the most recently opened songs/projects. I think this file is corrupt. I have no idea what the file is called, where it's located, but I think it's corrupt. Bascially, when you launch Logic but the drive to which a recent song isn't mounted/not available, that song will disappear from Logic's recent song list. But I have the feeling that Logic hasn't totally forgotten about the existence of that song. So when the drive is mounted and Logic loads up, it might just be trying to find the drive where the song lives but something gets screwy in the process.
Here's what I suggest:
a) quit Logic if it's running
b) mount the drive
c) copy the entire project to your internal HD
d) launch Logic
e) open the song from your HD
f) if this works without crashing, re-save the project to your FW drive under a new name
g) go to Logic's recent song list and count the number of songs in the list. Let's say it's 20 songs in the list...
h) hold option for one second and create a NEW song (this will be Logic's "default" song)
i) save it to your FW drive as a simple song (not project) called "a"
j) now save it 20 more times, changing the name each time, i.e., "b", "c", etc. What you're attempting to do is completely clear Logic's recent song list of all previous song titles with something known to be "benign"
k) re-load your real song as saved to your FW drive in step F above
l) if this works, quit Logic without saving
m) re-boot the computer
n) make sure the FW drive is mounted
o) launch Logic and load the song from step F from the FW drive
If all that works, then I think my theory is right about the recent file list being corrupt.
If it doesn't work, well, [Elmer Fudd = ON] I twied and I twied...

Why an I losing contact with Firewire drives and camera back?

One of my computers suddenly won't connect to a Phase One digital back via firewire.
Tried to plug in a external drive to check the port. No contact. (Tried various cables, etc.)
Tried camera on another computer. No contact. Tried firewire drives that had been running before on this same computer, and now it won't read these drives.
My PhaseOne dealer assures me that a digital back can't possible fry or disable a port. Still. there they are.
Took one of these drives to yet another computer that connects fine with yet another drive, tried the problem drive, and there was no connection. When I checked About This Mac there was a spinning wheel, as though it were looking for something.
Any thoughts, anyone? I don't want to test more drives if they are being damaged. And if they are, can they be recovered?
Many thanks
Sean Kernan

Hi, John.
1. I presume in Finder Preferences, in the General tab, you've selected "CDs, DVDs, and iPods" under "Show on desktop." Otherwise, FireWire drives won't display on the desktop, but they should still appear in the Finder's Sidebar.
2. If you did not Eject the drive before you disconnected it or powered it off, its partition map may be corrupted. That could explain the symptoms you are seeing. Your FireWire-based digital camera back may be seen as a FireWire drive.
Disconnecting a removable storage device — FireWire drive, USB drive, etc. — without first ejecting it can result in the drive's partition map being corrupted. Before disconnecting such a device, one must first Eject it by either:
- Dragging its icon to the Trash.
- Control-clicking the drive's icon and selecting Eject from its contextual menu.
- In Disk Utility, selecting the device, then selecting Eject in the Disk Utility toolbar.
If there's data on the drive you wish to recover, see my "Data Recovery" FAQ. Once you recover the data you want to save, if any, you will need to repartition and reformat the drive.
3. Before you panic w.r.t. item 2 above, Here is some general troubleshooting advice w.r.t. FireWire devices that may help:(1) Review the AppleCare Knowledge Base document "What to do if your computer won't recognize a FireWire device".
(2) If this problem occurred after installing a recent Mac OS X Update, and you are also unable to mount CDs, DVDs, or disk images perform the steps in this Mac OS X Hints article.
(3) The following additional steps will often help resolve problems with FireWire devices, particularly hard drives:(a) Power-on the FireWire drive before starting up (booting) your Mac.
(b) Reset PRAM and NVRAM.
(c) Reset the PMU or SMU: Select the appropriate knowledge base item for your model of Mac from this KB search. Follow the instructions on resetting the PMU or SMU carefully!
(d) Try a different FireWire port. James Wiebe, CEO of WiebeTech, has published FireWire Port Failures in Host Computers and Peripheral Devices, a white paper providing backgroud information and technical analysis concerning the causes of failure for FireWire ports. This may provide additional diagnostic information.
(e) Check with the manufacturer of your FireWire drive or enclosure to see if any firware updates are available for such.(4) Hopefully, the partition map on the FireWire drive is not damaged. If it still refuses to mount, you may need to employ data recovery tools or services: see my "Data Recovery" FAQ.Note that some of the information above is from the "FireWire Problems" chapter of my book, Troubleshooting Mac® OS X.
PS: You've not provided any info about the computer in question, i.e. Mac model, installed RAM, installed version of Mac OS X, etc. That's always important to include in a post, and I suggest you add it to your profile: click "My Settings" in the upper-right section of the sidebar on the right side of this page.
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

OSX Retrospect unhappy with FireWire Drive?

Dear folks,
I have no idea if this is a hardware, software, and/or OS problem. But it's a real puzzle.
I have an external firewire drive I use with a PC Card firewire adapter. It works fine under both OS 9 and OS X. It also works fine with Retrospect under OS 9, performing backups and verifies at over 200 MB per minute.
But, with Retrospect 6.1.2 under OS X Panther, performance to firewire is abysmal. When backing up my Panther volume to the firewire drive, it takes more than eight minutes for Retrospect to do its prep and then the backup proceeds at only 70 MB per minute (no compression). It takes another eight minutes for Retrospect to close the backup and prepare for the verification pass. The verification pass runs at only 2 MB per minute! Yes, you read that right, about 30 kilobytes per second.
By comparison, if I back up the Panther volume to a different volume on the same internal hard drive, it takes Retrospect less than 1 minutes to do the setup (and to close the backup), it writes the backup at 100 MB per minute, and it runs the verification pass at 140 MB per minute.
For reference, copying files to and from the firewire drive runs at over 200 MB per minute in any other application under OS X.
Anyone here have any thoughts at all? I really like Retrospect, but 6.1.2 seems to be useless with my Firewire drive.
pax / Ctein
[[ Please excuse any word-salad. ViaVoice in training! ]]
=========================================
-- Ctein's Online Gallery http://www.ctein.com
-- Digital Restorations http://photo-repair.com
=========================================

"Repair Disk Permissions" from Disk Utility may help.
Also, cmd-opt-n-v (Clear NV RAM) may help as well.
Mihalis.

Weird Problem with Firewire Drive on 17" MBP

I have an external firewire drive that worked great on my 15" MBP and with any other computer I have never had any problems. The problem occurs when I plug the drive into my 17" MBP with the magsafe connected, it just wont mount, but as soon as I unplug the magsafe the drive mounts. Really weird. Anyone have a similar problem? I am going to the Apple Store and see if I can duplicate the problem.

I'd backup your files if you can. If the drive is failing then the advise you've gotten is good advise. You can try software recovery if you are unable to use the drive:
Basics of File Recovery
Files in Trash
If you simply put files in the Trash you can restore them by opening the Trash (left-click on the Trash icon) and drag the files from the Trash to your Desktop or other desired location. OS X also provides a short-cut to undo the last item moved to the Trash -press COMMAND-Z.
If you empty the Trash the files are gone. If a program does an immediate delete rather than moving files to the Trash, then the files are gone. Recovery is possible but you must not allow any additional writes to the hard drive - shut it down. When files are deleted only the directory entries, not the files themselves, is modified. The space occupied by the files has been returned to the system as available for storage, but the files are still on the drive. Writing to the drive will then eventually overwrite the space once occupied by the deleted files in which case the files are lost permanently. Also if you save a file over an existing file of the same name, then the old file is overwritten and cannot be recovered.
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten with recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery.
If the above is not possible then sending the drive to a data recovery service may be your only option, and they are very expensive.

Finder crashes with External Drive on Sleep Mode

I purchased my new iMac 21,5" less than a week ago, and I haven't had a problem with it except for one that it's been bugging me a lot.
I have a LaCie 1TB Quadra d2 external drive that I use to store footage (since it's HD, the filesize won't fit in my 500TB internal hard drive), but I noticed that sometimes when LaCie external drive enters in Sleep Mode, the Finder freezes and the only two ways around this, is to force reboot, because the Finder won't answer and won't open again, or unplugging the external drive without ejecting him first, which it's not safe for me to do, because I'm afraid of hurting the device, and the files in it are pretty important.
This happens almost everytime, especially after a long time on sleep mode. I usually leave Final Cut Pro transferring files all night (since it takes a long time) so I kinda need the sleep mode, but when I wake up, Finder and Final Cut Pro won't answer.
I updated to Snow Leopard 10.6.8 on day one. Is there a way to fix this? Is it normal? I read somewhere that some users were having trouble with external drives on Sleep Mode, but I can't seem to find any further information about this problem.
Thanks!

I've got a MacBook Pro 13.3" that's a little over a month old, with a LaCie 1TB LaCie d2 Quadra with USB 3.0, #301542U and I'm suffering the same problems and a few others with it. I've got a partition on it set up as my Time Machine backup drive. I've turned off the Put the hard disk(s) to sleep when possible in the Energy Saver preferences but I'm still having the sleep problem with it. According to the LaCie Manual:
By default, your drive will enter Eco Mode after 30 minutes of inactivity in order to conserve energy. To exit Eco Mode, simply access data on the drive and the disk will automatically restart. You can manage this feature using LaCie Desktop Manager. Click the Eco tab.
The LaCie Desktop Manager (in my case) only takes me to the Energy Saver Preferences in OS X to adjust the time there. Turning off Put the hard disk(s) to sleep when possible doesn't seem to make any difference, the drive still goes to sleep after 30 minutes. However, after 15 minutes the drive seems to wake back up, but then during the next 15 minutes goes comatose (no power light). Sometimes it will go through multiples of these sleep wake cycles without going into a coma, but eventually it does go into a coma. This happens in between hourly Time Machine backups.
After locking up Finder, Disk Utility and Time Machine multiple times trying to access the drive in this state I figured out that I could cycle the power switch to regain use of it (with a Finder warning of course) but this will only lead to file corruption eventually and I shouldn't have to resort to this. I've also dismounted it, expecting it to turn off and instead it goes into an extended spin down cycle (rapidly flashing light) and never turns off (or goes to sleep or what ever it's supposed to do) and once again requires turning the power switch off.
This is just too unpredictible and unrelable for me and as soon as I get the opportunity to do a 7 pass erase I'll be returning to the place of purchase. Based on the reviews of other external hard drives a drive from another company doesn't look to be much better of a prospect so I'm not sure what I'm going to do.

Error -36 when reading/writing with firewire drives (400 & 800)

This is only happening when I connect the drives to my G5, but the drives work fine on my MacBook Pro. I first thought I had a problem with my drives, but then when they worked on my laptop I figured it must be a problem with my G5. One of the drives is a smartdisk firelite drive connected via firewire to the front of my G5, the other is a G-Drive connected via FW 800 in the back of my machine.
Any ideas of what I need to do on my G5 to fix this issue?
Thanks!

Hi-
The error is an I/O error. One possible cause is low power on the firewire bus, or, the drives require more power than is available. Placing a powered hub between the G5 and the drive may be the solution.

10.5.2 TIme Machine with Firewire Drives

I have seen other people post that they have had problems with Time Machine and 10.5.2. I have had similar problems -- The backup would fail after about 6-8gb with mysterious system.log lines saying there were errors copying files to the volume. The most interesting lines in system.log were from backupd producing error -36 (io error) followed by a mysterious -8062 error.
I checked the disk, no errors. I verified that the files listed in the log file were not erroneous -- they were ok. I reformatted the time machine drive and got the same result. I bought a new external drive on the chance that the old external drive was failing and still got the messages. Prior to the 10.5.2 update, Time Machine worked as advertised with no issues.
In an attempt to figure this out, I switched the external drive from firewire 400 to USB. Now, the backup seems to progressing normally. Interestingly, when Aperture tried to backup a vault to the same firewire drives, it also got an I/O error.
I suspect there is a problem with the 10.5.2 firewire drivers and PowerMac G5 (and maybe others)

I concur. Leopard's FireWire drivers still seem to be problematic. On my friend's computer, an iMac G4, using FireWire had consistently resulted in disk failures when running 10.5.1, so we had switched to USB as a workaround. After 10.5.2 arrived, we switched back, hoping Apple had fixed the problem. Unfortunately, that doesn't appear to be the case.
Soon after switching back to FireWire, Time Machine failed, and we ended up having to start from scratch. Time Machine got to about the 100-GB mark of the initial backup when it reported a disk error. Unlike your case, however, the volume was corrupted, and Disk Utility could not repair it. We're going back to USB for now.

Imac running 10.8.2 often does not start up with firewire drives connected

I have a mid 2007 imac running osx 10.8.2 and it will nit restart with two firewire drives connected if it has been running for sometime. If i disconnecr and restart and then connect the drives and then restart again it will restart.

a brody's guess is a good one. Please also look at what Apple says in Gray screen appears during startup

Solaris 10 01/06 hard crash with firewire drive attached

Similar Messages

Maybe you are looking for