The best way to fix this would be to roll back to a prior BE,
figure out what broke you upgrade, fix i, and try again.
On Tue, Dec 10, 2013 at 14:51:11 +0530, Sam M wrote:
Anyone? Am kind of stuck here.
Thanks.
On 04/12/2013, Sam M emu...@utmi.in wrote:
Hello.
I'm running OmniOS
You are likely getting older versions that don't rely on 151006.
At some point in the lifecycle of ms.omniti.com we opted to make the
packages depend on the release.
On Tue, Dec 10, 2013 at 10:42 AM, Dominik Hassler hassl...@gmx.li wrote:
hi there,
to be able to install
hmm, my point was the following:
these older versions (installed on my r151006) prevented me from
upgrading, but now can be installed again (the same versions that have
been installed) after the upgrade has been finished.
why does a piece of software prevent me from upgrading if it can be
You didn't have the same version as before you now have an older
version...
You likely had
omniti/library/uuid@1.41.14,5.11-0.151006:20131015T044739Z
installed on your box now you have
omniti/library/uuid@1.41.14,5.11-0.151002:20120401T185308Z
Likely true for a few of those other
This *looks* like its SAS drives, but can you confirm that you're using SAS
disks and not SATA drives in an expander or converter?
In particular, *really* bad things can happen when you use SATA drives with
SAS expanders, particularly when you start encountering errors. These
solutions work
That's right... direct connection *with nothing else on the bus* should be
fine.
On Mon, Dec 9, 2013 at 4:06 PM, Paul B. Henson hen...@acm.org wrote:
From: Garrett D'Amore [mailto:garr...@damore.org]
Sent: Monday, December 09, 2013 3:10 PM
This *looks* like its SAS drives, but can you
From: wuffers [mailto:m...@wuffers.net]
Sent: Monday, December 09, 2013 9:04 PM
I had some SCSI warnings as well relating to a target, and I found this
helpful
thread on determining a disk target (uses lsiutil):
While I was poking around, I discovered that while the syslog messages only
OmniOS v11 r151006
Hi,
I'm having many stability/performance issues with NFS. Server end is OmniOS;
client end is CentOS 5.
When the server end is functioning, I can mount OK, but there are really long
waits on simple things
like listing a directory. Often I will get an I/O error. I have been
This week brings us two new releases in each current stable
branch. r151006_032 has a fix in the `entire` incorporation to
allow users to upgrade and install new packages while staying on
151006, and r151008f brings a fix for pkg:/system/file-system/zfs
for 4347 ZPL can use dmu_tx_assign(TXG_WAIT)
IIRC (on vacation atm) we pulled it from one of the omniti repos. You do
need to run it with some options to get info out of SATA drives, and it
results in a cosmetic scsi error, but it gives the full drive info.
For us at least, our drives are noisy with errors before taking a dive; we
get smart
10 matches
Mail list logo
