19:59:47 upgrading an old host from 151038 to 151046. It mostly worked. However, it got really pissy about the "UsePAM no" command in sshd_config. 19:59:53 other than that it seems to have survived. 20:06:08 oh, it's also upset about svc:/system/hal 20:15:54 I think it warns about UsePam as deprecated, but did it do something else? 20:18:04 it failed to start ... several hundred times. 20:18:22 "Start method failed repeatedly, last exited with status 255" 20:18:31 I removed the line from sshd_config and it's starting now. 20:18:42 though it's ignoring my duo 2FA so I'll need to fix that. 20:19:47 pam, as far as know, has always been permanently on in the omnios openssh. I didn't think it was fatal to have it in the configuration file though, I wonder when that happened? 20:19:53 it also takes for-freakin-ever to mount filesystems after boot. I'm waiting to see if anything more shows up on the console about failed starts. 20:20:12 it was set to 'no' for this host for reasons long lost to history. 20:20:47 ah, it's failing to start svc:/system/hal so that's what's causing slow mounts. 20:21:05 STATE STIME FMRI 20:21:05 maintenance 13:20:01 svc:/system/hal:default 20:21:56 Reason: Start method exited with $SMF_EXIT_ERR_FATAL. 20:22:03 well that's useful information... not. 20:22:31 [ Jun 7 13:15:50 Executing start method ("/lib/svc/method/svc-hal start"). ] 20:22:31 hal failed to start: error 2 20:22:31 [ Jun 7 13:20:01 Method "start" exited with status 95. ] 20:22:44 but it starts fine with svcadm clear and svcadm enable. 20:22:53 so it's something it doesn't like during boot. 20:24:20 error 2 seems to be that one of its children timed out 20:24:34 - more than 250s for device probing 20:24:49 ah.. interesting. 20:24:58 * nomad wonders if mtp_sas0 is unhappy 20:25:47 I have to step afk, but good luck getting to the bottom of it, and welcome to r46! 20:26:18 thanks... I think :) 20:27:48 "dmesg | grep -i warning" has much to say about error recovery for port 4 and 5.