Bad ioctl DKIOCGEXTVTOC

Bad ioctl DKIOCGEXTVTOC

[mellowmutt]

[-- Attachment #1: Type: text/plain, Size: 668 bytes --]

errno= Operation not supported
Cannot read vtoc information.
No fdisk solaris partition found.

Where's prntvtoc gone? I know, it was obsoleted and removed, but when I got that memo, it said references to it were removed, calls to it were removed...

Apparently not. The project I'm doing this week, I really need prtvtoc. Because so does illumos, judging by the above error, and the fact that working through my problem has led me to numerous man pages, online help, etc. which all give me the answers I'm looking for...

By explaining to me how to use prntvtoc.

-Eric

Oh... to repeat the problem, mark your EFI partition inactive, then try format>fd.

[-- Attachment #2: Type: text/html, Size: 896 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote:
> errno= Operation not supported
> Cannot read vtoc information.
> No fdisk solaris partition found.
> 
> Where's prntvtoc gone? I know, it was obsoleted and removed, but when I 
> got that memo, it said references to it were removed, calls to it were 
> removed...
> 
> Apparently not. The project I'm doing this week, I really need prtvtoc. 
> Because so does illumos, judging by the above error, and the fact that 
> working through my problem has led me to numerous man pages, online 
> help, etc. which all give me the answers I'm looking for...
> 
At least up to illumos-cde3e94d79 (which is a few days old), prtvtoc is
available and has a man page (and there is no prntvtoc...).

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]

Thanks! No, I wasn't making that typo at the CLI, but prtvtoc tells me what I need to do.



I just don't know how. I thought "SOLARIS2" was the path to SMI/PMBR. I need to partition a disk with that scheme. I know it's in illumos because I found it once, but can't repeat.



-Eric






---- On Fri, 17 May 2024 05:31:28 -0700 Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote ---



On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote: 
> errno= Operation not supported 
> Cannot read vtoc information. 
> No fdisk solaris partition found. 
> 
> Where's prntvtoc gone? I know, it was obsoleted and removed, but when I 
> got that memo, it said references to it were removed, calls to it were 
> removed... 
> 
> Apparently not. The project I'm doing this week, I really need prtvtoc. 
> Because so does illumos, judging by the above error, and the fact that 
> working through my problem has led me to numerous man pages, online 
> help, etc. which all give me the answers I'm looking for... 
> 
At least up to illumos-cde3e94d79 (which is a few days old), prtvtoc is 
available and has a man page (and there is no prntvtoc...). 
 
------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df 
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 2397 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

On 17/05/2024 15:04, Eric J Bowman wrote:
> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc tells me 
> what I need to do.
> 
> I just don't know how. I thought "SOLARIS2" was the path to SMI/PMBR. I 
> need to partition a disk with that scheme. I know it's in illumos 
> because I found it once, but can't repeat.

fdisk is your friend ...

> 
> 
> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK) 
> <udo.grabowski@kit.edu>* wrote ---
> 
>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote:
>      > errno= Operation not supported
>      > Cannot read vtoc information.
>      > No fdisk solaris partition found.
>      >
>      > Where's prntvtoc gone? I know, it was obsoleted and removed, but
>     when I
>      > got that memo, it said references to it were removed, calls to it
>     were
>      > removed...
>      >
>      > Apparently not. The project I'm doing this week, I really need
>     prtvtoc.
>      > Because so does illumos, judging by the above error, and the fact
>     that
>      > working through my problem has led me to numerous man pages, online
>      > help, etc. which all give me the answers I'm looking for...
>      >
>     At least up to illumos-cde3e94d79 (which is a few days old), prtvtoc is
>     available and has a man page (and there is no prntvtoc...).
> 
>     ------------------------------------------
>     illumos: illumos-discuss
>     Permalink:
>     https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df>
>     Delivery options:
>     https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>
> 
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 2310 bytes --]

On 17/05/2024 15:07, Udo Grabowski (IMK) wrote:
> On 17/05/2024 15:04, Eric J Bowman wrote:
>> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc tells me 
>> what I need to do.
>>
>> I just don't know how. I thought "SOLARIS2" was the path to SMI/PMBR. 
>> I need to partition a disk with that scheme. I know it's in illumos 
>> because I found it once, but can't repeat.
> 
> fdisk is your friend ...

and format as well .


>>
>>
>> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK) 
>> <udo.grabowski@kit.edu>* wrote ---
>>
>>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote:
>>      > errno= Operation not supported
>>      > Cannot read vtoc information.
>>      > No fdisk solaris partition found.
>>      >
>>      > Where's prntvtoc gone? I know, it was obsoleted and removed, but
>>     when I
>>      > got that memo, it said references to it were removed, calls to it
>>     were
>>      > removed...
>>      >
>>      > Apparently not. The project I'm doing this week, I really need
>>     prtvtoc.
>>      > Because so does illumos, judging by the above error, and the fact
>>     that
>>      > working through my problem has led me to numerous man pages, 
>> online
>>      > help, etc. which all give me the answers I'm looking for...
>>      >
>>     At least up to illumos-cde3e94d79 (which is a few days old), 
>> prtvtoc is
>>     available and has a man page (and there is no prntvtoc...).
>>
>>     ------------------------------------------
>>     illumos: illumos-discuss
>>     Permalink:
>>     
>> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df>
>>     Delivery options:
>>     https://illumos.topicbox.com/groups/discuss/subscription
>>     <https://illumos.topicbox.com/groups/discuss/subscription>
>>
>>
> 
> 
> ------------------------------------------
> illumos: illumos-discuss
> Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade
> Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2774 bytes --]

I keep winding up with GUID or MBR.



-Eric






---- On Fri, 17 May 2024 06:09:16 -0700 Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote ---



On 17/05/2024 15:07, Udo Grabowski (IMK) wrote: 
> On 17/05/2024 15:04, Eric J Bowman wrote: 
>> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc tells me 
>> what I need to do. 
>> 
>> I just don't know how. I thought "SOLARIS2" was the path to SMI/PMBR. 
>> I need to partition a disk with that scheme. I know it's in illumos 
>> because I found it once, but can't repeat. 
> 
> fdisk is your friend ... 
 
and format as well . 
 
 
>> 
>> 
>> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK) 
>> <mailto:udo.grabowski@kit.edu>* wrote --- 
>> 
>>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote: 
>>      > errno= Operation not supported 
>>      > Cannot read vtoc information. 
>>      > No fdisk solaris partition found. 
>>      > 
>>      > Where's prntvtoc gone? I know, it was obsoleted and removed, but 
>>     when I 
>>      > got that memo, it said references to it were removed, calls to it 
>>     were 
>>      > removed... 
>>      > 
>>      > Apparently not. The project I'm doing this week, I really need 
>>     prtvtoc. 
>>      > Because so does illumos, judging by the above error, and the fact 
>>     that 
>>      > working through my problem has led me to numerous man pages, 
>> online 
>>      > help, etc. which all give me the answers I'm looking for... 
>>      > 
>>     At least up to illumos-cde3e94d79 (which is a few days old), 
>> prtvtoc is 
>>     available and has a man page (and there is no prntvtoc...). 
>> 
>>     ------------------------------------------ 
>>     illumos: illumos-discuss 
>>     Permalink: 
>> 
>> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df> 
>>     Delivery options: 
>>     https://illumos.topicbox.com/groups/discuss/subscription 
>>     <https://illumos.topicbox.com/groups/discuss/subscription> 
>> 
>> 
> 
> 
> ------------------------------------------ 
> illumos: illumos-discuss 
> Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade 
> Delivery options: https://illumos.topicbox.com/groups/discuss/subscription 
 
------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938 
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 5154 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3335 bytes --]

And, the first 34 sectors protected, simulating PMBR. Which tool doesn't want to be my friend?



-Eric






---- On Fri, 17 May 2024 06:15:12 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



I keep winding up with GUID or MBR.



-Eric







---- On Fri, 17 May 2024 06:09:16 -0700 Udo Grabowski (IMK) <mailto:udo.grabowski@kit.edu> wrote ---








https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mb9ba8124050ac3f50bcaaffc


On 17/05/2024 15:07, Udo Grabowski (IMK) wrote: 
> On 17/05/2024 15:04, Eric J Bowman wrote: 
>> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc tells me 
>> what I need to do. 
>> 
>> I just don't know how. I thought "SOLARIS2" was the path to SMI/PMBR. 
>> I need to partition a disk with that scheme. I know it's in illumos 
>> because I found it once, but can't repeat. 
> 
> fdisk is your friend ... 

and format as well . 


>> 
>> 
>> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK) 
>> <mailto:udo.grabowski@kit.edu>* wrote --- 
>> 
>>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote: 
>>      > errno= Operation not supported 
>>      > Cannot read vtoc information. 
>>      > No fdisk solaris partition found. 
>>      > 
>>      > Where's prntvtoc gone? I know, it was obsoleted and removed, but 
>>     when I 
>>      > got that memo, it said references to it were removed, calls to it 
>>     were 
>>      > removed... 
>>      > 
>>      > Apparently not. The project I'm doing this week, I really need 
>>     prtvtoc. 
>>      > Because so does illumos, judging by the above error, and the fact 
>>     that 
>>      > working through my problem has led me to numerous man pages, 
>> online 
>>      > help, etc. which all give me the answers I'm looking for... 
>>      > 
>>     At least up to illumos-cde3e94d79 (which is a few days old), 
>> prtvtoc is 
>>     available and has a man page (and there is no prntvtoc...). 
>> 
>>     ------------------------------------------ 
>>     illumos: illumos-discuss 
>>     Permalink: 
>> 
>> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df> 
>>     Delivery options: 
>>     https://illumos.topicbox.com/groups/discuss/subscription
>>     <https://illumos.topicbox.com/groups/discuss/subscription> 
>> 
>> 
> 
> 
> ------------------------------------------ 
> illumos: illumos-discuss 
> Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade
> Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 6710 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 4622 bytes --]



On 17/05/2024 15:15, Eric J Bowman via illumos-discuss wrote:
> I keep winding up with GUID or MBR.
> 

For SMI partitioning, you use 'fdisk /dev/rdsk/c*p0', erase existing
partitions, choose SOLARIS2 for a new partition (and make it active
if a boot disk), and then format '/dev/rdsk/c*s2'; or copy the vtoc
via 'prtvtoc /dev/rdsk/c1*s2|fmthard -s - /dev/rdsk/c2*s2' (but fdisk
is necessary anyway).

> 
> ---- On Fri, 17 May 2024 06:09:16 -0700 *Udo Grabowski (IMK) 
> <udo.grabowski@kit.edu>* wrote ---
> 
>     On 17/05/2024 15:07, Udo Grabowski (IMK) wrote:
>      > On 17/05/2024 15:04, Eric J Bowman wrote:
>      >> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc
>     tells me
>      >> what I need to do.
>      >>
>      >> I just don't know how. I thought "SOLARIS2" was the path to
>     SMI/PMBR.
>      >> I need to partition a disk with that scheme. I know it's in illumos
>      >> because I found it once, but can't repeat.
>      >
>      > fdisk is your friend ...
> 
>     and format as well .
> 
> 
>      >>
>      >>
>      >> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK)
>      >> <udo.grabowski@kit.edu <mailto:udo.grabowski@kit.edu>>* wrote ---
>      >>
>      >>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote:
>      >>      > errno= Operation not supported
>      >>      > Cannot read vtoc information.
>      >>      > No fdisk solaris partition found.
>      >>      >
>      >>      > Where's prntvtoc gone? I know, it was obsoleted and
>     removed, but
>      >>     when I
>      >>      > got that memo, it said references to it were removed,
>     calls to it
>      >>     were
>      >>      > removed...
>      >>      >
>      >>      > Apparently not. The project I'm doing this week, I really
>     need
>      >>     prtvtoc.
>      >>      > Because so does illumos, judging by the above error, and
>     the fact
>      >>     that
>      >>      > working through my problem has led me to numerous man pages,
>      >> online
>      >>      > help, etc. which all give me the answers I'm looking for...
>      >>      >
>      >>     At least up to illumos-cde3e94d79 (which is a few days old),
>      >> prtvtoc is
>      >>     available and has a man page (and there is no prntvtoc...).
>      >>
>      >>     ------------------------------------------
>      >>     illumos: illumos-discuss
>      >>     Permalink:
>      >>
>      >>
>     https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df> <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df>>
>      >>     Delivery options:
>      >> https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>
>      >>     <https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>>
>      >>
>      >>
>      >
>      >
>      > ------------------------------------------
>      > illumos: illumos-discuss
>      > Permalink:
>      >
>     https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade>
>      > Delivery options:
>     https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>
> 
>     ------------------------------------------
>     illumos: illumos-discuss
>     Permalink:
>     https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938 <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938>
>     Delivery options:
>     https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>
> 
> 
> *illumos <https://illumos.topicbox.com/latest>* / illumos-discuss / see 
> discussions <https://illumos.topicbox.com/groups/discuss> + participants 
> <https://illumos.topicbox.com/groups/discuss/members> + delivery options 
> <https://illumos.topicbox.com/groups/discuss/subscription> Permalink 
> <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mb9ba8124050ac3f50bcaaffc>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 9191 bytes --]

>

...erase existing partitions...

>



Heheh... try getting rid of GhostBSD that way, lol. ;-)



The cool thing is how you can burn Ghost to CDROM or USB and have it not only boot, but function.

SmartOS, you need to know how to make a USB yourself, because it's meant to be burned to CDROM.

"Boot Repair CD" Linux distro boots either way, but burn it to CDROM (I know, right?) and GRUB2 won't know what to boot.



My in-house ON distro, last released to my regional EC2 in 2009, was a lightweight hypervisor for running sparse-root Zones on SPARC or AWS Celeron.



I'm working on it again, but as a meta-distro / cross-platform thing you can burn either way. I will post bisonix.iso ("buffy") on ipfs, and link to it here.



I'll be using Tribblix to assemble a lightweight utility desktop a la Boot Repair CD (except you'll be able to burn mine to CDROM lol). But not for a while. At first, it will appear to be GhostBSD... unless you chainload the penguins, GRUB --> GRUB2 boot path.



If you figure out how to erase GhostBSD, it'll boot to the Boot Repair CD's GRUB2 error, because Solaris Boot was ignored. Please tell me how you did it, as I do not know.

I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 


If you figure out what seek setting to give dd, you can swap GhostBSD for SmartOS, and have a bootable USB for SmartOS. There are two possible answers, depending on if you want the result to follow the Linux boot path to rEFInd, or the Solaris boot path to GRUB. If the former, you can still boot SmartOS via rEFInd's iso9660.efi driver.



I think the problem comes when setting any partition "active". What I want, is to netboot.xyz into CAINE, as its Gparted/Disks installation is fully configured with all the fs support you could want to work on your crashed bootcamp'd iMac, partitioned up the wazoo after 3 years by this-and-that on either OS, oblivious to two OS's needing to grok the partition table... sorry... anyway, Disks will report PMBR and refuse to mount/alter any but the ESP partition. Now, I delete p1, which contains "Solaris Boot." It is now s0 to SunOS. Mark ESP active, Disks changes displayed "PMBR" to "GUID", and bingo. You have an interoperable partitioning scheme.



You'll need to "swap CDROM" from Ghosty to Smarty, to observe how all the hogs freed from pen six, will now push s9 to the new boundary; they'll want to cool off in z pool, after. If you make a tiny zpool in s6 and expect it to autoexpand, it will... up to s9, which won't move because you neglected to free all the hogs. FreeBSD won't re-pin s9 to the end of the drive. So far, this works, with circle-square compatibility, and you wind up with a functional 32GB-2TB boot drive with SmartOS, Boot Repair, Bodhi, and OpenMandriva all playing nicely together with others.



I've been reading too freakin' man(y)uals, don't get me started on the subtleties between mkisofs, genisoimage, and whatever the new GPL identical replacement of the identical replacement is called. What I've proven is that you don't need to use whatever wizard you used which uses antiquated (pre-UEFI and even pre-EFI) flags. I thought GhostBSD's use of FAT12 was somehow required, but I've used FAT32. I've also not resorted to "legacy bios boot."



My goal is an OmniTribblix ./free-hog_install.sh script which creates rpool in s5, and zonepool in s6. From there, I can install CAINE and Kali in Lx Zones, and script it such that from inside those zones, rebooting preserves state with a ZFS snapshot. Poweroff reverts to clean install and deletes all snapshots. I'll be including several installed distros in my installer, as detached-zone tarballs. I've installed Bodhi and Mandrake to btrfs, but in an Lx Zone, best use Ext4 to avoid a "COW pile" on SSD, you don't know how many COW/GC layers are on the controller, so best stick with just one on top. This makes it VERY difficult to remove GhostBSD. It's like Edge browser... just when you think it's gone, it comes back!



I know how to re-create all my steps except the first one.


-Eric







---- On Fri, 17 May 2024 06:35:05 -0700 Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote ---





On 17/05/2024 15:15, Eric J Bowman via illumos-discuss wrote: 
> I keep winding up with GUID or MBR. 
> 
 
For SMI partitioning, you use 'fdisk /dev/rdsk/c*p0', erase existing 
partitions, choose SOLARIS2 for a new partition (and make it active 
if a boot disk), and then format '/dev/rdsk/c*s2'; or copy the vtoc 
via 'prtvtoc /dev/rdsk/c1*s2|fmthard -s - /dev/rdsk/c2*s2' (but fdisk 
is necessary anyway). 
 
> 
> ---- On Fri, 17 May 2024 06:09:16 -0700 *Udo Grabowski (IMK) 
> <mailto:udo.grabowski@kit.edu>* wrote --- 
> 
>     On 17/05/2024 15:07, Udo Grabowski (IMK) wrote: 
>      > On 17/05/2024 15:04, Eric J Bowman wrote: 
>      >> Thanks! No, I wasn't making that typo at the CLI, but prtvtoc 
>     tells me 
>      >> what I need to do. 
>      >> 
>      >> I just don't know how. I thought "SOLARIS2" was the path to 
>     SMI/PMBR. 
>      >> I need to partition a disk with that scheme. I know it's in illumos 
>      >> because I found it once, but can't repeat. 
>      > 
>      > fdisk is your friend ... 
> 
>     and format as well . 
> 
> 
>      >> 
>      >> 
>      >> ---- On Fri, 17 May 2024 05:31:28 -0700 *Udo Grabowski (IMK) 
>      >> <mailto:udo.grabowski@kit.edu <mailto:mailto:udo.grabowski@kit.edu>>* wrote --- 
>      >> 
>      >>     On 17/05/2024 14:04, mellowmutt via illumos-discuss wrote: 
>      >>      > errno= Operation not supported 
>      >>      > Cannot read vtoc information. 
>      >>      > No fdisk solaris partition found. 
>      >>      > 
>      >>      > Where's prntvtoc gone? I know, it was obsoleted and 
>     removed, but 
>      >>     when I 
>      >>      > got that memo, it said references to it were removed, 
>     calls to it 
>      >>     were 
>      >>      > removed... 
>      >>      > 
>      >>      > Apparently not. The project I'm doing this week, I really 
>     need 
>      >>     prtvtoc. 
>      >>      > Because so does illumos, judging by the above error, and 
>     the fact 
>      >>     that 
>      >>      > working through my problem has led me to numerous man pages, 
>      >> online 
>      >>      > help, etc. which all give me the answers I'm looking for... 
>      >>      > 
>      >>     At least up to illumos-cde3e94d79 (which is a few days old), 
>      >> prtvtoc is 
>      >>     available and has a man page (and there is no prntvtoc...). 
>      >> 
>      >>     ------------------------------------------ 
>      >>     illumos: illumos-discuss 
>      >>     Permalink: 
>      >> 
>      >> 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df> <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M47e0457977e29ae4f09105df>> 
>      >>     Delivery options: 
>      >> https://illumos.topicbox.com/groups/discuss/subscription 
>     <https://illumos.topicbox.com/groups/discuss/subscription> 
>      >>     <https://illumos.topicbox.com/groups/discuss/subscription 
>     <https://illumos.topicbox.com/groups/discuss/subscription>> 
>      >> 
>      >> 
>      > 
>      > 
>      > ------------------------------------------ 
>      > illumos: illumos-discuss 
>      > Permalink: 
>      > 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mc70d3957e0db3d76d54aaade> 
>      > Delivery options: 
> https://illumos.topicbox.com/groups/discuss/subscription 
>     <https://illumos.topicbox.com/groups/discuss/subscription> 
> 
>     ------------------------------------------ 
>     illumos: illumos-discuss 
>     Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938 <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M28f459087ab0588b97f65938> 
>     Delivery options: 
> https://illumos.topicbox.com/groups/discuss/subscription 
>     <https://illumos.topicbox.com/groups/discuss/subscription> 
> 
> 
> *illumos <https://illumos.topicbox.com/latest>* / illumos-discuss / see 
> discussions <https://illumos.topicbox.com/groups/discuss> + participants 
> <https://illumos.topicbox.com/groups/discuss/members> + delivery options 
> <https://illumos.topicbox.com/groups/discuss/subscription> Permalink 
> <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mb9ba8124050ac3f50bcaaffc> 
 
------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M8ef90c85245d13e81ac6812a 
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 13916 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 208 bytes --]

On 17/05/2024 16:29, Eric J Bowman wrote
 > ...
> I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP.

Note that s2 is an alias for the WHOLE (SMI) disk, so there
will be nothing on s3 left ...

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

I'll admit it's a hack. Partition is named "iso-nly", labeled according to the .iso label, is wu but *really* it's ro, and all it does is mark ESP "hidden" which you can toggle on/off and see how that affects my boot-path setup. What really happens, is I've protected the first 4GB of the disk (and I've done it on spinning rust as well, circled all my squares and lined 'em up to sectors). I picture it like a CD on top of a 45 on top of a stack of LP's, some of which are those square promotional LP's from bitd. Except the CD is bigger than the 45, and most tools just see the entire disk as ISO9660. Anyway, does Solaris care if the fs is ZFS? Solaris Backup is a UFS thing, I thought.



-Eric






---- On Fri, 17 May 2024 07:37:12 -0700 Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote ---



On 17/05/2024 16:29, Eric J Bowman wrote 
 > ... 
> I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 
 
Note that s2 is an alias for the WHOLE (SMI) disk, so there 
will be nothing on s3 left ... 
 
------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98 
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 2179 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2913 bytes --]

The reason Bodhi's partition is hidden, is to prevent EFI stub-loading it, which it's fully capable of -- if you rebuild the kernel. I would include the Debian beta, but the installer fails on my systems. Mandrake works that way, and it's faster, but I use its GRUB2 to access Bodhi because, well, it's pretty, Bodhi doesn't have one, and it also picks up Boot Repair when it "scans" on install, so it comes last before I dd something to s0. It's very persnickety about even allowing you to run the installer, if it doesn't like your EFI setup; further, even if it allows the install to proceed, it will fail on creating bootloader, but be there to load from UEFI.



UEFI will not boot .iso from the BIOS menu unless it's burned to optical media and CDROM boot is enabled. Curiously, where Drakey's installer won't allow you to continue, Bodhi's will just say "see README". If you don't get that from Bodhi, you won't succeed even though you can install Drakey. It's not the easiest dual-boot. Notice I'm quadruple-booting to btrfs, iso9660, and ZFS-on-iso9660 (auto-expand to 4GB) filesystems at this point, no Ext or FAT12 or swap (because btrfs/zfs). 



-Eric






---- On Fri, 17 May 2024 07:55:25 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



I'll admit it's a hack. Partition is named "iso-nly", labeled according to the .iso label, is wu but *really* it's ro, and all it does is mark ESP "hidden" which you can toggle on/off and see how that affects my boot-path setup. What really happens, is I've protected the first 4GB of the disk (and I've done it on spinning rust as well, circled all my squares and lined 'em up to sectors). I picture it like a CD on top of a 45 on top of a stack of LP's, some of which are those square promotional LP's from bitd. Except the CD is bigger than the 45, and most tools just see the entire disk as ISO9660. Anyway, does Solaris care if the fs is ZFS? Solaris Backup is a UFS thing, I thought.



-Eric







---- On Fri, 17 May 2024 07:37:12 -0700 Udo Grabowski (IMK) <mailto:udo.grabowski@kit.edu> wrote ---








https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mce50e7fdde11c992c32f837e


On 17/05/2024 16:29, Eric J Bowman wrote 
 > ... 
> I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 

Note that s2 is an alias for the WHOLE (SMI) disk, so there 
will be nothing on s3 left ... 

------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 4832 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3206 bytes --]

Anyway, this is how I arrive at the Bad ioctl error, SunOS "forgets" that I used it to partition the drive in the first place.



-Eric






---- On Fri, 17 May 2024 08:07:50 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



The reason Bodhi's partition is hidden, is to prevent EFI stub-loading it, which it's fully capable of -- if you rebuild the kernel. I would include the Debian beta, but the installer fails on my systems. Mandrake works that way, and it's faster, but I use its GRUB2 to access Bodhi because, well, it's pretty, Bodhi doesn't have one, and it also picks up Boot Repair when it "scans" on install, so it comes last before I dd something to s0. It's very persnickety about even allowing you to run the installer, if it doesn't like your EFI setup; further, even if it allows the install to proceed, it will fail on creating bootloader, but be there to load from UEFI.



UEFI will not boot .iso from the BIOS menu unless it's burned to optical media and CDROM boot is enabled. Curiously, where Drakey's installer won't allow you to continue, Bodhi's will just say "see README". If you don't get that from Bodhi, you won't succeed even though you can install Drakey. It's not the easiest dual-boot. Notice I'm quadruple-booting to btrfs, iso9660, and ZFS-on-iso9660 (auto-expand to 4GB) filesystems at this point, no Ext or FAT12 or swap (because btrfs/zfs). 



-Eric







---- On Fri, 17 May 2024 07:55:25 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---








https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M4f20635b79863e58dbf4e2c4


I'll admit it's a hack. Partition is named "iso-nly", labeled according to the .iso label, is wu but *really* it's ro, and all it does is mark ESP "hidden" which you can toggle on/off and see how that affects my boot-path setup. What really happens, is I've protected the first 4GB of the disk (and I've done it on spinning rust as well, circled all my squares and lined 'em up to sectors). I picture it like a CD on top of a 45 on top of a stack of LP's, some of which are those square promotional LP's from bitd. Except the CD is bigger than the 45, and most tools just see the entire disk as ISO9660. Anyway, does Solaris care if the fs is ZFS? Solaris Backup is a UFS thing, I thought.



-Eric







---- On Fri, 17 May 2024 07:37:12 -0700 Udo Grabowski (IMK) <mailto:udo.grabowski@kit.edu> wrote ---









On 17/05/2024 16:29, Eric J Bowman wrote 
 > ... 
> I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 

Note that s2 is an alias for the WHOLE (SMI) disk, so there 
will be nothing on s3 left ... 

------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 5727 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3896 bytes --]

You have to start off aligned to none, then align to cylinder, then align to MiB, back to cylinder, back to MiB, and "Solaris Reserved" usually winds up being around 16MiB when aligned to cylinder so I set 24MB.



The stack of LP's... if a stack of squares lies between two rounds, all the squares must be in alignment. The top square must be aligned to sector.



There will always be padding between the edges of the square and the circumference of the circle. Some tools will report it, others will not.



-Eric







---- On Fri, 17 May 2024 08:12:28 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



Anyway, this is how I arrive at the Bad ioctl error, SunOS "forgets" that I used it to partition the drive in the first place.



-Eric







---- On Fri, 17 May 2024 08:07:50 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



The reason Bodhi's partition is hidden, is to prevent EFI stub-loading it, which it's fully capable of -- if you rebuild the kernel. I would include the Debian beta, but the installer fails on my systems. Mandrake works that way, and it's faster, but I use its GRUB2 to access Bodhi because, well, it's pretty, Bodhi doesn't have one, and it also picks up Boot Repair when it "scans" on install, so it comes last before I dd something to s0. It's very persnickety about even allowing you to run the installer, if it doesn't like your EFI setup; further, even if it allows the install to proceed, it will fail on creating bootloader, but be there to load from UEFI.



UEFI will not boot .iso from the BIOS menu unless it's burned to optical media and CDROM boot is enabled. Curiously, where Drakey's installer won't allow you to continue, Bodhi's will just say "see README". If you don't get that from Bodhi, you won't succeed even though you can install Drakey. It's not the easiest dual-boot. Notice I'm quadruple-booting to btrfs, iso9660, and ZFS-on-iso9660 (auto-expand to 4GB) filesystems at this point, no Ext or FAT12 or swap (because btrfs/zfs). 



-Eric







---- On Fri, 17 May 2024 07:55:25 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---










I'll admit it's a hack. Partition is named "iso-nly", labeled according to the .iso label, is wu but *really* it's ro, and all it does is mark ESP "hidden" which you can toggle on/off and see how that affects my boot-path setup. What really happens, is I've protected the first 4GB of the disk (and I've done it on spinning rust as well, circled all my squares and lined 'em up to sectors). I picture it like a CD on top of a 45 on top of a stack of LP's, some of which are those square promotional LP's from bitd. Except the CD is bigger than the 45, and most tools just see the entire disk as ISO9660. Anyway, does Solaris care if the fs is ZFS? Solaris Backup is a UFS thing, I thought.



-Eric







---- On Fri, 17 May 2024 07:37:12 -0700 Udo Grabowski (IMK) <mailto:udo.grabowski@kit.edu> wrote ---










On 17/05/2024 16:29, Eric J Bowman wrote 
 > ... 
> I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 

Note that s2 is an alias for the WHOLE (SMI) disk, so there 
will be nothing on s3 left ... 

------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription








https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mf93bf82fec40dc11a1fa2ef0

[-- Attachment #2: Type: text/html, Size: 7059 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Udo Grabowski (IMK)]

[-- Attachment #1: Type: text/plain, Size: 2259 bytes --]

On 17/05/2024 16:55, Eric J Bowman wrote:
> I'll admit it's a hack. Partition is named "iso-nly", labeled according 
> to the .iso label, is wu but *really* it's ro, and all it does is mark 
> ESP "hidden" which you can toggle on/off and see how that affects my 
> boot-path setup. What really happens, is I've protected the first 4GB of 
> the disk (and I've done it on spinning rust as well, circled all my 
> squares and lined 'em up to sectors). I picture it like a CD on top of a 
> 45 on top of a stack of LP's, some of which are those square promotional 
> LP's from bitd. Except the CD is bigger than the 45, and most tools just 
> see the entire disk as ISO9660. Anyway, does Solaris care if the fs is 
> ZFS? 

If the zpool has a property named 'bootfs' set (which usually points to
the rpool/ROOT/openindiana_whateverversion zfs filesystem), it will boot
from there.

Be aware that illumos based distributions don't use Grub/2 anymore, but
the BSD UEFI loader which is installed via the installboot command
(instead of installgrub).

> Solaris Backup is a UFS thing, I thought.

No, I think the name means just that you could start a dd from s2
directly to a tape to backup the whole (SMI) disk (regardless of
its contents). UFS is nowadays only used in the gzip-compressed
bootarchive (aka initrd on Linux), the target system is then mounted
from compressed iso images on the DVD (or CD for the "minimal" OI ISOs.

> 
> ---- On Fri, 17 May 2024 07:37:12 -0700 *Udo Grabowski (IMK) 
> <udo.grabowski@kit.edu>* wrote ---
> 
>     On 17/05/2024 16:29, Eric J Bowman wrote
>      > ...
>      > I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP.
> 
>     Note that s2 is an alias for the WHOLE (SMI) disk, so there
>     will be nothing on s3 left ...
> 
>     ------------------------------------------
>     illumos: illumos-discuss
>     Permalink:
>     https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98 <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98>
>     Delivery options:
>     https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription>
> 
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5804 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 503 bytes --]

The bubbabytes and booboobits of "VPMBR" i.e. Virtual:



s0 = 2048b, align=none

s1 = 1MiB, 4096e, Solaris Alternate which we'll use Disks to tag as MBR


s2 = 4GB - 320MiB, align=cylinder

s4/s5 = define in MiB, align to cylinder in parted, after deleting p0 after tagging s1=MBR

give ZFS all of s6



Everything works, before and after format>fd>ioct error.



How'd I make that PMBR/SMI "stick" that one time it worked? Because this is the error you otherwise get.



-Eric

[-- Attachment #2: Type: text/html, Size: 941 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3081 bytes --]

I wind up with GUID and all any OS sees in s2 is an ISO filesystem, and treats it as ro.



The problem is not *starting* with GUID.



What I wind up with, is SmartOS booting disk0 to GRUB, at which point you can chainload rEFInd and go to Tribblix rpool in s5, use zap to work with Zones, reboot to SmartOS as your hypervisor, and zlogin your zones from there if you want. Leaving s4 to be whatever you want it to be, I'll be keeping Drakey until Debodhi's out of beta, and putting my efforts at a lx/bhyve omnitribblix "Rescue CD" .iso which loads into RAM and runs Moksha desktop, so, two hypervisors on one disk, or one hypervisor/one GhostBSD, whatever.



-Eric






---- On Fri, 17 May 2024 08:45:32 -0700 Udo Grabowski (IMK) <udo.grabowski@kit.edu> wrote ---



On 17/05/2024 16:55, Eric J Bowman wrote: 
> I'll admit it's a hack. Partition is named "iso-nly", labeled according 
> to the .iso label, is wu but *really* it's ro, and all it does is mark 
> ESP "hidden" which you can toggle on/off and see how that affects my 
> boot-path setup. What really happens, is I've protected the first 4GB of 
> the disk (and I've done it on spinning rust as well, circled all my 
> squares and lined 'em up to sectors). I picture it like a CD on top of a 
> 45 on top of a stack of LP's, some of which are those square promotional 
> LP's from bitd. Except the CD is bigger than the 45, and most tools just 
> see the entire disk as ISO9660. Anyway, does Solaris care if the fs is 
> ZFS? 
 
If the zpool has a property named 'bootfs' set (which usually points to 
the rpool/ROOT/openindiana_whateverversion zfs filesystem), it will boot 
from there. 
 
Be aware that illumos based distributions don't use Grub/2 anymore, but 
the BSD UEFI loader which is installed via the installboot command 
(instead of installgrub). 
 
> Solaris Backup is a UFS thing, I thought. 
 
No, I think the name means just that you could start a dd from s2 
directly to a tape to backup the whole (SMI) disk (regardless of 
its contents). UFS is nowadays only used in the gzip-compressed 
bootarchive (aka initrd on Linux), the target system is then mounted 
from compressed iso images on the DVD (or CD for the "minimal" OI ISOs. 
 
> 
> ---- On Fri, 17 May 2024 07:37:12 -0700 *Udo Grabowski (IMK) 
> <mailto:udo.grabowski@kit.edu>* wrote --- 
> 
>     On 17/05/2024 16:29, Eric J Bowman wrote 
>      > ... 
>      > I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 
> 
>     Note that s2 is an alias for the WHOLE (SMI) disk, so there 
>     will be nothing on s3 left ... 
> 
>     ------------------------------------------ 
>     illumos: illumos-discuss 
>     Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98 <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98> 
>     Delivery options: 
> https://illumos.topicbox.com/groups/discuss/subscription 
>     <https://illumos.topicbox.com/groups/discuss/subscription> 
> 
>

[-- Attachment #2: Type: text/html, Size: 4480 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3753 bytes --]

If Tribblix's .iso were marked Joliet, it could be dd'd to s2, and used to update Tribblix in s5, by using rEFInd's iso9660.efi driver and zfsboot.efi driver. After chainloading into rEFInd, that is.



-Eric






---- On Fri, 17 May 2024 08:56:08 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



I wind up with GUID and all any OS sees in s2 is an ISO filesystem, and treats it as ro.



The problem is not *starting* with GUID.



What I wind up with, is SmartOS booting disk0 to GRUB, at which point you can chainload rEFInd and go to Tribblix rpool in s5, use zap to work with Zones, reboot to SmartOS as your hypervisor, and zlogin your zones from there if you want. Leaving s4 to be whatever you want it to be, I'll be keeping Drakey until Debodhi's out of beta, and putting my efforts at a lx/bhyve omnitribblix "Rescue CD" .iso which loads into RAM and runs Moksha desktop, so, two hypervisors on one disk, or one hypervisor/one GhostBSD, whatever.



-Eric







---- On Fri, 17 May 2024 08:45:32 -0700 Udo Grabowski (IMK) <mailto:udo.grabowski@kit.edu> wrote ---










https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M001c8dd8e23aded8a9fef1ce


On 17/05/2024 16:55, Eric J Bowman wrote: 
> I'll admit it's a hack. Partition is named "iso-nly", labeled according 
> to the .iso label, is wu but *really* it's ro, and all it does is mark 
> ESP "hidden" which you can toggle on/off and see how that affects my 
> boot-path setup. What really happens, is I've protected the first 4GB of 
> the disk (and I've done it on spinning rust as well, circled all my 
> squares and lined 'em up to sectors). I picture it like a CD on top of a 
> 45 on top of a stack of LP's, some of which are those square promotional 
> LP's from bitd. Except the CD is bigger than the 45, and most tools just 
> see the entire disk as ISO9660. Anyway, does Solaris care if the fs is 
> ZFS? 

If the zpool has a property named 'bootfs' set (which usually points to 
the rpool/ROOT/openindiana_whateverversion zfs filesystem), it will boot 
from there. 

Be aware that illumos based distributions don't use Grub/2 anymore, but 
the BSD UEFI loader which is installed via the installboot command 
(instead of installgrub). 

> Solaris Backup is a UFS thing, I thought. 

No, I think the name means just that you could start a dd from s2 
directly to a tape to backup the whole (SMI) disk (regardless of 
its contents). UFS is nowadays only used in the gzip-compressed 
bootarchive (aka initrd on Linux), the target system is then mounted 
from compressed iso images on the DVD (or CD for the "minimal" OI ISOs. 

> 
> ---- On Fri, 17 May 2024 07:37:12 -0700 *Udo Grabowski (IMK) 
> <mailto:udo.grabowski@kit.edu>* wrote --- 
> 
>     On 17/05/2024 16:29, Eric J Bowman wrote 
>      > ... 
>      > I burned bootrepair.iso to s2, "Solaris Backup"; s3 is ESP. 
> 
>     Note that s2 is an alias for the WHOLE (SMI) disk, so there 
>     will be nothing on s3 left ... 
> 
>     ------------------------------------------ 
>     illumos: illumos-discuss 
>     Permalink: 
> https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98 <https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M51cb9b4e8edb061b84a6be98> 
>     Delivery options: 
> https://illumos.topicbox.com/groups/discuss/subscription
>     <https://illumos.topicbox.com/groups/discuss/subscription> 
> 
>

[-- Attachment #2: Type: text/html, Size: 6144 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Bill Sommerfeld]

On 5/17/24 07:55, Eric J Bowman via illumos-discuss wrote:
> Anyway, does Solaris care if the fs is 
> ZFS? Solaris Backup is a UFS thing, I thought.

No, it lies below all filesystems.  It goes back at least as far as the 
era of BSD on vaxen (though partitions/slices were spelled differently, 
with single-letter suffixes rather than sN, so partition 'c' rather than 
slice 2), well before we had the ..p0 minor devices, when partition 
tables were compiled into disk drivers and you needed a partition that 
mapped the whole disk in one piece.

It is now redundant with ..p0 and it sticks around as tradition more 
than anything else.

Not sure why Solaris called it the 'Backup' slice but back in the day it 
occasionally was useful if you wanted to attempt to copy all partitions 
at once when a disk needed to be replaced ASAP (as long as you don't get 
confused about which disk is source and which is destination).

					- Bill

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]

So you're saying SunOS on UFS is still a COW?



I've been running this way for two months without illumos attempting to overwrite Boot Repair CD, seems to think it's rofs even if it says Solaris Backup to keep Linux from using it as swap.


-Eric


Sent using https://www.zoho.com/mail/








---- On Fri, 17 May 2024 09:13:18 -0700 Bill Sommerfeld via illumos-discuss <discuss@lists.illumos.org> wrote ---



On 5/17/24 07:55, Eric J Bowman via illumos-discuss wrote: 
> Anyway, does Solaris care if the fs is 
> ZFS? Solaris Backup is a UFS thing, I thought. 
 
No, it lies below all filesystems.  It goes back at least as far as the 
era of BSD on vaxen (though partitions/slices were spelled differently, 
with single-letter suffixes rather than sN, so partition 'c' rather than 
slice 2), well before we had the ..p0 minor devices, when partition 
tables were compiled into disk drivers and you needed a partition that 
mapped the whole disk in one piece. 
 
It is now redundant with ..p0 and it sticks around as tradition more 
than anything else. 
 
Not sure why Solaris called it the 'Backup' slice but back in the day it 
occasionally was useful if you wanted to attempt to copy all partitions 
at once when a disk needed to be replaced ASAP (as long as you don't get 
confused about which disk is source and which is destination). 
 
 - Bill 
 
 
------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M8ed335ba63e79f04543792a3 
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 2849 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

GhostBSD auto-expands ZFS to 4GB, in my setup it will overwrite ESP, unless ESP is hidden, which has no effect on anything else. I'm not sure what SmartOS does?



-Eric






---- On Fri, 17 May 2024 09:20:50 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



So you're saying SunOS on UFS is still a COW?



I've been running this way for two months without illumos attempting to overwrite Boot Repair CD, seems to think it's rofs even if it says Solaris Backup to keep Linux from using it as swap.



-Eric



Sent using https://www.zoho.com/mail/








---- On Fri, 17 May 2024 09:13:18 -0700 Bill Sommerfeld via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---








https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M2e32a6a3d142042398833e40


On 5/17/24 07:55, Eric J Bowman via illumos-discuss wrote: 
> Anyway, does Solaris care if the fs is 
> ZFS? Solaris Backup is a UFS thing, I thought. 

No, it lies below all filesystems.  It goes back at least as far as the 
era of BSD on vaxen (though partitions/slices were spelled differently, 
with single-letter suffixes rather than sN, so partition 'c' rather than 
slice 2), well before we had the ..p0 minor devices, when partition 
tables were compiled into disk drivers and you needed a partition that 
mapped the whole disk in one piece. 

It is now redundant with ..p0 and it sticks around as tradition more 
than anything else. 

Not sure why Solaris called it the 'Backup' slice but back in the day it 
occasionally was useful if you wanted to attempt to copy all partitions 
at once when a disk needed to be replaced ASAP (as long as you don't get 
confused about which disk is source and which is destination). 

 - Bill 


------------------------------------------ 
illumos: illumos-discuss 
Permalink: https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M8ed335ba63e79f04543792a3
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

[-- Attachment #2: Type: text/html, Size: 4423 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2368 bytes --]

> 
It is now redundant with ..p0 and it sticks around as tradition more 
than anything else.
 >



But it remains the case that my end result would be off by one if I didn't think in slices *and* partitions. Deleting p1 in Linux creates an empty s0 in Solaris, from there s/p is the same.



I believe I have everyone beat on archival storage. I am looking at my first boot drive, with a tape in it labelled "HWIAABL" containing the first code I ever wrote (with Dad's help). In 6502 assembly. "Hello World! I am a Bootloader." One ASCII character to spare, at the end of what was otherwise Apple's bootloader for the ][+ Dad brought home when I was 10. At first, while monitor and disk drives were on backorder, it lived on top of a Sony Trinitron, connected to a Yamaha Natural Sound tape deck I inherited. Dad's will said DO NOT REMOVE CASSETTE. I was touched!



It was copied from the Yamaha to a Sony Walkman, two 30-minute sides of Apple ][+ boot code. I've long since lost the MBR, the cassette box card was labeled with the rotation index of each of six boot loaders per side, so you'd let it know how long to play after bootstrapping, before hitting STOP/EJECT and putting in the tape with the program you wanted to execute. Boy did I ever drool over that stack of floppies that came with the machine, the only thing on tape was one bootloader.



Inspired by an article in Byte about how to put boot code at the beginning and end of both sides of your data tape to make a bootable exec. That tape deck plays my Dead/Phish collection just as well as my old Nakamichi 680zx, which we used an oscilloscope to tune to one type of tape on record, based on having a different type of tape as a source in the Yamaha. Nothing that isn't better preserved on archive.org, especially as the tapes finally begin to degrade.



Wish I had that old Walkman. When I told Dad about HTTP, he laughed at 502, said "that's the ol' code 52" and proceeded to tell me about leghorning your stack in case of accidental shuffle sort.


>
Not sure why Solaris called it the 'Backup' slice but back in the day it 
occasionally was useful if you wanted to attempt to copy all partitions 
at once when a disk needed to be replaced ASAP (as long as you don't get 
confused about which disk is source and which is destination). 
 
 - Bill
>



-Eric

[-- Attachment #2: Type: text/html, Size: 2861 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2975 bytes --]

Side A and B are different on the cassette, AHWIAABL and HWIAABLC depending on if we went big-endian or little-endian when we overwrote APPLEINC.



-Eric






---- On Fri, 17 May 2024 09:54:38 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



> 
It is now redundant with ..p0 and it sticks around as tradition more 
than anything else.
>



But it remains the case that my end result would be off by one if I didn't think in slices *and* partitions. Deleting p1 in Linux creates an empty s0 in Solaris, from there s/p is the same.



I believe I have everyone beat on archival storage. I am looking at my first boot drive, with a tape in it labelled "HWIAABL" containing the first code I ever wrote (with Dad's help). In 6502 assembly. "Hello World! I am a Bootloader." One ASCII character to spare, at the end of what was otherwise Apple's bootloader for the ][+ Dad brought home when I was 10. At first, while monitor and disk drives were on backorder, it lived on top of a Sony Trinitron, connected to a Yamaha Natural Sound tape deck I inherited. Dad's will said DO NOT REMOVE CASSETTE. I was touched!



It was copied from the Yamaha to a Sony Walkman, two 30-minute sides of Apple ][+ boot code. I've long since lost the MBR, the cassette box card was labeled with the rotation index of each of six boot loaders per side, so you'd let it know how long to play after bootstrapping, before hitting STOP/EJECT and putting in the tape with the program you wanted to execute. Boy did I ever drool over that stack of floppies that came with the machine, the only thing on tape was one bootloader.



Inspired by an article in Byte about how to put boot code at the beginning and end of both sides of your data tape to make a bootable exec. That tape deck plays my Dead/Phish collection just as well as my old Nakamichi 680zx, which we used an oscilloscope to tune to one type of tape on record, based on having a different type of tape as a source in the Yamaha. Nothing that isn't better preserved on archive.org, especially as the tapes finally begin to degrade.



Wish I had that old Walkman. When I told Dad about HTTP, he laughed at 502, said "that's the ol' code 52" and proceeded to tell me about leghorning your stack in case of accidental shuffle sort.



>
Not sure why Solaris called it the 'Backup' slice but back in the day it 
occasionally was useful if you wanted to attempt to copy all partitions 
at once when a disk needed to be replaced ASAP (as long as you don't get 
confused about which disk is source and which is destination). 

 - Bill
>



-Eric





https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-M8463ef92f99764f20c751b33

[-- Attachment #2: Type: text/html, Size: 4370 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.


-Eric


https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/T2e23d505617ba3d8-Mbfd00ce46a12a8ca86b68036

[-- Attachment #2: Type: text/html, Size: 2590 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2241 bytes --]

My laptop boots from disk0 as follows:



Solaris Boot (which is no more different from FreeBSD boot than HWIAABL is from APPLEINC) to GhostBSD menu, hit 6 to chainload rEFInd.



rEFInd presents you with three icons, left to right: CD icon labeled Tribblix, Penguin icon labeled GRUB2, ">" icon labeled Tribblix.



Tribblix CD icon is Peter's .iso cloned into an empty .iso tagged Joliet (took me two solid weeks to crack that nut), then burned to s2.



Grub2 menu will show Boot Repair CD, but only if it's in s2, or take you to Bodhi or OpenMandriva.



Branded Tribblix icon takes you to s6 rpool kitchen-sink. It isn't OmniTribblix, now I want it to be. Peter's included script does it from s2.

-Eric





---- On Fri, 17 May 2024 12:18:54 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.



-Eric











https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M57b0db8a8792d26afba78f40

[-- Attachment #2: Type: text/html, Size: 4196 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 2543 bytes --]

Or just lofi ghosty.iso, delete, copy from tribblix.iso... my way adds a seven-ASCII-character easter-egg string after it says Solaris.



-Eric






---- On Fri, 17 May 2024 12:58:33 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



My laptop boots from disk0 as follows:



Solaris Boot (which is no more different from FreeBSD boot than HWIAABL is from APPLEINC) to GhostBSD menu, hit 6 to chainload rEFInd.



rEFInd presents you with three icons, left to right: CD icon labeled Tribblix, Penguin icon labeled GRUB2, ">" icon labeled Tribblix.



Tribblix CD icon is Peter's .iso cloned into an empty .iso tagged Joliet (took me two solid weeks to crack that nut), then burned to s2.



Grub2 menu will show Boot Repair CD, but only if it's in s2, or take you to Bodhi or OpenMandriva.



Branded Tribblix icon takes you to s6 rpool kitchen-sink. It isn't OmniTribblix, now I want it to be. Peter's included script does it from s2.

-Eric






---- On Fri, 17 May 2024 12:18:54 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.



-Eric

















https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M36e9aa60fbdfc21a4d0dda53

[-- Attachment #2: Type: text/html, Size: 5015 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3222 bytes --]

Now I understand what I saw. I am testing with a variety of old and new drives, internal and external, various interfaces. The controllers abstract away the "gap space" between cirle and square, except NVMe which is DMA. Launch Bodhi from netboot.xyz (or download the .iso), use Gparted to make some partitions in MiB aligned to cylinder, nothing unexpected there, no unformatted space shown. Now, run the installer and select manual partitioning. Where did that unformatted space between the partitions come from?



-Eric






---- On Fri, 17 May 2024 13:34:41 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



Or just lofi ghosty.iso, delete, copy from tribblix.iso... my way adds a seven-ASCII-character easter-egg string after it says Solaris.



-Eric







---- On Fri, 17 May 2024 12:58:33 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



My laptop boots from disk0 as follows:



Solaris Boot (which is no more different from FreeBSD boot than HWIAABL is from APPLEINC) to GhostBSD menu, hit 6 to chainload rEFInd.



rEFInd presents you with three icons, left to right: CD icon labeled Tribblix, Penguin icon labeled GRUB2, ">" icon labeled Tribblix.



Tribblix CD icon is Peter's .iso cloned into an empty .iso tagged Joliet (took me two solid weeks to crack that nut), then burned to s2.



Grub2 menu will show Boot Repair CD, but only if it's in s2, or take you to Bodhi or OpenMandriva.



Branded Tribblix icon takes you to s6 rpool kitchen-sink. It isn't OmniTribblix, now I want it to be. Peter's included script does it from s2.

-Eric






---- On Fri, 17 May 2024 12:18:54 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.



-Eric






















https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M9a7b4dfc2cb0fa7a41dcaee7

[-- Attachment #2: Type: text/html, Size: 6251 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 3686 bytes --]

Top result from my Google search this morning:



[1] https://youtu.be/S8s9uzPIqQ4



Top result from the same search on DuckDuckGo:



[2] http://multiboot.solaris-x86.org/iv/3.html



Thanks for the laugh, Google, but the joke's on you... because you're the joke. A bad one.



-Eric







---- On Sat, 18 May 2024 10:05:10 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



Now I understand what I saw. I am testing with a variety of old and new drives, internal and external, various interfaces. The controllers abstract away the "gap space" between cirle and square, except NVMe which is DMA. Launch Bodhi from netboot.xyz (or download the .iso), use Gparted to make some partitions in MiB aligned to cylinder, nothing unexpected there, no unformatted space shown. Now, run the installer and select manual partitioning. Where did that unformatted space between the partitions come from?



-Eric







---- On Fri, 17 May 2024 13:34:41 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



Or just lofi ghosty.iso, delete, copy from tribblix.iso... my way adds a seven-ASCII-character easter-egg string after it says Solaris.



-Eric







---- On Fri, 17 May 2024 12:58:33 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



My laptop boots from disk0 as follows:



Solaris Boot (which is no more different from FreeBSD boot than HWIAABL is from APPLEINC) to GhostBSD menu, hit 6 to chainload rEFInd.



rEFInd presents you with three icons, left to right: CD icon labeled Tribblix, Penguin icon labeled GRUB2, ">" icon labeled Tribblix.



Tribblix CD icon is Peter's .iso cloned into an empty .iso tagged Joliet (took me two solid weeks to crack that nut), then burned to s2.



Grub2 menu will show Boot Repair CD, but only if it's in s2, or take you to Bodhi or OpenMandriva.



Branded Tribblix icon takes you to s6 rpool kitchen-sink. It isn't OmniTribblix, now I want it to be. Peter's included script does it from s2.

-Eric






---- On Fri, 17 May 2024 12:18:54 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.



-Eric





























https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M49dfbb4c980b6c06f4551b89

[-- Attachment #2: Type: text/html, Size: 7639 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 5244 bytes --]

I started down this path to fix my 3yo bootcamp'd iMac Pro that crashed two months ago, without just reinstalling and restoring from backup. I don't need to recover any data from it, which is a good thing because I haven't figured out how just yet. An OSX update caused the computer to not boot either OS, and no wonder.



I counted 89 partitions on the SDD, dozens hidden. No wonder it was slowing down. No wonder neither OS will boot. No clue what apps did that, or in which OS it was done, and some of those are the OS's implementing a backup strategy. I'm externally booting that machine, and learning a lot from the situation. I can only speculate how I wind up with seven hidden ReiserFS partitions, without having ever installed a ReiserFS driver... Edge? That you?



I'm building a USB rescue thingie that can handle what's out there, should also work with ARM where the platform has adopted GUEFI. My NanoPi R5c (Rockchip 5, OpenWRT) now boots OpenMandriva from the internal storage chip, but that's its own firmware boot procedure not UEFI, I don't think, but I haven't looked that closely as I have bigger computers to tackle.



My goal is to restore the iMac dual-boot. Then reformat that drive and never run either of those OS's bare-metal ever again. Not ever using them, is not possible due to apps I need which have no FOSS equivalent, or cross-OS support.


-Eric







---- On Sun, 19 May 2024 07:12:10 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



Top result from my Google search this morning:



[1] https://youtu.be/S8s9uzPIqQ4



Top result from the same search on DuckDuckGo:



[2] http://multiboot.solaris-x86.org/iv/3.html



Thanks for the laugh, Google, but the joke's on you... because you're the joke. A bad one.



-Eric








---- On Sat, 18 May 2024 10:05:10 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



Now I understand what I saw. I am testing with a variety of old and new drives, internal and external, various interfaces. The controllers abstract away the "gap space" between cirle and square, except NVMe which is DMA. Launch Bodhi from netboot.xyz (or download the .iso), use Gparted to make some partitions in MiB aligned to cylinder, nothing unexpected there, no unformatted space shown. Now, run the installer and select manual partitioning. Where did that unformatted space between the partitions come from?



-Eric







---- On Fri, 17 May 2024 13:34:41 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



Or just lofi ghosty.iso, delete, copy from tribblix.iso... my way adds a seven-ASCII-character easter-egg string after it says Solaris.



-Eric







---- On Fri, 17 May 2024 12:58:33 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



My laptop boots from disk0 as follows:



Solaris Boot (which is no more different from FreeBSD boot than HWIAABL is from APPLEINC) to GhostBSD menu, hit 6 to chainload rEFInd.



rEFInd presents you with three icons, left to right: CD icon labeled Tribblix, Penguin icon labeled GRUB2, ">" icon labeled Tribblix.



Tribblix CD icon is Peter's .iso cloned into an empty .iso tagged Joliet (took me two solid weeks to crack that nut), then burned to s2.



Grub2 menu will show Boot Repair CD, but only if it's in s2, or take you to Bodhi or OpenMandriva.



Branded Tribblix icon takes you to s6 rpool kitchen-sink. It isn't OmniTribblix, now I want it to be. Peter's included script does it from s2.

-Eric






---- On Fri, 17 May 2024 12:18:54 -0700 Eric J Bowman via illumos-discuss <mailto:discuss@lists.illumos.org> wrote ---



>

errno= Operation not supported

Cannot read vtoc information.

No fdisk solaris partition found.

>






Despite this error, fdisk will still work (not that I need it to do anything further, other than not report this error).



So will all other tools, everything all a-ok. The *only* thing that won't work, is when imaged to a larger drive, s9 will stay put.



If fdisk finds an EFI partition scheme, it assumes it's 100% of disk0, active or not.



Unless it found Solaris Boot, and followed it to the MBR Alternate Sector (my "VPMBR"), which it will only treat as MBR (instead of going to EFI partition to boot) if fdisk originally tagged it SMI/PMBR.



My clone of what I initially thought was a mistake, frees the hogs into a larger drive, to shove s9 out to the new boundary, Solaris builtin style, if s9 thinks it's SMI not EFI.



I don't know how to repeat my mistake, because now I know why it wasn't one. Pretty sure the "Operation not supported" refers to my desired free-hog behavior.



-Eric





































https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-Md5123496f63940585f7ec607

[-- Attachment #2: Type: text/html, Size: 9764 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

I have four optical drives I'm testing with, two internal, two external. One is on my Sun T5120, one is on an old MacBook Pro. One of the external drives is BD-RE, and therein lies the problem.

Now I understand why the security guys are saying to boot servers from single-layer optical media only, preferably CD. When burned to single-layer DVD (as it's too big for CD), GhostBSD boots as optical. When the BD-RE drive burns it to dual-layer DVD... it boots from that hidden FAT12 partition, even when using the DVD drive to boot. There is no way to tell the difference by observation.

So the 700MB distro limit, is imposed by the size limit of single-layer CD. The 4GB limit UEFI sets for optical media, refers to the 4.6GB limit, but uses 4GB in case someone mistakenly uses 4GiB, which is 4.22GB, so 4GB is the interop rule. The single-layer security recommendation, is legit.

-Eric
https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M4945d409b6320114c29f77b5

[-- Attachment #2: Type: text/html, Size: 2050 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 691 bytes --]

>

> There is no way to tell the difference by observation.

>


Using a boot disk with rEFInd, set logging=2 in refind.conf; boot GhostBSD single-layer DVD, chainload into rEFInd, swap in the dual-layer DVD, select reboot, chainload again, then diff refind.log vs. refind.old.log; you'll see it plain as day. The first boot says MBR, the reboot says ESP.

-Eric







https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M37c7d8acab3069d6e518ed7e

[-- Attachment #2: Type: text/html, Size: 1902 bytes --]

Re: [discuss] Bad ioctl DKIOCGEXTVTOC - updated

[Eric J Bowman]

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

Unintended side-effect whose ramifications just dawned on me:



>

>>
To make an optical-boot Tribblix installer:



dd if=tribblix.iso of=smartos.iso seek b=34



Now it's bootable, unless you want secure boot, in which case just...



***CENSORED***



...and UEFI will happily secure-boot Tribblix, thinking it's SmartOS.

>>
>



Actually, UEFI will happily secure-boot AnyOS, thinking it's AnyOS, from single-layer optical media "to boot."



Oopsies!


-Eric






---- On Mon, 20 May 2024 08:08:06 -0700 Eric J Bowman via illumos-discuss <discuss@lists.illumos.org> wrote ---



>

> There is no way to tell the difference by observation.

>


Using a boot disk with rEFInd, set logging=2 in refind.conf; boot GhostBSD single-layer DVD, chainload into rEFInd, swap in the dual-layer DVD, select reboot, chainload again, then diff refind.log vs. refind.old.log; you'll see it plain as day. The first boot says MBR, the reboot says ESP.

-Eric














https://illumos.topicbox.com/latest / illumos-discuss / see https://illumos.topicbox.com/groups/discuss + https://illumos.topicbox.com/groups/discuss/members + https://illumos.topicbox.com/groups/discuss/subscription https://illumos.topicbox.com/groups/discuss/Tc643026b8cfbd978-M78bfa4cab9df77fa06bb6f06

[-- Attachment #2: Type: text/html, Size: 3286 bytes --]