Separate names with a comma.
Discussion in 'SSDs & Data Storage' started by _Gea, Dec 30, 2010.
That was my thought..I pulled the drive. Lets see what happens.
Zpool v.45 shows up on Oracle's Solaris !
I would power off and connect "bad" disks to another HBA (optionally export/import/clear error)
If the "bad" disks remain at the HBA this is the problem otherwise more the backplane.
As always, thank you for your input. I have determined that I had a bad memory dimm. Upon removing the dimm and running a couple of clear/scrubs (only a few corrupt files), I am happy to say that the devices are all online again.
Ram problems can always affect stability. A little curious that only one vdev is affected. If the problem disappers it is clear that this was the reason.
I am trying to update from OmniOS 151020 to 151028.
My update to 151022 went OK.
When I tried to update to 151024 I was told invalid certificate. So I ran:
wget -P /etc/ssl/pkg https://downloads.omniosce.org/ssl/omniosce-ca.cert.pem
pkg update web/ca-bundle
Now I cant update to 151024, I get the message:
Reason: No version matching 'incorporate' dependency email@example.com can be installed
Reason: No version matching 'incorporate' dependency firstname.lastname@example.org can be installed
If anyone can point me in the right direction it will be appriciated.
I was also thinking it might be easier just to install 151028 from scratch (Esxi) and load datapools? But I became unsure when I read about backup/restore of users. The var/web-.gui/_log I did understand.
Thanks in advance
There are some problems regarding such an update like the certificate problem but also the switch from Sun SSL to Open-SSL. If you have installed something that is no longer available, you must first remove prior an update.
I would install the OmniOS 151028 ova, restore /var/web-gui/_log/* and all users/groups with same uid/gid. Then import the pool.
If you use ESXi 6.7u2 you cannot import the ova due a problem with the ESXi GUI and the ova deploy menu. Only solution is an import via ovftools or a downgrade of the ESXi gui or a wait to 6.7u3
With ESXi 6.7u2 I would
- install OmniOS 151030 on a 30GB vdisk with an e1000 and a vmxnet3 vnic (dhcp) from OmniOS iso
- add Openvmtools: pkg install open-vm-tools
- add napp-it via the wget command
- optionally add tls email, run a default tuning and update napp-it
This is how I create the ova
use e1000 for management and thge faster vmxnet3 for filer use
Thank you so much _Gea.
I will go with the 151028 option since I have ESXI 6.7u1.
Just 2 final questions:
I will have to add users manually (I mean I cant restore the users) right ?
This is the correct OVA file - zfs_vsan_omni028_esxi67v5.ova right ?
I see this workflow:
Remove VMs from inventory
Remove Napp-it from inventory and delete files
Import new Napp-it OVA
Passthrough of HBAs
Add users manually in Napp-it
Add datastore from Napp-it
Add VMs from Napp-it datastore
ova and workflow is correct
It is possible to copy over users when you copy/restore
I do this with the ZFS cluster functionality and current napp-it pro with jobs > backup and user > restore
Thank you much _Gea...!
What happens to your data on RAM problems without ECC?
Why it is superiour to have checksums then (ZFS)
nice example, see
I have now successfully upgraded to 151028 by importing new OVA.
I am a little unsure whether to run zpool upgrade or not. I case I dont need the new features, is there any other benefits from upgrading?
Once again - Thank you so much Gea for you always kind help
If you upgrade you may not be able to import again on the older OS versions so
if current featureset is ok you do not need to upgrade.
A new feature that you propably want is native ZFS encryption.
This is currently in OmniOS 151031. Possibly it will be backported to 151030 lts.
I have one pool that is causing my problems. Typically one disk is giving me IOstat errors and eventually the pool becomes unavailable.
This is a striped pool of 4 consumer grade SSDs connected to a LSI-2307 HBA. The pool is just for temporary non important data.
When it began like a year back, I changed the cable and eventually I replaced the disks. After I took out the original disks I did run a smart check on them in a different computer with no errors.
I am having the same problem with the new disks - 1 disk giving IOstat errors and eventually the pool becoms unavailable.
I changed the cable - no effect.
I just unplugged the disk giving the error and recreated a new pool using the remaining 3 disks. Now I get the same errors just on one of the other disks
I was thinking about replacing the HBA.
I tried to run zpool status -v but just got a "list of errors unavailable (insufficient privileges)" reply.
Does anyone have any ideas for me how to proceed?
Thanks in advance.
These errors indicate a hardware problem.
First check if LSI 2307 firmware has release p20.0 up to p20.004
This is buggy with SSDs. Update then to 20.007
I would then check ram with memtest86
Then connect the disks to onboard Sata to ruleout the HBA
Have you called zpool status -v as root?
I was already on 20.007
I learned that my memory sticks was not installed in the correct order, so I changed it.
I ran memtest86 for 16+ hours without any errors.
So I recreated the pool and tested and immediately I got the errors again
Fortunately I had a spare HBA, so I replaced the HBA and recreated the pool.
After testing with heavy copying of files everything is now running without errors
Yes, I did run the zpool status -v as root
Thank you so much for helping out.
State of SMB3 development on Illumos(NexentaStor, OmniOS, OpenIndiana)
newest feature: SMB3 for ZFS Cluster/ HA failover (Yes, I really want that)
Implement SMB3 persistent handles
(part of making SMB "cluster aware")
Steps to Reproduce:
Connect an SMB3 client (Win2012 or later)
Restart the SMB service, or force a fail-over
Take a network capture (from the client is easiest)
SMB3 client should reclaim it's CA handles after the restart or fail-over.
SMB3 client has to re-establish it's open handles (as seen in the network capture)
Search - illumos
SMB3 (kernelbased Solarish SMB server) is announced for OmniOS 151032 in November 2019,
If you want to try it now, use OpenIndiana (always newest Illumos) or OmniOS bloody 151031
ESXi 6.7 U3 is available
Fixed from 6.7U2
Import of ova templates not possible from the web-ui in 6.7u2
Deployment of my napp-it all-in-one webmanaged ZFS server template works now again
I am running OmniOS 151022 with Napp-It 19.01c1. I believe OmniOS should feature SMB 2.1.
Ever since I upgraded my Windows client to Windows 10 v1903, I cannot play any video file from my NAS anymore using VLC Player. I have an open thread in their forum here where everything is described in detail, but so far I got only hints, but couldn't solve the issue. Maybe you've got an idea whether this has to do with SMB mismatch? I tried enabling SMB1, but it didn't help either. Any hint would be much appreciated.
OmniOS stable supports SMB 2.1. Current Illumos/OI/OmniOS bloody 151031 support SMB 3.0.
Is this a VLC player problem only and you can access OmniOS via Windows file explorer?
As I do not asume that you have restricted OmniOS to SMB 1,
It may possible that your Windows demands SMB3. If so allow SMB 2.1
On your PC, execute "gpedit.msc" and on "Computer configuration > Administrative Templates > LANMAN Workstation > Enable guest session not secure" enabled this.