Jump to content

[Solved] Settings / plugins not saving on reboot


skot4th

Recommended Posts

After having multiple issues with Freenas 9 I thought I'd try unRaid as I've read several good reviews.  However now I'm starting to wish I hadn't bothered.

 

Several times now I have set up the server, configured the date / time zones, DNS / IP settings, etc. as well as installing the Plex plugin, however whenever I reboot the server (to ensure the settings have saved) when it reboots everything is set back to default.  The only items remaining in place are the shares which I have set up and the files within them.

 

The web gui also fails to launch each time, so I need to use the following command to re-launch it

 

nohup /usr/local/sbin/emhttp &

 

I even tried buying a proper license key as I thought that it could be an issue with the trial version, however this hasn't resolved the issue.

 

I have reconfigured the server the way I want it one last time in order to generate the system log.

 

Can anyone shed any light on why this keeps happening?

 

Thanks

 

Scott

Link to comment

I suspect your USB drive is possibly corrupted or set to read only. That's the only way the changes wont be persisted.

 

Are you running on bare metal or as a hypervisor guest?

 

Also, try using Dockers instead of plugins. They tend to be more stable and easier to setup and configure.

 

 

Link to comment

Can you post the diagnostics (Tools->Diagnostics) file so we can see your setup?

 

The command to start emhttp should be the only command in the default config/go file on the USB drive.  Are you sure you have that file and it has the correct contents?

 

When you talk about configuring the system are you saying that changes made through the GUI are being lost?    If so that often means that the USB drive has been set read-only for some reason  (if so there should be a message to that effect in the syslog).  If you are making changes via the Command line then they would be lost on reboot as unRAID runs from RAM.

Link to comment

Hi,

 

Yes, I'm making changes through the Web GUI.  The only command line I'm using is to launch the Web GUI as it fails to launch.

 

I'm running unRAID 6.0.1 on a HP N54L server with an 8GB Scandisk Cruzer Facet USB to boot from and when I make the changes / log in to the GUI I'm using "ROOT".

 

Which files is it you need from the diagnostics as there's about 20 different files in the .zip?

 

Cheers

Link to comment

in fact, I'll just attach the entire zip for you

The syslog contains the lines:

Sep  6 10:17:23 Tower kernel: FAT-fs (sda1): bogus number of reserved sectors
Sep  6 10:17:23 Tower kernel: FAT-fs (sda1): Can't find a valid FAT filesystem

I also noticed

Sep  6 10:21:13 Tower emhttp: import flash device: sda
Sep  6 10:21:13 Tower emhttp: Warning: Flash device not mounted!

and

Sep  6 10:21:13 Tower kernel: read_file: error 2 opening /boot/config/super.dat
Sep  6 10:21:13 Tower kernel: md: could not read superblock from /boot/config/super.dat
Sep  6 10:21:13 Tower kernel: md: initializing superblock
Sep  6 10:21:13 Tower emhttp: Unregistered (-3)

There is also no evidence of a license key file being found. These suggest that there is a problem with the USB drive (possibly corruption).    You might want to try plugging it into a PC/Mac to check that it is OK.

 

The diagnostics zip suggest that you do not have the config/go file on your USB drive that is used normally to start emhttp!  Can you check what is in the config folder by doing

ls -l /boot/config

from a  console or telnet session?

Link to comment

Doing that I get this...

root@MediaServer:~# ls -l /boot/config
total 40
-rw-rw-rw- 1 root root  256 Sep  6 18:08 Basic.key
-rw-rw-rw- 1 root root 9764 Sep  6 18:40 disk.cfg
-rw-rw-rw- 1 root root  135 Sep  6 19:04 docker.cfg
-rw-rw-rw- 1 root root   85 Sep  6 18:55 domain.cfg
-rw-rw-rw- 1 root root  366 Sep  6 18:35 ident.cfg
-rw-rw-rw- 1 root root  266 Sep  6 18:35 network.cfg
drwxrwxrwx 6 root root  140 Sep  6 19:04 plugins/
-rw-rw-rw- 1 root root  502 Sep  6 18:35 share.cfg
drwxrwxrwx 2 root root   40 Sep  6 18:21 shares/
drwxrwxrwx 2 root root  240 Sep  6 18:17 ssh/
-rw-r--r-- 1 root root 4096 Sep  6 19:06 super.dat

 

I ran write to the USB fine on my windows PC.  I originally loaded 6.1 to the usb but re-formatted it and loaded 6.0.1 as the plugin I wanted wasn't supported by 6.1.  That was only a few hours ago.

Link to comment

Doing that I get this...

root@MediaServer:~# ls -l /boot/config
total 40
-rw-rw-rw- 1 root root  256 Sep  6 18:08 Basic.key
-rw-rw-rw- 1 root root 9764 Sep  6 18:40 disk.cfg
-rw-rw-rw- 1 root root  135 Sep  6 19:04 docker.cfg
-rw-rw-rw- 1 root root   85 Sep  6 18:55 domain.cfg
-rw-rw-rw- 1 root root  366 Sep  6 18:35 ident.cfg
-rw-rw-rw- 1 root root  266 Sep  6 18:35 network.cfg
drwxrwxrwx 6 root root  140 Sep  6 19:04 plugins/
-rw-rw-rw- 1 root root  502 Sep  6 18:35 share.cfg
drwxrwxrwx 2 root root   40 Sep  6 18:21 shares/
drwxrwxrwx 2 root root  240 Sep  6 18:17 ssh/
-rw-r--r-- 1 root root 4096 Sep  6 19:06 super.dat

 

I ran write to the USB fine on my windows PC.  I originally loaded 6.1 to the usb but re-formatted it and loaded 6.0.1 as the plugin I wanted wasn't supported by 6.1.  That was only a few hours ago.

Well the syslog says that unRAID is not happy with it!  Maybe you should copy the files off again and reformat it to make sure?

 

The go file which should be there is missing from the config folder which explains why the GUI is not starting.  You can copy the default one from the ZIP distribution I assume you used to initially set up the USB stick.  I can see that there is a .key file there but since unRAID said it could not mount the USB stick that might explain why no key was being detected.

Link to comment

So I re-formatted the USB and copied over the files on a different laptop.

 

All seems to be working now.

 

Please can you check over these diagnostic files to make sure they look ok?  To me all seems good though.

Things look a lot better there.  There are no longer error messages in the syslog relating to the USB drive so hopefully that means any issues there are now resolved.

 

I guess the proof is when you find that your settings ARE now surviving a shutdown/restart.

Link to comment
  • 1 year later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...