[OmniOS-discuss] 2x acctual disk quantity

Saso Kiselkov skiselkov.ml at gmail.com
Mon Dec 2 14:59:28 UTC 2013


No, I need you to run "format" and hit Control-C to exit it. it will
print a disk list up front, like so:

# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c3t0d0 <DEFAULT cyl 8872 alt 2 hd 255 sec 63>
          /pci at 7b,0/pci1022,7458 at 11/pci1000,3060 at 2/sd at 0,0
       1. c6t600D0230006B66680C50AB7821F0E900d0 <ADVUNI-OXYGENRAID
416F4-347B-3.41TB>
          /scsi_vhci/disk at g600d0230006b66680c50ab7821f0e900
       2. c6t600D0230006C1C4C0C50BE5BC9D49100d0 <ADVUNI-OXYGENRAID
416F4-347B-3.41TB>
          /scsi_vhci/disk at g600d0230006c1c4c0c50be5bc9d49100
	(..etc..)

-- 
Saso

On 12/2/13, 2:55 PM, Hafiz Rafibeyli wrote:
> Saso is this you are asking for?
> 
>  id 	 part 	 identify 	 stat 	 diskcap 	 partcap 	 error 	 vendor 	 product 	 sn 
>  c1t5000C50041E9D9A7d0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2934YB40000923 
>  c1t5000C50041F1A5EFd0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2937JC90000924 
>  c1t5000C5004253FF87d0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z294403Y0000C25 
>  c1t5000C50055A607E3d0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2955HY80000931 
>  c1t5000C50055A628EFd0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z295857E0000931 
>  c1t5000C50055A62F57d0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2957MGA0000931 
>  c1t5000C5005600A6B3d0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2967CNZ0000C32 
>  c1t5000C5005600B43Bd0 	 (!parted) 	 via dd 	 ok 	   	 3 TB 	  S:0 H:4 T:0 	 SEAGATE 	 ST33000650SS 	 Z2967CF50000C32 
>  c1t5001517803D007D8d0 	 (!parted) 	 via dd 	 ok 	   	 120 GB 	  S:2 H:0 T:0 	 ATA 	 INTEL SSDSC2CW12 	 CVCV249102HG120 
>  c1t5001517959627219d0 	 (!parted) 	 via dd 	 ok 	   	 32 GB 	  S:2 H:0 T:0 	 ATA 	 SSDSA2SH032G1GN 	 CVEM130600KP032 
>  c1t5001517BB2747BE7d0 	 (!parted) 	 via dd 	 ok 	   	 32 GB 	  S:2 H:0 T:0 	 ATA 	 SSDSA2SH032G1GN 	 CVEM1404005G032 
>  c1t5001517BB2AFB592d0 	 (!parted) 	 via dd 	 ok 	   	 120 GB 	  S:2 H:0 T:0 	 ATA 	 INTEL SSDSC2CW12 	 CVCV245100J1120 
>  c3t1d0 	 (!parted) 	 via dd 	 ok 	   	 50 GB 	  S:2 H:0 T:0 	 ATA 	 STEC MACH16 M 	 STM0001681F1 
>  c3t2d0 	 (!parted) 	 via dd 	 ok 	   	 50 GB 	  S:2 H:0 T:0 	 ATA 	 STEC MACH16 M 	 STM0001681EE 
>  c4t500000E1168BB382d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FARTT 	 D001PAB0EUJ7104 
>  c4t500000E11693F232d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FARTT 	 D001PAB0EY64104 
>  c4t500000E11696D5A2d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FARTT 	 D001PAB0F12G104 
>  c4t500000E116974FB2d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FARTT 	 D001PAB0F1P5104 
>  c4t50000392C8008B7Ed0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FBDSP 	 EB01PA9013TD103 
>  c4t5000C5002BD75C05d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 EG0300FAWHV 	 6SE134XX0000B10 
>  c4t5000CCA0150597A5d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 DG0300FARVV 	 PFV32ANE 
>  c4t5000CCA01505A321d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:0 T:0 	 HP 	 DG0300FARVV 	 PFV333BE 
>  c6t500000E1168BB383d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FARTT 	 D001PAB0EUJ7104 
>  c6t500000E11693F233d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FARTT 	 D001PAB0EY64104 
>  c6t500000E11696D5A3d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FARTT 	 D001PAB0F12G104 
>  c6t500000E116974FB3d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FARTT 	 D001PAB0F1P5104 
>  c6t50000392C8008B7Fd0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FBDSP 	 EB01PA9013TD103 
>  c6t5000C5002BD75C06d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 EG0300FAWHV 	 6SE134XX0000B10 
>  c6t5000CCA0150597A6d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 DG0300FARVV 	 PFV32ANE 
>  c6t5000CCA01505A322d0 	 (!parted) 	 via dd 	 ok 	   	 300 GB 	  S:0 H:1 T:0 	 HP 	 DG0300FARVV 	 PFV333BE 
> 
> ----- Orijinal Mesaj -----
> Kimden: omnios-discuss-request at lists.omniti.com
> Kime: omnios-discuss at lists.omniti.com
> Gönderilenler: 2 Aralık Pazartesi 2013 16:39:43
> Konu: OmniOS-discuss Digest, Vol 21, Issue 2
> 
> Send OmniOS-discuss mailing list submissions to
> 	omnios-discuss at lists.omniti.com
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.omniti.com/mailman/listinfo/omnios-discuss
> or, via email, send a message with subject or body 'help' to
> 	omnios-discuss-request at lists.omniti.com
> 
> You can reach the person managing the list at
> 	omnios-discuss-owner at lists.omniti.com
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OmniOS-discuss digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Re-installing OmniOS after Crash (Piers Dawson-Damer)
>    2. 2x acctual disk quantity (Hafiz Rafibeyli)
>    3. Re: 2x acctual disk quantity (Saso Kiselkov)
>    4. 2x acctual disk quantity (Hafiz Rafibeyli)
>    5. Re: 2x acctual disk quantity (Saso Kiselkov)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 2 Dec 2013 20:26:34 +1100
> From: Piers Dawson-Damer <piers at mm.st>
> To: omnios-discuss at lists.omniti.com
> Subject: Re: [OmniOS-discuss] Re-installing OmniOS after Crash
> Message-ID: <B3452613-0C4C-4CD2-9B32-3358ADB0849F at mm.st>
> Content-Type: text/plain; charset="us-ascii"
> 
> Any update on this error?
> 
> I also cannot update my system.  Have tried removing the OmniTi repositories
> 
> Piers
> 
> SunOS prod 5.11 omnios-ef9657e i86pc i386 i86pc
> 
> piers at prod:~$ pfexec pkg update -v                                                                                     
> Creating Plan /                        
> pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
> The package involved is:pkg://omnios/runtime/python-26@2.6.8,5.11-0.151007:20130926T213513Z
> 
> 
> 
> On 27 Oct 2013, at 11:04 pm, Sam M <emunch at utmi.in> wrote:
> 
>> Hello all.
>>
>> After installing napp-it, OmniOS got hosed. Not sure what caused it, probably not napp-it, because I couldn't boot up my system with any of the boot images, including the original. 
>>
>> Now, on a brand new installation, I'm getting the following error - 
>>
>> # pkg update web/ca-bundle pkg
>> Creating Plan -                        
>> pkg update: The certificate which issued this certificate:/C=US/ST=Maryland/O=OmniTI/OU=OmniOS/CN=OmniOS r151007 Release Signing Certificate/emailAddress=omnios-support at omniti.com could not be found. The issuer is:/C=US/ST=Maryland/L=Fulton/O=OmniTI/CN=OmniTI Certificate Authority
>> The package involved is:pkg://omnios/library/python-2/pybonjour@1.1.1,5.11-0.151007:20130516T114553Z
>>
>> # uname -a
>> SunOS sequoia 5.11 omnios-df542ea i86pc i386 i86pc Solaris
>>
>> There were no errors earlier after the installation when updating packages. 
>>
>> How can I fix this? Where can I find OmniTI's CA certificate?
>>
>> TIA.
>>
>> Sam
>>
>>
>>
>> _______________________________________________
>> OmniOS-discuss mailing list
>> OmniOS-discuss at lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://omniosce.org/ml-archive/attachments/20131202/8a7686b8/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Mon, 2 Dec 2013 14:08:04 +0200 (EET)
> From: Hafiz Rafibeyli <rafibeyli at gmail.com>
> To: omnios-discuss <omnios-discuss at lists.omniti.com>
> Subject: [OmniOS-discuss] 2x acctual disk quantity
> Message-ID:
> 	<147167035.58244.1385986084129.JavaMail.zimbra at cantekstil.com.tr>
> Content-Type: text/plain; charset=windows-1254
> 
> 
> Saso thank you for your fast reply,
> 
> its ok about two ports(sas dp)I know it,
> 
> but my question is about ,which disk adresses to use in my zfs mirror or zfs raid config?
> 
> in my case:
> 
> c4t500000E1168BB382d0          
> c4t500000E11693F232d0          
> c4t500000E11696D5A2d0          
> c4t500000E116974FB2d0          
> 
> OR
> 
> c6t500000E1168BB383d0          
> c6t500000E11693F233d0          
> c6t500000E11696D5A3d0          
> c6t500000E116974FB3d0          
> 
> 
> If I understand right,when use first adresses I will use  1st controller only,and when use second addresses  2nd controller only?
> 
> regards
> 
> Hafiz
> 
> 
> Message: 6
> Date: Sat, 30 Nov 2013 11:26:57 +0000
> From: Saso Kiselkov <skiselkov.ml at gmail.com>
> To: omnios-discuss at lists.omniti.com
> Subject: Re: [OmniOS-discuss] 2x acctual disk quantity
> Message-ID: <5299CB81.7090101 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> On 11/30/13, 9:43 AM, Hafiz Rafibeyli wrote:
>> Hello,
>>
>> After adding 4 SAS dual port disks to my omnios system(omnios-b281e50+napp-it) ,I see number of disks 2x acctual quantity.
>>
>> I have dual controller backplane(supermicro) and 2 LSI 9211-8i,
>>
>> There is no any quantity problem with another disks,only with new added HP 300GB SAS DP.
>>
>>
>>  c4t500000E1168BB382d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0EUJ7104 
>>  c4t500000E11693F232d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0EY64104 
>>  c4t500000E11696D5A2d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0F12G104 
>>  c4t500000E116974FB2d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0F1P5104 
>>  c6t500000E1168BB383d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0EUJ7104 
>>  c6t500000E11693F233d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0EY64104 
>>  c6t500000E11696D5A3d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0F12G104 
>>  c6t500000E116974FB3d0          (!parted)          via dd          ok                     300 GB           S:0 H:0 T:0          HP          EG0300FARTT          D001PAB0F1P5104 
> 
> Hey Hafiz,
> 
> What you're seeing are the two ports of the disks. Using "mpathadm list
> lu" you should be able to determine which SAS addresses correspond to
> which disks. You can also use something like diskmap.py from
> https://github.com/swacquie/DiskMap (it requires the sas2ircu utility
> from LSI).
> 
> Cheers,
> 



More information about the OmniOS-discuss mailing list