Could a cheap fw drive used only for storage corrupt PT files?

[Nash BBQ]

I am in the in the process of engineering my first "real" record. It is a very exciting time and I want to be safe and professional about my file mgmt.
I use a 30gig firewire Glyph as my tracking drive but that has filled with the 15 songs in progress. We bought an 80gig Fantom drive that was used for backup copies that has filled up as well. We now bought a Western Digital 7200rpm 120gig firewire for backup as well. So I will still track to the Glyph by do more dragging between that and the Western Digital for works-in-progress before burning a DVD-R.
I tried to open a session off of the WD drive (not dragging it to the Glyph)and got a DAE 9060 error. I have never gotten such an error in my year and a half in Pro Tools heaven. Now I'm not positive (it was 3am and the end of a 14hr work day) but when I took the "corrupted" file and put it back on the Glyph, I got the same error (9060). No restart. I think.
QUESTION: Can this non-supported drive damage a file if I truely just use it for storage?
QUESTION: Does option+dragging files from drive to drive several times increase the chances of errors?

You guys are the best.
Thanks.
BBQ

[Chompers]

all drives can corrupt. THe WD drive isnt more suspect thatn the glyph. The issues are more random than "supported" or not.
THe oxford 911 chip should be in ALL firewire drives you use. Check the WD and see if its got it, (if its new its probably a 911)
HAving the firewire drive plugged in could be the problem. Make sure you unplug it before you troubleshoot the transfered file again.

ALSO it may just be a DAE error, having nothing to do with the file. THe 9060 error, I believe, is the error you get from the Beta 32 track DAE engine. Restart your mac, you may be happy after that.

THere are ways to get the file back.
For example... importing the need tracks to another session, and other methods.
Let us know if anything works.