Meridian Mail backup fails 1

[leatherneckdiver]

I have a MerMail 12.11, in a Option 61C, that fails backups either scheduled or manual. These are the SEER codes that I get:

11-49 6/04 10:37 Admin Inf 1 Null
Des: VS1 Starting on-line backup
66- 4 6/04 10:37 Error ** 1 Null
Act: Refer to DM Driver error checklist. Des: Disk 0 > driver error: 133
66- 4 6/04 10:38 Error ** 1 Null
Act: Refer to DM Driver error checklist. Des: Disk 0 > driver error: 133
15-35 6/04 10:38 Admin * 1 Null
Des: Error reading disk during backup VS1T near 658 1415

I have changed the tape drive, MMP40, & utility card and it continues to fail. Any thoughts on what else might be causing the backups to fail?

Also are the SCSI cables only on the tape & hard drive cards?

 

[GHTROUT]

I'd be looking at the hard drive as a possible problem.

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--

 

[leatherneckdiver]

In SEER 15-35 it says that:

15-35 6/04 10:38 Admin * 1 Null
Des: Error reading disk during backup VS1T near 658 1415

Cause: An error occurred reading the disk during a tape backup. The SEER reports the volume and block that could not be read.

Is the volume and block on the hard drive or tape drive? If it is on the hard drive, is there a way to recover or repair that block?

 

[GHTROUT]

There is a way to mark blocks bad on the hard drive, but I do not know it.. (I've had Nortel do it on a system years ago).

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--

 

[DFKSydney]

To mark the bad blocks, you need to get into the COBRA utilities etc. This is not a process for the faint hearted, and certainly not guaranteed.

There is a sundry issue in that if there are a huge amount of bad blocks, as you have to manually acknowledge the fault, it could take a long long time to go through the process

BUT...... theres no guarantee that the process is a fix.... reason is that it sounds as if the disk is failing.

COBRA utilities.... requires a password, and thats not for here.

 

[leatherneckdiver]

Turned out to be a bad tape drive and bad sectors on the hard drive. Thanks for your help.