lowbiker
-
Posts
11 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by lowbiker
-
-
On 3/17/2018 at 8:34 PM, lionelhutz said:
My ultimate solution was to move to Radarr. Importing existing files does work, along with everything else it does.
Are you really still using the Unplugged CouchPotato plug-in?
If Radarr was any kind of stable I'd love to move to it. Crashes all the time and can't figure out how to recover it without wiping it all and starting over. Hence are back on CouchPotato
-
1 hour ago, Squid said:
I have never had any issues with radarr (or nzbget / sonarr for that matter). System automatically updates every Friday to LSIO's latest image. Curious about one thing though (wild guess of a theory). When you go to the docker tab does it show Advanced View or Basic View. Try switching it to Basic View and then see if you get better longevity out of the containers.
Both the docker tab and the radarr page are both on basic view. I'm running 14 other dockers that all upgrade fine. The only other one I've had to reinstall is Unifi-Video but if i leave it, then it doesn't barf on itself
-
Has anyone had any stability issues with radarr lately? I can upgrade sonarr all day long and it's never broken. But I'm scared to upgrade radarr. Something goes wrong and it just gives me a white screen. And if I don't upgrade it, it eventually breaks anyways and I have to redo it all. I understand it's under development and things go wonky sometimes. But I'm on my 5th re-install. There are only a couple versions of radarr in the store. Which one is the most stable?
-
I'm seeing a lot of these in the syslog. Does it usually point to memory or other hardware issues?
i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
server-diagnostics-20190212-0009.zip
A couple times I've seen my /var/log/atop logs get to 128 megabytes filling up that log partition as well.
-
On 3/3/2018 at 10:57 PM, fryfrog said:
I think `server.log` is where I'd start.
I attached the last hundred lines. Trying to figure out what to make of it. The confusing thing is when I reset everything Friday night it actually did record me once while i was fixing it and I thought i was done. I may have to repeat the process. Checking it this morning.. it's graduated to recording a few things but not everything
Edit: Just as a follow up I finally figured out that it didn't like being pointed at my cache drive for some reason. Didn't think there was enough space. Pointed the recorder to the share on my array and all seems to be working again. Also reverted back to 3.9.0 and the 2nd most recent camera firmware
-
23 minutes ago, fryfrog said:
I assume if you live view the cameras, it works? Or the grid view? Have you checked the logs for errors? What are you passing in for data and video paths?
Yes the live view works fine.. and in grid view as well. Just used the default values for installing the app. I'm going to have to go through the logs. Busy day today with switches falling over at work. Will start with the error log and recording log unless anyone knows better
-
28 minutes ago, fryfrog said:
If the software is running and you see the cameras and their feeds, you should be able to record. What do you mean when you say it doesn't record? Do you set the cameras to always record? Record on motion?
Yes and yes.. Tried both. No recordings are showing up.
-
On 2/26/2018 at 4:29 PM, fryfrog said:
The fix for 3.9.2 is in and a pull request is up, it'd be reasonable to wait and just go to 3.9.2 and they'll be fine.
Last night I reset and downgraded my cameras to next to latest firmware. Ripped out the docker, cleaned out the cruft. Couldn't find an older version of the docker to install so I tried what was available. Upon install the docker re-upgraded my cameras and everything works... but still doesn't record. Is it reasonable to assume we can just wait on a software update for this to be fixed?
-
Anyone else get an error like this?
"Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 114382050000070232 bytes) in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 213"
Data Rebuild?
in General Support
Posted · Edited by lowbiker
Typo
This question is academic.
1. I lost a 6TB drive. It's just dead so I pull it out and it starts being emulated.
2. That feels weird and I have space so I run the Unbalancer to move the data to other free drives
3. I did this a couple times to make sure i got it all.
4. New drive comes in. Also 6 TB. Run the pre-clear. Takes forever
5. I shut down the array. Add the new drive back to the array.
6. Now it's doing a "data rebuild" with over 400,000,000 writes 30% done.
What is it doing? I thought I moved the data off the emulation? What exactly is it rebuilding? What should I have done different?