Jump to content

Teixeira

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Teixeira

  • Rank
    Member
  1. I found the problem to this issue. I have my 'system' share set to cache only, but some data was still on the array. I moved it all to the cache with the 'unbalance' plug in. Now the containers don't become unresponsive anymore when the array goes to shit. The reason i'm still here talking about something that has nothing to do with the mover is that my problem is exactly the same as the original post. The first 5 mins of the import makes the whole array unresponsive, meaning that nothing can be read from it. After 5 mins I gain access to it again but it is noticeably slower (kinda expected). After some time it goes back up to 100% CPU and nothing can be done, until it is done. You said this is probably because of slow drives. I've excluded that one drive that contains all the data, forcing unRAID to write to the next one. Plex still can't play the media that is on the "idle" drive.
  2. I am having a similar issue. I don't think it's related to the mover since my 'media' share doesn't use a cache drive. I use a seperate HDD outside the array for SABnzbd and when Radarr/Sonarr tries to import a file, everything becomes unresponsive (yes, not only plex but all the containers). Same thing happens when i copy a file from my PC to the server. I am aware that writing data to a parity protected array requires CPU power, but not 100% of my 2700X. I thought this was a problem with Radarr / Sonarr (Mono), but then i pinned them both to only 1 core and gave them each 500MB of RAM and this still happened.
  3. So i checked again and the iGPU was selected as primary graphics. Still no /dev/dri My diagnostics are attached. Do you think i can get this working on this chip? steelmountain-diagnostics-20181205-2001.zip
  4. Thanks for the quick response. I'm 99% sure i did that but i'll have to check again. Will report back.
  5. Hello everyone. I Just bought a 9600k and unfortunaly all the settings mentioned above doesn't work for me. "no such directory" on /dev/dri. Is it the CPU that isn't supported yet? It's the same iGPU (UHD630) so i don't see why it shouldn't work
  6. @johnnie.black I did that and its still running after 39 hours. It usually died after 48h. Will report back tomorrow! Still up. I think it's good now boss. Thanks.
  7. For the last couples of weeks i had to restart my server all 2 days because my shares disappears. After a reboot everything is fine again. The first time this happened i noticed that my ram was full. But i haven't seen this happen again since then. My Linux VM stays operational since its on a seperate SSD outside the array. How can prevent this from happening? My second problem is that i can't get the network bridge to work properly. This leads to me not being able to connect directly to my Plex Server (in a VM). In the logs i see those lines: Oct 21 22:29:55 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Down Oct 21 22:29:55 SteelMountain kernel: br0: port 1(eth0) entered disabled state Oct 21 22:30:11 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Oct 21 22:30:11 SteelMountain kernel: br0: port 1(eth0) entered blocking state Oct 21 22:30:11 SteelMountain kernel: br0: port 1(eth0) entered forwarding state Oct 21 22:30:12 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Down Oct 21 22:30:12 SteelMountain kernel: br0: port 1(eth0) entered disabled state Oct 21 22:30:15 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Oct 21 22:30:17 SteelMountain kernel: igb 0000:06:00.0: exceed max 2 second Oct 21 22:30:17 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Down Oct 21 22:30:20 SteelMountain kernel: igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Oct 21 22:30:20 SteelMountain kernel: br0: port 1(eth0) entered blocking state Oct 21 22:30:20 SteelMountain kernel: br0: port 1(eth0) entered forwarding state I should say that this server was running a 4790K before and because i thought the problem was the processor/motherboard i installed my main rigs hardware - 2700X. I don't think it has something to do with the hardware. Can someone help me out? Here are my logfiles **Edit: same problems on 6.3.5
  8. Hi guys. Im a bit late... Is it possible to do that? I dont have a second server to store my files temporarily, so moving it around is the best option for me.