[oi-dev] [developer] Illumos/Solaris zpool and GPT Partitions/Slices

Toomas Soome tsoome at me.com
Fri Sep 5 06:03:59 UTC 2025



> On 5. Sep 2025, at 06:14, Atiq Rahman <atiqcx at gmail.com> wrote:
> 
> > should probably be improved
> 
> parted is the standard now. Improvement on solaris / illumos will be to use one to one map with partitions / slices that parted prints as output, IMO
> 


Not going to discuss what parted might be or not be, it is worth to remember every OS has its own tools and reasons. It does not mean the illumos tools are in best shape (they are not!), but they are built to follow the system logic we do have today.

rgds,
toomas

> Cheers! <>
> Atiq <>
> 
> On Sat, Aug 16, 2025 at 7:23 PM Jason King <jason.brian.king at gmail.com <mailto:jason.brian.king at gmail.com>> wrote:
> >
> > Unfortunately, prtvtoc works by trying to convert a GPT into something that looks like more traditional solaris slicing, which isn’t always possible.
> >
> >  
> >
> > Currently the best way to view a GPT is `mdb -e ‘::load disk_label; ::gpt’ /dev/rdsk/xxxx` which isn’t great (and should probably be improved).
> >
> >  
> >
> > From: Atiq Rahman <atiqcx at gmail.com <mailto:atiqcx at gmail.com>>
> > Date: Saturday, August 16, 2025 at 9:03 PM
> > To: OpenIndiana Developer mailing list <oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>>
> > Cc: illumos-developer <developer at lists.illumos.org <mailto:developer at lists.illumos.org>>, John D Groenveld <groenveld at acm.org <mailto:groenveld at acm.org>>
> > Subject: [developer] Illumos/Solaris zpool and GPT Partitions/Slices
> >
> > > What does prtvtoc(8) report?  <URL:https://illumos.org/man/8/prtvtoc>
> >
> >  
> >
> > I changed the partition table (changed partition table number using gdisk) so illumos partition maps to s6 properly day before yesterday. Can't get prtvtoc output case anymore. All partition info I had earlier is in email below:
> >
> >  
> >
> > On Sat, Aug 16, 2025 at 4:33 PM Atiq Rahman <atiqcx at gmail.com <mailto:atiqcx at gmail.com>> wrote:
> >
> > Hi John,
> > Here's the partition order that repros that on my system.
> > ---
> > $ sudo parted /dev/rdsk/c2t00A075014881A463d0 print
> >
> > Model: Generic Ide (ide)
> > Disk /dev/rdsk/c2t00A075014881A463d0: 1024GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: gpt
> >
> > Number  Start   End     Size    File system  Name                          Flags  
> >  1      1049kB  269MB   268MB   fat32        EFI System Partition          boot  
> >  2      269MB   404MB   134MB                Microsoft reserved partition  msftres
> >  3      404MB   138GB   137GB   ntfs         Basic data partition                
> >  4      138GB   139GB   1074MB  ntfs        Basic data partition          hidden
> >  5      139GB   242GB   103GB   ntfs         Basic data partition                
> >  6      242GB   767GB   525GB                                                    
> >  7      767GB   768GB   1000MB  ext3       pop_os/boot                          
> >  8      768GB   1024GB  256GB                 solaris                              
> >
> > $ sudo format
> > * /dev/rdsk/c2t00A075014881A463d0 partition map
> > *
> > * Dimensions:
> > *         512 bytes/sector
> > *  2000409264 sectors
> > *  2000409197 accessible sectors
> > *
> > * Flags:
> > *   1: unmountable
> > *  10: read-only
> > *
> > * Unallocated space:
> > *         First       Sector      Last
> > *         Sector       Count      Sector
> > *            34        2014        2047
> > *     269223936     2097152   271321087
> > *     472647680  1027352576  1500000255
> > *    2000408576         654  2000409229
> > *
> > *                            First       Sector      Last
> > * Partition  Tag  Flags      Sector       Count      Sector  Mount Directory
> >        0     12    00         2048      524288      526335
> >        1     19    00       526336      262144      788479
> >        2     20    00       788480   268435456   269223935
> >        4     20    00    271321088   201326592   472647679
> >        (last entry came out to be 6 0 0 something that doesn't make sense...)
> > ----
> >
> >
> >
> > As a workaround, I changed the last partition's number using gdisk which led to a successful zfs pool creation. Till I did that OI wasn't able to find that partition (on slice 7 nothing was mapped, on slice 6 linux's /boot partition was mapped).
> >
> >  
> >
> > On Fri, Aug 15, 2025 at 7:21 PM John D Groenveld via oi-dev <oi-dev at openindiana.org <mailto:oi-dev at openindiana.org>> wrote:
> >
> > In message <CABC65rN6C2FwKs+miCtnGQK3-Mm3VaDZzbnwfA7npL6TuYCKKw at mail.gmail.com <mailto:CABC65rN6C2FwKs%2BmiCtnGQK3-Mm3VaDZzbnwfA7npL6TuYCKKw at mail.gmail.com>>
> > , Atiq Rahman writes:
> > >*zpool lists pool from unavailable GPT Partition/Slice:*
> > >When my solaris/illumos partition is 8 as the number as listed on parted,
> > >the OI live image format etc tools cannot find it anymore even though
> > >parted lists it fine (and number on parted output becomes greater than 7,
> > >s7 for example won't work with the tools, format won't show the slice)
> >
> > I am unable to reproduce on OI:
> > # zpool status
> >   pool: rpool
> >  state: ONLINE
> >   scan: none requested
> > config:
> >
> >         NAME        STATE     READ WRITE CKSUM
> >         rpool       ONLINE       0     0     0
> >           c2t0d0s9  ONLINE       0     0     0
> >
> > errors: No known data errors
> >
> > What does prtvtoc(8) report for your partition table?
> > <URL:https://illumos.org/man/8/prtvtoc>
> >
> > John
> > groeneld at acm.org <mailto:groeneld at acm.org>
> >
> > illumos / illumos-developer / see discussions + participants + delivery options Permalink
> illumos <https://illumos.topicbox.com/latest> / illumos-developer / see discussions <https://illumos.topicbox.com/groups/developer> + participants <https://illumos.topicbox.com/groups/developer/members> + delivery options <https://illumos.topicbox.com/groups/developer/subscription>Permalink <https://illumos.topicbox.com/groups/developer/Tf912a5c8c0f95a6c-M6584fa3fd7f3980244ddbe75>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20250905/b2049d87/attachment.html>


More information about the oi-dev mailing list