Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
AEBS sucks
- Thread starter cube
- Start date
- Sort by reaction score
Wrong forum. You would probably get better results having your thread moved to the Mac peripherals forum.
However, if you’ve already tried restoring the firmware it’s probably the drive.
For example, my WD external USB doesn’t play well with the AirPort Base Station. I ended up taking the drive out of the WD external case and bought a ThermalTake SATA toaster (like $40 on Amazon).
Works fine now. The AirPort can even power up and down the drive.
I know it is just anecdotal, but we have the same exact router in our house.
We have 2 White 17" C2D Intel iMacs, 1 Alu 20" C2D Intel iMac, 1 C2D Mac mini, 1 G4 Mac mini (wired, which shares an 802.11G connection to the AppleTV, Wii and 5 iPod touch through the built-in Airport) all running through the router.
We have This Drive attached to the router and have not had a single issue. Each computer has their own space and we share a common space.
I routinely recommend the router based on my experience with it. I wish you were having a better experience with it!
We have 2 White 17" C2D Intel iMacs, 1 Alu 20" C2D Intel iMac, 1 C2D Mac mini, 1 G4 Mac mini (wired, which shares an 802.11G connection to the AppleTV, Wii and 5 iPod touch through the built-in Airport) all running through the router.
We have This Drive attached to the router and have not had a single issue. Each computer has their own space and we share a common space.
I routinely recommend the router based on my experience with it. I wish you were having a better experience with it!
The Oxford chipsets are among the best.
Have you tried any other drive?
Dumb question, but you’re not trying to connect your drive to both the USB on the AirPort and another interface like FW400/800 on your Mac at the same time?
If not, I would call Apple and get it swapped out. We have the same device and other than the WD drive, I haven’t had any problems.
It may actually be your AirPort hardware. Apparently, firmware 7.5.1 is shipping on newer base stations and Time Capsules but hasn’t been released to the public by Apple yet.
Have you tried any other drive?
Dumb question, but you’re not trying to connect your drive to both the USB on the AirPort and another interface like FW400/800 on your Mac at the same time?
If not, I would call Apple and get it swapped out. We have the same device and other than the WD drive, I haven’t had any problems.
It may actually be your AirPort hardware. Apparently, firmware 7.5.1 is shipping on newer base stations and Time Capsules but hasn’t been released to the public by Apple yet.
Why don't you just run 7.3.2 ?
None of the 7.4.x versions has ever worked reliably with my Drobo. 7.3.2 has been rock solid.
Do you think it is a power saving issue that is causing the disconnect or will the drive disconnect when in use?
Have you tried a powered hub to add a layer of abstraction from the AEBS to see if it is the drive chipset that is causing the disconnect?
Have you tried a powered hub to add a layer of abstraction from the AEBS to see if it is the drive chipset that is causing the disconnect?
I had a NewerTech V3 enclosure with a 1TB drive that I was using attached to a AEBS, and it kept disconnecting. I ended up attaching it directly to my Mac using USB (I'd mislaid the FW cable, was using it for backup so didn't need FW speeds).
Then it started disconnecting from the Mac after a couple of hours being attached. So I bought a FW cable and everything was rosy for a few months. Then it wouldn't stay connected to any computer, Mac or PC, via any connection. Eventually, I had to discard the case. I put the drive into another enclosure and attached it to the AEBS and have had no problems ever since.
So your problem could be the case.
That made things even worse. The disk was disconnecting and reconnecting all the time while playing iTunes. I shut down the computer and even then the disk got corrupted in maybe the worst way so far: not even the disk name would appear when connecting it for repair (but it could be repaired with DiskWarrior).