[g8300]

S/W: Backup MyPC 5.0 (bought independently, then upgraded MyDVD which calls up Backup MyPC 5.0)

Msg: An error occurred while reading the media. The media cannot be read or contains an unknown media format. If the media contains valid data, please verify the device connections or try changing the device settings. Stream error (6146 1802)

Computer: Dell Inspiron 8300 3.4 GH, 1 GB, SB audigy etc., no recent device additions at change from error-free to faulting (verify) operation.

Additional H/W: Western Digital 400 GB SATA HD (to which I have been backing up since installation in Dec 2005, weekly, with no errors until Jan 2008).

OS: WinXP SP2

Consistent?: Yes, have attempted 4 full backups with same issue. S/W works as before (also as expected) up to verify operation (creates files, marks archived) then stops in the verify operation with the above message. Partial backup (limited set of files) backs up and verifies correctly.

Other applications (explorer, etc see this WD400GB drive with no issue).

Have verified HD Connectors (pwr and SATA) at HD and SATA at motherboard - no issues. Have not (knowingly) altered any device settings, and have not added any H/W devices at the transition from good backups (through Dec 2007) to recent bad verify backups starting in Jan 2008.

This post has been edited by g8300: 13 January 2008 - 11:07 PM

[marlinsinger]

S/W: Backup MyPC 5.0 (bought independently, then upgraded MyDVD which calls up Backup MyPC 5.0)

Msg: An error occurred while reading the media. The media cannot be read or contains an unknown media format. If the media contains valid data, please verify the device connections or try changing the device settings. Stream error (6146 1802)

Computer: Dell Inspiron 8300 3.4 GH, 1 GB, SB audigy etc., no recent device additions at change from error-free to faulting (verify) operation.

Additional H/W: Western Digital 400 GB SATA HD (to which I have been backing up since installation in Dec 2005, weekly, with no errors until Jan 2008).

OS: WinXP SP2

Consistent?: Yes, have attempted 4 full backups with same issue. S/W works as before (also as expected) up to verify operation (creates files, marks archived) then stops in the verify operation with the above message. Partial backup (limited set of files) backs up and verifies correctly.

Other applications (explorer, etc see this WD400GB drive with no issue).

Have verified HD Connectors (pwr and SATA) at HD and SATA at motherboard - no issues. Have not (knowingly) altered any device settings, and have not added any H/W devices at the transition from good backups (through Dec 2007) to recent bad verify backups starting in Jan 2008.

Have you tried reinstalling the standalone version? Sounds like something in the MyDVD version you got is out of whack.

[g8300]

Have you tried reinstalling the standalone version? Sounds like something in the MyDVD version you got is out of whack.

Took your suggestion, but this does not resolve the matter. I uninstalled BUMP, then reinstalled from original downloaded file. Nothing unusual about the installation.

I tried some other diagnostics.
(1) Split the whole backup task from one ~ 30 GB task to two ~15 GB tasks. Half being my documents/files, the other half being all of WinXP files excluding My Documents. These two ~15 GB backups execute correctly with completion of verification. Tried this scheme twice, same good results.

(2) Deleted all n/a excess residual Catalog files (some 50 old backups jobs I'd deleted, leaving some 10 jobs) then compressed. Was able to execute a near-complete backup (~29 GB) with completion of verification. (Near-complete meaning I excluded the temp directory and some program directories - otherwise a complete backup job selection.) Attempted a 2nd of same backup (saved same job with new name) and got errors in backup. Verify ended on an Acrobat file (AdobeFnt03.lst) "not found" on C: but I was able to find this same file with search in Explorer. Not sure if "not found" is an ancillary artifact of verify problem, or an indication the file on C: really wasn't found.

(3) Deleted all Browser temporary files. Seems to speed up BUMP and simple explorer operations. Ran Scan check on C: for disk errors (not syst file errors) with no corrections noted. However, I still get the verification error when I try to backup my whole C drive at once (~29 GB). Subsequent compare operation also fails at same file name "C:...\Temp\MSl6633b2.LOG. This file I do not find with an explorer search.

Verification errors do not seem to occur with consistency: not the same file shown as "processing" when the media error msg pops up, and these errors occur in ~20 and ~40 minutes into the verify ops. Maybe the file shown as "Processing" when BUMP hangs is not the file associated with the verification read error.

How best to diagnose from here? Thanks much

This post has been edited by g8300: 24 January 2008 - 10:05 PM

[marlinsinger]

Took your suggestion, but this does not resolve the matter. I uninstalled BUMP, then reinstalled from original downloaded file. Nothing unusual about the installation.

I tried some other diagnostics.
(1) Split the whole backup task from one ~ 30 GB task to two ~15 GB tasks. Half being my documents/files, the other half being all of WinXP files excluding My Documents. These two ~15 GB backups execute correctly with completion of verification. Tried this scheme twice, same good results.

(2) Deleted all n/a excess residual Catalog files (some 50 old backups jobs I'd deleted, leaving some 10 jobs) then compressed. Was able to execute a near-complete backup (~29 GB) with completion of verification. (Near-complete meaning I excluded the temp directory and some program directories - otherwise a complete backup job selection.) Attempted a 2nd of same backup (saved same job with new name) and got errors in backup. Verify ended on an Acrobat file (AdobeFnt03.lst) "not found" on C: but I was able to find this same file with search in Explorer. Not sure if "not found" is an ancillary artifact of verify problem, or an indication the file on C: really wasn't found.

(3) Deleted all Browser temporary files. Seems to speed up BUMP and simple explorer operations. Ran Scan check on C: for disk errors (not syst file errors) with no corrections noted. However, I still get the verification error when I try to backup my whole C drive at once (~29 GB). Subsequent compare operation also fails at same file name "C:...\Temp\MSl6633b2.LOG. This file I do not find with an explorer search.

Verification errors do not seem to occur with consistency: not the same file shown as "processing" when the media error msg pops up, and these errors occur in ~20 and ~40 minutes into the verify ops. Maybe the file shown as "Processing" when BUMP hangs is not the file associated with the verification read error.

How best to diagnose from here? Thanks much

I am beginning to think your catalog is becoming corrupt, especially since it occurs on different files that probably are not open, although the temp probably was as it looks like an install log. How many entries and how large is your catalog? I see different errors reported here and all seem to come back to the catalog, especially for those that have large catalogs. Save your catalog to another directory and try a full backup allowing it to start with a fresh one.
You also stated you cleaned up a bunch of entries. Did you also do a compact on the catalog after deletion?

[g8300]

I am beginning to think your catalog is becoming corrupt, especially since it occurs on different files that probably are not open, although the temp probably was as it looks like an install log. How many entries and how large is your catalog? I see different errors reported here and all seem to come back to the catalog, especially for those that have large catalogs. Save your catalog to another directory and try a full backup allowing it to start with a fresh one.
You also stated you cleaned up a bunch of entries. Did you also do a compact on the catalog after deletion?

Appreciate the quick reply.
1. >How many entries and how large is your catalog< Assuming these are the files in "BUMP\System\catalogs\primary" I have
catvset.dat 10kb, catvers.dat 81.198 kb, catmedm.dat 11kb, catgenr.dat 11 kb, catelem.dat 25,228 kb, catvset.idx 8 kb, catvers.idx 50876 kb,, catmedm.idx 8 kb, catgenr.idx 8 kb, catelem.idx 10604 kb. Nothing in directory tempca0. Up onE directory to "\Catalogs" I have these files: D0...fcs 1kb, L0...FCS 319 KB, S0...FCS 1 kb, and S0..1.FCS 1 KB.
1.1 prior to the catalog deletes and compact I performed in step (2) of my previous post, one of these files was a full 100MB, hence I was thinking (similarly to your thinking) that BUMP's catalog file exceeded some limit in the SW. Is there a limit on the catalog size?
2. >Save your catalog to another directory and try a full backup allowing it to start with a fresh one< Do you mean copy the files (for later use if necessary) to another directory -- and then just delete all the files in the directory "BUMP\System\catalogs\primary " and let BUMP create files in this directory? Or?
3. >you cleaned up a bunch of entries. Did you also do a compact on the catalog after deletion<
Yes, as I describe in 1.1 above, I compacted after the deletions prior to the good full backup. However, I don't believe I compacted prior to the subsequent full back up that did not verify.
Thank you very much for your help with this diagnosis.

[marlinsinger]

Appreciate the quick reply.
1.1 prior to the catalog deletes and compact I performed in step (2) of my previous post, one of these files was a full 100MB, hence I was thinking (similarly to your thinking) that BUMP's catalog file exceeded some limit in the SW. Is there a limit on the catalog size?

Unfortunately, only the developers probably know that. I can't say I ever had a 100MB catalog. Each time I did a backup I would do catalog cleanup as I would keep a series of 3 backups. So never more than 4 entries would be in the catalog at the same time. Also my total DR backups would only run about 15GB uncompressed. so I am assuming you have quite a few more files than I did. Each one of which will have a catalog entry.