• Posts

  • Joined

  • Last visited


  • Gender
  • URL
  • Location
    Portland, Or

pixelgraft's Achievements


Rookie (2/14)



  1. Got it, I think. Changed Plex docker to Bridge, then setup new container ports for all of the Plex required ports. I can access the web gui now, but access from mobile device with Plex app and also from streaming devices (EG: Roku on TVs) seems slower. Sometimes receive the "Not directly connected to server" message.
  2. I've narrowed it down to the dockers causing the IP conflict after some time. My hunch is that it is Plex causing it, but I have no idea why. I have Plex, krusader, and noIP installed as dockers. The raid and the dockers work fine for a day or so, and then (usually in the morning), we discover that we have no internet throughout the house and I have to power down the unraid box to fix it. At the moment, the unraid box is set as dhcp in network settings. I have assigned the unraid box to a specific reserved IP address in my router. I have tried the following: setting unraid with a static IP in unraid network settings and the assigned IP is outside of my router DHCP range. unraid with a dynamic IP in unraid network settings and then updating my router settings with a reserved IP address for the unraid box via the unraid mac address. Attached are screenshots of my docker setups. As a test, I will disable all dockers for a few days and see what occurs. If the network remains up, I will then enable 1 docker and then see what happens after a couple of days. Then repeat, enabling the other 2 dockers I have. I will reply back with updates on the testing, but if anyone has any ideas why the docker(s) would cause this, that would be greatly appreciated.
  3. Completely understand - thank you for the detailed reply. I used to have this feature, but now my ISP Comcast locked that down in the router and forces me to use their silly web interface in the customer portal. I can only setup the "to" port. No longer a from and to. I'll reach out to them.
  4. Having issues connecting to FTP via filezilla or other apps (like iOS FTP photo transfer). I'm using NoIP on my raid box and have a DDNS setup. I've confirmed that my ddns address is resolving into my router. Also confirmed that port 21 is open on my WAN using a port check tool. Someone mentioned in a previous post about not opening port 21, but rather opening a different port, than re-directing that to port 21 on my raid. If I open port xxxx on my router, how do I then specify that I want those requests going to port 21 on my unraid box? Validated via command line on my local machine that the FTP daemon is running by doing ftp 192.xxx.xx.xxx to check that FTP is running on my raid box. I can login with the specified ftpuser name and password and received a code 230 from command line that I was able to get in. My syslog / diagnostics is attached. Thanks in advance for any help! Reason I use FTP is via an iOS app (mebiaFTP) to transfer all media files from our phones into the unraid media library. unraid-diagnostics-20200614-1453.zip
  5. unraid is still crashing my entire network randomly after I have done the below. I'm almost to the point I want to start over with unraid using the guide in this post. I have done the following and none have helped the issue. My entire network connection goes down and once I hard boot the unraid box, everything comes back up. It then repeats randomly - losing network connection and then I have to hard boot it again. reset my router (it's an ARRIS router provided by my ISP Comcast). deleted the network.cfg file in flash/config Changed unraid network settings from fixed IP to DHCP. installed the latest BIOS on the unraid motherboard (ASUSTeK COMPUTER INC. ROG STRIX Z370-E GAMING Version) Attached is my complete diagnostics .zip if anyone can glean anything from that. unraid-diagnostics-20200614-0957.zip
  6. diagnostics attached. One thing I just noticed is that these log errors only start AFTER I start up dockers. For example, starting up Plex docker, or binhex-krusader docker starts doing these logs. unraid-diagnostics-20200614-0957.zip
  7. I've done the below and am still having the logging issues. The only PCI device I have in this box is a 2 port sata card. I do have another identical card I could swap it out for. I've no way of knowing what pci device it's referring to in the error. Would someone be able to tell which device is causing the issue? Log: Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: AER: Multiple Corrected error received: 0000:00:1c.1 Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jun 13 14:33:30 unraid kernel: pcieport 0000:00:1c.1: device [8086:a291] error status/mask=00000001/00002000 What I've done: Updated to the latest bios (motherboard is ASUSTeK COMPUTER INC. ROG STRIX Z370-E) updated the syslinux.config file within the flash > syslinux folder to the below (adding the pci=nommconfto to the append initrd=/bzroot line). Syslinux file: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot pci=nommconfto label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Memtest86+ kernel /memtest
  8. Hi, At times unraid randomly causes a conflicting IP address across the network and my network goes down. I have to hard shut down the unraid box to get the network back up. My unraid IP is being set via my router as a reserved IP I've chosen. Before I had the IP being set via the reserved IP, I had my unraid network.cfg file set as dhcp = no and was specifying the IP in the network.cfg file. The IP conflict issues happens randomly either way I do it. Either by reserved IP or setting the static IP in the network.cfg. Any ideas what may be going on? As a note, I have another open forum post below. I will be looking into this today. I call this out, as I am unsure of the conflicting IP has anything to do with this issue or not.
  9. Hi, My sys log is logging the below and doing it once or twice every second. Any ideas what this is? My NIC going bad? I have attached my entire log file. Jun 9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: AER: Corrected error received: 0000:00:1c.6 Jun 9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Jun 9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: device [8086:a296] error status/mask=00000001/00002000 Jun 9 08:25:48 unraid kernel: pcieport 0000:00:1c.6: [ 0] RxErr (First) unraid-syslog-20200609-1526.zip
  10. Trying to rotate photos in windows explorer via mapped network shares from my unraid. Any ideas why when I right click on any photo that I get the below? "you cannot rotate this image. The file might be in use or open in another program, or the file or folder might be read only."
  11. This, exactly. Parity WAS NOT valid. Do the new config again, but DON'T check the "parity is valid". You need to build parity for the current set of drives, then check it when it is finished building. Thank you. I've cancelled the current check, done the new config again, started the array WITHOUT checking the "parity is valid" box and the parity check is underway again. It's ~ 35 mb / sec now, but that's about what it was when I began the check this AM. I'll keep an eye on it. Thank you again.
  12. Attaching my diagnostics file. Currently getting around 9 mb/sec on a 4TB parity sync which says it'll take 4 days to complete. A couple of days ago, I moved many files from a 2TB WD green drive via midnight commander to other drives on the array. I then removed that drive, did a "new config" and checked the "parity is valid". Any thoughts why this sync is SO SLOW and why I currently see 45 million + sync corrections? I just got 2 new WD 4TB RED drives that are pre-cleared and ready to go into the array after I do this parity sync. unraid-diagnostics-20160418-1518.zip
  13. I currently have 1 WD 4TB RED as my parity. All my data drives are 2TB WD Caviar Greens. I'll be ordering 2 more 4TB REDs to replace the greens so that I can get the greens OUT of the NAS entirely. With that in mind, do I have this process correct below? pre-clear new 4TB RED drives stop the array add new drives into the array start the array format new drives and expand the array use midnight commander via telnet putty to move files off of the smaller discs and onto the new 4TB REDs once all data is copied off 2TB Greens, stop the array remove 2TB Greens from from the array Go to Tools > New Config > Apply remove 2TB greens from tower (will pre-clear these first to ensure all clear) start the array do parity sync DONE - rejoice & do happy dance?