fdisk can not be used on disk greater than 1TB. See the following 
documentation:

   http://docs.sun.com/app/docs/doc/819-2723/disksxadd-54639?l=en&a=view

  This may have changed with some recent changes to Nevada.

alex.

On 09/19/08 16:38, ram vegesna wrote:
> Hi Alexandre,
> 
>          Thanks a lot,It worked fine, I am able to do newfs and mount.
> But fdisk still says 
> 
>   format> fdisk
>   This disk must use an EFI label.
> 
>    Please, let me know if you have some thing for this.
> 
> Thanks for help,
> Ram
> 
> 
> 
> --- On *Sat, 9/20/08, Alexandre Chartre /<[EMAIL PROTECTED]>/* 
> wrote:
> 
>     From: Alexandre Chartre <[EMAIL PROTECTED]>
>     Subject: Re: [driver-discuss] 2TB lun issues.
>     To: [EMAIL PROTECTED]
>     Cc: "solaris driver" <[email protected]>
>     Date: Saturday, September 20, 2008, 4:22 AM
> 
>       Here your disk (c2t328d0) seems to have a valid EFI label, but
>     obviously you have to use newfs on that disk, not on
>      c0t0d0, i.e.:
> 
>       # newfs /dev/rdsk/c2t328d0s6
> 
>     alex.
> 
>     On 09/19/08 15:38, ram vegesna wrote:
>     > Hi Alexandre,
>     > 
>     >              I tried the same thing with Solaris iSCSI initiator, I saw 
>     > the same behaviour.
>     > 
>     >           Please, Let me know if you can get any thing from this.
>     >      
>     >       Here is the output.
>     > =======================================
>     >      selecting c2t328d0
>     > [disk formatted]
>     > 
>     > 
>     > FORMAT MENU:
>     >         disk       - select a disk
>     >         type       - select (define) a disk type
>     >         partition  - select (define) a partition table
>     >         current    - describe the current disk
>     >         format     - format and analyze the disk
>     >         fdisk      - run the fdisk program
>     >         repair     - repair a defective sector
>     >         label      - write label to the disk
>     > 
>             analyze    - surface analysis
>     >         defect     - defect list management
>     >         backup     - search for backup labels
>     >         verify     - read and display labels
>     >         inquiry    - show vendor, product and revision
>     >         scsi       - independent SCSI mode selects
>     >         cache      - enable, disable or query SCSI disk cache
>     >         volname    - set 8-character volume name
>     >         !<cmd>     - execute <cmd>, then return
>     >         quit
>     > format> label
>     > Ready to label disk, continue? y
>     > 
>     > format> fdisk
>     > This disk must use an EFI label.
>     > format> partition
>     > 
>     > 
>     > PARTITION MENU:
>     >         0      - change `0' partition
>     >         1      - change `1' partition
>     >         2      - change `2' partition
>     >         3      - change `3' partition
>     >         4      - change `4'
>      partition
>     >         5      - change `5' partition
>     >         6      - change `6' partition
>     >         7      - change `7' partition
>     >         8      - change '8' partition
>     >         9      - change `9' partition
>     >         select - select a predefined table
>     >         modify - modify a predefined partition table
>     >         name   - name the current table
>     >         print  - display the current table
>     >         label  - write partition map and label to the disk
>     >         !<cmd> - execute <cmd>, then return
>     >         quit
>     > partition> print
>     > Current partition table (original):
>     > Total disk sectors available: 4294950877 + 16384 (reserved sectors)
>     > 
>     > Part      Tag    Flag     First Sector          Size          Last 
> Sector
>     >   0       root    wm                34       128.00MB           262177
>     >   1       swap    wu            262178
>            128.00MB           524321
>     >   2 unassigned    wm                 0            0                0
>     >   3 unassigned    wm                 0            0                0
>     >   4 unassigned    wm                 0            0                0
>     >   5 unassigned    wm                 0            0                0
>     >   6        usr    wm            524322         2.00TB           
> 4294950876
>     >   7 unassigned    wm                 0            0                0
>     >   8   reserved    wu        4294950877         8.00MB           
> 4294967260
>     > 
>     > partition> q
>     > 
>     > 
>     > FORMAT MENU:
>     >         disk       - select a disk
>     >         type       - select (define) a disk type
>     >         partition  - select (define) a partition table
>     >         current    - describe the current disk
>     >         format     - format and analyze the disk
>     >         fdisk      - run the
>      fdisk program
>     >         repair     - repair a defective sector
>     >         label      - write label to the disk
>     >         analyze    - surface analysis
>     >         defect     - defect list management
>     >         backup     - search for backup labels
>     >         verify     - read and display labels
>     >         inquiry    - show vendor, product and revision
>     >         scsi       - independent SCSI mode selects
>     >         cache      - enable, disable or query SCSI disk cache
>     >         volname    - set 8-character volume name
>     >         !<cmd>     - execute <cmd>, then return
>     >         quit
>     > format> fdisk
>     > This disk must use an EFI label.
>     > format> q
>     > bash-3.00# new
>     > newaliases  newform     newfs       newgrp      newkey      news        
>     > newsp       newtask
>     > bash-3.00# newfs -Tv /dev/rdsk/c0t0d0s6
>     > /dev/rdsk/c0t0d0s6: I/O
>      error
>     > 
>     > 
>     > =================================
>     > 
>     > Thanks,
>     > Ram
>     > 
>     > 
>     > 
>     >    
>     > 
>     > --- On *Fri, 9/19/08, Alexandre Chartre
>     /<[EMAIL PROTECTED]>/* 
>     > wrote:
>     > 
>     >     From: Alexandre Chartre <[EMAIL PROTECTED]>
>     >     Subject: Re: [driver-discuss] 2TB lun issues.
>     >     To: [EMAIL PROTECTED]
>     >     Date: Friday, September 19, 2008, 6:16 AM
>     > 
>     >       Check that your LUN or any slice is not in use by another program.
>     > 
>     >     alex.
>     > 
>     >     On 09/18/08 17:43, ram vegesna wrote:
>     >     > 
>     >     >   I tried to do that I got the following error.     
>     >     > 
>     >     >    format> label
>     >     >         Unable to get current partition map.
>     >     >         Cannot label disk when partitions are in
>     >      use as
>      described.
>     >     > 
>     >     > -Ram
>     >     > --- On *Fri, 9/19/08, Alexandre Chartre
>     >     /<[EMAIL PROTECTED]>/* 
>     >     > wrote:
>     >     > 
>     >     >     From: Alexandre Chartre <[EMAIL PROTECTED]>
>     >     >     Subject: Re: [driver-discuss] 2TB lun issues.
>     >     >     To: [EMAIL PROTECTED]
>     >     >     Date: Friday, September 19, 2008, 6:03 AM
>     >     > 
>     >     >       You can use LUNs greater than 1TB but you have to put an
>     EFI label
>     >     on it.
>     >     > 
>     >     >       -> use format -e then "label" and chose
>     "[1]
>     >     >      EFI
>     >     >     Label"
>     >     > 
>     >     >     alex.
>     >     > 
>     >     > 
>     >     >     On 09/18/08 17:34, ram vegesna wrote:
>     >     >     >    So, I can use only luns less than 1TB right now. Is
>     it
>      true?
>     >     >     > 
>     >     >     > Thanks for help,
>     >     >     > Ram
>     >     >     > 
>     >     >     > --- On *Fri, 9/19/08, Alexandre Chartre
>     >     >     /<[EMAIL PROTECTED]>/* 
>     >     >    
>     >      > wrote:
>     >     >     > 
>     >     >     >     From: Alexandre Chartre
>     <[EMAIL PROTECTED]>
>     >     >     >     Subject: Re: [driver-discuss] 2TB lun issues.
>     >     >     >     To: [EMAIL PROTECTED]
>     >     >     >     Cc: "solaris driver"
>     >     <[email protected]>
>     >     >     >     Date: Friday, September 19, 2008, 5:44 AM
>     >     >     > 
>     >     >     >       The limit is 1TB for VTOC/SMI disk label (this is
>     limit is
>     >     being
>     >     >     extended to
>     >     >     >     2TB).
>     >     >     >
>      
>     >     >     >       I think the limit is very high for EFI label
>     (probably up
>     >     to 2^64 *
>     >     >     512
>     >     >     >     bytes)
>     >     >     > 
>     >     >     >     alex.
>     >     >     > 
>     >     >     >     On 09/18/08 17:03, ram vegesna wrote:
>     >     >     >     > Hi Garrett
>     >     >      ,
>     >     >     >     > 
>     >     >     >     >            So , what is the maximum
>     >     >     >  
>     >         supported lun size.
>     >     >     >     > 
>     >     >     >     > Thanks for help,
>     >     >     >     > Ram
>     >     >     >     > 
>     >     >     >     > --- On *Fri, 9/19/08, Garrett D'Amore
>     >     >     >     /<[EMAIL PROTECTED]>/* wrote:
>     >     >     >     > 
>     >     >     >     >     From:
>      Garrett D'Amore
>     >     <[EMAIL PROTECTED]>
>     >     >     >     >     Subject: Re: [driver-discuss] 2TB lun
>     issues.
>     >     >     >     >     To: [EMAIL PROTECTED]
>     >     >     >     >     Cc: "solaris driver"
>     >     >     <[email protected]>
>     >     >     >     >     Date: Friday, September 19, 2008, 5:17 AM
>     >     >     >     > 
>     >     >     >     >     I don't think we support LUNS > 2TB
>     at this
>     >     point. 
>     >     >     However,
>     >     >     >     there is a 
>     >     >     >     >     project underway to address that, and it
>     should be
>     >     coming
>     >     >   
>     >       soon.  (I 
>     >     >     >     >     think they're almost done with their
>     work.)
>     >     >     >     >
>     >     >      
>     >     >     >     > 
>             -- Garrett
>     >     >     >     > 
>     >     >     >     > 
>     >     >     >     >     ram vegesna wrote:
>     >     >     >     >     >
>     >     >     >     >      Hi,
>     >     >     >     >     >
>     >     >     >     >     >       The following are the
>     observations I made
>     >     when I
>     >     >     did log-in
>     >     >     >     to a 
>     >     >     >     >     > target of 2TB
>     >     >     >      size:
>     >     >     >     >     >
>     >     >     >     >     >        1) Format command showed the
>     following
>     >     output.
>     >     >     >     >     >
>     >     >     >     >     >             AVAILABLE DISK SELECTIONS:
>     >     >     >     >     >                0. c0t0d0 <DEFAULT
>     cyl 1911
>     >     alt 2 hd
>     >    
>      >     255 sec
>     >     >     >   
>     >       63>
>     >     >     >     >     >                  
>     >     >     >     >     >
>     >     >     /[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci8086,[EMAIL 
> PROTECTED]/pci1000,[EMAIL PROTECTED]/[EMAIL PROTECTED],0
>     >     >     >     >     >               1. c1t0d0
>     >     <Adaptec-2TB-V1.0-2.00TB>
>     >     >     >     >     >               
>     >     >      
>     >     >     /[EMAIL PROTECTED],0/pci8086,[EMAIL PROTECTED]/pci1004,[EMAIL 
> PROTECTED]/[EMAIL PROTECTED],0
>     >     >     >     >     >          
>     >     >     >     >     >           When I selected option 1 and
>     did
>     >     format , it
>     >     >     took
>     >     >     >     almost 12 
>     >     >     >     >     > hours to complete.
>     >     >     >     >     >
>     >     >     >     >     >       2)When I issued fdisk command,
>     he gave
>     >    
>      the
>     >     >     following
>     >     >     >     output.
>     >     >     >     >     >              format> fdisk
>     >     >     >     >     >              This disk must use an EFI
>     label.
>     >     >     >    
>     >      >     >
>     >     >     >     >     >           Please, let me know how to
>     label
>     >     >     >      the EFI label ?
>     >     >     >     >     >
>     >     >     >     >     >      3) When I did newfs
>     >     >     >     >      , It came out immediately saying I/O 
>     >     >     >     >     > Error.(This used to work with other
>     disks)
>     >     >     >     >     >         
>     >     >     >     >     >           newfs -T /dev/dsk/c1t0d0s2
>     >     >     >     >     >       
>     >     >        /dev/rdsk/c1t0d0s2: I/O error
>     >    
>      >     >     >     >
>     >     >     >     >     >     4) I tried smc (Solaris Managment
>     Console)
>     >     , It did
>     >     >     not
>     >     >     >     detect the 
>     >     >     >     >     > disks.
>     >     >     >     >     >
>     >     >     >     >     >         Do we have support in Solaris
>     for Luns
>     >     greater
>     >     >     than 2TB?
>     >     >     >    
>     >      >     >        
>     >     >     >     >     >          Any suggestions and thoughts
>     are
>     >     greatly
>     >     >     appresiated.
>     >     >     >     >     >
>     >     >     >     >     > Thanks,
>     >     >     >     >     > Ram
>     >     >     >     >     >                  
>     >     >     >     >     >
>     >     >     >     >     >
>     >    
>      >     >     >     >
>     >     >     >     >     >
>     >     >     >    
>     >     >    
>     >    
>     ------------------------------------------------------------------------
>     >     >     >     >     >
>     >     >     >     >     >
>     >     >     >      _______________________________________________
>     >     >     >     >     > driver-discuss mailing list
>     >     >     >     >    
>     >     >      > [email protected]
>     >     >     >     >     >
>     >     >     http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>     >     >     >    
>     >      >     >   
>     >     >     >     > 
>     >     >     >     > 
>     >     >     >     > 
>     >     >     >     >
>     >     >    
>     >   
>      
>     ------------------------------------------------------------------------
>     >     >     >     > 
>     >     >     >     > _______________________________________________
>     >     >     >     > driver-discuss mailing list
>     >     >     >     > [email protected]
>     >     >     >     >
>     >     http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>     >     >     > 
>     >     >     > 
>     >     > 
>     >     > 
>     > 
>     > 
>     > 
>     > ------------------------------------------------------------------------
>     > 
>     > _______________________________________________
>     > driver-discuss mailing list
>     > [email protected]
>     > http://mail.opensolaris.org/mailman/listinfo/driver-discuss
> 
> 
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to