guyonphone

Ram Tested Good. My array is rebuilding right now, what steps should I take next?

My array is in a degraded status right now because I was upgrading a drive from a 6tb to a 14tb. This error occurred during the rebuild process. I will do as you ask, i appreciate the help

I have launched Memtest on the machine with a usb drive with just memtest86+! on it. Ill report back on the memory test status. If anyone is good enough to interpret my logs and see perhaps what is wrong I would truly appreciate it

Hello, I have had some issues recently on and off with my server with XFS corruption on my cache drive. I repair the corruption with xfs_repair -v for the drive and then the issue comes back a week later. I just replaced a drive and now I am having some strange issues I don't know how to solve. But are not xfs corruption on the cache drive. It's showing a problem with md19 which is a drive im trying to replace. Please see my attached diagnostic logs. Previous post of issues: unraid-diagnostics-20200520-1051.zip I decided it would be a good idea to run memtest. However when I choose that from the UNRAID boot menu, it imediately reboots my server. I am unable to load Memtest

It looks like I am still having problems, going to try the suggestion found here: https://forums.unraid.net/topic/66749-xfs-file-system-corruption-safest-way-to-fix/ Actually, I don't know which device is having the xfs problem. md5 is a reiserfs disk. I unfortunately have a mix of xfs and reiserfs. Need help on what to do next. Going to attach diagnostics. Update: I think it's my nvme cache drive which is having issues. This is a bummer. Going to see if I can repair, but I think the drive might be having issues itself. I think my drive overheated After running a repair it appears as though my issues have been solved

Hello, My server frooze on me. I was able to pull the syslog, see attached. I rebooted the server but Unraid woudln't load the gui. I ended up pulling the USB drive and putting it into a windows computer to repair it. After that I was able to boot the server and it appears to be running fine now. Logs say that device md5 has corruption, i'm interested in knowing if I should do anything to check the health of the server. Syslog https://www.dropbox.com/s/mmmnz32pmqhzl9y/syslog.txt?dl=0

I had the same issue as you, I also had to update my ovpn file from the console. Something is clearly wrong with the docker.

Ah! Shoot, yes, you are right. I did change my MTU setting, to Jumbo frames a while back! I am using 10 gigabit so it's really been helping the speeds, and so far there hadn't been any negative consequences. I take it that's the cause? The thing that get's me here, MTU is Layer 2, I have a firewall. So when unRaid sends packets to my firewall, the MTU size is 9000, but the firewall should be tearing down those ethernet frames and rebuilding them to send to the cable modem at 1500 MTU with it's mac address, and in return the MTU size should be 1500 from the modem to firewall to unRAID on the return path. I guess I don't exactly get why this is hanging up this plugin. unRAID otherwise has perfectly fine access to the internet. Thanks!

Not that I can tell, or am aware of. I can browse to https://lsio.ams3.digitaloceanspaces.com/ in a browser and I get an XML page. So I don't believe I am being blocked.

I do have a piHole, and I did see some others having issues with that, but... I checked the query log, and refreshed after clicking on the plugin, and don't see the piHole blocking anything from "*digitalopenspaces.com". My unraid network settings, are not set to use the piHole for DNS. I have unRaid set to use 1.1.1.1 I disabled the piHole for 5 minutes, and tried, and had the same issue.

Hello, I have been using this plugin for a while now, and it's always worked great until unRaid 6.8.0. I want to upgrade to 6.8.2, however when I open the plugin, it just sits at "Updating Available Builds" and never progresses. unraid-syslog-20200216-2053.zip

Hello, I am interested in using the following script with this docker container: Plex Autoscan I am concerned that if I go through the install and configuration, that it will just be overwritten the next time the docker is updated. Is there a way for me to do this? Thanks

Having issues with Plex Loading after upgrading to newest version: Docker appears to be running, but when I visit the URL via a browser, I just get an empty white page and in chrome the spinning circle in the tab. Tried firefox and that also failed. False alarm, rebooted my local machine and this resolved my issue. Kinda weird, but I'm happy it fixed it.

I think I found the answer to my problems, it just took the right google keywords. https://wiki.unraid.net/Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily Gonna try this, wish me luck.

Hello! On the 1st of the month I ran a parity check which completed with no errors. Today I replaced my existing 12TB Parity Drive with a 14TB Parity drive, and started a rebuild. Wouldn't you know about 5 min into rebuilding my parity, Disk 5 is now showing a sector problem and 165 errors. I stopped the parity rebuild. Powered down the system, took out the 14TB Drive, and put my 12TB drive with valid parity back into the system, the system is not giving me the checkbox to mark Parity as valid, even though I know it is with this 12tb Parity drive. Because of this, I have not yet started the array. What is the best way to tell unraid that parity is valid again, so that I can replace my disk 5 first, before proceeding with increasing the size of my parity drive later? Don't want to loose any data. Thanks

I do, but that shouldn't be an issue right? Why is Sabnzbd reporting the array free space wrong?

Hello, I have Unraid 6.6.6 I have Sabnzbd 2.3.5 It is reporting incorrect Values for Free Space. Any ideas on how to correct? Thanks

<Redacted> Made a mistake an posted in wrong place

Hello, I am interested in using "Lock for Plex" https://forestfirefly.github.io/lockforplex/ I have installed the plugin but I get errors during the installation of the install.sh script because the docker doesn't seem to be to keen on the use of sudo. I tried removing the sudo commands from the install.sh script, but that didn't seem to resolve the issue either. The plugin is available in plex but the locking just doesn't appear to work. Additionally the file wants to restart the service "plexmediaserver" but that doesn't appear to work inside the docker, as it appears some other modification was made, and I don't know enough linux to determine what that is. Here is the contents of the install.sh script I am trying to run. #!/bin/bash # Init FILE="/tmp/out.$$" GREP="/bin/grep" #.... # Make sure only root can run our script if [[ $EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi cd "/config/Library/Application Support/Plex Media Server/Plug-ins" sudo chown -R plex:plex Lock_for_Plex.bundle cd "/config/Library/Application Support/Plex Media Server/Plug-ins/Lock_for_Plex.bundle/Contents/Resources/lock_support/" sudo a+x lock.sh sudo a+x unlock.sh sudo a+x sqlite3 service plexmediaserver restart Any help is appreciated.

Hello hurricanehrndz, I did not see that, I will try out, thanks!

Hello Hurricanehrndz, Just wondering if you had any update to ubooquity. Thanks!

Sweet! Can't wait to see if it fixes my issue!

Thanks CHBMB, It turns out this was an issue with chrome. I dumped my chrome cache settings, and closed and re-opened the browser and everything is working again. admittedly i should have done this prior to writing a forum post. Thanks for your help!

Hello! Suddenly today my Plex Docker won't play any videos. It loads the dashboard and menus just fine, but it will tell me it can't play the files, the orange circle will circle a couple times, it will act like it is about to start playing the video, the time code will click to 1 second, and then the "play" button overlays over where the video should be. Repeated clicks of the play button do nothing. Below is my plex docker 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.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # plex token found in the preference file # ##################################################### [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting dbus-daemon Starting Plex Media Server. [services.d] done. 6 3000 /config/Library/Application Support d dbus[275]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Found user 'avahi' (UID 106) and group 'avahi' (GID 107). Successfully dropped root privileges. avahi-daemon 0.6.32-rc starting up. No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. New relevant interface docker0.IPv4 for mDNS. Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.69.20. New relevant interface eth0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 192.168.69.20 on eth0.IPv4. Server startup complete. Host name is Unraid.local. Local service cookie is 3638159876. I have tried the following: 1. Creating a new preferences.xml 2. Removing the docker and docker image and rebuilding. 3. Rebooting the Unraid Host. 4. Changing DNS to 8.8.8.8 on unraid host. 5. I am running Unraid 6.2.1 Pleas Halp!

Sweet! Thanks for your help, and please take your time, i'm patient, and just appreciate your help. Thanks!