Veritas-bu

[Veritas-bu] Status Code 800 - HELP!

2006-07-24 10:21:23
Subject: [Veritas-bu] Status Code 800 - HELP!
From: simon.weaver at astrium.eads.net (WEAVER, Simon)
Date: Mon, 24 Jul 2006 15:21:23 +0100
No worries - I have arranged for a REBOOT of my Server this evening.

I can see the Hardware - just think it's a driver issue!

If you cannot get past the robot, then the OS wont see much :-(

Keep us all advised ok :-)

Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver at Astrium-eads.net



-----Original Message-----
From: Conner, Mike [mailto:MConner at imb.org] 
Sent: 24 July 2006 15:04
To: WEAVER, Simon
Subject: RE: [Veritas-bu] Status Code 800 - HELP!


That's strange that you are having the same issue.  I think we had a power
issue too.  The SCSI connections aren't valid and I've checked device
manager and rescanned for new hardware and it doesn't come up. The OS can't
see the drives...

We started your steps and can't get past the library...we get a fault code
4002 - I hope the library isn't fried.  I'm opening a call with overland to
find out what we can do to clear the fault.

Let me know how your situation goes, I'll let you know ours...if we can get
the fault code in the library fixed, then I can proceed because we don't
have to wait for down time.


-----Original Message-----
From: WEAVER, Simon [mailto:simon.weaver at astrium.eads.net] 
Sent: Monday, July 24, 2006 9:27 AM
To: Conner, Mike; veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Status Code 800 - HELP!


Hi Mike

SNAP !!!!!!!!! Guess what, have the SAME problem here too!!! I have been
working on this most of the morning.

Came in after a power outage, and 2 tape drives are not being seen by a SAN
Client, even though it can see another 2 drives without any problems.

What I have done so far:

1) Stopped all netbackup master services
2) Stopped SAN Media Services
3) Powered off Robot
4) Removed Power
5) powered on Robot and restarted
6) when its initial tests and online status appeared restarted NetBackup
Master Services
7) checked event logs
8) restarted SAN Media Services
9) checked event logs
10) checked Device Manager on one SAN Media Server as it was complaining it
could not see 2 drives (same errors as you have)
11) For some reason, Device Manager has "unknown" marked against 2 drives -
applied the correct drivers, but it wants a reboot!!

Trouble is, I cannot reboot this client until out of hours.

Basically, Netbackup has decided to lose all information about the drives -
you could try checking all the relevant hardware and verify all SCSI
connections are valid. Also, check device manager to be sure no other
devices are missing. Try scanning for new hardware too.

I am kind of thinking, that in my case (and yours) the devices were missing,
and MAY have come back, but not in a clean state. In my case, I have had to
reapply the drivers again!

If the OS CAN see your drives, then it could well be a NBU issue - but check
what the Windows Win2k3 can see first and go from there.

Its not nice, I know :-(



Regards

Simon Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver at Astrium-eads.net



-----Original Message-----
From: Conner, Mike [mailto:MConner at imb.org] 
Sent: 24 July 2006 14:12
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Status Code 800 - HELP!



Hi, we have Win2003, NBU 6 MP3.  Things have worked for a week and a half in
a very small environment, then all of a sudden we get status code 800 this
weekend on our backups.  When I go to device monitor and try to bring the
drives back up, we get the following error:

 

Unable to up the selected drive:  HP.ULTRIUM2-SCSI.000.

The drive is not ready or inoperable (277)

OK


The Library says something about shutting it down and bringing it back up,
but we do that and it does not help the situation.

 

When I go to drives in the Netbackup Console under Devices - Drives, the
Drive Path says Missing_drive:HUL4L01074 and Missing_drive:HUL4L01070 for
the other.

 

When I go to devices - robots and double-click the TLD robot, it brings up
the change robot, I click OK, and get the message: Device configuration
command </usr/openv/volmgr/bin/tpconfig -update -robot 0 -robtype tld -port
2 -bus 2 -target 6 -lun 0> failed on host No compatible device is registered
at these SCSI coordinates(51).


In event viewer, we get the following errors:
EventID 5691 - TLD(0) unavailable:  initialization failed: Unable to open
robotic path

EventID 5127 - TLD(0) (4536) Could not find SCSI coordinates {2,2,60} in the
registry

EventID 2747 - could not get drive path for drive HP.ULTRIUM2-SCSI.001
(device 1, SCSI coordinates MISSING_DRIVE:HUL4L01070)

What happened and what do we do?
Thanks!

Mike

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate
or otherwise deal with it. Please notify the sender by return email. The
views of the author may not necessarily constitute the views of Astrium
Limited. Nothing in this email shall bind Astrium Limited in any contract or
obligation.

Astrium Limited, Registered in England and Wales No. 2449259 Registered
Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or 
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of Astrium 
Limited.
Nothing in this email shall bind Astrium Limited in any contract or obligation.

Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England

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