Archive for May, 2017

25
May

   Posted by: RobPatton   in Transportation

Got the new truck back onto a fuel treatment. https://www.bellperformance.com/ is a local company that has  been around for many years, and I have used several of their products over the years.

Purchased the 1 gal and the 16oz dispenser.

Dee-Zol Concentrate Diesel Treatment

As I prepare for a coming trip, I’ve realized that the 16 oz wont be large enough for this trip, so I decided to purchase these.

and fill them with 3.5 oz (or so)of Dee-Zol! for the trip

 

 

 

19
May

   Posted by: RobPatton   in Fixing broken stuff, Tech

I have a love and hate relationship with this printer, this is my second, the first just stopped working, and they sent me a new one.  Its been pretty good, till today when it gave me the dreaded “No Cartridge Loaded” error message. This time I decided it was getting fixed, or hitting the trash.  Here is what I found.

Easy open. the sides pop off, 10 screws

 

Then I noticed the little pc board that connects to a chip in the cartridge was just floating around in the box

Pushed it back to its place, added some hot melt glue to hold it in, and reassembled.

 

 

 

Boom! Fixed, and back printing. Saved from the recycle bin.  Hope this helps someone else…

15
May

   Posted by: RobPatton   in Tech, Virtualization VMWare FreeNAS

 

I boot my hosts from a usb drive (The hosts have no local storage)

This process causes this error:

fetch_fixed_disk_status: fetch VSI_NODE_storage_scsifw_devices_smart_healthStatus(t10.SanDisk_Cruzer_Fit______

4C532000061012110161) failed Not supported, reporting unknown status

Clearly I understand that you can’t S.M.A.R.T. status this usb thumb drive, but how to tell esxi 6.5 NOT to try to check it?!??!

I can find many other people asking the same question, but have yet to find an answer…

Ongoing!

4
May

   Posted by: RobPatton   in Fixing broken stuff, Tech, Virtualization VMWare FreeNAS

After some recent upgrades:
Esxi 6.5
FreeNAS FreeNAS-9.10.2-U3 (e1497f269)

I noticed myself getting spammed with messages like:

May 4 13:21:42 138.128.161.188 2017-05-04T17:21:42.306Z serverblade1.robpatton.com vmkwarning: cpu0:67660)WARNING: ScsiDeviceIO: 6462: The Physical block size “16384” reported by the device naa.6589cfc0000005aac04099e50185e8c8 is not supported. The only supported physical blocksizes are 512 and 4096

FreeNAS acts as an iSCSI target with its LUNs backed by a ZFS Volume. This causes the blocksize to be reported as the ZFS size, which scares the host, I guess.

To help make the host feel better about itself, login to FREENAS and Sharing > Block (iSCSI) > Extents > Edit > Disable Physical Block Size Reporting

As shown here.

And it should feel better about itself.

For me, this did not work till I rebooted the FREENAS box, which means I had to vmotion all my stuff elsewhere. A fun exercise..