08:15:48 [illumos-gate] 17303 rmvolmgr: dprintf() cleanup -- Hans Rosenfeld 13:57:22 hi. I had questions about my recent smartos installation, and the site lists #smartos and #illumos channels for real time chat, but the former is vacant (although the topic is set) 13:58:31 basically my issue is that I installed it on one of 2 nvme drives, including a bootable zfs partition, but from the bios menu it's not recognizing the drive as bootable 13:59:38 I also tried using an omnios cd to get a loader menu, and I can see the devices correctly with lsdev, but I don't know how to manually boot into it 13:59:49 does anybody have an ideas? 14:01:44 are you using UEFI? 14:02:45 yes. the efi-loader command returns "2.80" 14:16:54 you could try dropping into the uefi shell 14:17:05 eh, i'm discovering that it's historical normal to boot smartos via usb key or network/pxe boot 14:17:12 and trying different 'drives' (it's like DOS, so you have fs0: fs1: etc) 14:17:33 and see if it can see it 14:17:36 you mean from the bios menu? 14:17:53 UEFI often inclues a uefi shell 14:18:06 i recall that as an option. i had no idea how to use it 14:18:38 one of the problems is that despite the UEFI spec being clear on certain things, certain vendors have decided to deviate from it for dubious 'value add' features... which includes things like booting 14:18:46 marino you installed smartos and are rebooting without the usb key or the installer did not work? 14:18:50 it's like command.com 14:19:06 but instead of A:, B: etc you have fs0: fs1: etc 14:19:54 some vendors e.g. supermicro do some non-standard "value add" (of dubious value) things to UEFI booting 14:20:30 where you have to jump through some extra hoops before it'll show you additional disks w/ bootable UEFI system partitions 14:20:35 neirac_: so it's a long story. I burned a usb key and it was a slick installer. I answered a few questions and turned away, and the box had rebooted to the other disk. I couldn't get the usb key to work right again, so I burned a ISO on a CD. I did successfully install it via ISO. but there's no loader menu option on that iso. 14:21:02 I had an omnios disk that does that loader menu and I can see the zfs devices but I'm stuck there 14:21:21 but from what I'm reading -- smartos doesn't just "boot" 14:21:22 marino oh ok, in smartos if you want to boot from disks you need to use piadm 14:21:47 let me google that -- never heard of it 14:22:22 if you don't want to use the usb anymore, you use piadm. but first you need to be able to login to your smartos box 14:23:04 marino https://docs.smartos.org/remotely-upgrading-a-usb-key-based-deployment/ 14:23:22 marino https://smartos.org/man/8/piadm 14:23:37 so I walked into this a bit ignorant 14:24:08 for the record, during the install I did set up the zfs pool to be bootable (something piadm supposedly does) 14:25:23 so I have a chicken-egg problem? I need to get this disk booted so I can use piadm? 14:27:12 i might try reburning that usb key and see if that helps 14:28:37 marino booting from the usbkey should work as long as your machine boot order usb is first, then the rest of devices. 14:29:42 which it is. for some reason the key stopped being recognized and the bios would skip it 14:30:01 which is why I switched to the iso which has a completely different interface 14:39:28 yeah, I just reburned it and the usb key is getting skipped. I used rufus on windows with the ".usb" image. it worked before. not sure what's changed. 15:07:56 okay, I burned the USB key again with linux (dd command) and now I can boot into smartos 15:27:27 marino great! 15:28:35 i'm trying to figure this piadm out to see if I can avoid the usb key. i haven't done so yet 15:34:34 i think my problem is that when I manually created the zones zpool I didn't specify the -B option which is why the bios isn't seeing it 15:35:34 but piadm list shows zones/boot as bootable so I don't know 15:52:49 i'll probably have to complete reinstall to create "zones" zpool with -B option 16:40:25 wow, it happened again. I rebooted the box and now the USB key is skipped again. 16:40:49 ah, disregard. I removed earlier! doh. 16:41:31 yeah, it's still working 17:29:38 it's not allowing me to re-install. the option is gone. i guess it sees a valid zones zpool and drops that option from the menu 17:47:14 marino If this server does not have any important data (this process will DESTROY all the data on the disks), and you understand that you will lose all your data, drop to a shell and type sdc-factory-reset, reboot and you will able to reinstall. 17:48:39 cool. to confirm, it's only going to destroy disks of the "zones" zpool (which is a single M2 drive for me) 17:49:05 i can't see how it could affect the other drive but doesn't hurt to ask 18:05:24 it's "sdc-factoryreset". So that worked until the point I created the zones zpool. it said it already existed and skipped it (meaning my change to support UEFI was skipped) 18:09:57 maybe it needed the -f flag for the zpool create command 18:16:35 nope. I think I went the wrong path. I had put "media" for the install and later it says it didn't make it bootable because it couldn't find install media, so I'll try again with "latest" 18:28:25 yep, it required "latest" to work 18:33:32 it's working now. Bios recognizes the drive and I can set it to boot directly without the usb key 20:19:15 marino that's great