I've been having a strange problem with my hard drive lately, but before I explain in detail, here's a little overview of everything that you need to know. I'm using a Mac Mini (1,1 I think) with a 1.5GHz Intel Core Solo CPU, 2GB 667MHz DDR2 RAM, running Mac OS X 10.5 (Leopard). The hard drive I'm using is a LaCie P'9220 500GB drive, connected directly (I mean no USB hub or anything) through USB 3.0 to a USB 2.0 port (maybe it matters, IDK) with HFS+ Journaled file system and it's not partitioned. The drive is practically mounted all the time and rarely disconnected. The drive isn't my boot disk, it's simply a storage disk.
Now I don't know if that's essential or not, but still I thought it's worth mentioning. Now here's the issue. About 2 months ago, this hard disk started acting weird where it would randomly prevent me from writing to it, though I was still reading from it constantly as I was running applications and had open files located in the disk. I restarted the computer and it worked again, but it happened again later on. It's worth noting that the computer never gets turned off, and the intervals between these unresponsiveness events are about 1-3 days.
I tried modifying anything on the disk directly from the Terminal and it just spit out the same message in all cases, "Invalid Argument"
. Here's one of the attempts to create a directory, for example:adminroots-computer:/ piero$ mkdir /Volumes/Piero\'s\ Lacie/test
mkdir: /Volumes/Piero's Lacie/test: Invalid argument
Being annoyed that I had to restart the computer every time this happened, I tried ejecting the disk and I believe it didn't work (though I'm not too sure). I tried linking this weird happenings to putting the computer to sleep, but I found out it happened without the computer ever going to sleep. Also I noticed just today that it had nothing to do with the disk being inactive, because I was downloading some files in parallel and the last file suddenly stopped, and guess what message popped up? "Download failed: Invalid argument"
. The screensaver might have something to do, but I haven't yet been able to confirm or deny this.
Lately what I do to fix the problem is to unmount the volume, though there's another issue here as well. While unmounting, this message pops up:adminroots-computer:/ piero$ diskutil unmount /Volumes/Piero\'s\ Lacie
Volume Piero's Lacie on disk1s3 failed to unmount
So I end up force-unmounting the volume because it refuses to unmount. After mounting it again it works perfectly once again. Note that I don't disconnect the disk after unmounting.
So, does anyone know what could be causing this? If so, how can I fix it?