It has been a while since I updated my NAS systems which run FreeNAS and my XenServer hosts which have my virtual hosts that I share to the world via my blogs and websites. My music server due to the high CPU utilization from running multiple audio streams with varied bit rates is a physical system that was unaffected except you couldn't see the website.
I decided to update the storage first but since I wanted to cut down on the time I decided not to migrate the storage and just shutdown all of the virtual systems. While the VM's shutdown I saved the FreeNAS configuration from both of my NAS systems to one of my local systems. Once the VM's shutdown I updated from the GUI my first NAS system I call "baja".
FreeNAS Update
Baja my first NAS system took the FreeNAS 9.2.1.8 update rebooted and looked ok until it hung with an "istgt_acceptor" error. I looked the error up didn't find much and decided to shut the power off of my NAS and then powered it back up performed a reboot on its own after coming all the way up almost then came up just fine. I tested by bringing up a couple of VM's that had used the iSCSI targets from that device and they came up nicely as well.
Mojave my second NAS system which I also use FreeNAS now that really caused some headaches! After updating to FreeNAS 9.2.1.8 from the GUI it started to come up and it had a CPU issue with some errors that had been logged. After I took care of the CPU issues on my NAS system "Mojave" I turned on a switch to stop on serious errors in the motherboards bios.
Well reboot my system stops in a bios error window with an "8525" memory error on DIMM B2! Well I located a system that I don't use as frequently and could stand a little less RAM and started to open it up and then stopped. I went ahead and opened up my "mojave" NAS system reseated DIMM B2 and confirmed the system would bypass that error and then slid it back into the rack. On reboot of second NAS system I now started getting a timeout error on my USB drive with my FreeNAS installation.
The error code I get now on my "mojave" NAS system is a timeout associated with the error "quirks no_6_byte" and it refuses to go any further. I powered the system down removed the USB blew on it and placed it back in and then the system hung on my iSCSI target just like my other NAS so I rebooted and then got hung up on the USB issue again. I went back and forth on this with reboots about 5 times with different results.
Wanting to take the USB out of the equation I downloaded the USB FreeNAS 9.2.1.8 image, placed the original USB I had the image on into another USB slot on my NAS server booted the system while I went to locate my travel bag of USB sticks. As I sat down to update my new USB stick that I had just removed some files from my second NAS system booted up just fine on the original USB stick on the different USB port. I tested with a few VM's and everything looks fine.
XenServer Update
I then installed about 5 patches to catch up on my XenServer patching I hadn't done since I updated to XS62ESP1 XenServer SP1 around December last year. The patching (patches I put on system: XS62E015, XS62ESP1003, XS62ESP1005, XS62ESP1009, XS62ESP1013, XS62ESP1014) was uneventful except for the multiple reboots. I updated via a putty shell ssh into my XenServer slave hosts that used to be my master. Everything looks good except I have two Centos 7 systems that have disks that are not activein XenServer. All my Fedora and Windows systems seem to be coming up fine.
I'm still working on trying to activate the disks on the Centos 7 VM's. I am taking two approaches on activating the disks. One VM system I had done some work but it's not a lot so that one I am in the process of exporting and then will import back to see how that works. A slow process so started writing this. The other centos 7 VM system I will try to activate by using the "vbd-plug" command and see how that flies.
My XenServer update to be continued later tonight, this morning or sometime this weekend. This post is just another test to see if my blog running on Fedora is working.
******************Update of XenServer Update****************
I took care of the two Centos 7VM's that I could not bring up after the updates of my FreeNAS and XenServer. I ended up going to the XenCenter console and placing the XenTools into the DVDCD and with the XenTools attached both VM's came up.
I then mounted XenTools ISO and installed XenTools without the supplied script:
#mount -t iso9660 /dev/sr0 /media
#cd /media/Linux/
#yum install ./xe-guest-utilities-6.2.0-1137.x86_64.rpm ./xe-guest-utilities-xenstore-6.2.0-1137.x86_64.rpm
Rebooted the Centos 7 VM's and everything looks great!
Yes I went down the wrong hole late but quickly corrected that and got it working! J