Event Log: Adamm Mover Error: Read Retry!

All,

I have this error on the event log from last nites back up.
I cannot find any specific reference to this type error ANYWHERE.
Well anyways today I think it maybe needing cleaning.
We'll see if this error is still on tomorrow.

My hardware doesnt inform me when it needs cleaning. How do I get the hardware to message it needs cleaning. My old drive had an LCD screen that displays it needs cleaning.

Anyways:
Windows Server Machines 2000AS
Back Up 9.0
PowerVault 110t 320 drive using SDLT tapes.
Thanks
Joe
Event Type:Warning
Event Source:Backup Exec
Event CategorySmiley Very Happyevices
Event ID:33152
Date:5/11/2005
Time:8:14:48 AM
User:N/A
Computer:
Description:
Adamm Mover Error: Read Retry!
Error = ERROR_INVALID_FUNCTION
Drive = "DELL 1"
{E87560BC-3B50-4CD8-9167-2E13FD24EE27}
Media = "DLT000009"
{1BCDDE56-F994-40CB-98A4-3DFC42FA4B5A}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Data:
0000: 00 00 00 00 00 00 00 00 ........
0008: 00 00 00 00 00 00 ......
8 Replies

Re: Event Log: Adamm Mover Error: Read Retry!

Hi,

You can deactivate write Single Block Mode.

Also ensure that you are not getting event IDs 7,9, 11, 15 on your SCSI card in system Logs. Check if you have updated the SCSI firmware. Ensure that the Removable Storage Service is stopped, it should be deactivated.

How to Troubleshoot Event 9 and Event 11 Error Messages

http://support.microsoft.com/default.aspx?scid=kb;en-us;154690

Hopefully this helps you resolve the issue. Cleaning the device atleast once in a week is recommended.

NOTE : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Re: Event Log: Adamm Mover Error: Read Retry!

My problem still havent been solved. What are the typical solutions? -besides upgrading and the ones you mentioned.

Thanks

Re: Event Log: Adamm Mover Error: Read Retry!

Hi,

For cleaning Job please refer the Technote given below :

How to configure and submit cleaning jobs for autoloaders in Backup Exec 9.x and 10.0 for Windows Servers
http://seer.support.veritas.com/docs/257265.htm

Have you installed the latest Veritas device drivers?

Have you checked that are there any event IDs 7,9, 11, 15 on your SCSI card in system Logs. Check if you have updated the SCSI firmware. Ensure that the Removable Storage Service is stopped, it should be deactivated.

-----------------------------------------------------------------------
Additional Information:

If you are not at the latest build of Backup Exec 9.1 for Windows Servers
revision 4691, we would suggest you download and install it using the
following technotes:


http://seer.support.veritas.com/docs/264658.htm


http://seer.support.veritas.com/docs/262414.htm

# BEWS 9.1 is a free downloadable upgrade inclusive of previously installed
agents and options from Backup Exec 9.0 for Windows Servers agents and
options.

# Update all agents/options on all remote systems.

----------------------------------------------------------------------
Thank you.

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.

Re: Event Log: Adamm Mover Error: Read Retry!

It is not an autoloader.
I have a no errors.
I have tried cleaning. I havent trying upgrading.
New errors on the log:

I have not found even id: 5 7 9 etc

Event Type:Error
Event Source:Backup Exec
Event CategorySmiley Very Happyevices
Event ID:33152
Date:5/24/2005
Time:12:25:13 AM
User:N/A
ComputerSmiley Very Happyescription:
Adamm Mover Error: Write Failure!
Error = ERROR_NO_MEDIA_IN_DRIVE
Drive = "DELL 1"
{E87560BC-3B50-4CD8-9167-2E13FD24EE27}
Media = "DLT000017"
{56F31B80-45E9-4C74-BF9A-DBEE1E8F8CD4}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Data:
0000: 70 00 02 00 00 00 00 16 p.......
0008: 00 03 1d 30 04 03 ...0..
Event Type:Error
Event Source:Backup Exec
Event CategorySmiley Very Happyevices
Event ID:33152
Date:5/24/2005
Time:12:25:13 AM
User:N/A
Computer: Description:
Adamm Mover Error: Write Not Ready Failure!
Error = ERROR_NO_MEDIA_IN_DRIVE
Drive = "DELL 1"
{E87560BC-3B50-4CD8-9167-2E13FD24EE27}
Media = "DLT000017"
{56F31B80-45E9-4C74-BF9A-DBEE1E8F8CD4}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(1), ScsiPass(1)
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:57665
Date:5/24/2005
Time:12:25:13 AM
User:N/A
ComputerSmiley Very Happyescription:
Storage device "DELL 1" reported an error on a request to write data to media.

Error reported:
No media in drive.
.

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Data:
0000: 58 04 00 00 d7 fd ff ff X...×ýÿÿ
0008: 00 00 01 00 00 00 00 00 ........
0010: 93 03 00 00 “...
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:34113
Date:5/24/2005
Time:12:30:07 AM
User:N/A
ComputerSmiley Very Happyescription:
Backup Exec Alert: Job Failed
(Server: "SYSEXCH") (Job: "Backup 0001") Backup 0001 -- The job failed with the following error: A communications failure has occurred between the Backup Exec job engine and the remote agent.


For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Please review. And see if you can help me.

Thanks

Re: Event Log: Adamm Mover Error: Read Retry!

I did a test run:

Completed status: Failed Expand AllCollapse All
Job Information
Server name : SYS
Job name : TestRun 0002
Job log : D:\Program Files\VERITAS\Backup Exec\NT\Data\BEX00730.xml
Device name :

Test Run Job Information
Credentials Check
Device : \\SYS, C:Check status : Success
Device : \\SYS, D:Check status : Success
Device : \\SYS, G:Check status : Success
Device : \\SYS, \\SYS\Microsoft Exchange MailboxesCheck status : Success
Device : \\SYS, \\SYS\Microsoft Exchange Public FoldersCheck status : Success
Device : \\SYS, \\SYS\Microsoft Information Store\First Storage GroupCheck status : Success
Device : \\SYS, \\SYS\Check status : SuccessDevice : \\SYS, \\SYSH\System?StateCheck status : Success
Device : \\PRO2, \\PRO2\Microsoft SharePoint Portal ServerCheck status : Success
Device : \\PRO2, \\PRO2\Microsoft SharePoint Portal Workspaces\ATTCheck status : Success
Device : \\PRO2, \\PRO2\Microsoft SharePoint Portal Workspaces\CAMSCheck status : Success
evice : \\PRO2, \\PRO2\Microsoft SharePoint Portal Workspaces\CorporateCheck status : Success
Device : \\PRO2, \\PRO2\Microsoft SharePoint Portal Workspaces\demoCheck status : Success
Device : \\PRO2, \\PRO2\Microsoft SharePoint Portal Workspaces\eReportsPortalCheck status : Success
Device : \\PRO2, \\PRO2\C:Check status : Success
Device : \\PRO2, \\PRO2\D:Check status : Success
Device : \\PRO2, \\PRO2\Check status : SuccessDevice : \\PRO2, \\PRO2\System?StateCheck status : SuccessDevice : \\SERVER1, \\SERVER1\C:Check status : Success
Device : \\SERVER1, \\SERVER1\D:Check status : Success
Device : \\SERVER1, \\SERVER1\E:Check status : SuccessDevice : \\SERVER1, \\SERVER1\G:Check status : Success
Device : \\SERVER1, \\SERVER1\Check status : Success
Device : \\SERVER1, \\SERVER1\I:Check status : Success
Device : \\SERVER1, \\SERVER1\System?StateCheck status : SuccessDevice : \\ACTIVE-DIR, \\ACTIVE-DIR\C:Check status : SuccessDevice : \\ACTIVE-DIR, \\ACTIVE-DIR\Check status : SuccessDevice : \\ACTIVE-DIR, \\ACTIVE-DIR\System?StateCheck status : Success
Device : \\ACTIVE-DIR2, \\ACTIVE-DIR2\C:Check status : Success
Device : \\ACTIVE-DIR2, \\ACTIVE-DIR2\System?StateCheck status : SuccessDevice : \\PROD, \\PROD\C:Check status : Error: ffffdfc4, The job failed.Device : \\PRO, \\PRO\Shadow?Copy?ComponentsCheck status : Error: a000848c, The job failed with the following error: Unable to attach to one of the drives.
Device : \\PRO, \\PRO\D:Check status : Error: a000848c, The job failed with the following error: Unable to attach to one of the drives.
Device : \\PRO, \\PRO\System?StateCheck status : Error: a000848c, The job failed with the following error: Unable to attach to one of the drives.


Media Capacity Check
Device : DELL 1Online append capacity : 1,330,593 MBOnline overwrite capacity: 2,661,900 MBTotal append capacity : 1,330,593 MBTotal overwrite capacity : 2,661,900 MBCapacity check status : Success
Miscellaneous :

Media CheckOnline media check : Media is online or nearline to start job.Overwrite media check: There is media online or nearline that can be overwritten.
Media check status : Success

Backup job name : Backup 0001 Test run status : Fail Media protection: Overwrite Target device : All Drives (SYS) Target media : Media Set 1
Total byte count: 181,191,720,960


Job Completion Status
Job started : Tuesday, May 24, 2005 10:21:21 AMJob ended : Tuesday, May 24, 2005 11:14:04 AMFinal error code: a0008703 HEXFinal error description: Job failed running its test run. See logfile for details.
Final error category: Job ErrorsCompleted status: Failed

Re: Event Log: Adamm Mover Error: Read Retry!

My question still having been answered.
Again I ask why isnt my backsoftware not backing up correctly for last 1 month.
1- deactivated the single SCSI
2- changed AOFO setting
3-Choose the NIC card.

My email server and the tape drive is on the same PE server with w2k and Veritas 9.0. The Tape drive is a PV 110t SDLT 320.

Sill my back up isnt becoming optimium.
Current error:
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:34113
Date:6/3/2005
Time:2:03:16 AM
User:N/A
ComputerSmiley FrustratedYS
Description:
Backup Exec Alert: Job Failed
(Server: "SYS") (Job: "Backup 0002") Backup 0002 -- The job failed with the following error: A communications failure has occurred between the Backup Exec job engine and the remote agent.

Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:57665
Date:6/3/2005
Time:2:00:25 AM
User:N/A
ComputerSmiley FrustratedYS
Description:
Storage device "DELL 1" reported an error on a request to write data to media.

Error reported:
No media in drive.

Event Type:Error
Event Source:Backup Exec
Event CategorySmiley Very Happyevices
Event ID:33152
Date:6/3/2005
Time:2:00:25 AM
User:N/A
ComputerSmiley FrustratedYS
Description:
Adamm Mover Error: Write Not Ready Failure!
Error = ERROR_NO_MEDIA_IN_DRIVE
Drive = "DELL 1"
{E87560BC-3B50-4CD8-9167-2E13FD24EE27}
Media = "DLT000025"
{11678EEF-2DDB-42B8-BA5C-62BEC0677AFE}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(0), ScsiPass(1)

Event Type:Error
Event Source:Backup Exec
Event CategorySmiley Very Happyevices
Event ID:33152
Date:6/3/2005
Time:2:00:25 AM
User:N/A
ComputerSmiley FrustratedYS
Description:
Adamm Mover Error: Write Failure!
Error = ERROR_NO_MEDIA_IN_DRIVE
Drive = "DELL 1"
{E87560BC-3B50-4CD8-9167-2E13FD24EE27}
Media = "DLT000025"
{11678EEF-2DDB-42B8-BA5C-62BEC0677AFE}
Read Mode: SingleBlock(0), ScsiPass(0)
Write Mode: SingleBlock(0), ScsiPass(1)
Data:
0000: 70 00 02 00 00 00 00 16 p.......
0008: 00 0c 5e 2e 04 03 ..^...

And no I dont have removable storage entries in the system log.

I have another quick note: In the services my Backup Exec Remote Agent for Windows Servers shows log on as LOcalSystem. Whereas the 4 for services for BackUp is under domain/administrator

Could this be the cause????????????????????

Please test it out and let me know.

Joe

Re: Event Log: Adamm Mover Error: Read Retry!

The problem is fixed. I replaced the tape drive.I updated the fireware and drivers.

Re: Event Log: Adamm Mover Error: Read Retry!

Since the issue is resolved marking this as assumed answered.