[zorro23]

I have problem with my startup hard disk partition. After some time of normal work it seems that Tiger system partition becomes locked.

This is my system log where you can see DMA failure notice:
Jul 2 13:56:05 mac-g4 kernel[0]: disk1s10: DMA failure.
Jul 2 13:56:05 mac-g4 kernel[0]: jnl: do_jnl_io: strategy err 0x5
Jul 2 13:56:05 mac-g4 kernel[0]: jnl: end_transaction: only wrote 0 of 369152 bytes to the journal!
Jul 2 13:57:25 mac-g4 /Applications/Safari.app/Contents/MacOS/Safari: Couldn't create temp file /Users/zorro/Library/Keychains/~Doj9hTJAuX6KpC5g: Invalid argument
Jul 2 13:58:33 mac-g4 kernel[0]: bsd_write_page_cache_file: Can't write header 1f5

After that I can't write (or move) anything on Tiger partition. There is also another partition on the same disk and I can write on it.
I have tried to change hard disk but same thing is happening again.
The Tiger is installed on clean partition formatted with Mac OS Extended (Journaled) format. I have tried repairing volume in Disk Utility but nothing is reported.

My config: G4 Powerlogix 1.4GHz Digital Audio / 1024MB RAM / Radeon 8500 / 3x120GB HD

Help

[OreoCookie]

I would check the ATA cable to your hd: change it and try again.

If that doesn't help, use TechTool or DiskWarrior to check your harddrive.

[CharlesS]

Although I pretty much agree with what OreoCookie said, I have to ask - why did this get moved to Peripherals? His problem is with his startup disk, which would have come inside the computer, and is sort of an essential component. How is that a peripheral?

[OreoCookie]

It was in MacOS, and I'm pretty sure it's hardware-related. Since I didn't know what kind of system he has, I moved it here. (There are a few other harddrive threads here, so I don't think it's the wrong forum.) If another mod disagrees, feel free to move it again.

[zorro23]

I have OS X 10.4.1.

[Drakino]

I had a similar problem on my powerbook. A few months after I had it, the thing would lock the hard drive into read only mode somehow. Never tracked it down initially, and it wouldn't happen if I would reboot every few days.

This feburary though it got bad. I noticed some corrutped data, dug deeper, and found a ton of the DMA errors in my system log. The hard drive was replaced with a known good one, and the same errors came up. The service center ran additional diags, found a memory module that was bad and replaced it. I got the system back, went to install World of Warcraft, and it would trigger these DMA errors near instantly when processor peformance was set to high. Took the system back with the WoW CD, and the service center ended up replacing the mainboard to finally solve the problem.

Feb 18 18:43:11 dragonbook kernel: disk0s9: DMA failure.
Feb 19 09:43:34 dragonbook kernel: disk0s9: DMA failure.
Feb 19 09:47:42 dragonbook kernel: disk0s9: DMA failure.
Feb 19 22:46:07 dragonbook kernel: disk0s9: DMA failure.
Feb 20 00:23:01 dragonbook kernel: disk0s9: DMA failure.
Feb 20 00:48:05 dragonbook kernel: disk0s9: DMA failure.
Feb 20 00:51:50 dragonbook kernel: disk0s9: DMA failure.
Feb 20 03:35:51 dragonbook kernel: disk0: DMA failure.