01:51:57 lol is this like when zfs tells you file <0x0> is corrupted, but everything on the dataset still seems to work and you have no idea what it's talking about 07:37:20 current Hipster kernel seems broken (https://i.imgur.com/IzcK8IT.png) - known? 07:38:05 My last good beadm seems 9/28. 08:45:47 arekinath: lol, Ive got some pools with corrupt blk devices.... and the users never say a thing lol 14:48:48 Good afternoon. Guten Nachmittag. Bon après-midi. Добрый день. 18:17:55 trn: that looks like your boot archive is hosed, you should be able to boot an old BE, and rebuild a boot archive in a new be by mounting that BE and doing bootadm update-archive -R /path/to/new/be/mount 18:45:45 richlowe: I've got no problem booting any old BE - when I update it again though, and nothing special, just a "simple" `pkg update`, I end up in the same situation. 18:46:47 richlowe: I can actually boot into an older BE without any problem, but the problem happens again just doing a standard update with IPS (`pkg update`, nothing special) and trying to boot into the new BE. 18:47:02 right, try updating the boot archive manually and see if that fixes it for that BE 18:47:09 if so, you need to work out why doing it automatically isn't working properly. 18:47:13 I've not tried to look into it further. 18:47:24 Apparently, it's happening to just me :) 18:47:27 so the bootadm command I gave you should rebuild it from another BE 18:47:37 you can add '-v' to make it verbose, if that helps 18:47:48 but mysterious ELF complaints from early boot like that are almost always a corrupt boot-archive 18:48:02 it's very difficult to _build_ an object that broken, much easier to have the boot-archive be truncated 18:48:05 I'll give it a shot. I've never had any major problems with OI lately. I'm just wondering what could have changed. 18:49:00 I usually update my OI images ever 2 weeks or so (I use them for CI/CD). 18:54:44 richlowe: Interestingly, I see an ATA error (informational, read error) in my log. But that's a bit odd. 18:55:19 (it's actually a disk is that is being served to the VM over iSCSI) 18:56:21 so perhaps the problem is something in virtio drivers, or further up the chain. 18:58:17 richlowe: I just tried your suggestion of bootadm update-archive before booting into the new be, same error. 18:58:47 hm 18:58:52 then I don't know what's going on 18:59:09 I don't think toomas did anything to the loader or any of that recently 18:59:12 I'm going to try to verify all the packages first, see if there is any other corruption or something odd. 18:59:17 toasterson: is this familiar? 19:01:04 It's trivial for me to bring up a completely new image as well, so it's not a showstopper. But I'd feel like that's admitting defeat. 19:03:21 I'll also actually look at the kernel file size and such, and try bootadm verbose too, after I verify the installed packages and filesystems. 19:03:26 Thanks for the suggestions. 19:10:37 All packages verified without errors. 19:10:55 I'm doing an update and then I'll see what bootadm verbose says, etc. 19:24:49 richlowe: Everything seems to be mostly normal. https://i.imgur.com/NFYv5MP.png 19:24:55 Sorry for the images, using a SPICE console. 19:26:21 that looks normal yes, except it not having had the etc/system.d file 19:26:28 I don't know, sorry :\ 19:28:16 Well, well. 19:28:25 It booted into the new be fine this time. 19:28:46 I'm at a loss to explain it, because I didn't do anything differently. 19:29:25 And the verification didn't need to fix anything. I'll run pkg fix again now, and I'll scrub the whole pool. 19:30:27 If there is anything I can provide that might be helpful, let me know. I'll keep that particular older be around for awhile. 19:39:06 hm, hash with length 0x0? 19:46:05 No errors after scrubbing the pool. 19:52:54 Who can I complain to that OI's gdb requires python37? :) 19:53:45 I hate having three Python-3's installed... 20:34:04 Also, speaking of weirdness. I haven't tested it lately, but strip seems to totally destroy go binaries. 20:34:28 But Go in general seems to work really well on illumos these days, I'm really pleased with it. 20:59:25 looks like someone just did: https://www.illumos.org/issues/15091 20:59:26 → BUG 15091: strip(1) rips go binaries apart (New) 21:01:30 oh dear XD 22:06:48 Is OmniOS well supported? 22:23:43 I don't know the status of it, but quite a few of the principals hang around here. 22:25:52 I had a problem with libuv and andyf here had debugged it and fixed it before I even had a chance to look into it. :) 22:26:40 I use OmniOS on my VPS that uses illumos - so I'd hope so. 23:13:29 trn: me :) gdb probably needs a rebuild then. Let me have a look 23:19:01 it looks like go binaries are incorrect, but I'm not sure that's why we destroy them 23:19:46 and I'm looking at older binaries, it's possible newer binaries are incorrect-er 23:20:08 one for nahamu to fix for us in go, and then see if we still screw it 23:25:55 seoul: I use OmniOS LTS r151038 for a number of production services. Security patches are promptly available and I've not had things break because of upgrades. 23:26:07 I've been very happy with it 23:37:09 Sounds great, thank you. 23:52:07 toasterson: Ah, thanks. I saw that migration from python-35 is in progress. But besides some system components that are using 3.5, the only item I have that has a Python 3.7 dependency is gdb. 23:52:36 Everything else is 3.9 23:53:28 trn: yeah looks like gdb had an update when we where working with python 3.7 and before 3.9