This may be the root of your issue. There is a registry/gpo edit that might be
of assistance.
https://blogs.technet.microsoft.com/askpfeplat/2018/05/07/credssp-rdp-and-raven/
Richard Jahnel
Backups Team
2201 Lakeside Blvd, Richardson, Tx 75007
Office: (972) 810-2527
From: OmniOS-discuss
I have briefly touched on this panic condition before, however since upgrading
to R151022ce the previous mitigation of restricting the pool to 3 specific
flags is no longer working. So here I am for some further discussion and
hopefully more clues with which to chase the core issue down and
/agreed for internal network transfers, netcat is the way to go. I have used it
in the past for ZFS sends between internal machines with SSD backed volumes.
All the crypto work from ssh/scp and other secure copy methods are the
bottleneck in these cases.
Obviously if you transfers leave the
Yes, this issue has been lurking around since they made the arcs compressible.
I really wish they would revert that change. There have been at least 3 illumos
issues filed for this and two fixes attempted. So far it still persist. For now
I have my cache drives removed from my production pools.
So a few days after I upgraded one of my machines to R151022 and switched to
the BSD loader, I lost one of the drives in the boot mirror.
So the question of the day is: What is the command sequence for replacing a
drive in a BSD loader rpool mirror?
I know the sequence for GRUB, but I don't
From:
http://omnios.omniti.com/wiki.php/ReleaseNotes?rev=a0d510f34690cfe285ec3a775d1f10d3464b684e
OmniOS has moved to a per-release package repository setup. Each major release
going forward will have its own IPS repository.
The previous repo for releases
It would appear the r151020 either doesn't like the onboard LSI3108 chipset or
doesn't like the fact that there are no drives hooked up to it.
It's working fine with r151016 right now and before I attempted the pkg update
to r1510120.
The symptoms are the system becomes unresponsive while
I'm trying to update some omnios machines I use a fibre targets from 101514 to
current one step at a time.
In step one just trying to get to 16 I've already gotten stuck. Any ideas on
how to get the upgrade to proceed?
# cat /etc/release
OmniOS v11 r151014
Copyright 2015 OmniTI Computer
ectors in the event of
a power loss during a write operation. So when discards the incomplete txg on
reboot, it won't do anything about the other 7 512e sectors it doesn't know
were affected.
Richard Jahnel
Network Engineer
On-Site.com | Ellipse Design
866-266-7483 ext. 4408
Direct: 669-80
You’re the best :)
Richard Jahnel
Network Engineer
On-Site.com | Ellipse Design
866-266-7483 ext. 4408
Direct: 669-800-6270
-Original Message-
From: Matej Žerovnik [mailto:ma...@zunaj.si]
Sent: Friday, March 18, 2016 3:28 PM
To: Richard Jahnel <rjah...@ellipseinc.com>
Cc: Dan Mc
Speaking of which, does anyone have a diskmap.py that works with the sas3 lsi
cards?
Richard Jahnel
Network Engineer
On-Site.com | Ellipse Design
866-266-7483 ext. 4408
Direct: 669-800-6270
-Original Message-
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com
First off, love SuperMicro good choice IMHO.
This board has two on board controllers.
LSI SAS1068E (not 100% sure there are working illumos drivers for this one)
And
Intel ICH10R SATA (So I'm guessing your using this one.)
-Original Message-
From: OmniOS-discuss
Yes, you looked at it around Oct 12th or 13th of this year.
-Original Message-
From: Dan McDonald [mailto:dan...@omniti.com]
Sent: Monday, December 14, 2015 1:48 PM
To: Richard Jahnel <rjah...@ellipseinc.com>; Dan McDonald <dan...@omniti.com>
Cc: omnios-discuss@lists.omniti
mirror to minimize the write performance
impact.
Example:
stmfadm modify-lu -p wcd=true
[Ellipse Communications]
Richard Jahnel | Senior Network Engineer
Ellipse Communications - Corporate Office
14800 Quorum Dr, Suite 420 Dallas, TX 75254
TF: 888-678-3869 | F: 972-479-9115
Email<ma
, October 13, 2015 6:40 AM
To: Johan Kragsterman; Dan McDonald
Cc: wuffers; Richard Jahnel; imemo; omnios-discuss@lists.omniti.com
Subject: Re: Ang: Re: [OmniOS-discuss] Two panics now while writing eager zeros
to zvols
> On Oct 10, 2015, at 4:49 AM, Johan Kragsterman <johan.kragster...@capv
While the system did not panic, VMware lost all communication with all zvols
shortly after I attempted to add a new vmdk to one of them.
-Original Message-
From: Dan McDonald [mailto:dan...@omniti.com]
Sent: Tuesday, October 13, 2015 1:16 PM
To: Richard Jahnel
Cc: Johan Kragsterman
Scratch that. Just panicked again on 250gb disks.
From: Richard Jahnel
Sent: Monday, October 12, 2015 9:46 AM
To: wuffers; Dan McDonald
Cc: imemo; omnios-discuss@lists.omniti.com
Subject: RE: [OmniOS-discuss] Two panics now while writing eager zeros to zvols
Hmmm seems possible. Both panics
That would be the hourly snapshot destroy and create for VS20.
-Original Message-
From: Dan McDonald [mailto:dan...@omniti.com]
Sent: Friday, October 09, 2015 10:34 PM
To: Richard Jahnel
Cc: omnios-discuss@lists.omniti.com; imemo
Subject: Re: [OmniOS-discuss] Two panics now while writing
Hmmm seems possible. Both panics included attempts to make eager zeroed volumes
larger than 2 TB.
From: wuffers [mailto:m...@wuffers.net]
Sent: Saturday, October 10, 2015 2:19 AM
To: Dan McDonald
Cc: Richard Jahnel; imemo; omnios-discuss@lists.omniti.com
Subject: Re: [OmniOS-discuss] Two panics
. Please refer to the knowledge article for
additional information.
-Original Message-
From: Dan McDonald [mailto:dan...@omniti.com]
Sent: Friday, October 09, 2015 12:47 PM
To: Richard Jahnel
Cc: omnios-discuss@lists.omniti.com; imemo; Dan McDonald
Subject: Re: [OmniOS-discuss
compression turned on.
Twice in the past 24 hours the Omnios host has panicked after about 8 hours of
writing eager zero to one or more vmdks.
Any ideas? Dump available upon request.
[Ellipse Communications]
Richard Jahnel | Senior Network Engineer
Ellipse Communications - Corporate Office
21 matches
Mail list logo
