10.5 kernel panic from update process?

[macprobuffalo]

Within the last 2 days my powermac g5 has crashed twice because of the update process. From what i've read this process is related to updating the filesystem on storage disks. Any idea what the underlying issue is or how I solve it? Having trouble finding info, anything I google with the process name is related to updated software. I have disks in both drive bays and a Sonnet PCIE SATA card with another two disks. Computer has 4gb of new ECC Ram. This setup hasn't had any issues since setting it up in December.

Here is the crash log:

Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x00000000583C4000 PC=0x000000000011128C
Latest crash info for cpu 1:
Exception state (sv=0x828d2a00)
PC=0x0011128C; MSR=0x00009030; DAR=0x583C4000; DSISR=0x40000000; LR=0x00111264; R1=0x6EB4BBE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00111264 0x001117D0 0x0025E5A4 0x001089A4 0x000F742C 0x000F27B4
0x000F7478 0x003100AC 0x000B4448 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFFE80

Proceeding back via exception chain:
Exception state (sv=0x828d2a00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x828ae500)
PC=0x96ACF8B8; MSR=0x0000D030; DAR=0xA0AEB934; DSISR=0x40000000; LR=0x00001F7C; R1=0xBFFFFE80; XCP=0x00000030 (0xC00 - System call)

BSD process name corresponding to current thread: update

Mac OS version:
9L31a

Kernel version:
Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
System model name: PowerMac11,2

System uptime in nanoseconds: 386644871727781
unloaded kexts:
com.apple.driver.Apple02DBDMAAudio 2.5.8f1 - last unloaded 3166594445
loaded kexts:
com.sonnettech.SonnetSATABlockStorage 2.2.4
com.sonnettech.driver.SonnetSATA 2.2.4
com.apple.filesystems.autofs 2.0.2 - last loaded 883248287
com.apple.nke.pptp 1.5
com.apple.nke.l2tp 1.5
com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1
com.apple.driver.AppleTopazAudio 2.5.8f1
com.apple.driver.AppleOnyxAudio 2.5.8f1
com.apple.iokit.IOGraphicsFamily 1.7.3
com.apple.driver.AudioIPCDriver 1.0.6
com.apple.driver.AppleTexasAudio 2.5.8f1
com.apple.driver.AppleTexas2Audio 2.5.8f1
com.apple.driver.AppleDACAAudio 2.5.8f1
com.apple.driver.PowerMac11_2_ThermalProfile 3.4.0d0
com.apple.driver.AppleSCCSerial 1.3.2
com.apple.driver.IOI2CMaxim1631 1.9d0
com.apple.driver.AppleI2S 1.0.1f1
com.apple.driver.IOI2CLM7x 1.9d0
com.apple.iokit.IOFireWireIP 1.7.7
com.apple.driver.AppleK2Driver 1.7.2f1
com.apple.driver.AppleHWSensor 1.9d0
com.apple.driver.IOI2CMaxim6690 1.9d0
com.apple.driver.AppleSMUMonitor 1.9d0
com.apple.driver.IOI2CSMUSat 1.9d0
com.apple.driver.IOI2CPulsar 1.5.2d0
com.apple.driver.IOI2CControllerSMU 1.1.1d2
com.apple.driver.AppleFileSystemDriver 1.1.0
com.apple.driver.XsanFilter 2.7.91
com.apple.iokit.IOATABlockStorage 2.0.6
com.apple.driver.AppleUSBHub 3.4.9
com.apple.iokit.IOUSBUserClient 3.5.2
com.apple.driver.AppleK2SATA 1.0.4f2
com.apple.driver.AppleGPIO 1.3.0d0
com.apple.driver.MacIOGPIO 1.3.0d0
com.apple.driver.AppleMPIC 1.5.3
com.apple.driver.AppleI2C 4.0.0d2
com.apple.driver.IOI2CControllerPPC 1.1.1d2
com.apple.iokit.AppleBCM5701Ethernet 2.2.3b1
com.apple.driver.AppleFWOHCI 3.9.7
com.apple.driver.AppleKauaiATA 1.2.1f4
com.apple.driver.AppleK2SATARoot 1.0.5b1
com.apple.driver.AppleUSBEHCI 3.4.6
com.apple.driver.AppleUSBOHCI 3.4.6
com.apple.driver.AppleK2 1.7.2f1
com.apple.driver.AppleSMU 1.2.1d1
com.apple.driver.AppleMacRiscPCI 3.4.0
com.apple.driver.AppleCore99NVRAM 1.1.1
com.apple.driver.AppleFlashNVRAM 1.0.5
com.apple.security.seatbelt 107.12
com.apple.nke.applicationfirewall 1.8.77
com.apple.security.TMSafetyNet 3
com.apple.iokit.IOHIDFamily 1.5.5
com.apple.BootCache 30.4
com.apple.driver.DiskImages 199
com.apple.driver.AppleMacRISC4PE 2.0.4d9
com.apple.nke.ppp 1.5
com.apple.driver.AppleOnboardAud`

 

[happyfrappy]

I've seen KPs if the OS X installer/updater hit a bad sector/corruption on a HDD(s), my parents Intel iMac was sunk by a failing disk that didn't report any SMART errors so you never know until it happens. If you have a PPC Linux CD/DVD laying around you could check the SMART status via GParted. (OS X Disk Utility doesn't show raw stats)

 

[macprobuffalo]

Would the sector have to be on the startup disk to cause that? 3 of the 4 disks (including the startup disk) are new with less than 3000 hours. The other disk has 26,000 hours. But according to SMART Utility (https://www.volitans-software.com/apps/smart-utility/) everything is fine. I know i'm on borrowed time with that old disk, nothing important is on it

Going through the system log it seems like the SMART app is constantly checking the drives despite me telling it to only check once a day. I stopped that app and will see if this happens again. What linux distro do you use?

Also are you guys using jumpers on your HD's to slow them down to lower SATA speeds. This machine is using SATA 6GB/s drives so even with the jumper they would go down to SATA 3GB/s which still is twice as fast as the powermac SATA 1.5GB/s. The drives currently have no jumpers and seem to work fine. Using WD Reds

 

[happyfrappy]

When doing OS X updates it usually runs a multi-step optimization(rebuilding databases), if it KP-ed during or exactly at the optimization point it'll be the boot drive but if it occurred a bit longer it could be any drive that you installed 3rd party programs that have used the OS X Installer(OS X Installer has a plist of alt-installed locations and that is part of the optimization of the databases)
Did you format the drive by zeroing it when originally installing OS X? With some of the recent drives you're taking a huge risk of not doing so.

I don't own a Power Mac but I've also experienced KPs/non-recoverable beachball of doom with external USB/Firewire HDDs if there is a bad sector/corruption. Sometimes you can run Disk Utility to verify/repair but other times you'll need something like Disk Warrior to rebuild the directory which is often the best option to avoid a total reformat when its just corruption. If you do have bad sectors it might require zeroing the drive with 3-passes so the drive's firmware can remap usable sectors & rule out any surrounding bad sectors--the extra passes are a precaution.

Lubuntu LTS has GParted, there is a menu for drive info which should display detailed/raw SMART data--haven't used Linux on a PPC machine in awhile.

 

[macprobuffalo]

When I say update process I mean a the process name titled "update" in activity monitor. I have not been installing any software updates on the machine. In the crash reporter it says "BSD process name corresponding to current thread: update" The computer is a file and VPN server so applications are only on the startup drive.

Did a long SMART test on all my drives and they came back fine (2+ hours per drive). Haven't had any issues with it today so fingers crossed.

 

[happyfrappy]

Automated scheduled update process does check the OS plist/database of previous updates, its possible booting to Linux then booting back forced OS X to re-verify the journaled state which is supposed to be a mini-safety net from KPs/hard shutdowns from a non-responsive system state.

When it comes to old drives once you reach 5 years of near 24/7 usage the reliability curve drops quite a bit, Western Digital & Hitachi/HGST typically can push 8-10 years max before something internally contaminates the platter(pieces of the head parking ramp or platter coating separation).

 

[macprobuffalo]

Thank you for helping me clear that up! Appreciate you insight. Replacing that drive is definitely on my to-do list