12:17:46 Hm. Not sure if it's just me, but the alpine-3 image seems broken in SmartOS? For example, I can't start sysfs by default, unless I modify /etc/init.d/sysfs. 12:20:31 Basically, I get this: /lib/rc/sh/openrc-run.sh: /etc/init.d/sysfs: line 4: syntax error: unexpected "}" 13:09:43 back in town and still unable to boot SmartOS from SSD. no bootable device found. any ideas what went wrong during installation? 13:50:42 mongole is it uefi or bios boot? 14:09:14 pure uefi. csm is disabled 14:11:09 [root@smartos ~]# piadm bootable 14:11:10 zones ==> BIOS and UEFI 14:11:24 [root@smartos ~]# piadm list 14:11:24 PI STAMP BOOTABLE FILESYSTEM BOOT IMAGE NOW NEXT 14:11:24 20241128T004404Z zones/boot next yes yes 14:11:54 is ESP present? 14:12:28 how to check that? 14:12:48 I booted from usb and chose to make the pool bootable. ssd was empty before 14:14:42 there is 2 options for that -- if your firmware boot manager does let to browse the disk for bootable file or if you check disk partition from the running system (like usb boot) 14:15:38 the ssd should be partitioned to have slice 0 for ESP (EFI system partition) with FAT32 and in it efi/boot/bootx64.efi 14:17:39 https://paste.f1sh.de/?3c5b5a848ed6a407#BgfFAHKggKuTtkDMcSDBDLibhB3H4qrYcBPM534TJcuT 14:17:43 does that help? 14:18:57 ok, the partition is there. so you want to verify its content as well. mount -F pcfs /dev/dsk/c1t1d0s0 /mnt ; ls -lR /mnt 14:19:03 and then umount /mnt 14:19:39 https://paste.f1sh.de/?5d5cc729018a1e91#6c5nYFm89uvufoUhQFEbFcpwQeJjYtmBap21b1mwgXJd 14:21:11 so the content seems to be good as well. 14:21:45 this means, you would need to try to browse this disk from firmware 14:21:59 so boot into uefi shell? 14:22:48 it is possible that your firmware does not want to fall back to default efi/boot/bootx64.efi file load and needs to have boot entry created from firmware boot manager 14:23:17 uefi shell or just try to use the boot from file option if you have one 14:24:02 thei default file path is basically meant for removable media and it is possible the boot from internal disk does not use it. 14:25:32 havent had enough time to implement efirt module and userland option to enable installer to create boot manager entry... 14:26:27 boot manager == UEFI firmware boot manager, thats the component in firmware to load and start OS boot loader. 14:29:17 hmm seems my device does not have an uefi shell and also no option to boot from a file 14:30:14 maybe I need to boot a linux and use efibootmgr to create an UEFI boot entry? 14:30:42 thats one way. or, check if there is firmware update:D 14:31:57 once had the case where firmware did not create memory mapped framebuffer on lenovo laptop and so there was no console, fortunately firmware update did fix it.... 14:33:07 no uefi update available :) I will try with a live linux later. thanks for your help up to here 14:35:38 what you can try is start from usb, press esc to get out of boot menu and then: use lsdev -v to get device name and: chain disk1p1:/efi/boot/bootx64.efi to boot from ssd 14:35:58 thats assuming disk1 is your ssd 20:14:27 so.. I was able to create the uefi boot entry using an ubuntu live iso 20:14:45 efibootmgr --create --disk /dev/sda --part 1 --label "SmartOS" --loader '\EFI\Boot\bootx64.efi' 20:14:56 now smartos boots from ssd :) 20:16:23 thanks tsoome and danmcd 20:17:06 ok, so it was needing the boot entry? what hw is it btw? 20:17:25 it's a thin client. Fujitsu Futro S920 20:17:34 yes there was no boot entry 20:17:57 yep, we do not create any because we have no tool for that yet. 20:18:04 maybe that should be part of thee installation instructions 20:18:44 does it tell the vendor of the firmware? 20:19:59 how do I find out. not yet very familiar with the userland tools of illumos :) 20:22:03 https://paste.f1sh.de/?df6f7b1393fab9aa#3nj83S72kvTBGHY7R34ywNkLuBy1dduKTUhyUtVDxi2h 20:26:08 I wonder if piadm(8) needs to Do More there? 20:26:42 I mean, it shouldn't? But maybe the programs it invokes (e.g. installboot?) should? 20:27:27 I *thought* '\EFI\Boot\bootx64.efi" was a standard UEFI entry that every UEFI boot rom knew about? 20:27:46 mongole usually when you enter to formware setup, it does tell, but of course, in case of Fujitsu it is likely to be Fujitsu anyhow:D 20:28:18 danmcd they do know, but as always, there is room for interpretation 20:28:42 Eeesh. 20:29:28 same way some vendors interpret FAT12/FAT16 to be used only with removable media and only accept FAT32 on fixed disks - which is why we do create FAT32 in ESP:) 20:31:22 I guess, we should really get efirt module implemented and then we can port efibootmgr ... 20:33:10 interestingly, the home assistant installation instructions state exactly the same thing. boot a live linux and create the uefi entry manually if it is missing after installation https://www.home-assistant.io/installation/generic-x86-64#start-up-your-generic-x86-64 20:35:47 :) I guess it is common enough issue. altho, I think I have heard about it only once before:) 21:33:59 is there an easy way to get OmniOS running as zone on smartos? it's not in the list of available images 22:28:00 via bhyve brand. 22:49:48 but this is a vm, not a container, correct? 22:54:03 It _is_ possible to build your own container images, though that's not exactly "easy".