-
DarkUranium
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.
-
DarkUranium
Basically, I get this: /lib/rc/sh/openrc-run.sh: /etc/init.d/sysfs: line 4: syntax error: unexpected "}"
-
mongole
back in town and still unable to boot SmartOS from SSD. no bootable device found. any ideas what went wrong during installation?
-
tsoome_
mongole is it uefi or bios boot?
-
mongole
pure uefi. csm is disabled
-
mongole
[root@smartos ~]# piadm bootable
-
mongole
zones ==> BIOS and UEFI
-
mongole
[root@smartos ~]# piadm list
-
mongole
PI STAMP BOOTABLE FILESYSTEM BOOT IMAGE NOW NEXT
-
mongole
20241128T004404Z zones/boot next yes yes
-
tsoome_
is ESP present?
-
mongole
how to check that?
-
mongole
I booted from usb and chose to make the pool bootable. ssd was empty before
-
tsoome_
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)
-
tsoome_
the ssd should be partitioned to have slice 0 for ESP (EFI system partition) with FAT32 and in it efi/boot/bootx64.efi
-
mongole
-
mongole
does that help?
-
tsoome_
ok, the partition is there. so you want to verify its content as well. mount -F pcfs /dev/dsk/c1t1d0s0 /mnt ; ls -lR /mnt
-
tsoome_
and then umount /mnt
-
mongole
-
tsoome_
so the content seems to be good as well.
-
tsoome_
this means, you would need to try to browse this disk from firmware
-
mongole
so boot into uefi shell?
-
tsoome_
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
-
tsoome_
uefi shell or just try to use the boot from file option if you have one
-
tsoome_
thei default file path is basically meant for removable media and it is possible the boot from internal disk does not use it.
-
tsoome_
havent had enough time to implement efirt module and userland option to enable installer to create boot manager entry...
-
tsoome_
boot manager == UEFI firmware boot manager, thats the component in firmware to load and start OS boot loader.
-
mongole
hmm seems my device does not have an uefi shell and also no option to boot from a file
-
mongole
maybe I need to boot a linux and use efibootmgr to create an UEFI boot entry?
-
tsoome_
thats one way. or, check if there is firmware update:D
-
tsoome_
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....
-
mongole
no uefi update available :) I will try with a live linux later. thanks for your help up to here
-
tsoome_
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
-
tsoome_
thats assuming disk1 is your ssd
-
mongole
so.. I was able to create the uefi boot entry using an ubuntu live iso
-
mongole
efibootmgr --create --disk /dev/sda --part 1 --label "SmartOS" --loader '\EFI\Boot\bootx64.efi'
-
mongole
now smartos boots from ssd :)
-
mongole
thanks tsoome and danmcd
-
tsoome
ok, so it was needing the boot entry? what hw is it btw?
-
mongole
it's a thin client. Fujitsu Futro S920
-
mongole
yes there was no boot entry
-
tsoome
yep, we do not create any because we have no tool for that yet.
-
mongole
maybe that should be part of thee installation instructions
-
tsoome
does it tell the vendor of the firmware?
-
mongole
how do I find out. not yet very familiar with the userland tools of illumos :)
-
mongole
-
danmcd
I wonder if piadm(8) needs to Do More there?
-
danmcd
I mean, it shouldn't? But maybe the programs it invokes (e.g. installboot?) should?
-
danmcd
I *thought* '\EFI\Boot\bootx64.efi" was a standard UEFI entry that every UEFI boot rom knew about?
-
tsoome
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
-
tsoome
danmcd they do know, but as always, there is room for interpretation
-
danmcd
Eeesh.
-
tsoome
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:)
-
tsoome
I guess, we should really get efirt module implemented and then we can port efibootmgr ...
-
mongole
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
home-assistant.io/installation/gene…x86-64#start-up-your-generic-x86-64
-
tsoome
:) I guess it is common enough issue. altho, I think I have heard about it only once before:)
-
mongole
is there an easy way to get OmniOS running as zone on smartos? it's not in the list of available images
-
tsoome
via bhyve brand.
-
mongole
but this is a vm, not a container, correct?
-
pjustice
It _is_ possible to build your own container images, though that's not exactly "easy".