summary: solaris 8 disk replacement

Thanks to the couple of folks who replied.
The jbod array is semi-intelligent and likes to assign it's own scsi ids 
to certain slots. This isn't working correctly.
I rebooted the jbod.
I now have my new ultra-320 drive with an id of 15 where it should have an 
id of three.  I can label the disk but can seem to get disksuite to write 
to it.
I'm going to chalk this up to an incompatible replacement drive and move 
on to plan b... rooting around in my spares and finding a good used drive 
as a replacement.


MIchael Horton <i75.bjc@gmail.com> wrote on 03/10/2010 12:56:28 PM:

> MIchael Horton <i75.bjc@gmail.com> 
> 03/10/2010 12:56 PM
> 
> To
> 
> DRoss-Smith@reviewjournal.com
> 
> cc
> 
> Subject
> 
> Re: solaris 8 disk replacement
> 
> you wrote, "killed the scsi bus"
> now the OS doesn't recognize a new disk.
> 
> in troubleshooting, go from the easiest to the hardest.
> 
> try a known good hard drive.  (a new drive is not a known good drive.)
> try an actual reconfiguration reboot.
> check to see if the new hard drive is seen at the boot prom level 
> (ok> prompt)?
>   if it isn't you have a hardware problem and maybe a real failure.
>   if it is and the reconfiguration doesn't fix it, you have an OS 
> subsystem failure.
> 
> On Wed, Mar 10, 2010 at 1:30 PM, <DRoss-Smith@reviewjournal.com> wrote:
> Hi all-
> It's been a while since I've had to do this...
> I've had a 420r chugging along running solaris 8 and sybase 11 on a
> mirrored jbod for many years.  It had uptime of 3.5 years until a couple
> of weeks ago when a disk died, killed the scsi bus and panicked the
> server.  The disk was 9GB large and served a good life (from ~1999!). I
> ordered a new 73GB disk, slapped it into the jbod, ran devfsadm, went to
> label it and format doesn't see the disk.
> 
> -snip---
>       4. c1t3d0 <drive not available: formatting>
>          /pci@1f,4000/scsi@4/sd@3,0
> ---snip---
> 
> but selecting the disk, it asks me to choose the drive type and then 
lists
> the correct drive type
> AVAILABLE DRIVE TYPES:
>        0. Auto configure
>     --snip--
>        23. FUJITSU-MBA3073NP-0102
> --snip--
> Specify disk type (enter its number): 23
> 
> selecting c1t3d0
> [disk unformatted]
> 
> so I try to format
> format> format
> Ready to format.  Formatting cannot be interrupted.
> Continue? y
> Beginning format. The current time is Wed Mar 10 10:27:39 2010
> 
> Inquiry failed
> failed
> format>
> 
> and at this point I'm stumped.
> iostat -En looks ok....
> Vendor: FUJITSU  Product: MBA3073NP        Revision: 0102 Serial No:
> BBR0PA102CM7
> Size: 73.54GB <73543163904 bytes>
> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
> Illegal Request: 0 Predictive Failure Analysis: 0
> c3t1d0          Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
> 
> Anyone have a fix?
> TIA
> Dean Ross-Smith
> _______________________________________________
> 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/sunmanagers