Jump to content

dopray

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dopray

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Thank you! I looked inside the appdaemon.yaml file and first tried commenting it out like you suggested. This made the docker launch like you said. After manually adding [myhostip]:5050 to dash_url in appdaemon.yaml I could launch the WebUI as well.
  2. While setting up a Docker for Appdaemon I'm getting the exact same error as @wyleekiot: File "/usr/local/lib/python3.6/site-packages/appdaemon/admain.py", line 82, in run self.rundash = rundash.RunDash(self.AD, loop, self.logger, self.access, **hadashboard) File "/usr/local/lib/python3.6/site-packages/appdaemon/rundash.py", line 130, in __init__ dash_net = url.netloc.split(":") TypeError: a bytes-like object is required, not 'str' No dashboards or config set, just trying to connect to HA. Anyone have an idea what might fix this?
  3. Quick update in case anyone else has similar problems : I tried a different PSU, but got the same errors. Now I've reconnected the old PSU but skipped all the SATA2 ports on the motherboard. Sync is now running and so far so good. Fingers crossed!
  4. They keep increasing each and every time. I've changed cables (one disk to another), bought new cables, bought the new SATA controller, checked power and sata cables. Changed the connections to the motherboard, but they keep showing up and it seems to be hitting all disks so I can't pinpoint it.
  5. Hi, The last few weeks I've been having all sorts of problems. I need to rebuild my parity, but I see a whole bunch of errors on several disks when i try to start this. I've replaced SATA-cables, rechecked them. I bought a new PCI-e SATA controller, but I keep seeing the same problems each time. I've run short SMART reports and those complete without error. This system with the same disks used to run just fine, so now I'm thinking it might be a faulty power supply? Can anyone check my diagnostics and tell me if I'm on the right track or if I need to look elsewhere first/instead. tower-diagnostics-20180728-1008.zip
  6. Memtest had 5 full passes without any errors or weird characters on screen. (no disks attached, 1, 2 , 3 and all 6). I've now been rebuilding for the last 7 hours and all seems stable. No idea what caused this so I'm still worried this might return at any moment but I'll take it. Thank you guys for your advice. Fingers crossed... and happy holidays!
  7. Thanks. I disconnected all power cables to my drives. Weird thing now is that I created another flash drive just to run Memtest. It succesfully completed a pass and has been running for 25 minutes straight without any hiccups. Could this at all be flash drive related? Or would you rather suspect a power problem in this case? Edit: I just started from my unraid flash drive and Memtest also seems to run without problems. So the only changed factor is the fact that all my drives stopped drawing power / are no longer connected. Do I need to look for another power supply or could something else still be causing this?
  8. The only other card in there is a "Promise Pci Sata 300 TX4 Controller Card (4x SATA) [HDCPROSATA300TX4]" No PCIe though. Caps all seem to be in normal condition (as far as I can tell) Buying another piece of RAM certainly should be possible. Next on the list then probably would be a new MB ? Anything I need to/can do to hopefully save my data (as I was rebuilding my 'missing' - drive during the failure)?
  9. Good point: I don't have a syslog, but I can at least give you some info on my system : CPU : Core™ i3-2100 (2x 3100 MHz) HR3I01 MB : H67M (Intel® H67 Express) GRIR02 (on-board GPU) RAM : 4 GB DDR3-1333 (4096 MB) ICIF50 Flash drive : Cruzer 4GB As I only have one piece of RAM removing half is a bit tough ... Anything else I can try to give you guys a clearer picture?
  10. Hi, I've been using my system for quite some years without real trouble, but now I seem to be in kind of a rough period. Yesterday I got a disk read error but it slipped by without me noticing. This morning I was moving a whole bunch of data on my Unraid but all of a sudden I got a message that there was not enough space. When I checked out the GUI my biggest data disk had disappeared. As I've run into trouble with faulty/loose SATA-cables in the past I thought it was just going to be that so I opened up my system and made sure everything was attached securely. However when I tried to reboot the system did not seem to detect my flash drive. I've run into this in the past and sometimes had to reboot several times before it got detected. At the same time my system acts up display-wise. HDMI always seems to output (but I only have a screen downstairs), VGA is about as reliable as my flash drive detection. The moment I attach an HDMI screen , USB flash detection works like it should. So you'd probably think just attach an HDMI screen and you're set? I wish.... Seems like the problem comes from somewhere else. During rebuilding my 'missing' drive I all of a sudden couldn't connect anymore to the GUI, nor ping my server. When I went upstairs to check it out I had all kinds of garbage-characters filling up my VGA-attached screen. I now moved the system downstairs again and attached it to a HDMI-screen. It boots like normal so I decided to run a memory test. I tried it multiple times but each time after a few minutes it gives me a screen like the attached screenshot. Now I've disconnected the flash drive and it booted until I now just have a blinking cursor. This screen stays in perfect 'blinking' condition. Could it be that my flash drive is faulty or do I need to test other stuff out first? Thanks a bundle to anyone who can help me along...!
  11. I tried that, but didn't seem to work. Do I have to put another command in front of it (wait?) so it doesn't load too early or isn't that possible?
  12. Hi all, I have the following question : I'm looking for the best way to run the following command each time my system runs : "ethtool -s eth wol g". If I run this manually I can perfectly WOL the next time but the time after that it has reset to "d". I've looked around the forums and tried several things : - added the command to my go script - tried to add it to the powerdown script (but possible didn't do it in the right place?) - added it to the sleep settings in Dynamix ("to Set WOL options before sleep:" , to "Custom commands before sleep:" and to "Custom commands after wake-up:" Can anyone point me to the best way to go to make sure "g" is activated before every shutdown or can this really only be done by running the command myself manually? Thanks in advance and sorry if I overlooked this somewhere on the forum but there is so much information here (spread over different versions of unRaid / scripts from the past) that I'm having a hard time finding the right solution.
  13. Has this been fixed in the current beta (14) ? I tried to search the forums for more info but this old post was the most relevant recent item i could find on the matter.
  14. dopray

    New Build

    The offer for the 2100 I had my eye on is gone so now i'm thinking about these parts : 760GM-P23 (FX) (AMD 760G) Athlon II X3 450 (3x 3200 MHz) Corsair 4GB DDR3-1333 Kit (4096 MB) any thoughts? I couldn't find the Greenleaf suggested 760GM-P33 but the board seems more or less similar (except a Realtek 8111E on this one)
  15. dopray

    New Build

    I have to buy from European stores so a lot of recommendations aren't even for sale here. I now have my eye on an i3-2100 (already have one of those in my regular desktop so easily replaced if necessary) and the following mobo : MSI B75A-G43 . It has 6 SATA's onboard, onboard video and 2 PCI-e / 3 PCI slots. However it also has the Realtek RTL8111E. Is this still a problem or has this been solved?