This is blogpost that’s really a big thank you to someone in our community, Gabrie Van Zanten. He has a blogpost helped fixed a problem with my IOmega StorCenter ix4-200d. What happened is my mother came to stay with us on the weekend, and my homelab is the spare room – although the lab is pretty quiet, its not quiet enough for someone to sleep in there with the gear powered on. So I did a graceful power down.
After my mother had departed I worked on bringing the whole lab backup – network switch first, followed by the storage (iomega/synology) and then the servers. All I then needed to do was bring the “infrastructure” VMs (DC, SQL, VC and so on). The only trouble I had was all my NFS exported were disconnected and wouldn’t remount. Mercifully, none of my important stuff is on the IOMEGA – it hold’s legacy templates and my software share – and I occasionally use it as “bronze” storage for VMs I don’t care too much about (these are usually Skinny Linux VMs that have tiny boot drives and don’t do anything in the way of IOPS).
Try as I may I couldn’t get the NFS volumes to mount on the IOMEGA, although intriguingly the iSCSI drives were unaffected. I was about to give up and copy the data from my NFS shares (I could still access them as SMB/CIFS from Windows/Mac) but I thought I’d do a quick google before doing that – and up came Gabrie Van Zanten’s post:
When you can’t reconnect to NFS share on your IX4-200D
Turns out some peculiarity in DNS on the IOMEGA was the source of the problem. That was rather odd in my situation as the DC/DNS was up, and so was my router – so the IOMEGA “should” have worked. Simply removing the DNS references altogether on the IOMEGA fixed my problem.
THANKS GABE!