This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C29969.12B060C0
Content-Type: text/plain
Since it's a boot -r issue, it might be a /kernel/drv/sd.conf file issue.
You might go check out of this file has been stomped on somehow or is still
appropriate for your new hardware layout.
I'd also drop it to the bios prompt and then:
setenv auto-boot? false
reset-all
probe-scsi-all
...and see if the device is visible from this level.
$.02,
-Mark
-----Original Message-----
From: Terry Newnham [mailto:terry.newnham AT showads.com DOT au]
Sent: Thursday, November 28, 2002 7:48 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Possible firmware issue
Hi
Had a nasty shock yesterday. I was adding some raid 5 boxes to our
Solaris 6 server. Naturally I had to do a "boot -r" to pick them up.
Although that part of the excercise was okay, the Netbackup daemons
would not start.
Checking of the logs revealed that Netbackup could not see one of the
optical drives. I had to remove that drive fron the configuration before
I could even get the device daemons to start. After that functionality
was okay, but I'm down a drive.
More than a month ago a service engineer came in and replace the same
drive. That drive had since worked okay, but the engineer upgraded the
firmware at the time. Though that upgrade didn't seem to affect things
then, the boot -r seems to have made it an issue. The device is not even
appearing at the UNIX level. The opticals are configured as hard drives.
But this drive not longer even appears under "format".
Getting the engineer back in to downgrade the firmware will be easy
enough, but I will need to reconfigure the drive as a hard disk.
Does all of this sound familiar to anybody. I'm only assuming that the
firmware caused all this trouble. Won't know until I've changed it back.
Terry
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C29969.12B060C0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Possible firmware issue</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Since it's a boot -r issue, it might be a =
/kernel/drv/sd.conf file issue. You might go check out of this =
file has been stomped on somehow or is still appropriate for your new =
hardware layout.</FONT></P>
<P><FONT SIZE=3D2>I'd also drop it to the bios prompt and then:</FONT>
<BR><FONT SIZE=3D2>setenv auto-boot? false</FONT>
<BR><FONT SIZE=3D2>reset-all</FONT>
<BR><FONT SIZE=3D2>probe-scsi-all</FONT>
</P>
<P><FONT SIZE=3D2>...and see if the device is visible from this =
level.</FONT>
</P>
<P><FONT SIZE=3D2>$.02,</FONT>
<BR><FONT SIZE=3D2>-Mark</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Terry Newnham [<A =
HREF=3D"mailto:terry.newnham AT showads.com DOT au">mailto:terry.newnham@showad=
s.com.au</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, November 28, 2002 7:48 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Possible firmware issue</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Hi</FONT>
</P>
<P><FONT SIZE=3D2>Had a nasty shock yesterday. I was adding some raid 5 =
boxes to our</FONT>
<BR><FONT SIZE=3D2>Solaris 6 server. Naturally I had to do a "boot =
-r" to pick them up.</FONT>
<BR><FONT SIZE=3D2>Although that part of the excercise was okay, the =
Netbackup daemons</FONT>
<BR><FONT SIZE=3D2>would not start.</FONT>
</P>
<P><FONT SIZE=3D2>Checking of the logs revealed that Netbackup could =
not see one of the</FONT>
<BR><FONT SIZE=3D2>optical drives. I had to remove that drive fron the =
configuration before</FONT>
<BR><FONT SIZE=3D2>I could even get the device daemons to start. After =
that functionality</FONT>
<BR><FONT SIZE=3D2>was okay, but I'm down a drive.</FONT>
</P>
<P><FONT SIZE=3D2>More than a month ago a service engineer came in and =
replace the same</FONT>
<BR><FONT SIZE=3D2>drive. That drive had since worked okay, but the =
engineer upgraded the</FONT>
<BR><FONT SIZE=3D2>firmware at the time. Though that upgrade didn't =
seem to affect things</FONT>
<BR><FONT SIZE=3D2>then, the boot -r seems to have made it an issue. =
The device is not even</FONT>
<BR><FONT SIZE=3D2>appearing at the UNIX level. The opticals are =
configured as hard drives.</FONT>
<BR><FONT SIZE=3D2>But this drive not longer even appears under =
"format".</FONT>
</P>
<P><FONT SIZE=3D2>Getting the engineer back in to downgrade the =
firmware will be easy</FONT>
<BR><FONT SIZE=3D2>enough, but I will need to reconfigure the drive as =
a hard disk.</FONT>
</P>
<P><FONT SIZE=3D2>Does all of this sound familiar to anybody. I'm only =
assuming that the</FONT>
<BR><FONT SIZE=3D2>firmware caused all this trouble. Won't know until =
I've changed it back.</FONT>
</P>
<P><FONT SIZE=3D2>Terry</FONT>
</P>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C29969.12B060C0--
|
