Hi,

 

I've just upgraded to 6.4 without hassle. However, after reboot, my server has neither network, nor webGUI. I noticed some network and webGUI related errors in console:

 

modprobe: FATAL: Module bonding not found in directory /lib/modules/4.14.13-unRAID
Cannot find device "bond0"

 

/usr/local/sbin/emhttp: line 54:  1644 Segmentation fault  /usr/local/sbin/emhttpd
warning: commands will be executed using /bin/sh

 

What can I do now to fix it?

 

Thank you.

If this cannot be fixed, is there any way to downgrade to previous version with command line tools ?

I searched the forum and found the solution: there's a 'previous' folder on flash drive, copy its content to flash drive root, reboot, and it returns to previous working version. I guess I'll have to wait for some days til the new 6.4-stable really stable.

Don't expect a fix if you can't give any information to base a fix on. Did you read the release notes for 6.4? Do you have a monitor and keyboard attached?

Did you get a diagnostics file while you were on the console?  (Type   diagnostics   on the command line.  That will write the file to the logs folder/directory on the flash drive.) 

 

What version did you start from? 

 

What plugins, VM's and Dockers do you have installed?  

 

Did you check for updates for these before installing version 6.4.0?

Thanks for the replies. I noticed other people had the same issue, so this is kinda common for some people. I just gave it another try in order to gather the logs, hope it helps to hunt the bug.

tower-diagnostics-20180116-1833.zip

You should try booting using a different flash drive with a clean v6.4 install, just to confirm if the issue is related to v6.4 or some config or customization you're using.

12 minutes ago, johnnie.black said:

You should try booting using a different flash drive with a clean v6.4 install, just to confirm if the issue is related to v6.4 or some config or customization you're using.

 

Thank you. A clean install works like a charm, network working, webGUI lists all disks. So what's the next step to find what's going wrong in my working environment ?

I would backup the current flash drive, create a new install on it and copy just super.dat (disk assignments) and your key from the current flash, both on the config folder, then start reconfiguring the rest one thing at a time.

You also start several scripts from your go file. Have a look at these. In general it is recommended to keep your go file as virgin as possible.

 

I second the advice of johnnie.black and start with a clean install. It helps getting rid of unnecessary files and folders from the past.

Ok, I'll go the clean install way, we'll see what the trouble source is.