Jump to content

Firewire hard drive failure after backup crash


Recommended Posts

Hello. Having some problems here today.

 

 

 

Yesterday I installed Retrospect 5.0.205 on a machine (OSX 10.1.4 on a G3) to run as a backup server. I also installed a 20GB firewire Travan tape drive from Imation. The same server machine also runs other backups (using unix utilities like perl and rsync) onto a 60GB firewire hard drive from LaCie. These are scheduled every night at 3:30 am and pull data off several machines on our network.

 

 

 

I set up a test run of Retrospect to back up two other machines and the server itself onto the tape starting at 3:00 am, then logged out and went home.

 

 

 

Today when I came in I found several windows open on the screen although no one was logged in and the machine was hung with the spinning beach ball of death. We were even unable to ssh into it from another machine so I had to do a hard reboot. When it came back up I got an error message that it was unable to mount the firewire hard drive because it had no recognizable volumes. We tried the hard drive on another machine and got the same problem.

 

 

 

The backup tape seems to be okay (it verified), except that it did not get the final volume. It backed up the two remote machines and one of the local volumes before failing on the second one.

 

 

 

The retrospect log doesn't show anything interesting, just an entry for backing up the final volume, then six hours later it shows me starting up Retrospect after rebooting.

 

 

 

If anyone has thoughts on what would have toasted the hard drive I'd appreciate it.

 

 

 

Here's the end of the log file:

 

 

 

7/30/2002 6:26:16 AM: Connected to shiva

 

Resolved container shiva to 2 volumes:

 

Documents on shiva

 

Users on shiva

 

 

 

- 7/30/2002 6:26:18 AM: Copying Documents on shiva…

 

7/30/2002 6:27:01 AM: Comparing Documents on shiva…

 

7/30/2002 6:30:55 AM: Execution completed successfully.

 

Completed: 1340 files, 7076 KB, with 34% compression

 

Performance: 13.8 MB/minute (12.1 copy, 15.9 compare)

 

Duration: 00:04:37 (00:03:37 idle/loading/preparing)

 

 

 

- 7/30/2002 6:30:57 AM: Copying Users on shiva…

 

 

 

Retrospect version 5.0.205

 

launched at 7/30/2002 12:37 PM

Link to comment
Share on other sites

In reply to:

I set up a test run of Retrospect to back up two other machines and the server itself onto the tape

 

 

 

{snip}

 

 

 

The backup tape seems to be okay (it verified), except that it did not get the final volume. It backed up the two remote machines and one of the local volumes before failing on the second one.


 

 

 

Is the final/second volume the external firewire drive?

 

 

 

I seem to remember another thread on the Forum about backing up _from_ an external FW hard drive _to_ an external FW tape drive...

 

 

 

Can DiskUtility see/partition the firewire drive now?

 

 

Link to comment
Share on other sites

> Is the final/second volume the external firewire drive?

 

 

 

No. The tape backup shouldn't have looked at the firewire hard drive at all.

 

 

 

> Can DiskUtility see/partition the firewire drive now?

 

 

 

Yes. It does see it, but executing Verify tells me I have an Invalid Sibling Link. The repair option doesn't seem to help.

 

 

 

On the good side (sort of), Retrospect completed successfully last night. Maybe I need to move it to a machine with no other firewire accessories.

Link to comment
Share on other sites

I've been having problems with Retrospect locking up when working with external firewire drives; sometimes a crash would make the drive unreadable. Using Nortons on a different computer (OS9) could recover the drive; OSX Disk Utilities could not.

 

 

 

I'm pretty sure I had a bad HD, though. I replaced the HD, and haven't had the 'corrupts the HD' problem on a crash (although Retrospect still crashes more often than it works on a nightly basis).

 

 

 

I've got 3 external FW HD's, and I have "Duplicate" scripts that copy large amounts of data (well over 6Gb of .tar files from Unix utilites backing up our Linux servers) from one of the external drives to two other of the external drives. The original release of Retrospect (and earlier version of OSX) failed miserably at this, but the latest updates to OSX and Retrospect seem to have taken care of that problem.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...