FN9.2 box being used to provide VMs to ESXi; managed by vSphere.
Successfully migrated to FN9.3 (FreeNAS-9.3-STABLE-201412142326) via CD.
Attempted the later update to FreeNAS-9.3-STABLE-201412142326 using GUI.
Failed through lack of internet access (#7139 related).
Later, downloaded the manual update – but omitted to collect the SHA256 info (who knew? First time doing this stuff)
Got part way through the manual update process; seemed to be going fine then got asked for SHA256.
Couldn't give it. Had no internet access to look it up. Cancelled the manual update.
FN didn't seem happy … most things I tried gave an error or no response, so I reset the machine.
It fired up OK. I then started the ESXi host.
Checked the startup with vSphere client.
That had found the iSCSI target but decided that there was no data in the 500GB … frightening.
Mild panic for a while trying to work out the best path forward.
Nothing much useful came to mind.
Without the firewall and gateway VMs running, the whole setup was a bit nobbled for doing major research or surgery.
Ended up concluding that the best route might be to go backwards.
Had the FN 9.3 install CD to hand, used that to wipe and rebuild the 16GB USB system drive back to a clean copy of FreeNAS-9.3-STABLE-201412090832.
Thankfully, vSphere was then able to see all the files in the iSCSI share and sanity was restored.
I've learned some lessons, but does any of this suggest a problem with the manual update process?
Did it not do enough clean-up after the Cancel?
In passing, iSCSI performance improvement between 9.2 and 9.3 quite noticeable.
Haven't tried to measure it, but VM performance seems a fair bit snappier.
Successfully migrated to FN9.3 (FreeNAS-9.3-STABLE-201412142326) via CD.
Attempted the later update to FreeNAS-9.3-STABLE-201412142326 using GUI.
Failed through lack of internet access (#7139 related).
Later, downloaded the manual update – but omitted to collect the SHA256 info (who knew? First time doing this stuff)
Got part way through the manual update process; seemed to be going fine then got asked for SHA256.
Couldn't give it. Had no internet access to look it up. Cancelled the manual update.
FN didn't seem happy … most things I tried gave an error or no response, so I reset the machine.
It fired up OK. I then started the ESXi host.
Checked the startup with vSphere client.
That had found the iSCSI target but decided that there was no data in the 500GB … frightening.
Mild panic for a while trying to work out the best path forward.
Nothing much useful came to mind.
Without the firewall and gateway VMs running, the whole setup was a bit nobbled for doing major research or surgery.
Ended up concluding that the best route might be to go backwards.
Had the FN 9.3 install CD to hand, used that to wipe and rebuild the 16GB USB system drive back to a clean copy of FreeNAS-9.3-STABLE-201412090832.
Thankfully, vSphere was then able to see all the files in the iSCSI share and sanity was restored.
I've learned some lessons, but does any of this suggest a problem with the manual update process?
Did it not do enough clean-up after the Cancel?
In passing, iSCSI performance improvement between 9.2 and 9.3 quite noticeable.
Haven't tried to measure it, but VM performance seems a fair bit snappier.
