karma Posted April 21, 2010 Report Share Posted April 21, 2010 Starting last night, Retrospect is giving me "Trouble matching (Volume) to (Catalog), error -36 (i/o error, bad media?)" for all connected networked volumes. This is being backed up onto a 2 TB desktop hard drive via firewire, to a file set. The backup file is about 980 GB at this point, and the catalog is about 2.04 GB. - The destination drive has been verified with Apple Disk Tools. - it is a 2 TB Iomega UltraMax (non-removable), FireWire - formatted Mac OS Extended (Journaled), Partition scheme: Apple Partition Map - 981 GB used, 881 GB available - Several of the source hard drives have been verified as well, but since anything on the network does it, not a likely part of the problem. === Specs ================================ Retrospect 6.1.230; driver update 6.1.15.101 Mac Clients: 6.2.234 Windows Clients: 7.6.107 - Main machine: MacPro Quad (2 x 3.0 Ghz Dual-Core Intel Xeon) OS X 10.4.11, 12 GB RAM ========================================= From the log: + Normal backup using House 101 at 4/21/2010 3:32 PM To backup set UltraMax(2TB)2-123009… - 4/21/2010 3:32:45 PM: Copying House101 on Iomega 400GB 3… Trouble matching House101 on Iomega 400GB 3 to UltraMax(2TB)2-123009, error -36 (i/o error, bad media?). I ran a normal backup on the above volume again just to watch what happens. It starts matching files, gets up to "matched 231 of 330 sessions..." - and then stops with the above error. The main machine backed itself up (to the same set) with no problems; just networked volumes all fail with the same error. I tried shutting down and restart the router that the main machine is connected to, still does the same thing. Any ideas? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted April 22, 2010 Report Share Posted April 22, 2010 Repair the catalog file: Tools-->Repair. Quote Link to comment Share on other sites More sharing options...
karma Posted April 22, 2010 Author Report Share Posted April 22, 2010 Thanks for the reply - I was reading about that in the help, and it only said to use it if having catalog sync issues (which I didn't have). ? I'm presently in the middle of running a Verify on it which looks like it could take many more hours.... Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted April 22, 2010 Report Share Posted April 22, 2010 The help says: "You cannot use a backup set unless it has a catalog file, so you should rebuild the catalog whenever the original catalog file is lost or damaged." It seems as your catalog file is damaged. Quote Link to comment Share on other sites More sharing options...
karma Posted April 25, 2010 Author Report Share Posted April 25, 2010 OK, so I finished a Verify. It took more than 24 hours. It told me: + Executing Verify at 4/21/2010 10:51 PM To backup set UltraMax(2TB)2-123009… Can't load source session tree for 4/20/2010 6:42 AM, error -36 (i/o error, bad media?). Can't save catalog, error -36 (i/o error, bad media?). Couldn't verify 7433 files due to missing or incomplete media. 4/22/2010 7:34:14 AM: Execution incomplete. Remaining: 7433 files, 5.1 GB Completed: 3661415 files, 974.5 GB Performance: 1917.7 MB/minute Duration: 08:40:18 So I decided to rebuild the catalog. This took at least 30 hours. Then I got this: + Executing Recatalog at 4/22/2010 1:58 PM To backup set UltraMax(2TB)2-123009… Can't save catalog, error -24201 (chunk checksum didn't match). 4/23/2010 10:40:38 PM: 1 execution errors. Completed: 3668848 files, 979.5 GB Performance: 511.1 MB/minute Duration: 32:42:05 It says "can't save catalog", but then it finished, and the catalog is indeed there. So I tried backing up one volume to it. No problems. Then I tried a few more. Now I am getting: - 4/24/2010 5:08:15 PM: Copying Office G4-1 on Office G4… Trouble matching Office G4-1 on Office G4 to UltraMax(2TB)2-123009, error -24201 (chunk checksum didn't match). 4/24/2010 5:26:49 PM: Execution incomplete. Total performance: 278.9 MB/minute with 39% compression Total duration: 01:05:18 (00:42:44 idle/loading/preparing) So now I am getting these "chunk checksum didn't match" errors. What do I do, rebuild the catalog again for another 30+ hours? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 26, 2010 Report Share Posted April 26, 2010 -36 error usually means a bad block on a hard disk. You need to run a Disk check on the drive and check for problems. Quote Link to comment Share on other sites More sharing options...
karma Posted April 26, 2010 Author Report Share Posted April 26, 2010 Thanks, but error -36 also happens when drives simply aren't online, and as I mentioned, I already ran Apple's DiskRepair utility on it and the disk is fine. And I'm now getting a different error as mentioned above. Quote Link to comment Share on other sites More sharing options...
twickland Posted April 26, 2010 Report Share Posted April 26, 2010 Thanks, but error -36 also happens when drives simply aren't online...Are you referring to your source drives here? If, as I suspect, you have a problem with the volume on which your destination file backup set and its companion catalog are stored, that volume would have to be mounted for you to be able to access the backup set. Please clarify what you mean by drives not being online. Retrospect pushes hardware to the max. It will often reveal problems with a failing hard drive long before Disk Utility detects any problems. Quote Link to comment Share on other sites More sharing options...
karma Posted April 26, 2010 Author Report Share Posted April 26, 2010 Thanks' date=' but error -36 also happens when drives simply aren't online...[/quote']Are you referring to your source drives here? If, as I suspect, you have a problem with the volume on which your destination file backup set and its companion catalog are stored, that volume would have to be mounted for you to be able to access the backup set. Please clarify what you mean by drives not being online. What I meant was: for example, I have a subvolume created on a Windows Client that holds Mac files. If I don't have the client actually mounted on the main machine (Mac) during backup, then when it tries to back up this sub-volume, it will say: Can't access volume KARMA Backup on XP HARD DRIVE, error -36 (i/o error, bad media?). 4/25/2010 9:47:35 AM: Execution incomplete. Total duration: 00:12:02 (00:10:34 idle/loading/preparing) This is clearly unrelated to any bad media. It just can't find the sub-volume. Retrospect pushes hardware to the max. It will often reveal problems with a failing hard drive long before Disk Utility detects any problems. These are fairly new drives (less than a year old). Anyway, where does that leave me then? It might possibly be an undetectable hard drive issue revealed by Retrospect's hard use? Or just a general problem with Retrospect (every day it's something with this software.) I guess I'll try rebuilding the catalog again - another 30 hours+. Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted April 27, 2010 Report Share Posted April 27, 2010 -36 error usually means a bad block on a hard disk. You need to run a Disk check on the drive and check for problems. as I mentioned, I already ran Apple's DiskRepair utility on it and the disk is fine. Apple's Disk Utility will NOT check for bad blocks. It will only check for disk catalog consistency. You will need something like TechTool Pro to check for bad blocks. Quote Link to comment Share on other sites More sharing options...
twickland Posted April 27, 2010 Report Share Posted April 27, 2010 ...when it tries to back up this sub-volume, it will say: Can't access volume KARMA Backup on XP HARD DRIVE, error -36 (i/o error, bad media?). I haven't seen a -36 error under those circumstances; it's typically either a -53 (volume off-line) or -35 (volume doesn't exist) error. However, note the difference in lead-in ("Can't access volume..." vs. "Trouble matching..." or "Can't save catalog..."). These latter errors would seem to be referencing the volume that holds the catalog and file backup data. I think you'll find that your destination volume is failing. Quote Link to comment Share on other sites More sharing options...
karma Posted April 29, 2010 Author Report Share Posted April 29, 2010 Alright, thanks for the advice, I've ordered TechTool Pro, I'll see what it says and get back to this... Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.