cancel
Showing results for 
Search instead for 
Did you mean: 

BESR corrupts file system on RDX Drive - Cannot Backup

aychekay
Level 5
Partner

BESR 8.5 attempts to backup to the RDX cartridge but appears to corrupt the RDX cartridge and then the backup job fails with an error.

 

BESR starts to backup to the RDX drive then fails and logs the following error:

Info 6C8F1C2F: A recovery point operation on drive Drive Backup of (C:\) was cancelled by the user. Error ED800013: Operation cancelled by user. Error ED800017: The media is write protected or otherwise unwritable. Details: the operation was canceled by the user.

 

On closer inspect I find that the following errors were logged in the Windows Event Viewer during the attempted backup operation:

Event ID: 57 - Source: symsnap - Description: The system failed to flush data to the transaction log. Corruption may occur.

 

After the above error we are seeing the following errors in the event viewer:

Event ID: 51 - Source: disk - Description: An error was detected on device\Device\Harddisk1\DR1 during a paging operation.

Event ID: 57 - Source: volmgr - Description: The system failed to flush data to the transaction log. Corruption may occur.

Event ID: 55 - Source: Ntfs - Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume.

 

 

Hardware/Software:

HP ML350 G5 Server

Small Business Server 2008

BESR 8.5.0.28843

Tandberg Data RDX Drive plugged into a Promise SATA300 TX4 Card

5 REPLIES 5

Jacob_A
Level 6
Employee
Please see if the following article helps with the issue: http://support.veritas.com/docs/315695

aychekay
Level 5
Partner
Does not apply. GUI doesn't hang until you install SP1 and currently we can't install SP1 on BESR 8.5 on SBS 2008.

aychekay
Level 5
Partner
OK, it appears that this problem is caused by a compatibility issue between the RDX drive and the Promise SATA300 controller. We will be testing a different SATA controller in a few days.

aychekay
Level 5
Partner
We have solved this problem by using SIL 3114 chipset SATA controllers with all SATA RD1000 and RDX Drives we install.

Jacob_A
Level 6
Employee
I'm glad you were able to correct the issue.