From: Crist Clark (Crist.Clark@globalstar.com)
Date: Fri Aug 24 2007 - 13:25:09 EDT
Thanks to Jeremy Gillow for the following solution. It worked
for me. My original question follows the solution.
> Crist,
>
> This has worked for me before on the V245:
>
> You may want to remove all the hard drives except the troubled one
> first.
>
> ok setenv fcode-debug? true
> fcode-debug? = true
> ok setenv auto-boot? false
> auto-boot? = false
> ok reset-all
>
> ok show-disks
> a) /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk
> b) /pci@1e,600000/pci@0/pci@1/pci@0/ide@1f/cdrom
> c) /pci@1e,600000/pci@0/pci@1/pci@0/ide@1f/disk
> q) NO SELECTION
> Enter Selection, q to quit: q
> ok select /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1
>
> ok show-volumes
> Volume 0 Target 0 Type IM (Integrated Mirroring)
> Optimal Enabled
> 2 Members 143112591 Blocks, 73 GB
> Disk 1
> Primary Online
> Target 4 FUJITSU MAY2073RCSUN72G 0401
> Disk 0
> Secondary Online
> Target 1 FUJITSU MAY2073RCSUN72G 0401
>
> ok 0 delete-volume
> The volume and its data will be deleted
> Are you sure (yes/no)? [no] yes
> Volume 0 has been deleted
>
> ok show-volumes
> No volumes to show
>
> ok setenv auto-boot? true
> auto-boot? = true
> ok setenv fcode-debug? false
> fcode-debug? = false
>
> You can now boot the system, run devfsadm to see the fixed hard
drive,
> and run the format utility to detect the type and label the drive.
>
> Note that when you run the show-volumes command one of the physical
> disks in the array will be shown as Missing.
Original question:
>> I just added a disk to a V245 running Solaris 10. The new
>> (actually reused) disk will NOT be part of a RAID. However,
>> upon rebooting with the new disk, I don't see it in format(1M),
>> but I do see,
>>
>> # raidctl
>> RAID Volume RAID RAID Disk
>> Volume Type Status Disk Status
>> ------------------------------------------------------
>> c1t132d0 IM RESYNCING - MISSING
>> c1t2d0 OK
>> c1t0d0 IM OK c1t0d0 OK
>> c1t1d0 OK
>>
>> So the disk is there, but the system seems to think it is
>> in an array. It very may well have been part of one in its
>> previous life. But when I try to break up that ghost volume,
>>
>> # raidctl -d c1t132d0
>> Not a volume 'c1t132d0'
>>
>> Since the controller, an LSI1064 HBA, is in between the OS
>> and the disk, I can't figure out a way to get in there to
>> kill any disk labels that are confusing the controller.
>>
>> How do I break up that phantom volume and get access to that
>> disk? Thanks.
BB<information contained in this e-mail message is confidential, intended
only for the use of the individual or entity named above. If the reader
of this e-mail is not the intended recipient, or the employee or agent
responsible to deliver it to the intended recipient, you are hereby
notified that any review, dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this e-mail
in error, please contact postmaster@globalstar.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:42:14 EDT