Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
Install grub did not fix the issue. Its booting up with temp BE’s everytime. This issue is really weird. I noticed that the zpool thinks that one of its disks are c6t0d0s0 but its actually using c5t0d0s0 could this be related? Thanks for your help this evening. On 11/29/16, 7:30 PM, "Dan

[OmniOS-discuss] USB3 repo & media updated!

2016-11-29 Thread Dan McDonald
Now that a new bloody is out, so is a new bloody+xhci/USB3: The repo is:http://pkg.omniti.com/omnios/USB3/ The install media path is still here, but with refreshed files: http://kebe.com/~danmcd/USB3-media/ md5 (OmniOS-USB3-initial.iso) = 63db82350619b01a7267aee6a3d0f5ce sha1

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
So that’s the final caveat here lol…bootadm says that the menu file is at that path but that file structure doesn’t actually exist. Been racking my brain on this most of the afternoon. ls /tmp total 87 drwxrwxrwt 21 root sys1536 Nov 29 18:54 . drwxr-xr-x 27 root root 31 Nov

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread Dan McDonald
Hmmm, try re-writing your rpool's menu.lst: cp /tmp/bootadm_mnt_zfs_legacy.1603/boot/grub/menu.lst /rpool/boot/grub/. See if that helps out. Dan ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
Thanks Dan, One issue…I can’t backup my BE for a like reason. beadm create omnios-backup2 Unable to create omnios-backup2. Missing boot menu file. On 11/29/16, 7:11 PM, "Dan McDonald" wrote: > On Nov 29, 2016, at 8:06 PM, John Barfield

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread Dan McDonald
> On Nov 29, 2016, at 8:06 PM, John Barfield wrote: > > Hi Dan, > > I hit a bad key combination and outlook sent me email prematurely. > > I’d like to update to the latest stable release. The old nfs lockd bug is on > my last nerve. Oh my... I also just

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
pkg On 11/29/16, 7:00 PM, "Dan McDonald" wrote: > On Nov 29, 2016, at 7:51 PM, John Barfield wrote: > > Good evening, > > I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg src: > >

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
Hi Dan, I hit a bad key combination and outlook sent me email prematurely. I’d like to update to the latest stable release. The old nfs lockd bug is on my last nerve. This box doesn’t have any active production zones any longer its only acting as SAN/NAS. Thanks for your help and quick

Re: [OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread Dan McDonald
> On Nov 29, 2016, at 7:51 PM, John Barfield wrote: > > Good evening, > > I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg src: > > WARNING: The boot environment being modified is not the active one. Changes > made will not be reflected

[OmniOS-discuss] boot environment mounting on /tmp/tmp.x

2016-11-29 Thread John Barfield
Good evening, I’m trying to upgrade an omnios 151012 and I keep getting errors from pkg src: WARNING: The boot environment being modified is not the active one. Changes made will not be reflected on the next boot. If I try to activate the “omnios” be it says: Unable to activate omnios. Missing

Re: [OmniOS-discuss] Intel Corporation 82599ES 10-Gigabit not working since upgrade to r151020

2016-11-29 Thread Michael Rasmussen
On Tue, 29 Nov 2016 10:37:19 -0500 Dan McDonald wrote: > > You can still use your cisco one with the unsupported_sfp check off. If it's > been working for you, why not? > > OTOH, I hear (I don't use much SFP) that they can be tricky to debug when > problems DO occur. I

Re: [OmniOS-discuss] OpenSSH and reverse DNS

2016-11-29 Thread Dan McDonald
> On Nov 29, 2016, at 6:50 AM, Lauri Tirkkonen wrote: > > On Tue, Nov 29 2016 13:30:17 +0200, Lauri Tirkkonen wrote: >> On Tue, Nov 29 2016 10:47:10 +0100, Olaf Marzocchi wrote: >>> Dear all, >>> Since I upgraded to OpenSSH I have the following problem with DNS: >>> reverse

Re: [OmniOS-discuss] Intel Corporation 82599ES 10-Gigabit not working since upgrade to r151020

2016-11-29 Thread Dan McDonald
> On Nov 29, 2016, at 9:02 AM, Richard Skelton wrote: > > What SFP+ P/N should I use? You can still use your cisco one with the unsupported_sfp check off. If it's been working for you, why not? OTOH, I hear (I don't use much SFP) that they can be tricky to debug when

Re: [OmniOS-discuss] Intel Corporation 82599ES 10-Gigabit not working since upgrade to r151020

2016-11-29 Thread Richard Skelton
Hi, After setting the allow_unsupported_sfp = 1; I now see :- Nov 28 20:59:46 myhost pcplusmp: [ID 805372 kern.info] pcplusmp: pciex8086,10fb (ixgbe) instance 0 irq 0x43 vector 0x64 ioapic 0xff intin 0xff is bound to cpu 6 Nov 28 20:59:46 myhost pcplusmp: [ID 805372 kern.info] pcplusmp:

Re: [OmniOS-discuss] OpenSSH and reverse DNS

2016-11-29 Thread Lauri Tirkkonen
On Tue, Nov 29 2016 13:30:17 +0200, Lauri Tirkkonen wrote: > On Tue, Nov 29 2016 10:47:10 +0100, Olaf Marzocchi wrote: > > Dear all, > > Since I upgraded to OpenSSH I have the following problem with DNS: > > reverse mapping checking getaddrinfo for hostxxx.retail.telecomitalia.it > > [_ip_]

Re: [OmniOS-discuss] OpenSSH and reverse DNS

2016-11-29 Thread Lauri Tirkkonen
On Tue, Nov 29 2016 10:47:10 +0100, Olaf Marzocchi wrote: > Dear all, > Since I upgraded to OpenSSH I have the following problem with DNS: > reverse mapping checking getaddrinfo for hostxxx.retail.telecomitalia.it > [_ip_] failed - POSSIBLE BREAK-IN ATTEMPT! > The remote SSH server has always

[OmniOS-discuss] OpenSSH and reverse DNS

2016-11-29 Thread Olaf Marzocchi
Dear all, Since I upgraded to OpenSSH I have the following problem with DNS: reverse mapping checking getaddrinfo for hostxxx.retail.telecomitalia.it [_ip_] failed - POSSIBLE BREAK-IN ATTEMPT! The remote SSH server has always been OenSSH, the issue appeared when the client (OmniOS) got updated.