Search results

No errors, just 'no disk found'. I suspect it's the bios in the nic, since windows sees everything just fine. thanks...

Ok, but that wasn't really my point. Whether it's a NIC, an HBA or a SW initiator, I would like to be able to debug on the omnios end, by seeing what comstar is doing.

Ah, that makes sense, thanks. Any thoughts on diagnosing the 'no disk found' the iSCSI nic is printing?

So I set up 3 zvols shared via comstar. I then backed up the comstar config file and move it off the root disk. I was messing around and decided to restore the config. The pull down menu for this doesn't seem to accept a file to restore (e.g. it's got some file hardcoded with the current...

If you're willing to pay $200/yr (approx) for a VMUG membership, 7.0 VSAN has been rock-solid for me..

No idea, sorry.

I first tried the ISO upgrade method but that failed as expected (some issue where it doesn't play well with updates done via the online method.) So I created a temporary baseline called 'upgrade from 6.7 to 7.0' lol. Applied it to all 3 machines with no issues. Well, there was one on all...

So I deployed a new NAS which had been serving up a datastore to vsphere. One of the functions was a repo of ISO files. Another was acting as the 2nd heartbeat for HA. Unnoticed by me, the permissions on the NFS share's root were wrong, and vsphere hosts were unable to write heartbeat files...

I've looked high and low and can't find an answer, hopefully I just missed it. I have 2 stacked switches. My 3 esxi hosts each have enet connections to them, but not using LACP, just failover order (e.g. nic teaming?) Is it possible to do this for my OmniOS storage appliance? Looking at...

Ugh ugh ugh. No time to experiment - it isn't just that pool - nothing is working and guests are failing, so time to do a hard reboot. Damn!!! Even though it said jbod was stuck, apparently I/O involving the ssd raid1 (serving vsphere) was also hosed.

Annoying situation just now. 4x2 raid10 of spinners, with 1 ssd as SLOG device. This is running on latest omnios. I meant to plug in another ssd to do hotplug backups, but pulled the slog device by mistake. Plugged it back in, but the pool is stuck: NAME STATE...

I remember back i the early 90's building a server running linux 0.99. Initially had 16MB (not a typo). Started needing more RAM. Best deal I could get for 16MB more? $300 or so.

yea. if I had extra ports on my SAS controller, i'd move them there. i think i have a fan-out cable - need to check.

ok, thanks. very strange i had that leftover disk, but oh well...

Very mysterious. Sata hotplus was enabled in the bios. Rebooted omnios, and the orphaned drive is gone. Still concerned about that hotplug setting that napp-it says should NOT be set.

This is puzzling. Looking at the appliance tuning screen, it says: *set sata:sata_auto_online=1 (do not set in OmniOS 151030+) omnios-r151038v is this wrong?

that's what I was afraid of, thanks :) I do have also 2 2TB sata drives in a mirror for backups, so it would be nice to have hotplug work. I'll schedule downtime to fix this. EDIT: very weird. Looking at the config file now: set sata:sata_auto_online=1 <=== already enabled? Maybe I have...

Doesn't that require a reboot to take effect? I'm sorry, I think I was unclear. I don't really want to enable hotplug, just to clean up that leftover device...

So I just finished migrating from Linux ZFS back to omniosce. Everything is working fine, except I had a brain cramp and forgot to pull the sata ssd that had centos8 installed. Solarish OS don't by default hot-plug sata disks, so now the format command shows: AVAILABLE DISK SELECTIONS...

yup. My company sent out an edict a couple of weeks ago, instructing folks to uninstall virtualbox if using it. I don't, but rolled my eyes at oracle anyway...

I'm still puzzled as to why a 'home isp' is a requirement.

I didn't mention it because it didn't seem relevant, but I do in fact have shared storage for the cluster...

maybe i am misunderstanding you, but i have a 2-xeon cluster and have no witness node, and it works fine. it is set up with datastore heartbeats (dunno if that's germane here?)

Don't hold back, bro! Tell us what you REALLY think!

yeah, i don't recommend that either. Even somewhat incompatible processors of the same family can be problematic, disabling live migration. And you might not even find out until you try to do a live migration.

I'm confused. I've never actually touched that stuff on the host GUI itself, only ever through the VCSA GUI.

veeam agent for windows.

The links to download big sur are dead.

Hopefully last step: enabled and turned on the failover service (auto mode). Tested by using ipmi manually to power off the master. It all seems to work. The one thing I'm wondering, is in the Appliance Cluster page, ipmi is showing a red indicator?

Okay, looking good. I've got ipmi working using ipmitools. I tested the failover time by running a linux guest with the dd command using 'status=progress', from /dev/sda to /dev/null, starting a manual failover, and starting a timer when disk I/O stopped, and stopping the timer when it...

A lesson learned about SSL. I fat-fingered when I set the date. Thanks!

Well, their cert is certainly not expired. I never thought of the system date. I will check, thanks!

Very strange. I tried to do 'pkg update'. It works on 1 of the 3 installs (omnios1) but not omnios2 or omnios-cc. I get this: WARNING: Errors were encountered when attempting to retrieve package catalog information. Packages added to the affected publisher repositories since the last...

Success!

Ah, I didn't notice I needed to add appliance group. Checking that now.

Well, I'm not sure what I am doing wrong. I'm trying to follow the instructions in the Z-RAID pdf, but no matter what I do, after I enter all the settings in the CC appliance, it fails totally. Here is the screenshot enclosed. BTW, I think I was not clear - I have 10.0.0.0/24 as LAN and...

I'm trying to compare this with the pacemaker/corosync HA ZFS I was using before. So in my case, 192.168.3.0/24 is the 10gb storage network. Host #1 is 192.168.3.44 and host #2 is 192.168.3.45. I intend to use 192.168.3.40 as the HA IP that vsphere will connect to. If I am understanding you...

Hopefully one last question: what does 'Net Link head 2 name of the nic link ex vmxnet3s and add :3 ex vmxnet3s0:3 (HA ip will use this link)' mean? Is this intended to be a dedicated heartbeat link between the two hosts?

Thanks, makes my job much simpler :)