I’m a personal user of Contabo’s cloud services, and I’ve been delighted with them. They offer a wide range of services to choose from, including VPS, dedicated servers, and cloud storage. I’m currently using a VPS to host my personal website and email, and I have also used their Storage VPS and object storage in the past. I have had no issue with my VPS over the years. I’ve also been impressed with Contabo’s customer support....
Just as a reference for future needs. To resize a zvol exported as an iSCSI LUN to a Windows OS, you need to change the zvol size, then change the “iSCSI backend” the LUN changed size and then do a disk rescan on your Windows initiator. Commands are: zfs set volsize=1T tank/volume sbdadm modify-lu -s 1T Then on Windows, go to Server manager, choose Storage, right click on Disk management and select rescan....
After a few weeks using FreeNAS 8.3.1, I noticed I could not create new volumes because the pool was out of space. The problem was that I should have had enough space, by a long shot. In fact, one of my “block” volumes was taking space more than twice it’s size. I had other volumes that seemed unaffected (or less affected), the only difference was that the problematic volume had volblocksize=8k set ....
So, here’s a short checklist of what to do right after I install FreeNAS 8.3 (not necessarily in order). configure link aggregation (LACP seems to work with 2 switches, failover or other algorithms don’t) change admin and root password enable ssh with root password when LAN is secure configure SMART tests (monthly long test) configure general settings (timezone, syslog, email server) create zpools with lzjb compress, atime off and no deduplication create zfs datasets and volumes and inherit options active directory synchronization iSCSI targets and stuff SMART checks enable SNMP
I’ve just got my hands on a new server to store backups and archived files before being sent offsite, and it wouldn’t boot off my USB key. Even after many dd, dd with skip and FreeNAS installations, I was getting a “GPT table corrupt” message. Finally, the fix was easy enough: boot FreeNAS installation CD and choose Shell instead of Install type gpart show , it listed my device and that GPT table was corrupt type gpart destroy -F return to the menu choose Install when it’s finished, go back to the shell type gpart show again to check that it’s not corrupt anymore reboot enjoy your FreeNAS That’s it....