{"id":1064,"date":"2018-02-25T17:40:43","date_gmt":"2018-02-26T01:40:43","guid":{"rendered":"http:\/\/dhoytt.com\/mainblog\/?p=1064"},"modified":"2021-12-19T22:18:42","modified_gmt":"2021-12-20T06:18:42","slug":"doing-it-big-with-late-wild-saturday-night-in-my-computer-room","status":"publish","type":"post","link":"http:\/\/dhoytt.com\/mainblog\/2018\/02\/doing-it-big-with-late-wild-saturday-night-in-my-computer-room\/","title":{"rendered":"Doing it Big with Late Wild Saturday Night\u2026\u2026 in My Computer Room"},"content":{"rendered":"

That\u2019s right a wild Saturday night in my computer room revolving around my secondary FreeNAS<\/a> server\\disk array. I have had so many issues updating this server to FreeNAS 11.1 I decided tonight I would make sure I came to a conclusion to alter my HW or see if this is a 11.1 FreeNAS issue so that I would know how to proceed with my main FreeNAS system I had to take back to FreeNAS 9.1 due to update issues and lack of time to properly spend on this.<\/p>\n

I need to know how I want to invest my money going forward in my computer room and I build items redundantly meaning if I rebuild one FreeNAs server I would end up building two with the first rebuild being the model and test platform until I get things where I like which can mean multiple tries at various hardware and firmware configurations. I often times have controller cards, chassis, hard drives and network cards<\/a> leftover from these tests and I don\u2019t use consumer level gear so the costs can add up quickly even with planning and checking of posted requirements and hardware compatibility lists.<\/p>\n

The first thing I did was boot my secondary FreeNAS and enter the bios and went through every screen to make sure I had configurations I wanted enable and anything unneeded disabled since I had replaced the dead battery on my motherboard with a new one and kept losing my settings every time I unplugged the system and there were several changes that needed to be made.<\/p>\n

Secondly I attempted to install from a FreeNAS CDROM I had burned from an SATA<\/a> connected DVD\/RW to an internal flat SSD hard drive of the type created for laptops attached to SATA. This test ended like my prior attempts to install FreeNAS 11.1 and rebooted @ \u00a0the 70% mark copying files to the SSD drive<\/a>.<\/p>\n

Next I tried to install to an external USB thumb drive<\/a> and met with the same results system rebooted after reaching 70%.<\/p>\n

I also want to note that prior to last night I had tested the memory extensively and pulled out every card in turn and even disconnected all drives and disabled IPMI on the mother board and numerous other isolation techniques going as bare metal as possible with the same results.<\/p>\n

Well this time I found a version of FreeNAS 9.3 and attempted to install it with same hardware configuration but to the SATA SSD and that went fabulously proving that my configuration was valid!<\/p>\n

While I was trying the install to the thumb drive and testing out the 9.3 install I downloaded the newest version of FreeNAS 11.1u2 which was released sometime in January. I then started browsing my thumb drives I have laying around looking for my FreeNAS thumb drive that was the previous boot drive for this system even though FreeNAS said it had issues that couldn\u2019t be fixed via GUI or\u00a0 manually clear with ZFS in case I hadn\u2019t save off my configuration database of this FreeNAS system. The FreeNAS website had never stated they had an updated version of 11.1 or I missed it but it wasn\u2019t apparent that it was different until I saw the file being downloaded listed as \u201cFreeNAS-11.1-U2.iso\u201d. I was downloading only thinking maybe I had a corrupted version of 11.1 not to get a new version but I felt a little hope seeing the new version \u201cFreeNAS-11.1-U2.iso\u201d.<\/p>\n

Now starting the install to my SATA SSD from FreeNAS 11.1u2 and I\u2019m at first disappointed to see it do its initial DD after I select my SATA SSD have \u201cdd records in\u201d then \u201c dd records out\u201d be different as it had been in my previous 11.1 install failures while they were the same with 9.x installs. So I get up stretch start going through next steps but keeping an eye out for when this 11.1u2 install will fail when the install scoots past 70% then 80% and I\u2019m thinking it will still fail because prior times I had made some configuration changes to get it to go from 50% to 70% but this version FreeNAS 11.1u2 installed then successfully came up!<\/p>\n

Well my work is not over I changed my 3 NIC\u2019s on the system to the appropriate network settings for the various networks from DHCP to static and started importing volumes. Still this did not share out my CIFS or NFS shares, iSCSI<\/a> targets or any other configuration items I had made on this server and I didn\u2019t feel like recreating something already so I started looking on my Linux workstation I was running the GUI<\/a> from for my config files for this FreeNAS server and could not find them in the place I thought they should be. I jumped to the cli and did a find and found them on one of the path\u2019s I had browsed but had not gone deep enough in and uploaded the configuration file to my server and after a couple of reboots it came up with a configuration minus a lot of my iSCSI targets. I looked and I had not uploaded the latest configuration file but once I did and a few mere reboots I had my FreeNAS up with proper configuration at 11.1u2!<\/p>\n

 <\/p>\n

One of My Routers WAN<\/a> Configured Incorrectly<\/b><\/p>\n

My next step was to see if there were any updates for FreeNAS 11.1u2. This system did not bring up \u201cpending updates\u201d but \u201cno route to hosts\u201d or a similar message to that. I go to my primary FreeNAS system which populates the \u201cpending update\u201d field properly. Check my network config and routes which all look fine on my secondary updated FreeNAs system.<\/p>\n

Suspecting what I call my third physical network is the issue I ssh on one of my systems that has access to all my routers and networks start pinging from first the primary interface to the outside world using \u201cyahoo.com\u201d to see if there is an issue then I try my 3rd<\/sup> interface. The primary interface card pings correctly over the WAN while I cannot get out over the WAN from my 3rd<\/sup> interface (#ping \u2013I <interface>).<\/p>\n

I login into my GUI\u2019s interface via a browser and my WAN information is all wrong to go over my third static WAN ip. I make the changes and try again but still get the issue. Looking in the setup of my router again I see 2 typo\u2019s in WAN ip and my gateway is still showing my gateway of my old ISP I changed away from last month. I re-apply the changes and my gateway will not change! I keep trying and no matter what my gateway will not accept changes for the gateway!<\/p>\n

Now I start an internet search to see if anyone else has seen this issue since I have DD-WRT<\/a> installed on this old\u00a0 \u00a0and find that I have indeed ran into a bug with my older firmware per the DD-WRT forum string I found. I don\u2019t feel like detaching this router from the network getting one of my laptops and installing new firmware tonight! Thank goodness on this forum string (https:\/\/www.dd-wrt.com\/phpBB2\/viewtopic.php?p=751544<\/a>) they have a workaround that saved me some time and effort here is the workaround you can double-check with the link above:<\/p>\n

OK, so I tried to replace the onclick event on the apply button to bypass the validation<\/p>\n

\n\n\n\n\n
Code:<\/b><\/td>\n<\/tr>\n
onclick=”to_apply(this.form);”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

with<\/p>\n

\n\n\n\n\n
Code:<\/b><\/td>\n<\/tr>\n
onclick=”applytake(this.form);”<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

After doing the above using a Firefox browser<\/a> on my Centos 7 server that touches all my networks \u00a0\u00a0I was able to save my gateway and other settings in my DD-WRT router.<\/p>\n

I go to my cli on this system and still I cannot ping via my 3rd<\/sup> network interface to any outside networks via the WAN. Now I look at the routing table on my system and note the only gateway is my primary NIC. I then try pinging out using my 2nd<\/sup> NIC and cannot and I verify those WAN router settings are correct. I now go into the network config files for each interface (\/etc\/sysconfig\/network-scripts\/ifcfg-<interface-name>) change the parameter \u201cDEFROUTE=\u201d from \u201cno\u201d to \u201cyes\u201d bring the interface down with \u201cifdown\u201d then back up with \u201cifup\u201d and I have a gateway out to the WAN for each network now\u00a0 and can ping out on any interface.<\/p>\n

None of this of course helped with FreeNAS 11.1u2 not seeing update information but it did help me straighten out my 3rd<\/sup> router and my Centos 7 routing though I may go back sometime and make other routing changes there.<\/p>\n

Looking today my FreeNAS 11.1u2 is populating its \u201cpending update\u201d window properly so I think it was something ultimately at IX Systems end the company who creates FreeNAS.<\/p>\n

 <\/p>\n

Backing up Data from Primary FreeNAS to Secondary using Rsync<\/b><\/p>\n

Now that I have the secondary system up I need to make sure that it has all of my NFS data that my primary system has. What I have done in the past is rsync using cli of the Centos system that has access to all of my networks with both systems mounted on that system but I wanted a FreeNAS system to FreeNAS system approach this time in case I\u00a0 needed to do other things on that Centos 7 system unrelated to FreeNAS.<\/p>\n

I decided to use rsync from one FreeNAS to another server and started to do this via cli and putty but then decided to use the FreeNAS GUI \u201crsync tasks\u201d instead. I went to the guide they had which was pretty straightforward https:\/\/doc.freenas.org\/11\/services.html#rsync<\/a> minus one detail I missed because of the way I like to browse the GUI using the top navigation at times. Where it gives you the breadcrumb trail (g\u00a0Services \u2023 Rsync \u2023 Rsync Modules \u2023 Add Rsync Module<\/span>.) to create \u201cRsync Module\u201d as the \u201crsync target\u201d or \u201crsync server\u201d , it doesn\u2019t mention you can only access that via the left handed navigation not the top navigation menu.<\/p>\n

Then from the \u201crsync target\u201d FreeNAS server that is pushing the data you need to recall the basic \u201crsync\u201d rules if you have existing data on the source and you don\u2019t need a whole new directory structure as is my situation then you need to put in a trainilg \u201c\/\u201d at the end of your source path so that \u201crsync\u201d doesn\u2019t create a whole new directory if that\u2019s not what you want. Just make sure you consult the very robust \u201crsync man pages\u201d from a Linux\\Unix\\BSD system as they seem to have the same switches.<\/p>\n

There is no way to monitor the \u201crsync\u201d progress from the FreeNAS GUI so you will have to ssh into the server or bring up the shell in the GUI and perform a \u201cps ax | grep rsync\u201d to see the progress. I am also monitoring the directory growth via my Centos 7 system that accesses all my networks and I have the NFS filesystems of each FreeNAS mounted to. This also reminded me I needed to grow my second FreeNAS\u00a0 system’s NFS volume and did this via the GUI striping in 2 spare 3TB SAS disks I had while still running rsync to this volume<\/p>\n

That was my very wild Saturday night a bit different from some non-computer flavored wild and wordy but still not expressing all the hurdles as any of you in this field know. \u00a0This Saturday night ended with my FreeNAS systems syncing to each other and still doing so as I write this.<\/p>\n

FreeNAS rsync trailing “\\”:<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

FreeNAS Rsync Module Navigation Location:<\/p>\n

\"\"<\/a><\/p>\n

 <\/p>\n

Monitoring rsync proceess:<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

That\u2019s right a wild Saturday night in my computer room revolving around my secondary FreeNAS server\\disk array. I have had so many issues updating this server to FreeNAS 11.1 I decided tonight I would make sure I came to a … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":1067,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wprm-recipe-roundup-name":"","wprm-recipe-roundup-description":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[7,6],"tags":[501,657,421,661,366,650,663,389,654,291,662,653,321,658,660,659,422,655,656,652,264,651,472],"class_list":["post-1064","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technical-non-site-related","category-whole-site-development","tag-centos-7","tag-computer-hardware","tag-dd-wrt","tag-defroute","tag-disk-array","tag-doing-it-big-with-late-wild-saturday-night-in-my-computer-room","tag-firefox","tag-freenas","tag-freenas-11-1u2","tag-lan","tag-linksys-g-router","tag-network-routing","tag-nic","tag-ping","tag-rsync","tag-rsync-module","tag-sas","tag-sata","tag-ssd","tag-ssh","tag-wan","tag-wild-saturday-night","tag-zfs"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/dhoytt.com\/mainblog\/wp-content\/uploads\/sites\/3\/2018\/02\/freenas-shell-cli-ps-rsync.png?fit=1920%2C1053","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/posts\/1064","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/comments?post=1064"}],"version-history":[{"count":3,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/posts\/1064\/revisions"}],"predecessor-version":[{"id":1070,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/posts\/1064\/revisions\/1070"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/media\/1067"}],"wp:attachment":[{"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/media?parent=1064"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/categories?post=1064"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/dhoytt.com\/mainblog\/wp-json\/wp\/v2\/tags?post=1064"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}