Johnyb62

I recently had an issue whereby the camera stream from a ring doorbell stopped working, tried to resolve but couldn't so bit the bullet, uninstalled & re-installed everything. But the process has changed since I orignally installed using an earlier version & updated, however this time I had problems which might be worth considering looking at / fixing if possible. Kicked off stopping the ring-MQTT container, renamed the data folder, then deleted the container Then removed the ring authorised client device from my Ring online web portal However trying to install the ring-mqtt container via Unraid Apps is where things didnt go quiet right. So within the 'add container' page you can configure the basic settings (eg data path / mqtt host / username / password / Enabled cameras:true / snapshot mode: all) but when I try to start the container - it just keeps restarting - when I try to look at the logs the page just closes. Reading though the docker install on the wiki, it confirms you need a config.json in order for it to start up. But looking in the data folder this file isn't created. I thought as I'd entered the basic parameters on the 'add container' page this would be covered, but it doesn't seem so. The way around this was for me to copy my previous config.json file to the new data folder, at which point the docker would fire up & remain running. That then allowed me to use the http://<host>:55123/ to obtain the refresh token - and all was good. Looking at the contents of the config.json this included some of parameters I had configured when setting up the container { "mqtt_url": "mqtt://user:[email protected]:1883", "mqtt_options": "", "livestream_user": "", "livestream_pass": "", "disarm_code": "", "enable_cameras": true, "enable_modes": false, "enable_panic": false, "hass_topic": "homeassistant/status", "ring_topic": "ring", "location_ids": [ "" ] } / Is there a need to change the template you provide to accommodate for this as I'd image could cause first time users (on Unraid) some problems ? Thanks

If I use the latest build (in either bridge or host) doesn't work, but qmcgaw/gluetun:v3.35.0 does (in bridge)

Ok but strangely :v3.35.0 runs just fine in bridge mode?

Have the same issue, your fix got me back up & running (thanks). Case reported: here

Built a new system using some older drives (they may have been used in an unraid array before) however they show 20.9Gb used, but looking at the files systems they are empty. Is this just a parity overhead? Its not the docker image / System files as they sit on the cache drive:- Found a similar post, but that issue has been excluded. https://forums.unraid.net/topic/51014-new-array-22gb-used-space/

I has an issue whereby my server was crashing when doing a parity check, turns out it was the cheaper controller (SATA port multiplier) although nothing showed up on the system logs. This was the card I went for, based upon the AMS1166 chipset as advised in the recommended controller post. I don't have a x4 slot on the MB so had to go with the x1. That said the speed of this thing compared to my older dodgy card is a big jump (parity check went from around 36MB/s to 100MB/s) https://www.amazon.co.uk/dp/B097RBLM9G?ref_=pe_27063361_487360311_302_E_DDE_dt_1

Swapped out RAM, still didn't resolve the issue - so was looking at replacing the MB next. As it was advised above to replace my controller (SATA port multiplier) I took a punt with this first. Low & behold this cracked it, was able to run a parity check in one go without a system crash. Well chuffed. So it looks like whilst unlikely, it was the dodgy controller card causing the issue. Thanks to those who posted suggestions. This was the card I went for, based upon the AMS1166 chipset as advised in the recommended controller post. I dont have a x4 slot on the MB so had to go with the x1. That said the speed of this thing compared to my older dodgy card is a big jump (parity check went from around 36MB/s to 100MB/s) https://www.amazon.co.uk/dp/B097RBLM9G?ref_=pe_27063361_487360311_302_E_DDE_dt_1

Tried option (1) replacing the PSU, however the issue still remains. Whilst the RAM test worked, I may try to swap this out first rather than moving to swapping out the MB / replace the machine.

Thanks for the feedback, much appreciated. There we're insufficient SATA ports on the m/b hence why I added the SATA PCI card but its a relatively cheap one as I didn't realise there would be much of a difference in them. (Desktop PCI-E to SATA 3.0 Controller Expansion Card 4-Port SATA 3.0 6Gbp.) So looks like my options here are:- 1) PSU Issue: - Source another PSU to try replacing current one totally. (its a Dell m/b so waiting for the adaptor to arrive which allows me to use standard PSU) 2) MB Issue - Think as its a Dell its a proprietary size board not ATX so only option is to seek an identical replacement or bin the PC & build using a suitable MB with a decent amount of SATA connections 3) RAM - I've conducted the RAM test which didn't show any issues, but will try running with a single stick to be sure 4) Replace SATA card - Would welcome recommendations here on what to look for, don't want to purchase another which is not up to the mark

Parity check has been running since aprox 8am, server crashed just afer 8pm. syslog

Cannot believe I forgot about this for so long, but system crashed recently so reminded me. Things ive tried: 1. Run Memory test as suggested above, pass - no issues 2. Using different PSU. As its a Dell with a proprietary PSU connector for the m/board - I used another PSU to power the drives, therefore lightning the load on the main PSU. But issue still remaind. Whilst this doesn't completely rule out the PSU, thought maybe the issue was at load. Any suggestions welcomed. Thanks. ms-diagnostics-20220909-1631.zip

Thanks. Turned out a server reboot solved it and started working as expected.

You are absolutely right, yes I do need to resolve the underlying issue. Truth be told I'd completely forgotten about the parity check issue until a recent server crash which started a parity check. My initial instinct was to get the parity check to run through to make sure my data was ok (by slowing the process down), then revisit the underlying problem. I'll update my original post. thanks

I’m having issues with my system whereby it’s crashing when a parity check is left running continuously. If I manually resume for 20mins & pause for 45 mins it seems to be ok, but doing this manually is not great. I’ve tried this add on which seems ideal but it doesn’t seem to be working for me. The pause occurs but the resume doesn’t. Probably something I’m doing wrong, but would appreciate some help. Settings shown below. But effectively I’m trying to use custom with increment resume time ‘35 * * * *’ , and increment pause time ‘55 * * * *’

Delete the file... rm /mnt/disk4/system/docker/docker.img

Thanks for the advice. Was just concerned as the unraid OS showed the two locations of that file deleting may cause issues.

Not sure why but I've got two docker.img files, one sitting on the cache drive and one on the array disk4. Last modified date of the disk4 file is back in Nov2021 which suggests its no in use. How can I resolve this issue & end up with one docker.img file on the cache ? (Without having to rebuild the containers). Thanks I tried changing system share setting Use Cache Pool from pefer to yes, stoping docker & invoking mover but no change.

Found an issue when running parity check on my array after about 10mins caused the system to crash (not just GUI unresponsive but no longer connected to router) . Booting in "Unraid OS GUI Safe Mode (no plugins)" allowed the parity check to progress so though all was good. Coming back this morning the server was again unresponsive, physical power down / up required, however after restarting it confirmed the check had completed. I thought I'd cracked the issue (being one of the plugins was causing it), but seeing as it crashed some point after completing the parity check this cannot be true. Any ideas? Thanks

Is there a way to change the ownership / access rights of a share on an Unassigned device? I've got a 40Gb USB drive attached which I used as the Temporary Download Folder for SABnzbd (docker). Although the d/l works ok, sab reports 'Cannot change permissions of /incomplete-downloads/temp'. When I look at the owner of the folder its root, but I don't seem to be able to change that via chown -R nobody:users /mnt/disks/tempdrive/temp, nor does newperms /mnt/disks/tempdrive/temp make any difference. Any ideas? Suppose I could change Sabnzbd docker to run as root, but hoping there's another way. Thanks

Is there a way to change the ownership / access rights of a share on an Unassigned device? I've got a 40Gb USB drive attached which I used as the Temporary Download Folder for SABnzbd (docker). Although the d/l works ok, sab reports 'Cannot change permissions of /incomplete-downloads/temp'. When I look at the owner of the folder its root, but I don't seem to be able to change that via chown -R nobody:users /mnt/disks/tempdrive/temp, nor does newperms /mnt/disks/tempdrive/temp make any difference. Any ideas? Suppose I could change Sabnzbd docker to run as root, but hoping there's another way. Thanks

Any ideas on this please?

Would appreciate some help. I've been running kodi library via MySQL for a few years now, with sickchill pushing updates on shows to kodi on a firestick (thats powered on constantly). Want to move to headless kodi (didn't know this existed until recently) but its not working when trying to test connection from sickchill. Steps taken:- 1. Installed kodi-headless from Apps (latest version as I'm using Leia), using port 8085 (as already running sabnzb docker on 8080) , bridge network, mapping Container Path: /config/.kodi to /mnt/user/appdata/kodi/. Copied contents of PC folder \AppData\Roaming\Kodi (which includes \userdata) to /mnt/user/appdata/kodi/, which includes the \userdata\advancedsettings.xml with correct reference to mysql 2. Docker runs ok 3. Tried updating sickchill repointing from Kodi on firestick to new docker container, but test never competes There's mention of making the PUID&PGID for the docker the same as that from the 'data volume directory' but I'm not sure who owns that (assuming root?), and using this instruction 'id dockeruser' does work for me.

Ok thanks, but there are no VM's or dockers running, just plugins. Could one of these be causing the issue?

Doesn't seem to be much logging prior to the crash (reboot at aprox 12:14 today) syslog.txt

Installed latest version on HP N36L that's previously been running OMV for years solidly (so hardware should be fine), but for the past three days the server crashes with hard drive LED permanently on & no IP allocated on router. Connecting to monitor, not responsive - nothing shown. Didn't respond to ctrl+alt+del so had to hard power down the unit. Upon reboot it starts a parity/read check which shows 7760 errors (assume this was form the hard power down as none shown before). After last crash I run the memtest but no issues found. Another post suggested running tail /var/log/syslog -f from console and take picture from screen when crashes, but the screen times out after a while (not the monitor) so even though left video camera recording it captured nothing. I'm keen to move to unraid permanently but need this issue resolved before I can do so. Help would be much appreciated. Let me know if there is anything else I can add. Thanks (Note: At the time of the crash its been copying data over via RSYC from another server, but not sure if this is relevant or not) tower-diagnostics-20210605-0905.zip