I learned this week that “Automatic” often means “Crap” in the world of network auto negotiations – I have a new internet connection, and when I allow my modem to auto-negotiate a connection, it gets “taken for a fool” by my ISP. I guess the ISP want’s to stop me from using all of the bandwidth I pay for, so they “encourage” customers modems to auto negotiate a slower connection. Upon digging into my ADSL 2+ modems settings, I found that under the “Line Mode” option in the ADSL Parameters menu, I could FORCE my modem to negotiate the ADSL2+ connection I am paying for, instead of the slower standard generic ADSL profile my ISP sneakily seems to want the device to auto negotiate.
If your connection seems to be slow, check your ADSL Parameter settings and make sure your line mode is equivalent to the ADSL plan you are paying for.
Like most FreeNAS errors, this one just appeared out of nowhere, on a system that has been untouched, and running trouble free for some months. Once the error showed up on the screen, I was unable to connect to my shares, or the Web GUI to trouble shoot it. The term “RE0” was a giveaway, because I remember when I assigned the NIC it was given this label. My first thought was that the NIC card died, and I replaced it with an identical card I have here which I know is good. This didn’t change anything unfortunately.
After a short search through my files and found a backup of the FreeNAS configuration XML file I had made recently (A habit I have gotten into with this system). With this in hand, I selected option 4, and reset the system to Factory Defaults. After rebooting and re-assigning the interfaces, to my surprise everything came back up. After logging in through the Web GUI and being able to access things again, I tried to restore the settings from the configuration.xml file. This failed badly. The system would not boot from the hard drive now, and even though all the data is backed up, I still got that sinking feeling in my stomach.
After inserting the Freenas Disc in the drive and setting the boot order in bios, I was able to boot the system from the Live CD. Knowing I had my raid configuration in the XML file, I re-installed the FreeNAS operating System onto the hard drive, re-assigned the interfaces, and was again back to factory defaults. I again logged in through the Web GUI and backed up the clean install XML file, and then opened it in text editor. I also opened my original backup file from when things were good, and compared the two. I did find the problem.
When I compared the two files together I noticed dozens of additional lines in the backup XML file, that weren’t in the fresh one. They looked like these:
Then it struck me that what must have happened, is that FreeNAS was tweaking itself, and I guess it must have made a mistake somewhere along the way. I unchecked the box in the Advanced settings panel, removed all of the extra lines of code that contained “System tuning” from the backup XML file, and restored it into FreeNAS, and VOILA! It was all back online, my Raid 5 was in tact, and everything was back to normal.
I have been using it for a bout 5 days now since implementing the fix, and it is back to its old self again. It hasn’t skipped a beat!
11 Aug 2011 – I have just been playing around again with my Freenas and found I can trigger this error immediately by filling in the MTU option. Leaving this field blank works fine, but the second I try to set it for something like Jumbo MTU (9000) it goes into error mode the second I try to remotely access a share.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
I learned this week that “Automatic” often means “Crap” in the world of network auto negotiations – I have a new internet connection, and when I allow my modem to auto-negotiate a connection, it gets “taken for a fool” by my ISP. I guess the ISP want’s to stop me from using all of the bandwidth I pay for, so they “encourage” customers modems to auto negotiate a slower connection. Upon digging into my ADSL 2+ modems settings, I found that under the “Line Mode” option in the ADSL Parameters menu, I could FORCE my modem to negotiate the ADSL2+ connection I am paying for, instead of the slower standard generic ADSL profile my ISP sneakily seems to want the device to auto negotiate.
