MP 1,1-5,1 cMP 3,1 external FW800 drive keeps ejecting - can't finish a TM backup. Any tips?

[brian.tully]

Hey there. I'm hoping someone might have some insights on how to debug this maddening problem. I'm using a cMP 3,1 and had been using a G-Drive FW drive for my Time Machine backups. It was working great for 5 years or so until it died a couple of months ago. I wound up immediately replacing it with an OWC Mercury Elite Pro because I can't handle not having a TM backup. The problem is that with the new drive I've had nothing but problems with it, where it would randomly eject itself. This led to data corruption and I wound up having to reformat the drive twice already. I was never able to complete a TM backup successfully. I gave up on that drive (another $350 down the drain) and recently ordered a Glyph Studio drive. I received it today and was immediately impressed by its build quality -- the thing is a brick **** house. I excitedly set it up on my computer and started a Time Machine backup, knowing full well that it was going to take a day or two to complete. I stepped away from the computer for a few hours, and came back to find the dreaded "disk was not ejected properly" error and the TM backup aborted.

Now I'm starting to think that maybe something is up with my cMP's Firewire 800 ports (I tried using both with similar results).

The real kicker was that I purchased a cMP 5,1 recently and I was hoping to use a TM backup to migrate all my apps/data over to the new computer so that I wouldn't have to reinstall (and authorize) everything from scratch.

I've made sure that "put hard disks to sleep when possible" is unchecked in Energy Saver preferences. I also switched Computer sleep from 3 hours to "Never". I also reinstalled Keep Drive Spinning.

Anyone have any other ideas as to how I can fix or debug this frequent "disk not ejected properly" error so that I can get a full TM backup?

Or is there another way for me to migrate my user and data over to the new Mac without using Time Machine backup?

Many thanks in advance!

Regards,
Brian

 

[KeesMacPro]

The real kicker was that I purchased a cMP 5,1 recently and I was hoping to use a TM backup to migrate all my apps/data over to the new computer so that I wouldn't have to reinstall (and authorize) everything from scratch.

Data migration to your "new" MP works fine with a TM backup or the "old" startup disk.
So a TM backup is not necessary for the migration.

Although I'm not sure what exactly causes the problem with TM backups and the "disk ejected" warning, you could consider making backups with CarbonCopyCloner.
CCC is so much faster in making a backup than TM and works very reliably ; I've been using it for years now and never had any issue.
You could give it a try ; it comes with a 30-day trial for free.

I realise I cant give you any clues about the FW issues you're experiencing (I stopped using FW years ago).
It could be related to the OS version installed IINM newer OSes don't (really) support FW anymore.
Perhaps others could chime in about this FW issue....

Most people install a USB 3.0/3.1 PCIe card and use that for faster data transfer speed.

 

[Soba]

Hey there. I'm hoping someone might have some insights on how to debug this maddening problem. I'm using a cMP 3,1 and had been using a G-Drive FW drive for my Time Machine backups. It was working great for 5 years or so until it died a couple of months ago. I wound up immediately replacing it with an OWC Mercury Elite Pro because I can't handle not having a TM backup. The problem is that with the new drive I've had nothing but problems with it, where it would randomly eject itself. This led to data corruption and I wound up having to reformat the drive twice already. I was never able to complete a TM backup successfully. I gave up on that drive (another $350 down the drain) and recently ordered a Glyph Studio drive. I received it today and was immediately impressed by its build quality -- the thing is a brick **** house. I excitedly set it up on my computer and started a Time Machine backup, knowing full well that it was going to take a day or two to complete. I stepped away from the computer for a few hours, and came back to find the dreaded "disk was not ejected properly" error and the TM backup aborted.

Now I'm starting to think that maybe something is up with my cMP's Firewire 800 ports (I tried using both with similar results).

The real kicker was that I purchased a cMP 5,1 recently and I was hoping to use a TM backup to migrate all my apps/data over to the new computer so that I wouldn't have to reinstall (and authorize) everything from scratch.

I've made sure that "put hard disks to sleep when possible" is unchecked in Energy Saver preferences. I also switched Computer sleep from 3 hours to "Never". I also reinstalled Keep Drive Spinning.

Anyone have any other ideas as to how I can fix or debug this frequent "disk not ejected properly" error so that I can get a full TM backup?

Or is there another way for me to migrate my user and data over to the new Mac without using Time Machine backup?

Many thanks in advance!

Regards,
Brian

There are many possible causes, but I would try a different cable and Firewire port, if you have not done so already. It's possible the Mac itself has developed a hardware problem; it is almost 14 years old!

Since you have a new Mac, I recommend setting up the new system and then transferring your data from the old Mac using Migration Assistant. You can directly connect the two Macs together using a standard network cable or have them connected to the same wired network with a switch. (Wi-Fi technically works, but is not as reliable for this process and I don't recommend it.) You do not need a Time Machine backup to accomplish this; all you need is for the 3,1 to also be powered on and connected to the same network.

On your 5,1, I strongly recommend doing a clean install of macOS and then importing your data when the installer prompts you. It is possible to migrate after the system is installed, but this can create confusion with user accounts and is not as seamless.

I also suggest checking out the following threads for tips on getting it updated to the latest BootROM and other handy upgrades.

MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)

Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...

forums.macrumors.com

cMP {classicMacPro}{4,1 & 5,1} - Upgrade Guide Sticky Discussion

Hey Folks, Lets start a discussion and collect everything relevant for cMP upgraders out there. Topics to consider: CPU Upgrades Compatibility chart CPU Delid / standoffs 4,1 to 5,1 firmware upgrade Memory Compatibility and Upgrades UDIMM Model Numbers RDIMM Model Numbers RAM...

forums.macrumors.com

Regarding your 3,1, I quickly glanced at some of your older posts on the forum and it looks like you were at one point trying to do some patching to get the 3,1 to run a recent macOS. Nothing wrong with this at all, but it's possible your system is in an unknown or unsupported state and this might be contributing to your Firewire woes. When you have your 5,1 up and running with your data successfully migrated over, and after you also have a successful Time Machine (or other) backup of your new 5,1, I suggest wiping out your 3,1 and doing a clean install of a supported version of macOS, then troubleshooting from that point.

 

[brian.tully]

There are many possible causes, but I would try a different cable and Firewire port, if you have not done so already. It's possible the Mac itself has developed a hardware problem; it is almost 14 years old!

Since you have a new Mac, I recommend setting up the new system and then transferring your data from the old Mac using Migration Assistant. You can directly connect the two Macs together using a standard network cable or have them connected to the same wired network with a switch. (Wi-Fi technically works, but is not as reliable for this process and I don't recommend it.) You do not need a Time Machine backup to accomplish this; all you need is for the 3,1 to also be powered on and connected to the same network.

On your 5,1, I strongly recommend doing a clean install of macOS and then importing your data when the installer prompts you. It is possible to migrate after the system is installed, but this can create confusion with user accounts and is not as seamless.

I also suggest checking out the following threads for tips on getting it updated to the latest BootROM and other handy upgrades.

MP5,1: What you have to do to upgrade to Mojave (BootROM upgrade instructions thread)

Please fully read this first post, you will probably find that you have one or more problems described into the various notes below. Mojave will only install if you have upgraded your BootROM to the current release and your Mac Pro have a Metal capable GPU*. If you are trying to install Mojave...

forums.macrumors.com

cMP {classicMacPro}{4,1 & 5,1} - Upgrade Guide Sticky Discussion

Hey Folks, Lets start a discussion and collect everything relevant for cMP upgraders out there. Topics to consider: CPU Upgrades Compatibility chart CPU Delid / standoffs 4,1 to 5,1 firmware upgrade Memory Compatibility and Upgrades UDIMM Model Numbers RDIMM Model Numbers RAM...

forums.macrumors.com

Regarding your 3,1, I quickly glanced at some of your older posts on the forum and it looks like you were at one point trying to do some patching to get the 3,1 to run a recent macOS. Nothing wrong with this at all, but it's possible your system is in an unknown or unsupported state and this might be contributing to your Firewire woes. When you have your 5,1 up and running with your data successfully migrated over, and after you also have a successful Time Machine (or other) backup of your new 5,1, I suggest wiping out your 3,1 and doing a clean install of a supported version of macOS, then troubleshooting from that point.

Thank you @Soba ! I forgot that Migration Assistant works over the network and/or over an ethernet cable connected between two Macs. I think that is my best bet. Thanks for suggesting the clean install and import!

 

[Soba]

Thank you @Soba ! I forgot that Migration Assistant works over the network and/or over an ethernet cable connected between two Macs. I think that is my best bet. Thanks for suggesting the clean install and import!

Good luck! Let us know how it goes.