RedXon

I don't know if a new controller would solve this problem, as I have seen people with different controllers who had or have this problem. So I use two Dell Perc H310 flashed as LSI Megaraid 9211-8i with 12 disks in total. Then I have two parity disks on the onboard Sata connectors. And others just use the onboard connectors and have a similar problem. So I don't know if a controller swap would really solve this problem. I could try some other stuff but I am currently in a rebuild due to a disk failure so I can only try after this has concluded of course.

Yeah, I have a mix and match between seagate and WD. But still, it is still working for me in 6.10 RC1 but I wonder if this is just because some plugin didn't update yet or why it is. It is mindboggling when something suddenly works and you don't know why. Edit: Somehow my server has sensed, that I just made that comment and started spinning disks up without any reason again. It's getting really annoying... Come on, please sort this out.

If I may jump in, I have upgraded my server to 6.10 RC1 because I was annoyed with this behavior and so far it's looking fine. I can't report on the auto spindown issue, as this one was working for me, only for the disks to spin up again immediately with the read SMART message in the log. So far, the disks have remained spun down after telling them to spin down manually. So this is encouraging so far, as before with 6.9.2 they wouldn't stay spun down for even 5 seconds after spinning back up with the aforementioned read SMART output in the log. So looking good so far. Additionally I have to say that I do not and have not in 6.9.2 used any of the plugins autofan, telegraf or turbo write which often get referred to as the offenders. But it still didn't work in 6.9.2 but seems to do in 6.10 RC1 so this is looking good. Now I just hope it stays this way (especially in future releases and the final).

Hello So I've followed some threads on here and on reddit and tried out the various solutions that were recommended to solve this problem, none of which really have done anything for me. For some reason for some time now my array just wont spin down. It never does. Even when I tell it to spin down manually, it just immediately spins back up as if something constantly would need the disk. This is weird as on every setting I see, all the system and docker files are on the cache. Also, in the plugins for active streams and file activity nothing shows up. In open files all the files that are open and on the disks are from the process SHFS, and afaik that shouldn't affect anything I think. What am I missing? I tried it with and without the cached directories plugin, both to no avail. Attached is the diagnostics log so I hope someone can find something as it get's really annoying (especially in summer). And yes, I know one of my drives is failing, I'll replace that shortly. azeroth-diagnostics-20210810-1259.zip

For a few days now I can't connect to my owncloud via my reverse proxy anymore as I get a 400 bad request anytime I try to do it. I have not changed anything in my proxy conf and have already contacted the dev of the owncloud docker container. He said that nothing has changed in the container since the issue came up for me, leading me to believe the error has to lie somewhere with the proxy. Does anyone know what it could be? It's now been a few weeks and I've tried to solve it on my own, without success. It worked until the 7th of may but has not worked since. I can not connect from either the browser, my phone, the owncloud windows or owncloud android client. Nothing works unfortunately. Does anyone have an idea? Here is my proxy conf that has, at least until the 7th of may, worked wonderfully. server { listen 443 ssl; listen [::]:443 ssl; server_name owncloud.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_owncloud owncloud; proxy_pass https://192.168.0.2:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Forwarded-Port $server_port; proxy_set_header X-Forwarded-Proto $scheme; } }

Thanks for your answer. Unfortunately not really. I get this in my logs at startup, which doesn't seem that strange to me. After this it's conly the cron repeated with nothing else. May 12 02:20:24 1c9933409ffc cron[592]: (CRON) INFO (pidfile fd = 3) May 12 02:20:24 1c9933409ffc cron[592]: (CRON) INFO (Running @reboot jobs) 210512 02:20:24 mysqld_safe Logging to '/config/database/1c9933409ffc.err'. 210512 02:20:24 mysqld_safe Starting mysqld daemon with databases from /config/database May 12 02:25:24 1c9933409ffc mariadb: Upgrading databases... May 12 02:25:24 1c9933409ffc mariadb: This installation of MySQL is already upgraded to 10.3.29-MariaDB, use --force if you still need to run mysql_upgrade May 12 02:30:01 1c9933409ffc CRON[994]: (root) CMD (/sbin/setuser abc php /config/www/owncloud/occ system:cron &>/dev/null) May 12 02:39:01 1c9933409ffc CRON[1005]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi) Only thing I can think of is that it's some issue with my SWAG/Letsencrypt reverse proxy configuration, but I haven't changed anything in there, and all my other proxies still work. It still worked a few days ago, in fact the last sync action I had successfully was on the 7th of may. Because yes, also on my owncloud destkop app I get 400: Bad request (which is to be expected, as it also uses HTTP as a protocol I think). So unfortunately I have no idea what might have broken it. I have only my domain through the proxy as trusted domains, so I can't connect via local connection. I think I'll add the local IP to my trusted domains and try to access directly via the local IP and report back... Edit: in fact, yes. The issue lies with my reverse proxy it seems. All other sites still work but I get 400 with owncloud. Local connection to the IP works. Was there any change which needs a change in the reverse proxy conf?

Since some last update I have an error when I want to connect to the owncloud. I get Error 400 - Bad Request, regardless of what PHP Version I select. I tried version 7.2, 7.3 or 7.4. Does anyone know what the issue could be here?

Ah right, and even if another one were to fail during rebuild it should still rebuild it correctly due to the dual parity? The timing is a little bad, because I had planed to upgrade the server to 16TB parity disks and a new Mobo and CPU anyways on Friday but now the dying disk obviously is more important. And doing a parity swap now, no thanks. So steps are: - emulating disk 2 until replacement arrives. - Rebuilding disk 2 - upgrading MoBo, CPU, Ram - Replacing one of the two parity disks with the bigger one - Replacing the other one - If disk 3 gets worse replace that as well - All fine and dandy (hopefully?)

A few days ago I was confronted with what everyone who has a server hopes will not happen but knows, that it some day inevitably will - a slowly dying drive. Now, due to me not having my notifications correctly configured I noticed this only pretty late, as before I would only get the Array Pass, Fail or whatever notices and no warning with email or push. So while playing around with my server I noticed the S.M.A.R.T. values of one drive being bad. It had some relocated and pending sectors but worst of all it had 2 offline sectors. I must have seen these before but probably not noticed them or have just purposely ignored them because eh "it's probably fine -ish(?)" and after all, all the notifications I received just told me the array was fine as it passed (apparently unRaid sees nothing bad with it but okay) But now that I saw them again I thought, right, let's just replace that drive, no biggie right? Well, I ordered a replacement but due to the current situation it takes a while till your ordered stuff arrives. But I thought well as long as the server as no errors, as long as the drive stays green and so on. Well, the count increased to 6 and I thought uh, well I still have no errors so let's just hope it stays green and if not, I have my dual parity so it should be fine right? So today was the day the server should have done the monthly parity check (and so far every one of those have been fine) and just as it started I received read errors from the disk (disk 2). Now that's when I panicked because I think that these checks are correcting ones. So this would mean that it reads all the disks and reads the errors on disk two and therefore has different data for disk 2 from the data in the parity and would "correct" the parity to the faulty data from disk 2. So my parity would be compromised and if I rebuild disk 2 I would lose the data from these offline sectors. Is this correct? Because I stopped the parity check as soon as I could and it gave me the message parity check canceled (0 errors). Then I shut down the server out of fear of corrupting anything. So my current plan is the following: - Keep server offline until the new drive arrives (should be later today or tomorrow) - Power on server and remove disk 2. - Assign the new drive as disk 2 and let the rebuild run. - Everything should be back to normal (right?) Does this work? Would it be safe to run the server in its current condition? I know that as soon as unraid detects a write error it just takes the disk offline and emulates the content but so far it hasn't done that so I think my parity should still be good (with the files in the bad sectors intact in parity). Last month parity check run without errors and I didn't have and unexpected shutdowns or anything and no write errors so it should be okay right? Because another thing I noticed is that disk 3 also has some issues. It has some relocated sectors but no pending ones and no offline ones. I mean, I guess I'll need to replace that disk soon but at the moment it should be fine even for the rebuild of disk 2. And even should it fail during the rebuild it should still be okay because I have dual parity. Yes, the array would be unprotected then but I should not lose anything. Will the rebuild of disk 2 still go through okay in this case so that I can replace the other one after that is done, so that the array would be protected to rebuild the other one? So is my thought process correct on this one? And could I let the server run in its current state? I mean, it would be nice if I could but it wouldn't be a catastrophe if I couldn't... I would like to avoid losing data (as only the irreplaceable data is backuped but it would be a hassle to reacquire the other things).

Fair point, I don't know if it would be possible to just monitor all the changes that have been done to the emulated disc after the physical one being disabled and just restore this. But anyways, back to my original question, is the error, if it was a connection/cable/raid-card one more likely to occur during high usage (so for example during the current data rebuild) or is it entirely random and could in theory just occur again after the rebuild is complete?

Okay thank you. I am now in the progress of rebuilding it to itself (shame that can't just "trust" it again and just write the changes to it). I switched out the connection as mentioned and am now connected directly with the motherboard. Rebuild is 60% complete and no errors or any more CRC errors so far, but then again last time they only occurred after 4 days on power so I'll see, hopefully that was the last of that.

Hello So I know I have at least one slot in my backplane that doesn't function properly, because I've had multiple "disk disabled" errors in those. So I switched the disks around and haven't had any errors for over a year, until today. I installed a new disk on the 18. (4 days ago) into a up until now unused slot and just a few minutes ago it reported errors and disabled itself. It is disk 10 (sdp) and it is a seagate ironwolf (and from what I know seagate disks report their smart values very weirdly), So the only thing I really see there is UDMA CRC Error count on 6 which again, would be a bad cable or connection at least. The diagnostics are attached below, and I am not sure how to read all this so any help is highly appreciated. Now for my setup, I run 3 Icy Box IB-565SSK backplanes. I know that one slot on backplane 2 does spit out errors and now it is one on backplane 3. The backplanes are connected to 2 dell perc h310 (in LSI 9211-8i IT mode) only the parity drives are connected directly to the motherboard. I switched the cables and everything on the one particular slot on backplane 2 and now I think I'm trying to connect that disk directly too, just to see if it helps. The motherboard is a Asus p10s-m and the power supply is a corsair RM750 (with a single 12V rail so I doubt it has anything to do with power shortage). So can anyone maybe read from the smart or syslog what the culprit here could be? Thank you very much for reading azeroth-diagnostics-20190422-1613.zip

Unfortunately this does not work for me. After I restart Plex, I see the other telly (one I have already configured) for a short time but when I attempt to add it, it vanishes. Also, I have manually added DEVICEID, FRIENDLYNAME and auth, as they were not in the version from the app store on Unraid. But the Tuner just is named HDHomerun(telly) and does not carry over the FRIENDLYNAME; even after multiple restarts of both Plex and the server itself. So I guess Plex does not recognize the other ID and name, even though it should, right?

I actually found out what the problem was, by trying something completely different, thanks for all your help. The file was encoded in UTF-8-BOM, which somehow was not compatible. I changed it to UTF-8 and tada, it works.

Thank you, I did exactly that But unfortunately it does nothing, not when I hit Force Scan not on adding it, nothing. Anything else that could be wrong here? The file works in VLC and other apps. It also works if I enter the m3u url from where I got it, but it has over 10000 entries, so I edited it with only the ones I want. There should be about 200 in there... For further clarification, I don't think there's a fault in the list, just in the way I put it in. I can for example load the list in Kodi with the Simple plugin included. It works fine but I unfortunately have no EPG there, that's what I try to do with Tvheadend. I hope that this can do that there.

How can I add a local m3u file to TVheadend? If I try every combination with file:// it doesn't work, if I try absolute path, if I try mapped path, no matter what I try, it doesn't work unfortunately.

Thanks, I just realized the same and your method worked fine, finally Thank you.

Any update on this? I've tried the above suggestion, added 5666 to the container but it hasn't solved anything for me. I even tried privileged mode and stuff but stîll nothing when I try to load the Web UI...

Does this work with an USB 3.0 Bluray drive?