ADSM-L

Re: ANS1289W - bad areas on disk

2005-06-20 10:40:12
Subject: Re: ANS1289W - bad areas on disk
From: "Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 20 Jun 2005 09:39:59 -0500
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
Behalf Of Matthew Large
>We had an image backup failure over the weekend. The schedule 
>started as
>it normally does at 08:30am, but it was stopped a few hours 
>later (he had
>expected it to use two drives), so he updated the schedule to 
>start a few
>minutes later. it started again, and failed with these messages in the
>dsmerror.log
>
>It's the ANS1289W's that I'm interested in.
>
>18-06-2005 10:16:47 sessSendVerb: Error sending Verb, rc: -50
>18-06-2005 10:16:47 sessSendVerb: Error sending Verb, rc: -50
>18-06-2005 10:16:47 ANS1017E (RC-50)  Session rejected: TCP/IP 
>connection
>failure
>18-06-2005 10:16:47 ANS1424W Retrying failed image operation for volume
>\\tsml902a\f$.
>18-06-2005 10:16:59 sessSendVerb: Error sending Verb, rc: -50
>18-06-2005 10:16:59 sessSendVerb: Error sending Verb, rc: -50
>18-06-2005 10:17:01 ANS1228E Sending of object '\\tsml902a\f$' failed
>18-06-2005 10:17:01 ANS1017E Session rejected: TCP/IP 
>connection failure
>
>18-06-2005 10:17:01 ANS1813E Image Backup processing of '\\tsml902a\f$'
>finished with failures.
>
>18-06-2005 10:37:28 ANS1289W Bad areas on '\\tsml902a\f$' 
>between sectors
>0:8b0bea8 and 0:8b0c0a7
>[snip]
>18-06-2005 10:37:42 ANS2026W Bad sectors were detected on the volume
>'\\tsml902a\f$'.
>18-06-2005 10:37:42 ANS1425W Retry of failed image operation for volume
>\\tsml902a\f$ is not possible due to severe error.
>18-06-2005 10:37:44 ANS1228E Sending of object '\\tsml902a\f$' failed
>18-06-2005 10:37:44 ANS1069E An error occurred while reading 
>data from the device
>
>This is a 2TB disk and so far I've been unable to convince the 
>sysadmins
>that they should run a some kind of disk check before trying to run the
>backup again.

Making an educated WAG here, but I'd say that the drop in communication
(rc: -50) between the client and server is more likely the source of
your problem, rather than bad disk sectors. Image backups are very
sensitive to interruptions in the data stream. Try the image backup
again.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
  Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Office 262.521.5627

 

<Prev in Thread] Current Thread [Next in Thread>