 |
 |
Can't hook up second firewire drive
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Jul 2005
Status:
Offline
|
|
Hi,
I've been trying to do a backup of a dying drive. Got a second firewire enclosure and slapped in a 120GB drive that used to be the boot drive of my Beige G3.
Since the Mini only has one firewire port, I have to daisychain it on the other firewire external.
But it's not coming up on the desktop or seen in Disk Utility. Could it be the jumper settings on the second (Western Digital) drive that are blocking that?
I thought once you hooked up to firewire, the jumper issue didn't matter.
Thanks for any help.
|
|
|
| |
|
|
|
|
|
|
|
Mac Enthusiast
Join Date: Nov 2005
Location: New York City
Status:
Offline
|
|
Does the drive show up when it's the only drive in the chain?
Try changing the jumpers. It can't hurt...
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Oct 2005
Location: Houston, TX
Status:
Offline
|
|
I've seen this before with some cheap enclosures that all had the same firewire ID (they should be unique).
|
|
|
| |
|
|
|
|
|
|
|
Admin Emeritus  Join Date: Oct 1999
Location: Zurich, Switzerland
Status:
Offline
|
|
FireWire devices are automatically enumerated by the bus -- they aren't hard-coded.
As for jumpers... the jumpers matter within the case. Get that new drive working externally on its own, then troubleshoot it working/not working daisy-chained.
tooki
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Oct 2005
Location: Houston, TX
Status:
Offline
|
|
Originally Posted by tooki
FireWire devices are automatically enumerated by the bus -- they aren't hard-coded.
I'll see if I can dig up the thread (it was in this forum). Some guy had two enclosures with the same ID, so he couldn't chain them with each other.
edit: I can't find the old thread, perhaps I'm imagining things.
(Last edited by mduell; Dec 27, 2005 at 07:01 PM.
)
|
|
|
| |
|
|
|
|
|
|
|
Admin Emeritus Join Date: Oct 1999
Location: Zurich, Switzerland
Status:
Offline
|
|
FireWire device IDs are generated on the fly -- there is no way for the device nor the user to set them. Device IDs plain and simply could not have been the source of the problem.
tooki
|
|
|
| |
|
|
|
|
|
|
|
Posting Junkie
Join Date: Oct 2005
Location: Houston, TX
Status:
Offline
|
|
Originally Posted by tooki
FireWire device IDs are generated on the fly -- there is no way for the device nor the user to set them. Device IDs plain and simply could not have been the source of the problem.
From the Wikipedia:
All FireWire devices are identified by an IEEE EUI-64 unique identifier (an extension of the 48-bit Ethernet MAC address format) in addition to well-known codes indicating the type of device and protocols it supports.
I believe it was that ID that was being duplicated (all of the enclosures were flashed with the same ID) in the cheap enclosures that another user was having trouble with.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top
