Interstellar

Updated this morning. System totally locked up after about 10 mins. Nothing in the console or flash drive syslog. Forced a reboot - everything ok 8 hours later so hoping it is a one off!

Update. Managed to achieve isolating Docker/VMs in the end thanks to the following threads: Essentially your second/third/forth NIC needs to be set as follows in UnRAID's network settings: UnRAID Network Settings Enable bonding: No Enable bridging: No IPv4 address assignment: None UnRAID Docker Settings (Example) - Use your own IP ranges. Subnet: 10.10.2.0/24 Gateway: 10.10.2.1 DHCP pool: 10.10.2.100/27 (32 hosts) Then in each of your docker containers you need to pick eth1 (or br1 if you picked 'Enable Bridging' = Yes above). Then add a fixed IP if you want, otherwise it'll be set an IP based on the range set above. Now all my Dockers can communicate with each other, the outside world and UnRAID (and vice-versa)!

Still struggling with this if anyone has any ideas? Cheers.

Any ideas why I'm now getting this error in the preview window? (Only change I've made is upgrading from 6.7.1 to 6.7.2) tput: unknown terminal "tmux-256color" Thoughts? Cheers.

Updated from 6.6.5 (just shy of 90 days uptime...) All seems to have gone OK. Updated all my plugins and dockers before hand and again afterwards for those plugins that required 6.7.0. I'll be staying at this version for another 90 days 😂

As a side note I hate monochrome icons. When the sidebar icons changed from colour to monochrome in OSX it takes longer for me to work out which one I want. Style over functionality!!!

Im not up to date with the changes that cause your issues, but if it’s a change for newer hardware then you might be SOL. Cant keep putting effort in supporting 10+ year old platforms.

Indeed. In a time where most upgrades are becoming paid every year this is welcome. Almost getting to the point where I'll buy another pro license, just incase!

Well certainly a welcome improvement! Just need to sort out the way we login and it’s be a perfect package for me. It’s been running absolutlely perfectly for over a year now. Bit of a pain loosing internet whilst the machine restarts but other than that 99.9% uptime. Other than the BIOS update I did preventing my NIC from working in the server anymore it’s been flawless. Up to date quad NIC bought so should resolve that one tomorrow..!

Updated my X10SLL-F from a 2014 BIOS to a 2018 one. It made my Intel Pro 1000PT Quad NIC stop working! (New BIOS seems to have fixed a bug where previously the bottom slot would negotiate pci-e v1a but now negotiates v2, and the 1000PT doesn’t work with v2! New NIC inbound! Other than that the flash went fine and everything working...

Absolutely fine here. Even seems to start faster than before (not timed it, just feels like the time I hit restart to the time pfsense comes back up is way shorter than it used to be!)

Upgraded from rc1 here. All good and a speedy boot from what I can tell. No log errors and everything working.

All good and speedy here! Passthrough VMs started much quicker than usual from cold. SuperMicro X10SLL-F, 1230v3, RX560, Intel quad NIC

Nope. I think I just pulled the drive and let parity rebuild as it was faster. Although I have a vague recollection that I re-formatted the drives so I could mount them then filled them with a massive/dev/zero file (at full speed!), then did the /dev/md* command to clear the first 500M, then pulled the drive and forced the parity to remain valid. Ended up with a handful of parity errors after the 11 hour check. Not ideal but at least I had a 99.999% valid parity whilst it checked it. System works perfectly otherwise and I haven’t tried it again on newer versions.

6.5.0 to this last night - no issues I’ve come across yet!

Not reset when re-started or restarting UnRAID. If I delete the data folder I have to do it again.

Sorry, stupid mistake not including them... here you go: Seems to be running the scripts, I'll run them again once its started... Mar 30 13:32:44 eaf70ed4c604 syslog-ng[14]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [792 kB] Fetched 2060 kB in 3s (650 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 16456852 bytes Starting services * Starting MariaDB database server mysqld ...done. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[474]: Upgrading MySQL tables if necessary. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysql' as: /usr/bin/mysql Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[485]: Checking for insecure root accounts. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[489]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Mar 30 13:33:11 eaf70ed4c604 zmdc[572]: ERR ['zmc -m 1' exited abnormally, exit status 255] Mar 30 13:33:11 eaf70ed4c604 zmeventnotification[612]: INF [Push enabled via FCM] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (Skipping @reboot jobs -- not system startup) success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Edit: OK, ran the following after start: chown -R root:www-data /var/cache/zoneminder chmod -R go+rw /var/cache/zoneminder And it works. So it begs the question, what is changing the permissions after start?

Hi, Sadly no dice. Creates the events/images/temp folders and then nothing. Restarted it a few times and tried it using the default setup, to an array disk, to the cache disk and finally to my intended out-of-array disk. Nothing works. From the docker side: root@eaf70ed4c604:/var/cache/zoneminder# ls -al total 0 drwxrwxrwx 5 root www-data 46 Mar 30 09:26 . drwxr-xr-x 1 root root 70 Mar 14 23:42 .. drwxr-xr-x 2 root www-data 6 Mar 29 18:44 events drwxr-xr-x 2 root www-data 6 Mar 29 18:44 images drwxr-xr-x 2 root www-data 6 Mar 29 18:44 temp From the server side: root@UnRAID:/mnt/disks/CCTV1/Front_Door# ls -al total 0 drwxrwxrwx 5 root sshd 46 Mar 30 09:26 ./ drwxrwxrwx 3 root sshd 24 Mar 29 18:38 ../ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 events/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 images/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 temp/ Is that right?

I've also got the "web_php[9233]: ERR [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]" error... /config <-> /mnt/cache/appdata/Zoneminder /var/cache/zoneminder <-> /mnt/cache/appdata/Zoneminder/data This is a default install (bar changing the unraid side of things as I don't use /mnt/user/appdata...) From within the docker: oot@03fff72fd46e:/# ls -l /var/cache/zoneminder/ total 0 drwxr-xr-x 2 root www-data 6 Mar 29 18:47 events drwxr-xr-x 2 root www-data 6 Mar 29 18:47 images drwxr-xr-x 2 root www-data 6 Mar 29 18:47 temp From the docker log... Mar 29 18:55:04 03fff72fd46e zmwatch[9307]: ERR [Error getting last capture time for Front-Door] Mar 29 18:55:04 03fff72fd46e zmwatch[9307]: INF [Restarting analysis daemon for Front-Door] Mar 29 18:55:04 03fff72fd46e zmdc[9262]: INF ['zma -m 1' starting at 18/03/29 18:55:04, pid = 9472] Mar 29 18:55:04 03fff72fd46e zmdc[9472]: INF ['zma -m 1' started at 18/03/29 18:55:04] Mar 29 18:55:04 03fff72fd46e zma_m1[9472]: ERR [Can't make events/1: Permission denied] Mar 29 18:55:04 03fff72fd46e zma_m1[9472]: FAT [Can't symlink '1' to 'Front-Door': Permission denied] Mar 29 18:55:04 03fff72fd46e zmdc[9262]: ERR ['zma -m 1' exited abnormally, exit status 255] Mar 29 18:55:07 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:07 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:12 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:13 03fff72fd46e zmc_m1[9365]: INF [Front-Door: 5000 - Capturing at 25.00 fps] Otherwise it works...!

Missed this thread, but we need a way of keeping/running VMs with the array stopped. E.g. Disk failed whilst your away? Tough luck! It is abit silly that I can’t seem to have VMs running with the array stopped.

Bumping this because it’s desperately needed for those running pfsense and the like.

Dunno what it is but it just isn’t happy. Just going to pull the drives and do a rebuild - only 4 hours as it only needs to do half the array.

Regarding the clearing an array drive script - why is it so slow (even with reconstruct write on?) Doing dd bs=4M if=/dev/zero of=test to a mounted disk = max disk speed (~130MB/sec) dd bs=1M if=/dev/zero of=/dev/md7 results in ~2MB/sec. There should be no difference? Take years to clear 2TB drive at 2MB/sec!

Quick question: Replacing two of my 2TB array drives with 4TB versions, (one at a time obviously). However I need the array to mount and VMs to start otherwise I have no internet (pfSense VM!). I'm fairly sure the array DOES mount whilst the disk is rebuild - correct? I'm fairly sure it did last time but then I wasn't running pfsense! Thanks.

Nope - just by doing thinkbroadband's new speed test which maxes out my connection results in that kind of level. Can we disable the patch? (If they've got to my server already I doubt this will make much of a difference!)