2 Simultaneously connected fw800 red drives autoeject issue

[Alexander Alexandrov]

I have a mac pro 2008 late generation. when i connect 2 red drives simultaneously via fw800 (one to back port and the other to the front port) i get a message of "your drive wasn't ejected properly".

if one of the drives was able to mount while the 2nd one is still initializing, it will unmount shortly after.

after this message, the only way to mount any of the red drives again at least individually is to reboot the system.

i've tried mounting via fw800 a red drive and any other non-red drive like (g-raid, g-tech etc.) together, and it works just fine. only when 2 red drives are connected at the same time i get this issue. (occurs on red drives from different jobs).

i also tried this: connecting a red drive to 1 fw800 port, connecting a gdrive to another fw800 port and then connecting a 2nd red drive to gdrive's 2nd fw800 port. same eject issue occurs with red drives, bud gdrive stays mounted.

any thoughts?

[Tony Lorentzen]

Always, always, ALWAYS make sure you connect the RED Drive power supply before connecting the drive to the computer. You're basically drawing too much power from the FW800 bus and the port is being shut down until you restart to protect it from power surges.

[Alexander Alexandrov]

thanks Tony. will give it a try.

[Gunleik Groven]

Connecting 2 red drives to the same FW bus have never worked for me. Seems they share the same logical address so they will cancel eachother out - with or without AC adaptors.

[Alexander Alexandrov]

it didn't work for me with 1 power adapter. will find 2nd one and try again, but i also suspect it's more than power.

[ericyoung]

This issue has come up before, and more than one REDdrive can't be mounted at the same time on FW800 at least. Never tried USB as it's so slow.

[Gunleik Groven]

One with USB + one with FW will work, or connecting via network and another Mac.

G

[Michael Romano]

Have the same issue on the MacPro. Workaround: Used gigabit ethernet to connect to a laptop with FW800. It must be an addressing issue, the power supply seems to have no bearing on dis-functionality in this instance.