I got a quice response from "Firmin, Julie" <Julie.Firmin@capita.co.uk>, so thank you for that. I just want to head this off -- we're currently working with Sun's storage support group, and through failing/reviving drives and identifying some faulty array ID settings, they're helping us through the problem, though it looks like we're going to lose the data on one dead LUN. Thanks again, -Adam On Tue, 24 Sep 2002, Adam and Christine Levin wrote: > We've got a situation here. We had something happen to a tray in an a3500 > -- the techs don't know what. However, in diagnosing the problem (the > LUNs just disappeared with I/O errors at the Solaris level), we tried > replacing the cables as suggested by Sun. > > Unfortunately, we pulled the cables in the *wrong* a3500. So, now, the > second a3500 is exhibiting the same problems. > > We shut down the machine and the array, we finished replacing cables, and > we brought the array back up. The machine came up, but there are all > kinds of errors from the array monitor. In Raid Manager, one of the LUNs > is listed as "dead", the other is "optimal". I tried reviving the dead > LUN, but it doesn't seem to have worked. > > Is there any way to get that LUN back after having pulled a SCSI cable off > the D1000 tray, or are we hosed such that we have to go back, reformat the > LUN, and restore data from tape? > > Thanks, > -Adam > _______________________________________________ > sunmanagers mailing list > sunmanagers@sunmanagers.org > http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Oct 3 17:16:09 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:55 EST