rjstott

And here is another +1

I am watching this with interest as I too would like to run a docker with FreePBX so I can shut down and redeploy a Raspberry PI. This application seems to have defeated everyone here 'cos despite all the requests it hasn't been done. I think the database aspect ought to be the simple bit to fix especially as I think (at least originally) the config came from config files run at startup? The more difficult part would surely be the add on modules (I'll call them plug-ins for want of the right terminology). Not only are these a user choice but are also individually updateable. In fact the whole structure here is very similar to unRaid and its plugin system? I'll happily help test out anythng you produce as I think I do have some working knowledge of FreePBX and I do have a working system on my Pi which I can compare to? What I can't do is help with Docker setups as unless they work, the best I can do is complain that they don't! Sounds negative I know but its a 'black art' for which only the results are the valuable bit to me.

Hi, All deleted and a fresh start. This is the log: => Installing MySQL ... Installing MySQL system tables... OK Filling help tables... OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /usr/bin/mysqladmin -u root password 'new-password' /usr/bin/mysqladmin -u root -h 5e73e4deab69 password 'new-password' Alternatively you can run: /usr/bin/mysql_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the manual for more instructions. You can start the MySQL daemon with: cd /usr ; /usr/bin/mysqld_safe & You can test the MySQL daemon with mysql-test-run.pl cd /usr/mysql-test ; perl mysql-test-run.pl Please report any problems at http://bugs.mysql.com/ Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... And of course it goes on this way. Here are the mappings: /var/lib/phpfiwa /mnt/cache/apps/Docker/apps/emon/fiwa/ /var/lib/phpfina /mnt/cache/apps/Docker/apps/emon/fina/ /var/lib/phptimeseries /mnt/cache/apps/Docker/apps/emon/time/ /etc/mysql /mnt/cache/apps/Docker/apps/emon/mysql/ /var/lib/mysql /mnt/cache/apps/Docker/apps/emon/mysqllib/ The environment variable MYSQL_PASSWORD is set to emoncms but yet there is still no GUI. The log implies I should be doing some extra things directly, should I?

Hi thanks but I created the additional folders so each fas its own. The CMS log has changed to look like => Using an existing volume of MySQL Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... Waiting for MySQL to start... I think I did see it start once in the log but now it is a long wait! I don't have sql anywhere else, unless Emby or Plex hide it. The WebUI still doesn't run. The unRaid main log file now has this for Start through to Stop Nov 28 20:09:30 Media autofan: Highest disk temp is 29°C, adjusting fan speed from: OFF (0% @ 0rpm) to: 372 (145% @ 903rpm) Nov 28 20:09:34 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Emoncms' Nov 28 20:09:34 Media kernel: device vethce9f7e9 entered promiscuous mode Nov 28 20:09:34 Media kernel: docker0: port 1(vethce9f7e9) entered forwarding state Nov 28 20:09:34 Media kernel: docker0: port 1(vethce9f7e9) entered forwarding state Nov 28 20:09:34 Media avahi-daemon[21294]: Withdrawing workstation service for vetha0b9f82. Nov 28 20:09:34 Media kernel: docker0: port 1(vethce9f7e9) entered disabled state Nov 28 20:09:34 Media kernel: eth0: renamed from vetha0b9f82 Nov 28 20:09:34 Media kernel: docker0: port 1(vethce9f7e9) entered forwarding state Nov 28 20:09:34 Media kernel: docker0: port 1(vethce9f7e9) entered forwarding state Nov 28 20:09:36 Media ntpd[1424]: Listen normally on 9 docker0 172.17.42.1:123 Nov 28 20:09:36 Media ntpd[1424]: new interface(s) found: waking up resolver Nov 28 20:09:38 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Emoncms Nov 28 20:09:49 Media kernel: docker0: port 1(vethce9f7e9) entered forwarding state Nov 28 20:11:39 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Nov 28 20:12:21 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Emoncms Nov 28 20:12:26 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Emoncms Nov 28 20:12:52 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'stop' 'Emoncms' Nov 28 20:13:02 Media kernel: vetha0b9f82: renamed from eth0 Nov 28 20:13:02 Media kernel: docker0: port 1(vethce9f7e9) entered disabled state Nov 28 20:13:02 Media kernel: docker0: port 1(vethce9f7e9) entered disabled state Nov 28 20:13:02 Media avahi-daemon[21294]: Withdrawing workstation service for vetha0b9f82. Nov 28 20:13:02 Media kernel: device vethce9f7e9 left promiscuous mode Nov 28 20:13:02 Media kernel: docker0: port 1(vethce9f7e9) entered disabled state Nov 28 20:13:02 Media avahi-daemon[21294]: Withdrawing workstation service for vethce9f7e9. Nov 28 20:13:04 Media ntpd[1424]: Deleting interface #9 docker0, 172.17.42.1#123, interface stats: received=0, sent=0, dropped=0, active_time=208 secs Thanks for your help

I pointed all the volume mappings to a folder called emon on my cache drive.Below is the list from the Docker page.: /var/lib/phpfina /mnt/cache/apps/Docker/apps/emon/ /var/lib/phptimeseries /mnt/cache/apps/Docker/apps/emon/ /etc/mysql /mnt/cache/apps/Docker/apps/emon/mysql /var/lib/mysql /mnt/cache/apps/Docker/apps/emon/mysql /var/lib/phpfiwa /mnt/cache/apps/Docker/apps/emon/ This is probably hopelessly wrong. Could you let me know what I need or where to find info? Most installs 'probably' aren't like unRaid so being a novice and a User rather than a developer shows my limits!

I just set up this docker (or at least I think I did), two problems. 1) "Waiting for MySQL to start" is repeating in the log file so startup isn't right (probably 'cos I got the setup wrong) 2) The WEBUI isn't running so no way to get into the package. Anyone got this working and could elaborate on the setup requirement? If I can get this working then I can move on to buy some of the "Openenergymonitor" kit! Thanks

OK recreated the Docker.img and can now run openhab without log errors as below. Note I deliberately restarted the openhab because the UI is back to complaining there is no config file. "NO openhab.cfg CONFIGURATION FOUND" Anyway if I type http://192.168.1.103:8080/openhab.app?sitemap=demo then it works. Any chance this could be corrected in the script that starts the wenGUI or is this something I need to do somewhere. Anyways now I can have a play! Thanks. And deleting the img file and re-creating it is a breeze as all previous settings are retained!

Thanks for the quick reply. You're almost certainly right. Selecting the advanced docker view shows up four old docker image files but the remove command doesn't remove them. So I researched increasing the docker.img file size and came across "btrfs filesystem resize +20G /docker.img" but trying that gave an error that basically states the wrong action will happen if the command is completed. <trfs filesystem resize +20G /mntimgche/apps/Docker/docker. s ERROR: resize works on mounted filesystems and accepts only directories as argument. Passing file containing a btrfs image would resize the underlying filesystem instead of the image. So I think I will have to delete the image and start again. That will have to wait as Plex is currently being used and I have to schedule downtime!

Hi, I thought I had this cracked but 'user' error has defeated me again. I re-installed this latest version and then realised I should have created a proper place for the openhab config directory. So I did this and then got a load of errors about python and something being full. The error didn't say what was full. Anyway this has now killed the installation and I get this error whenever I try to create a new docker image? root@localhost:# /usr/bin/docker run -d --name="openhab" --net="bridge" -e TZ="Europe/Berlin" -p 8080:8080/tcp -v "/mnt/user/apps/Docker/apps/openhab/config/":"/etc/openhab":rw jshridha/openhab Error response from daemon: EOF Has anyone any clues as to what might have been full abd what I should do to fix it. Could it be the Docker.img file isn't big enough at 10GB as I also have three other docker apps (Plex, Emby and Uboquity) installed and running?

I'm also experiencing similar problems. 1) When copying files to unRaid, finder crashes and can leave partial files on the share. 2) Webgui becomes unresponsive and I'm pretty sure it's due to a corruption somewhere when Plex is running a scan (the scan doesn't complete) (Webgui not accessible until a forced restart) I'm currently running a file system test on my drives. One drive has passed and the other is in progress. A recent parity check was fine. I have two almost identical servers at present both running 6.1 rc2, and only one has a problem. They're not hardware identical though!

Problem accessing /openhab.app. Reason: Sitemap 'default' could not be found Having a problem with the OpenHAB install. It installs fine but it can't find either the default or demo config or indeed any other that I try. It seems that there are perhaps two configuration methods? .cfg files and a folder (configurations) of more detailed files which are now at release 18. Anyway, I continually get the sitemap not found message so I'm obviously not putting it in the right place? I loaded an addons.cfg file which is being found and Openhab seems to be running, just the Web UI won't work? I have had a similar problem trying to run Openhab under OS X and there I'm sure the problem is ports and difficulty in start/stopping Openhab. That's easy with the Docker. Anyone else got this working and can help to get me started?

I'm just about to do this. There is mention of needing to change the port for the Unraid Management Interface. I wasn't sure whether this meant the older unMenu interface accessed by IP:8080. If it is the new interface then this might explain your problem. In any event I would have expected two complimentary changes?

Thanks for the explanation of drive allocation and I'll try another cable but that would make two bad cables, maybe these nice round flexible cables aren't so clever after all! Given that the server is mainly for PLEX there probably isn't any need to cache anyway? Regards to all

Here's the latest bit of log: May 10 19:57:31 Tower kernel: res 41/84:00:c8:f2:2c/84:00:05:00:00/40 Emask 0x10 (ATA bus error) May 10 19:57:31 Tower kernel: ata5.00: status: { DRDY ERR } May 10 19:57:31 Tower kernel: ata5.00: error: { ICRC ABRT } May 10 19:57:31 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED May 10 19:57:31 Tower kernel: ata5.00: cmd 60/20:10:70:f5:2c/00:00:05:00:00/40 tag 2 ncq 16384 in May 10 19:57:31 Tower kernel: res 41/84:00:c8:f2:2c/84:00:05:00:00/40 Emask 0x10 (ATA bus error) May 10 19:57:31 Tower kernel: ata5.00: status: { DRDY ERR } May 10 19:57:31 Tower kernel: ata5.00: error: { ICRC ABRT } May 10 19:57:31 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED May 10 19:57:31 Tower kernel: ata5.00: cmd 60/10:18:f8:f9:2c/00:00:05:00:00/40 tag 3 ncq 8192 in May 10 19:57:31 Tower kernel: res 41/84:00:c8:f2:2c/84:00:05:00:00/40 Emask 0x10 (ATA bus error) May 10 19:57:31 Tower kernel: ata5.00: status: { DRDY ERR } May 10 19:57:31 Tower kernel: ata5.00: error: { ICRC ABRT } May 10 19:57:31 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED May 10 19:57:31 Tower kernel: ata5.00: cmd 60/a8:e8:c0:96:2c/00:00:05:00:00/40 tag 29 ncq 86016 in May 10 19:57:31 Tower kernel: res 41/84:00:c8:f2:2c/84:00:05:00:00/40 Emask 0x10 (ATA bus error) May 10 19:57:31 Tower kernel: ata5.00: status: { DRDY ERR } May 10 19:57:31 Tower kernel: ata5.00: error: { ICRC ABRT } May 10 19:57:31 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED May 10 19:57:31 Tower kernel: ata5.00: cmd 60/18:f0:90:98:2c/00:00:05:00:00/40 tag 30 ncq 12288 in May 10 19:57:31 Tower kernel: res 41/84:00:c8:f2:2c/84:00:05:00:00/40 Emask 0x10 (ATA bus error) May 10 19:57:31 Tower kernel: ata5.00: status: { DRDY ERR } May 10 19:57:31 Tower kernel: ata5.00: error: { ICRC ABRT } May 10 19:57:31 Tower kernel: ata5: hard resetting link May 10 19:57:31 Tower kernel: ata5: nv: skipping hardreset on occupied port May 10 19:57:31 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) May 10 19:57:31 Tower kernel: ata5.00: configured for UDMA/133 May 10 19:57:31 Tower kernel: ata5: EH complete May 10 19:57:31 Tower kernel: ata5.00: Enabling discard_zeroes_data Looks very similar to me. Except we're now faulting ata5 not ata4! Could this be a MB problem? The board is an Asus m2npv-vm with a Phenom X4 cpu. There are just 4 SATA ports and it has legacy PATA (not used). When I first swapped the cable the problem became ata6 and if you looked back the cache was ata4. The Directory Cache settings are all default as when I read this up before there seemed to be no need to constrain anything?

Yes I was running directory caching and when I disabled it the disk activity stopped. Perhaps I need to read up about the level of caching to use? So on the disk error saga I swapped around a pair of Sata cables and the error moved. OK so I changed out what seemed to be the faulty cable and now I've got similar errors on a drive I didn't touch? I plan to leave directory caching off for a while and see if things settle down. At least the drive reporting errors isn't the cache and changes to other drives are much less frequent. Thanks to everyone for their input.

I didn't mention that I have a continuous background disk read acivity of average 256K/s that I don't understand as well as associated cpu use. I don't run docker or VM on this box but it does have Plex. I have stopped Plex but this didn't kill the background activity. I ran the 'smart tests' on all drives and checked the error logs and all passed ok. The SSD cache drive doesn't show any errors logged which is strange? Overnight, there was an error report about every 30 mins but it varies between 10-40 mins. Apart from the disk operation timeouts, reading and writing to the array seems ok. I've attached a snapshot of activity, Plex is stopped!

I noticed a few post back someone else is getting disk reports similar to mine, which I'll post below. I too have just filled a data disk though the reports below are for the SSD cache. These failures cause long freezes when carrying out most file oerations. I'm also curious why the SATA SSD connections is limited at 1.5G when it should go at 3G or even 6G? It is a Samsung 840. May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:58:a8:59:22/00:00:00:00:00/40 tag 11 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:60:80:31:10/00:00:00:00:00/40 tag 12 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:68:90:c3:18/00:00:00:00:00/40 tag 13 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:70:90:32:10/00:00:00:00:00/40 tag 14 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:78:80:24:10/00:00:00:00:00/40 tag 15 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:80:50:03:10/00:00:00:00:00/40 tag 16 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED May 10 00:00:06 Tower kernel: ata4.00: cmd 60/08:88:d0:1a:10/00:00:00:00:00/40 tag 17 ncq 4096 in May 10 00:00:06 Tower kernel: res 41/84:38:28:25:10/84:00:00:00:00/40 Emask 0x10 (ATA bus error) May 10 00:00:06 Tower kernel: ata4.00: status: { DRDY ERR } May 10 00:00:06 Tower kernel: ata4.00: error: { ICRC ABRT } May 10 00:00:06 Tower kernel: ata4: hard resetting link May 10 00:00:06 Tower kernel: ata4: nv: skipping hardreset on occupied port May 10 00:00:07 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) May 10 00:00:07 Tower kernel: ata4.00: configured for UDMA/133 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 19 b0 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1055152 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 3d 28 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1064232 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 25 28 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1058088 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 24 d8 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1058008 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 04 2d e8 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 273896 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 18 f4 40 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1635392 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 22 59 a8 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 2251176 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 31 80 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1061248 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 18 c3 90 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1622928 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] UNKNOWN Result: hostbyte=0x00 driverbyte=0x08 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] Sense Key : 0xb [current] [descriptor] May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] ASC=0x47 ASCQ=0x0 May 10 00:00:07 Tower kernel: sd 4:0:0:0: [sde] CDB: May 10 00:00:07 Tower kernel: cdb[0]=0x28: 28 00 00 10 32 90 00 00 08 00 May 10 00:00:07 Tower kernel: blk_update_request: I/O error, dev sde, sector 1061520 May 10 00:00:07 Tower kernel: ata4: EH complete May 10 00:00:07 Tower kernel: ata4.00: Enabling discard_zeroes_data

This started out ok and then went very technical and now I've lost the plot and which episode you're on. I think this was leading to the creation of a vanilla Ubuntu system running in a container. If there is a need for a GUI then some sort of remote access might work, such as Microsoft Remote Desktop? The purpose of such a container would be to allow Users (simple people like me) to add in one or two applications that work well in Ubuntu land whilst running them in a safe haven alongside an unRaid system. I'm interested because I'd like to run Asterisk. It uses hardly any cpu (2% on a raspberry pi, only needs a TCP/IP connection to the outside world and just very occasionally it needs a tweak through the very basic GUI. There are probably some other similar apps such as a basic mail server that could be run too either in the same container or a duplicate Ubuntu container? Perhaps someone would comment so that I know what's going on and perhaps it's time to create a new non-technical thread with instructions how to get a basic Ubuntu container set up and let us non-technical folk try to use it and post back feedback on what works and what doesn't?

Squid, so many thanks, instant fix!

CTRL-F5 is a quick way to do both. Tried the key-combo, no change. Restarted the browser and tried a different browser no improvement. I'm sure I need to update the Webgui plugin which is named "dynamix-2014.12.01" so that the new updates work? Where are the new files?

What exactly do you mean by this? Essentially the WebGUI has lost all the formatting and graphics so the first few displayed lines of the Main page are as follows:- [unRAID] unRAID Server Plus Server Description Version Uptime Tower • 192.168.1.102 Media server 6.0-beta12 Dashboard Main Shares Users Settings Plugins Docker Stats Tools Help Info Log My best guess is that something hasn't downloaded or installed properly but now I can't use the plugin update page as there are no update buttons (see attached screenshot)

Somewhere in the update process my WebGUI has become scrambled. I can't find a location to download the Webgui plug-in from. Any help appreciated as at present it's not even possible to go back to where I was?

Quick post. My DNS issue is fixed. The problem came from an Orange Livebox router broadcasting a Bonjour service and a reboot stopped it. Now I get the router address when the server asks for an IP from DHCP. So one cause of failures to update Dynamix and subsequent difficulties with re-install were for me caused by a bad DNS address. I'm not convinced the Network Control panel works properly though as I could not override the incorrect DNS IP.

Frank1940 Thanks for the help and you are right again, the relief was temporary and the incorrect 169.254.179.233 DNS address is back. I can't seem to do anything about it. Using the Network Control Panel if "Obtain DNS automatically" is on then up comes 169.254.179.233 (uneditable) and if "Obtain DNS auto" is off then I can edit it but it reverts in seconds back to 169.254.179.233. This isn't in the Network.cfg file and it isn't in my router which only has entries for my ISP (Orange). In any event I was using a manual IP setting but I've changed this to a static IP but nothing seems to budge the 169 address! Unless someone has a magic fix, tomorrow I'll set up a local network without the ISP just to remove that as well as turning off other local devices save the unRaid box and one Apple mac. I looked through the log and Sep 24 23:24:14 Tower avahi-dnsconfd[8250]: New DNS Server 169.254.179.233 (interface: 2.IPv4) So I guess something is sending this IP address, so perhaps tomorrow will solve it!

THXs Frank1940, you were right. Although the Network config file looks ok, the network settings file (wherever it is) showed that a 169 ip was set for the DNS server. Bizarrely this was unchangable and I had to resort to editing the resolv.conf file. I have at last got back to a working webGui and the ability to update. Still don't know why there is a strange DNS setting in the resolv file or why I can't change this from the settings screen.