violincredible
Registered
I'm desperately and doggedly trying to solve an intermittent problem on a PM dual G5 2.3, OSX 10.4.11, 4.5GB ram, GeForce 6600, Photoshop CS3 10.0
What happens is that the desktop background and sometimes the menu bar suddenly develop lines like this:
http://www.filedump.net/dumped/dtlines11205987003.jpg
http://www.filedump.net/dumped/menuline11205987103.jpg
and then photoshop files start getting corrupted (PS says file corrupted by disk error etc) It seems to occur when a .psd is saved then reopened, and only affects some layers. It looks like this:
http://www.filedump.net/dumped/pscorruption11205987207.jpg
http://www.filedump.net/dumped/pscorruption21205987243.jpg
http://www.filedump.net/dumped/pscorruption31205987330.jpg
This problem first started with Leopard on the G5 and PS7 (or 8, not sure) when there was a Windows Server 2003 RAID setup hosting files. (a nightmare setup in a Mac production environment- file name problems, flakyness etc etc, but not the cause of this problem)
Since then I've:
-replaced the server with a G5 PM (OSX10.4.11) with a startup HD on the Mac's SATA port and a RocketRaid 8 channel Raid card, 4 drives internally using a G5 Jive, (2TB RAID5), plus external X4 box (hot spares and another backup array) It's a magnificent setup- fast, stable, no problems.
-got rid of Leopard on the offending machine and did a fresh install of Tiger to a new internal HD (tried both slots, removing old HD completely, no difference, so it's a backup drive now). Did all OS updates, checked everything with Disk utility, Disk Warrior, latest TechTool etc etc
-installed PS CS3 and a few production apps like ProSelect, Virtual TimeCard, etc (bare minimum, no frills)
-checked and rechecked drive cables, ram seating, etc etc
-forbidden users to open or save PS files over the network (maybe they cheat ;-) (Adobe have always said not to open or save over the network, but to save/open to/from local drive and copy across)
-done all the 'reset nvram, repair permissions, Disk utility, Disk Warrior, latest TechTool, MemTest, delete prefs, new user, reinstall PS, wipe HD and start again etc etc' sort of things (repeatedly)
Time after time the problem seems to be solved, but it always comes back. Given that it's persisted through different OSs, Hard drives, versions of PS, server types and several complete format and reinstalls, I strongly suspect a hardware issue, but nothing ever shows up in any hardware tests, and no other app ever gives trouble.
We have another G5 DP with exactly the same OS and software, and a Mac Pro almost exactly the same, neither of which ever do anything like this.
Strangely, the issue has only ever happened when one particular user is working, (it never happens to him on any other Macs, though). The only things we can think of that he does that no-one else does is using grouped adjustment layers, and saving and closing files before working on another file (others tend to leave 10+ images open while working on them)
Any thoughts or suggestions would be mightily appreciated -as a Tech on this site myself, I know this is a rambling and messy question, but it's got me pulling out my hair!!
Ask me and I'll provide any detail, try any suggestion, donate a kidney if I have to, but this problem is making me look bad to an important client and I MUST get it resolved. (I'm almost tempted to throw this G5 off the balcony and run screaming into the night)
Thanks,
Alex
What happens is that the desktop background and sometimes the menu bar suddenly develop lines like this:
http://www.filedump.net/dumped/dtlines11205987003.jpg
http://www.filedump.net/dumped/menuline11205987103.jpg
and then photoshop files start getting corrupted (PS says file corrupted by disk error etc) It seems to occur when a .psd is saved then reopened, and only affects some layers. It looks like this:
http://www.filedump.net/dumped/pscorruption11205987207.jpg
http://www.filedump.net/dumped/pscorruption21205987243.jpg
http://www.filedump.net/dumped/pscorruption31205987330.jpg
This problem first started with Leopard on the G5 and PS7 (or 8, not sure) when there was a Windows Server 2003 RAID setup hosting files. (a nightmare setup in a Mac production environment- file name problems, flakyness etc etc, but not the cause of this problem)
Since then I've:
-replaced the server with a G5 PM (OSX10.4.11) with a startup HD on the Mac's SATA port and a RocketRaid 8 channel Raid card, 4 drives internally using a G5 Jive, (2TB RAID5), plus external X4 box (hot spares and another backup array) It's a magnificent setup- fast, stable, no problems.
-got rid of Leopard on the offending machine and did a fresh install of Tiger to a new internal HD (tried both slots, removing old HD completely, no difference, so it's a backup drive now). Did all OS updates, checked everything with Disk utility, Disk Warrior, latest TechTool etc etc
-installed PS CS3 and a few production apps like ProSelect, Virtual TimeCard, etc (bare minimum, no frills)
-checked and rechecked drive cables, ram seating, etc etc
-forbidden users to open or save PS files over the network (maybe they cheat ;-) (Adobe have always said not to open or save over the network, but to save/open to/from local drive and copy across)
-done all the 'reset nvram, repair permissions, Disk utility, Disk Warrior, latest TechTool, MemTest, delete prefs, new user, reinstall PS, wipe HD and start again etc etc' sort of things (repeatedly)
Time after time the problem seems to be solved, but it always comes back. Given that it's persisted through different OSs, Hard drives, versions of PS, server types and several complete format and reinstalls, I strongly suspect a hardware issue, but nothing ever shows up in any hardware tests, and no other app ever gives trouble.
We have another G5 DP with exactly the same OS and software, and a Mac Pro almost exactly the same, neither of which ever do anything like this.
Strangely, the issue has only ever happened when one particular user is working, (it never happens to him on any other Macs, though). The only things we can think of that he does that no-one else does is using grouped adjustment layers, and saving and closing files before working on another file (others tend to leave 10+ images open while working on them)
Any thoughts or suggestions would be mightily appreciated -as a Tech on this site myself, I know this is a rambling and messy question, but it's got me pulling out my hair!!
Ask me and I'll provide any detail, try any suggestion, donate a kidney if I have to, but this problem is making me look bad to an important client and I MUST get it resolved. (I'm almost tempted to throw this G5 off the balcony and run screaming into the night)
Thanks,
Alex
Last edited: