let me clarify. you're right, a couple months ago (i really can't believe you remember!) i was getting in I/O disk read/write error from azureus. i was also getting some other errors, though i can't remember specifically -- some of the same ones i'm getting now and some different ones i think -- at the moment. disk utility also said there was a problem but it couldn't repair it no matter how many times i ran it. i took it to the apple store and they said my only option was to wipe and reinstall.
so that's what i did. everything seemed fine for a while, and then i started getting other problems cropping up (see this recent post:
http://macosx.com/forums/showthread.php?t=275190). and now recently i've started getting this "Error: Disk read error - Direct buffer memory" error for the first time today. and now i seem to get it with every single download i'm running. if i stop and start the download, or restart azureus the error goes away and it will continue downloading again for a while, but always ends up with the same error after a while. i ran disk utility and it found nothing wrong.
i haven't tried another client besides azureus, although i the previous time (the former spring-time posts you were referring to) i did use tomatotorrent (or whatever it's called) and experienced the same error, though granted it was a different error that what i'm seeing now.
nothing has really helped. i wish i could give you a list of the things that have worked but there really hasn't been. except maybe the complete reformat i did, but i really don't like to think that as a common solution.
the things i've tried that
haven't worked:
ran disk utility
freed up space on my hard
uninstalled and reinstalled azureus
started a new directory for downloads in case current one was writing on corrupted bits
and i suppose some other things i'm not thinking of right now. so i'm definitely open to other suggestions!
thanks!
--e
ps. it just occured to me as i am about to submit this, that though the error is different this time around, maybe it isn't. maybe azureus has been updated since the last time i had a similar issue and is now reporting the same error using a different description? just a thought...