Well. My guess seemed to be true again. Here is the output of Linux's fdisk:
fdisk -l /dev/sdc GPT PMBR size mismatch (4008112 != 30031871) will be corrected by write. The backup GPT table is not on the end of the device. This problem will be corrected by write. Disk /dev/sdc: 14.3 GiB, 15376318464 bytes, 30031872 sectors Disk model: Cruzer Force Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E34D276B-2790-236C-E97C-E1EFEEAEAD80 Device Start End Sectors Size Type /dev/sdc1 256 69887 69632 34M EFI System /dev/sdc2 69888 71935 2048 1M Solaris boot /dev/sdc3 71936 3991694 3919759 1.9G Solaris root /dev/sdc9 3991696 4008079 16384 8M Solaris reserved 1 You just dd-ed your iso image into /dev/sdc3 (don't know which Solaris name it is, to be fair!) No way to expand or extend or modify this scheme! Since there is no writable file system to be expand or extend or modify at all! Perhaps Linux's Gparted could do something with the partition table and possibly creating new partition. But who care? The point is having an read/write area for OI on the usb stick. And it seemed unfeasible now. ---- On Tue, 26 Jan 2021 08:18:16 +0700 Hung Nguyen Gia via openindiana-discuss <[email protected]> wrote ---- > v1 is failed because no one could give a solution. > > https://openindiana.org/pipermail/openindiana-discuss/2021-January/023341.html > > > So I start v2. > > As I said here: > https://openindiana.org/pipermail/openindiana-discuss/2021-January/023555.html > > > I only left with fdisk. And my guess was right, it's not work. > > The ONLY thing it showed me is a EFI partition with Length is 250, no other > partitions to expand, no actual partition that contain the distro's data. > > The Solaris fdisk is extremely limited compared to Linux fdisk or even > FreeBSD, to be fair! > > I don't know your partitioning scheme on your live usb. > > Please explain and give me DETAIL answer, not kind of DIY answers I > previously received on v1. > > If my guess is not wrong, then: > > You just have an EFI partition in order to boot. > > Then you just dd-ed your iso image into the unallocated space and let your > boot loader mount it during boot. > > This is the reason why fdisk only shows just one EFI partition and nothing > else. Does it true? > > I saw no UFS partition, no writable file systems at all to be fair. On > Linux, Gparted only display a bunch of black and very small partitions: > https://imgur.com/FmcrVMF.png > > If there was an UFS file system, Linux could mount it automatically, auto > mount is turned on on all Linux nowadays, albeit just read-only for UFS. > But, I saw nothing. > > _______________________________________________ > openindiana-discuss mailing list > [email protected] > https://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ openindiana-discuss mailing list [email protected] https://openindiana.org/mailman/listinfo/openindiana-discuss
