optiman

Members
  • Posts

    1071
  • Joined

  • Last visited

Everything posted by optiman

  1. Got it, thanks again. I'm ready to kick this off. I'll report back once finished. Cheers!
  2. Thanks for the info and link. I only want to remove the old disk8 (which will still have all the files on it, as I only COPY the data). I don't care about zeroing it, unless that is necessary. I can just delete the files, or perhaps just reformat disk8 to clear. My goal is to remove disk8 and keep parity. I will just preclear the old disk8 later on, and save it as a spare. In the shrink array instructions, why do I need steps 7 and 8? If I have already deleted all files, the drive should be empty and parity good. Make sure that the drive you are removing has been removed from any inclusions or exclusions for all shares, including in the global share settings. Make sure the array is started, with the drive assigned and mounted. Make sure you have a copy of your array assignments, especially the parity drive. You may need this list if the "Retain current configuration" option doesn't work correctly. It is highly recommended to turn on reconstruct write, as the write method (sometimes called 'Turbo write'). With it on, the script can run 2 to 3 times as fast, saving hours! In Settings -> Disk Settings, change Tunable (md_write_method) to reconstruct write. Make sure ALL data has been copied off the drive; drive MUST be completely empty for the clearing script to work. Double check that there are no files or folders left on the drive. Note: one quick way to clean a drive is reformat it! (once you're sure nothing of importance is left of course!) Create a single folder on the drive with the name clear-me - exactly 7 lowercase letters and one hyphen Run the clear an array drive script from the User Scripts plugin (or run it standalone, at a command prompt). If you prepared the drive correctly, it will completely and safely zero out the drive. If you didn't prepare the drive correctly, the script will refuse to run, in order to avoid any chance of data loss. If the script refuses to run, indicating it did not find a marked and empty drive, then very likely there are still files on your drive. Check for hidden files. ALL files must be removed! Clearing takes a loooong time! Progress info will be displayed, in 6.2 or later. Prior to 6.2, nothing will show until it finishes. If running in User Scripts, the browser tab will hang for the entire clearing process. While the script is running, the Main screen may show invalid numbers for the drive, ignore them. Important! Do not try to access the drive, at all! When the clearing is complete, stop the array Go to Tools then New Config Click on the Retain current configuration box (says None at first), click on the box for All, then click on close Click on the box for Yes I want to do this, then click Apply then Done Return to the Main page, and check all assignments. If any are missing, correct them. Unassign the drive(s) you are removing. Double check all of the assignments, especially the parity drive(s)! Click the check box for Parity is already valid, make sure it is checked! Start the array! Click the Start button then the Proceed button (on the warning popup that will pop up) Parity should still be valid, however it's highly recommended to do a Parity Check Thanks again for your help. I'm trying to do good planning so I don't f*ck this up.
  3. Great, thanks guys! Kids are watching a movie right now, but I will reboot into Safe mode later today and start the conversion. I think I will just erase or clear the contents of disk8 at the end to keep parity. For the New Config - It's been a while since I did that. I stop the array, remove disk8, move disk 9 to slot 8, then do the New Config and tick the box to keep existing configuration, then start array - is that correct?
  4. ok good, so I can leave disk9 as is at the end, even though I won't have a disk8. What about my dual Parity drives? Is that a issue? I guess the rest of my instructions / Plan look ok?
  5. I have a new drive ready to go and I have created my plan using the feedback from you guys. That said, before I start, I am sharing my plan so you can tell me if I am missing anything. I do have a couple of questions. I have dual Parity drives. Do I need to do anything extra, like remove the 2nd parity drive before I start and put it back at the end? I have 8 data drives to convert, all of them are 6TB drives. I have added a 8TB drive (disk9), which will remain in the array when conversion is completed. This means I will have a extra 6TB drive at the end of this procedure. So the very last step for me is to remove the empty disk8 drive. I don’t have any more room in my case to add another data drive, so one must be removed at the end of this process. Because I am on Unraid 6.3.5, I am using the instructions (with help from this thread) at https://lime-technology.com/wiki/File_System_Conversion Share based, no inclusions, preserving parity *Use physical server Console *No New Config needed for this process *Boot into SAFE mode, no plugins and no dockers running, no mover 1. Start copying from console – from disk1 to the new XFS disk9 rsync -arv /mnt/disk1/ /mnt/disk9>/boot/copy.txt 2. After copy completes, run Verify and check output file (if successful there should be no files listed) rsync -narcv /mnt/disk1/ /mnt/disk9>/boot/verify.txt 3. Stop array, change to XFS format type on empty disk1, start array, verify only empty disk wants formatting, format disk. 4. COPY (not move) next reiserfs disk to freshly formatted XFS disk, verify copy, stop array, change desired format type of the disk you just copied from, start array, verify only one disk wants formatted. Repeat until all drives are converted. Copy Plan: disk1 to disk9 disk2 to disk1 disk3 to disk 2 disk4 to disk3 disk5 to disk4 disk6 to disk5 disk7 to disk6 disk8 to disk7 disk8 is now empty and can be removed from the array. After removing the old 6TB disk8, do I need to move disk9 to disk8 slot or does it matter? Thanks!
  6. thanks for the additional info. I'll get started as soon as my new drive is precleared.
  7. ok, I will use rsync. I'll boot into SAFE mode and run the two rsync commands at the console Thanks for the rsync commands jonathanm! So run the first rsync command to copy. When that one finishes, then run the second rync command to verify and confirm output file has no files listed. Preclearing the new drive now Thanks!
  8. I have no share inclusions nor exclusions and I don't care where the data ends up. All 8 of my data drives are 6TB. I have a spare 8TB that I want to use for this process and it can remain in my array afterwards. I will just have a spare 6TB at the end of the conversion. In your steps, would I still need to do the New Config part? I read it's best to boot into SAFE mode, so no plugins, no docker, no Mover, etc. I don't care if my server is offline the entire time. I'm more interested in the fastest process that keeps Parity. I was planning to use log into my server console and use MC to "copy" and verify, instead of the command line option. As long as I'm copying from disk share to disk share, then I this process should work. Do you agree this is ok, or should I reconsider using unbalance or the command line options?
  9. Thanks guys, point well made. I just wanted to be sure there wasn't another issue going on here that I should address first. I have new drives to preclear and I'll start working on the plan to convert. I assume the process hasn't changed much from last year, unless somebody has created an even easier process. That is why I deferred this task, as it seems it would take a long time. I guess it's time to just getter done. Thanks
  10. Thanks for the replies guys. As pwm points out, I too have not had any reiserfs issues, until recent release updates. Does the htop information agree that is the cause? How can I confirm my issue is for sure connected to reiserfs and converting my drives will solve this issue? Thanks again and cheers!
  11. I have been running into a issue where for some reason my server will become unresponsive. This can happen at any time it seems with no logic as to what is causing it. When this happens, I’m unable to do much at all. I have not made any resent changes to hardware or apps (plugins and dockers). All of that said, I have suspicion that the Mover may be involved. It was running almost every time that my server has become unresponsive. I’m running Unraid Pro 6.3.5. My signature has current hardware specs. I only run two Docker containers, sabnzbd and sickrage. For plugins, I have attached a screenshot to show the plugins installed. This issue started back with unraid 6.2 and happens every 2 or 3 weeks. The webgui dashboard shows that my cpu and memory are barely being used at all during normal operations. I also have green balls on all drives and the syslog doesn’t show any thing that helps me identify the cause. When this occurs the following happens: - SMB shares become unresponsive, no access - Webgui unresponsive, even on the server console - Command line commands do not execute, Powerdown, Shutdown, etc will not run - CPU goes to 100% - A cold restart is the only way to shutdown or reboot the server. This caused a Parity Check to start, which in most cases has zero errors. - If a manual copy is in process (or the Mover is running) then the active or current directory will become inaccessible. The only way I can get back into that directory is to use the “chmod -R 777”. - HTOP shows process that is eating up cpu, something about a “shfs error noatime.big_writes.allow only”. I’ve had no luck searching for forums. I am unable to KILL this process. What still works when this happens; - I can putty or use server console to login to the command line, although can’t do much. - I can copy the syslog to flash drive. - I can logout and login to the sever console, but the webgui will not come up, just hangs - Docker containers continue to run normal So far I have used the Server Console to view HTOP and that is how I know the cpu is at 100%. It shows a process that I do not recognize or understand, see attached screenshot of HTOP. I cannot KILL the process, not using htop and not using command line. The system will simple ignore the commands. I also tried to just leave the server alone and see if it would recover, no luck. After 3 days it was still screwed up and unresponsive. I’m still using reiserfs (I need to convert this when I have time) so I ran file system checks and reviewed SMART data on all drives - no errors. For my cache pool (btrfs) I ran the SCRUB command. I also ran memtest – no issues. After a fresh reboot I’m able to run tower-diagnostics and I can PM that and my Syslog files to LT support if it helps. This WILL happen again and I’m concerned with having to do a COLD restart. Because I’m unable to KILL the process that is pushing the cpu to 100%, it leaves no option but to turn off the power each time this happens – NOT GOOD. My main question is what can I do the next time this happens to help me identify what is causing this? Please help if you can. Thanks!
  12. I have both dockers up and running now, sabnzbd and sickrage (binhex-sickrage). I have installed the nzbtomedia script and configured it from scratch - really started over. Now everything is working again, except that I get a script error in sabnzbd, which means it shows the download as failed. However, the download has not failed and sickrage finds files and even moves them into my main show directory. The other thing I noticed is that the downloads that actually fail, are never added to Sickrage Manage Failed Downloads section. Here is a nzbtomedia log file for a download that worked just fine, and the show has been fully added without any issues. However, sabnzb shows it as a failed download on the main screen. [14:29:19] [INFO]::MAIN: Loading config from [/nzbToMedia/autoProcessMedia.cfg] [14:29:19] [INFO]::MAIN: Checking database structure... [14:29:19] [INFO]::MAIN: Checking if source needs an update [14:29:19] [ERROR]::MAIN: Unknown current version number, don't know if we should update or not [14:29:19] [INFO]::MAIN: nzbToMedia Version:11.03 Branch:master (Linux 4.9.30-unRAID) [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: ## ..::[nzbToMedia.pyc]::.. ## [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: Script triggered from SABnzbd [14:29:19] [INFO]::MAIN: Auto-detected SECTION:SickBeard [14:29:19] [INFO]::MAIN: Calling SickBeard:tv to post-process:Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.nzb [14:29:19] [INFO]::MAIN: SickBeard:tv fork set to sickrage [14:29:19] [INFO]::MAIN: FLATTEN: Flattening directory: /downloads/complete/tv/Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot [14:29:20] [INFO]::TRANSCODER: Checking [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] for corruption, please stand by ... [14:29:20] [INFO]::TRANSCODER: SUCCESS: [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] has no corruption. [14:29:20] [POSTPROCESS]::SICKBEARD: SUCCESS: The download succeeded, sending a post-process request [14:29:22] [POSTPROCESS]::SICKBEARD: Unable to figure out what folder to process. If your downloader and SickRage aren't on the same PC make sure you fill out your TV download dir in the config. [14:29:22] [ERROR]::MAIN: A problem was reported in the /nzbToMedia/nzbToSickBeard.py script. SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.! I don't know what the error code means, or why I'm now getting the message about Unable to figure out...... Both Dockers are on the same box and I have configured Categories in sabnzbd. I'm running the latest version and I have Unraid 6.3.5
  13. ok, thank you. I'll try the unraid general support.
  14. Hello binhex,

     

    Are you still actively supporting your docker containers?  I have posted in two threads looking for your support with no response.

     

    [SOLVED] SickRage Convert - Having trouble installing nzbtomedia Script

     

    [Support] binhex - SickRage

     

    Please respond if you are still with us.

  15. So is this thread and support still active? I'm having a nzbtomedia issue and I'm looking for the best thread to post in for help. Below is what I posted in another thread, but got no help. I have both dockers up and running now, sabnzbd and sickrage (binhex-sickrage). I have installed the nzbtomedia script and configured it from scratch - really started over. Now everything is working again, except that I get a script error in sabnzbd, which means it shows the download as failed. However, the download has not failed and sickrage finds files and even moves them into my main show directory. The other thing I noticed is that the downloads that actually fail, are never added to Sickrage Manage Failed Downloads section. Here is a nzbtomedia log file for a download that worked just fine, and the show has been fully added without any issues. However, sabnzb shows it as a failed download on the main screen. [14:29:19] [INFO]::MAIN: Loading config from [/nzbToMedia/autoProcessMedia.cfg] [14:29:19] [INFO]::MAIN: Checking database structure... [14:29:19] [INFO]::MAIN: Checking if source needs an update [14:29:19] [ERROR]::MAIN: Unknown current version number, don't know if we should update or not [14:29:19] [INFO]::MAIN: nzbToMedia Version:11.03 Branch:master (Linux 4.9.30-unRAID) [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: ## ..::[nzbToMedia.pyc]::.. ## [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: Script triggered from SABnzbd [14:29:19] [INFO]::MAIN: Auto-detected SECTION:SickBeard [14:29:19] [INFO]::MAIN: Calling SickBeard:tv to post-process:Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.nzb [14:29:19] [INFO]::MAIN: SickBeard:tv fork set to sickrage [14:29:19] [INFO]::MAIN: FLATTEN: Flattening directory: /downloads/complete/tv/Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot [14:29:20] [INFO]::TRANSCODER: Checking [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] for corruption, please stand by ... [14:29:20] [INFO]::TRANSCODER: SUCCESS: [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] has no corruption. [14:29:20] [POSTPROCESS]::SICKBEARD: SUCCESS: The download succeeded, sending a post-process request [14:29:22] [POSTPROCESS]::SICKBEARD: Unable to figure out what folder to process. If your downloader and SickRage aren't on the same PC make sure you fill out your TV download dir in the config. [14:29:22] [ERROR]::MAIN: A problem was reported in the /nzbToMedia/nzbToSickBeard.py script. SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.! I don't know what the error code means, or why I'm now getting the message about Unable to figure out...... Both Dockers are on the same box and I have configured Categories in sabnzbd. I'm running the latest version and I have Unraid 6.3.5 Is this the best thread to get support for this issue?
  16. hey everyone, I'm having a nzbtomedia issue and I'm looking for the best thread to post in for help. Below is what I posted in another thread, but got no help. I have both dockers up and running now, sabnzbd and sickrage (binhex-sickrage). I have installed the nzbtomedia script and configured it from scratch - really started over. Now everything is working again, except that I get a script error in sabnzbd, which means it shows the download as failed. However, the download has not failed and sickrage finds files and even moves them into my main show directory. The other thing I noticed is that the downloads that actually fail, are never added to Sickrage Manage Failed Downloads section. Here is a nzbtomedia log file for a download that worked just fine, and the show has been fully added without any issues. However, sabnzb shows it as a failed download on the main screen. [14:29:19] [INFO]::MAIN: Loading config from [/nzbToMedia/autoProcessMedia.cfg] [14:29:19] [INFO]::MAIN: Checking database structure... [14:29:19] [INFO]::MAIN: Checking if source needs an update [14:29:19] [ERROR]::MAIN: Unknown current version number, don't know if we should update or not [14:29:19] [INFO]::MAIN: nzbToMedia Version:11.03 Branch:master (Linux 4.9.30-unRAID) [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: ## ..::[nzbToMedia.pyc]::.. ## [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: Script triggered from SABnzbd [14:29:19] [INFO]::MAIN: Auto-detected SECTION:SickBeard [14:29:19] [INFO]::MAIN: Calling SickBeard:tv to post-process:Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.nzb [14:29:19] [INFO]::MAIN: SickBeard:tv fork set to sickrage [14:29:19] [INFO]::MAIN: FLATTEN: Flattening directory: /downloads/complete/tv/Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot [14:29:20] [INFO]::TRANSCODER: Checking [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] for corruption, please stand by ... [14:29:20] [INFO]::TRANSCODER: SUCCESS: [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] has no corruption. [14:29:20] [POSTPROCESS]::SICKBEARD: SUCCESS: The download succeeded, sending a post-process request [14:29:22] [POSTPROCESS]::SICKBEARD: Unable to figure out what folder to process. If your downloader and SickRage aren't on the same PC make sure you fill out your TV download dir in the config. [14:29:22] [ERROR]::MAIN: A problem was reported in the /nzbToMedia/nzbToSickBeard.py script. SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.! I don't know what the error code means, or why I'm now getting the message about Unable to figure out...... Both Dockers are on the same box and I have configured Categories in sabnzbd. I'm running the latest version and I have Unraid 6.3.5 Is this the best thread to get support for this issue?
  17. Hello everyone - I have both dockers up and running now, sabnzbd and sickrage (binhex-sickrage). I have installed the nzbtomedia script and configured it from scratch - really started over. Now everything is working again, except that I get a script error in sabnzbd, which means it shows the download as failed. However, the download has not failed and sickrage finds files and even moves them into my main show directory. The other thing I noticed is that the downloads that actually fail, are never added to Sickrage Manage Failed Downloads section. Here is a nzbtomedia log file for a download that worked just fine, and the show has been fully added without any issues. However, sabnzb shows it as a failed download on the main screen. [14:29:19] [INFO]::MAIN: Loading config from [/nzbToMedia/autoProcessMedia.cfg] [14:29:19] [INFO]::MAIN: Checking database structure... [14:29:19] [INFO]::MAIN: Checking if source needs an update [14:29:19] [ERROR]::MAIN: Unknown current version number, don't know if we should update or not [14:29:19] [INFO]::MAIN: nzbToMedia Version:11.03 Branch:master (Linux 4.9.30-unRAID) [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: ## ..::[nzbToMedia.pyc]::.. ## [14:29:19] [INFO]::MAIN: ######################################################### [14:29:19] [INFO]::MAIN: Script triggered from SABnzbd [14:29:19] [INFO]::MAIN: Auto-detected SECTION:SickBeard [14:29:19] [INFO]::MAIN: Calling SickBeard:tv to post-process:Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.nzb [14:29:19] [INFO]::MAIN: SickBeard:tv fork set to sickrage [14:29:19] [INFO]::MAIN: FLATTEN: Flattening directory: /downloads/complete/tv/Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot [14:29:20] [INFO]::TRANSCODER: Checking [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] for corruption, please stand by ... [14:29:20] [INFO]::TRANSCODER: SUCCESS: [Outlander.S03E03.All.Debts.Paid.1080p.AMZN.WEBRip.DDP5.1.x264-NTb-postbot.mkv] has no corruption. [14:29:20] [POSTPROCESS]::SICKBEARD: SUCCESS: The download succeeded, sending a post-process request [14:29:22] [POSTPROCESS]::SICKBEARD: Unable to figure out what folder to process. If your downloader and SickRage aren't on the same PC make sure you fill out your TV download dir in the config. [14:29:22] [ERROR]::MAIN: A problem was reported in the /nzbToMedia/nzbToSickBeard.py script. SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.! I don't know what the error code means, or why I'm now getting the message about Unable to figure out...... Both Dockers are on the same box and I have configured Categories in sabnzbd. I'm running the latest version and I have Unraid 6.3.5 Is this the best thread to get support for this issue? Or should I be looking for a nzbtomedia support thread?
  18. I installed this version during the false DMCA takedown request. I see this note in SR News section; 2017-08-05 Our main repository on Github SickRage/SickRage is now available. If you installed SickRage using a mirror of our repository, or switched your installation to get updates from a mirror, please make sure that you're back on the main repo URL in order to be able to receive future updates. Instructions are to: Stop SickRage, SSH(Linux)/CMD(Windows) and enter SickRage folder git remote set-url origin https://github.com/SickRage/SickRage.git git fetch origin git checkout master git branch -u origin/master git reset --hard origin/master git pull After stopping SR and SSH, changed to the SR folder and get the following error: -bash: git: command not found Is this a path issue or do I need to install something? With this being a Docker, do I even need to follow the above instructions? Or will the Docker Updates take care of this for me?
  19. I'm seeing this in my sr log after telling it to do a Mass Update, rescan and update: This episode showname - S01E05 has no name on theTVDB. Setting to an empty string Seems it only does this for some shows, others seem to update just fine. I'm running the latest version of unraid and sr docker and everything seems to be working fine, no errors in log. I also have a separate issue that I see in sabnzbd. I'm using the nzbtomedia script and it was working find for over a year. Now in sabnzbd, it shows added by sickrage as failled downloads However, it downloads fine and the script runs and even moves the movie file to the correct folder. Therefore I'm not sure why sabnzbd is showing a sickbeard.py script error when the nzbtomedia scriptruns. SICKBEARD: Unable to figure out what folder to process. If your downloader and SickRage aren't on the same PC make sure you fill out your TV download dir in the config. [19:48:30] [ERROR]::MAIN: A problem was reported in the /config/nzbToMedia/nzbToSickBeard.py script. SickBeard: Failed to post-process - Returned log from SickBeard was not as expected.!
  20. Update: the sickrage docker install from linuxserver is broken. The errors have something to do with the source of the downloads. CHECKVERSION :: Unable to contact github, can't check for update: GithubException() I tried the binhex one and it installed just fine, no errors at all. I then copied over my config.ini and the sickbeard.db and sickbeard.db.v0, v43, and v44 files from my previous sickrage backup. Restarted docker and sickrage came right up with all my previous settings. Seems to be ok now. I would like to know what happened. WTF?
  21. ok, I guess I have more issues. I can install and it says it was sucessful, however it does not write any files into my app/sickarage folder and I get several errors saying files does not exist. I then removed SR altogether. My sys log shows this, Jul 28 12:59:46 Tower root: Warning: file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 146 Jul 28 12:59:46 Tower root: Jul 28 12:59:46 Tower root: Warning: file_get_contents(https://microsoft/windowsservercore): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 146 Jul 28 12:59:50 Tower root: Updating info... Done. Jul 28 12:59:50 Tower emhttp: shcmd (102): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 |& logger Jul 28 12:59:50 Tower kernel: BTRFS: device fsid 42e33d3a-393f-44fa-8bb1-738501d22b22 devid 1 transid 255 /dev/loop1 Jul 28 12:59:50 Tower kernel: BTRFS info (device loop1): disk space caching is enabled Jul 28 12:59:50 Tower kernel: BTRFS info (device loop1): has skinny extents Jul 28 12:59:50 Tower root: Resize '/etc/libvirt' of 'max' Jul 28 12:59:50 Tower kernel: BTRFS info (device loop1): new size for /dev/loop1 is 1073741824 Jul 28 12:59:50 Tower emhttp: shcmd (105): /etc/rc.d/rc.libvirt start |& logger Jul 28 12:59:50 Tower root: Starting virtlockd... Jul 28 12:59:50 Tower root: Starting virtlogd... Jul 28 12:59:50 Tower root: sed: can't read /etc/libvirt/qemu/*.xml: No such file or directory Jul 28 12:59:50 Tower root: sed: can't read /etc/libvirt/qemu/*.xml: No such file or directory Jul 28 12:59:50 Tower root: Starting libvirtd... Jul 28 12:59:50 Tower kernel: tun: Universal TUN/TAP device driver, 1.6 Jul 28 12:59:50 Tower kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Jul 28 12:59:50 Tower emhttp: nothing to sync Jul 28 12:59:51 Tower kernel: Ebtables v2.0 registered Jul 28 12:59:51 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Jul 28 12:59:51 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state Jul 28 12:59:51 Tower kernel: device virbr0-nic entered promiscuous mode Jul 28 12:59:51 Tower avahi-daemon[14723]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jul 28 12:59:51 Tower avahi-daemon[14723]: New relevant interface virbr0.IPv4 for mDNS. Jul 28 12:59:51 Tower avahi-daemon[14723]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jul 28 12:59:51 Tower kernel: virbr0: port 1(virbr0-nic) entered blocking state Jul 28 12:59:51 Tower kernel: virbr0: port 1(virbr0-nic) entered listening state Jul 28 12:59:51 Tower dnsmasq[16275]: started, version 2.76 cachesize 150 Jul 28 12:59:51 Tower dnsmasq[16275]: compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify Jul 28 12:59:51 Tower dnsmasq-dhcp[16275]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Jul 28 12:59:51 Tower dnsmasq-dhcp[16275]: DHCP, sockets bound exclusively to interface virbr0 Jul 28 12:59:51 Tower dnsmasq[16275]: reading /etc/resolv.conf Jul 28 12:59:51 Tower dnsmasq[16275]: using nameserver 10.11.79.190#53 Jul 28 12:59:51 Tower dnsmasq[16275]: read /etc/hosts - 2 addresses Jul 28 12:59:51 Tower dnsmasq[16275]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Jul 28 12:59:51 Tower dnsmasq-dhcp[16275]: read /var/lib/libvirt/dnsmasq/default.hostsfile Jul 28 12:59:51 Tower kernel: virbr0: port 1(virbr0-nic) entered disabled state I removed sickrage completely and rebooted server. I did a new sickrage install again and I get the follow errors in my sickrage log, in addition to the above errors in my sys log. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.[s6-init] ensuring user provided files have correct perms...exited 0.[fix-attrs.d] applying ownership & permissions fixes...[fix-attrs.d] done.[cont-init.d] executing container initialization scripts...[cont-init.d] 10-adduser: executing...-------------------------------------_ _ _| |___| (_) ___| / __| | |/ _ \| \__ \ | | (_) ||_|___/ |_|\___/|_|Brought to you by linuxserver.ioWe gratefully accept donations at:https://www.linuxserver.io/donations/-------------------------------------GID/UID-------------------------------------User uid: 99User gid: 100-------------------------------------[cont-init.d] 10-adduser: exited 0.[cont-init.d] 30-install: executing...Cloning into '/app/sickrage'...fatal: could not read Username for 'https://github.com': No such device or address[cont-init.d] 30-install: exited 0.[cont-init.d] done.[services.d] starting services[services.d] done.python: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directorypython: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directorypython: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directorypython: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directorypython: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directorypython: can't open file '/app/sickrage/SickBeard.py': [Errno 2] No such file or directory Sickrage was working fine for a year and there have been no changes and no other issues with other Dockers. Some of these errors may be related to VM, as I was playing with that a few weeks ago. That said, sickrage was working as of last week, so not sure this is related at all. I have now disabled VM completely. Any ideas?
  22. ah, ok thanks. Installing now. I still would like to use my previous config settings if possible so I don't have to reconfig everything. Do you know how or which files I need, or can I just install in the same dir?
  23. I didn't find isio version. I did find linuxserver Looks like most selected that one. Do you still recommend the binhex version over the linuxserver one? Setting up the initial docker settings is easy, but is there a way to keep the sickrage settings? Perhaps there is a config file I can copy so I don't have to configure all over again? I cannot get into my existing sickrage because it won't start, so I can't even take screen shots of my settings. I set this up a while back so don't recall all the settings I used. If I install the new one in the same directories, will it use the existing config files? Thanks!
  24. Ah, thanks for that information, I was not aware. That sucks, as now I have reconfigure all that crap again.