Jump to content

dgtlman

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by dgtlman

  1. 17 minutes ago, wgstarks said:

    /mnt/user/appdata/binhex-qbittorrentvpn/qBittorent/config

     

    Scroll down to [preferences].

     

    16 minutes ago, wgstarks said:

    This is assuming you are using the default location for appdata. If not you’ll need to adjust the path.

     

     

    Ahh.... thank you so much!

     

    Just in case anyone else isn't sure, once in the .../config directory, edit the qBittorrent.conf file. Add the string below to the bottom of the preferences, restart qbittorrent and then log in with adminadmin as the password. After that, you should change the password.

     

    WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

     

  2. On 11/26/2023 at 10:23 AM, nraygun said:

    FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.

     

    Adding this line under [Preferences], in the config file, works, for setting the default password manually to: adminadmin

    WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

     

     

    Maybe i am missing something.... I am assuming the config file is where you edit the docker, but I don't see preferences anywhere. Am I looking in the right space?

  3. Here is the syslog. I also noticed from the monitor that I had hooked up, that the system went down from a kernel panic. Hopefully this log defines what is causing that and the easiest way to resolve this. 

     

    The kernel panic happened on 6/1. I was unable to post this since then. Since then, it captured more of the log. Sorry if this add to the complexity of figuring things out. 

     

    Thanks

    syslog-192.168.1.50.log

  4. Recently, my unraid box has started going off line. I am unsure if it is a hardware or software issue. Additionally, I don't know if it is that the whole system goes down or just the networking. It happens randomly and I haven't been able to determine if it is caused by anything specific. My concern is when this happens, the only solution is to power cycle it which I know isn't good for the health of the data array. 

     

    Today I hooked up a monitor to be able to better determine what is causing this. But additionally, I figured I would post my diagnostics here to see if there is something going on behind the scenes. 

     

    Any insight would be really helpful. 

    unraid-diagnostics-20230531-1133.zip

  5. 1 hour ago, Squid said:

    Also, regarding the slowdowns, you might want to check the what the BIOS has for thermal TDP's.  Vast (ie: nearly every) motherboard manufacturer on the chipsets for the 10th and 11th gen CPUs figured it would be a good idea to do an "inherent" overclock on the CPUs by setting the TDPs to effectively be 4096 Watts and hope that the CPU would throttle itself down to prevent a nuclear accident in the case.  It should be illegal (but isn't).  Set your TDPs in the motherboard to be 65Watts, NOT auto (or 4096W)

     

     

    is thermal TDP the same as:

     

    package power limit1 TDP (watts)

     

    That is what is listed in my gigabyte bios for the z590 Aorus Master. 

  6. 3 minutes ago, Squid said:

    Also, regarding the slowdowns, you might want to check the what the BIOS has for thermal TDP's.  Vast (ie: nearly every) motherboard manufacturer on the chipsets for the 10th and 11th gen CPUs figured it would be a good idea to do an "inherent" overclock on the CPUs by setting the TDPs to effectively be 4096 Watts and hope that the CPU would throttle itself down to prevent a nuclear accident in the case.  It should be illegal (but isn't).  Set your TDPs in the motherboard to be 65Watts, NOT auto (or 4096W)

     

     

     

    Thanks for parsing though this. I appreciate the explanation and the bios setting recommendation. I will make that update and see how it runs after that. Once again thank you!

  7. 1 minute ago, ChatNoir said:

    I would try to stub the device as if to pass it to a VM so it does not load on boot (if I understand that part right). But since I am not that versed in those parts of the OS, maybe try that only if no one has a suggestion that works. :) 

     

    If I understand correctly, in one of my VMs specify that the bluetooth is strictly associated with only that VM and not with Unraid. Correct?

  8. I have a Gigabyte Z590 Aorus Master motherboard. After updating the bios, searching through the the bios settings,  and then scouring the internet; it appears that wifi and bluetooth can not be disabled from the bios. So I am kinda stuck with finding another way to deal with this. 

     

    What should I try next?

  9. This morning I woke up and checked the status on the backup (using MC to usb drive). It had a little over an hour left. After a moment. I reliazed that it actually had stopped and the connection via ssh had been dropped.

     

    After an hour of being patient and troubleshooting, I realized that the entire thing must have locked up as it was not responding via ip or attaching a monitor. I even verified the switch logs, and the port was no longer getting any status back from the ethernet card. So, not that I wanted to, but I did an unclean shut down as that was the only way to get back in. 

     

    On boot up, it looks like the issue of the array not staying corrected has been resolved. I am assuming that this was a mismatch state caused by two instances of the emhttpd running. Now that the second instance is commented out. The GUI seems to be running fine, although it reverted back to the default identification name (tower). This is not the first time this has happened and I am not sure why it keeps doing that. 

     

    Now I need to either determine and resolve what is causing the directory not allowing things to write to it... or re-setup the entire Unraid box from a clean install. 

    tower-diagnostics-20211201-1128.zip

  10. Two weeks ago, our house had several power outages. We have a whole house generator that powers the house automatically 90 seconds after the power goes out. To help bridge the gap, I have a UPS connected to my Unraid box. In addition, I have the Unraid install set up to reboot on power loss and automatically mount the array as soon as it is powered up.

     

    We were out of town for a week and while so, the power went out four times. Which shouldn't have affected Unraid at all. Unfortunately, the battery on the UPS went bad and when the power went out, the Unraid box immediately turned off. (I have since replaced the battery to prevent this from happening again).

     

    Each time it came back online it triggered a parity check and would pass. Except, during the third check it, the power went out again in the middle of the check. This has caused some weird anomalies. For example, I can't write to the plex movies folder. I have run the permission checker (from tools) and it doesn't change things. Also, even though the array is started, the web GUI says it is stopped, which causes dockers to act erratically (including the cloudcommander which I use to manage files and folders).

     

    Fortunately, there are two lucky situations. First, in the past few weeks, Best Buy had 14TB easystore drives on sale. So I had a few of them that I hadn't added into the Unraid yet. Second, midnight commander still works and I have ssh'ed in and backing up everything to the easystore, drives. It is taking a while, but the backup will allow me some breathing room before trying to fix this.

     

    *exhale*

     

    So, I am strongly leaning towards just rebuilding the Unraid box from scratch after backing it all up. This should ensure that all weirdness and problems are gone. There seems to be too many really big issues to put my finger on, and wipe everything and reload. It will take time to do the data shuffle, but in the long run it may actually be the fastest and best option. Any suggestions or recommendations about this would be appreciated.

     

    Second, I want to restore everything the easiest and best way possible. Most of the dockers are pretty straightforward. The one I am not looking forward to is Plex. I have spent a disgusting amount of time customizing the libraries with art and collections. I don't want to lose all the work. I wish there was a clean way to do a database backup and restore. Since there is not, does anyone have a suggestion or tutorial on how to do it without losing all the work I have done on the library?

     

    I have been using using Unraid as my primary NAS for 4 years now without a problem. I am assuming that this is just an anomaly caused by the frequent power cycles that caused the array to stop uncleanly too many times. But then again, that is just an educated guess.

     

    Any advice, tips, assistance.... or even smacks against the back of the head (kidding) would be greatly appreciated.

    iron-diagnostics-20211130-1547.zip

×
×
  • Create New...