Best posts made by Coloradogeek

I'm trying to get the work servers upgraded, most everything we're running is on either an NFS Share (Isilon) or a FreeNAS appliance, yet the upgrade wizard keeps barking about VMs being on local storage. I've gone through and verified the UUIDs in the console of the affected server, and nothing that is running is on the local disk at all. Everything else that is running already shows those aforementioned network drives.

Should I initiate a host reboot or am I missing another detail that would clear that error?

Weird, I thought I created an account ages ago. In any case, halloooo

None. #1 and #2 have been rock solid. I introduced #3 some time after them, but it's had issues before, so I knew if it did it again, I would be removing it.

Initially I removed it via the GUI by disabling HA, but that got hung up and started this whole mess. XS7 is a gem to set up, but like a vindictive mistress, it gets really twitchy when you try to change something I'm noticing.

I finally just yanked the power plugs in desperation and gave #1 and #2 a timeout in the corner, then powered them up again. Guess what? VM's are starting now and the cluster is functional again. Even managed to re-enable HA.

/facedesk

I didn't say introducing the #3 server caused this - I just mentioned that after I added #3 to the pool a while back, it had a similar event. The first time it happened, I let it slide, waiting to see if it would do it again. Yesterday at 10am, it had the same type of problem (isolated itself and rebooted) so today I decided I'd better pull it so that it wouldn't do that during business hours. At the time it only had two VMs running on it, and they weren't at all taxing the system.

They are all identical systems - Dell R610's with the same CPUs, the only difference is that #3 uses 48GB of RAM while the other two are 96 GB. I even upgraded all of them to the exact same firmware revisions before putting them into production and after testing them. #3 is just a bad egg. Not sure what the problem is, but it's powered off right now and I'll take a look at it if I get time to this week.

@RojoLoco How else will you drive the stock price down for an acquisition? Gosh guys, get with the times.

Is there no blasted way to get around the damned 07b stop error? Since XenServer doesn't have a standard BIOS for a VM, there's no way to change HDD controllers, etc. I'm at my wits end. I even tried to use Unitrends to do a bare metal restore and even THAT didn't work.

I was told to have this system up by today, and as it stands, I have to babysit a VMware 6 server now just to run this fricking VM.

These are the HDD controller settings, nothing special. I could try and take it down to a basic IDE controller, but I don't know how much that's going to help.

Lost #3 over the weekend again. I'm removing the host from the pool and leaving it out - the server isn't reliable. However in the process of doing so, #2's network stack is failing to come up, and even after a reboot of the master, I'm not feeling rosy about this system this morning. I'm sure I'll figure it out, but after coming off the high on Friday (Got Commvault working on a critical CentOS system) coming into Monday like this is a kick in the pants. The front side.

@NetworkNerd It's not coincidence. Many of the community elements, including the sign in package are part of ma-Spiceworks.

@scottalanmiller https://twitter.com/Spiceworks/with_replies

@scottalanmiller Yeah, reading more into the context, I believe so.

But bottom line, don't log out if you're logged into your local helpdesk or you may not get back in again until after this blows over.