ZiRiuS

Is it possible to add this to Open WebUI? If not is that something that might be available in the future? Thanks!

I think I figured out what was wrong. There were more than one problems but the biggest was permission. After I set up the appdata folder again I needed to fix the permissions. Thanks as always for the help @JorgeB!

After I updated to 7 I had to recreate the docker because the cache didn't work after the update. Do I have to do it again? I don't have any custom networks.

Yes, I get a network error like when the internet is out.

Long story short, I was tinkering with Tailscale and I saw in a video that there was an individual docker Tailscale options in 7.0.0-rc.1 so I decided to upgrade and test from 6.12.14. When I upgraded my cache drive didn't mount so I fixed it but realized no dockers where visible even though they were still there on the drive. I decided to build it back up from a backup. After that I can't access some of my dockers (around half of them). I have no idea what is happening or why I can't see them. I tried disabling Tailscale but it doesn't work. Any idea what's going on? Thanks! There my diagnostics. cybertron-diagnostics-20241215-2216.zip

How did you solve this?

I tested further and it seems to be only present on Firefox. Also I can move the position of the subtitles but not the size, color or shadows.

I'm using version 10.9.1 and all of a sudden my subtitles are huge and changing it in settings does nothing. Any idea what's going on?

I swapped slots on the motherboard and that seemed to have fixed this. I at least have the disks back without errors after parity check. Could you explain why this could have happened? Is my motherboard not good for this? Should I use a HBA board? This makes me scared to touch anything on the server if it's so fragile haha. But thank you so much like always @JorgeB!

These disks where both with the same cable/slot. WRQ25FRW was the 8TB replacement disk. But he's no longer in the case. I changed the cable and still get the error. cybertron-diagnostics-20240407-1614.zip

Hey guys. I am a beginner in the sense of understanding when something goes wrong with the array but I've been trying to troubleshoot all day. The thing is I wanted to add another drive to my array. All my drives are 4TB, 6 in total where 1 is parity. I wanted to transition to 8TB drives so the plan was to move the parity over to the 8TB new disk and move the old one to the pool. So I turned off the server, dusted cleaned it, put in the new drive and booted up. That's where everything went to hell. Two of my drives acted up, one was missing and drive emulated (red X) and one was "Unmountable: Unsupported or no file system" but the icon was green. I had similar issues with the missing disk in October 2022 but I solved it by doing xfs_repair and it had no issues after that for all this time. I was so annoyed I went and bought another 8TB disk today to replace it, but that's when the strange things started. My server said both my new 8TB drives had errors on them, but they were new and not even formatted yet, so I formatted them and tried repairing but nothing worked. It's worth mentioning I only have 6 SATA ports on my motherboard so I bought this 6 port SATA controller (Similar to this one: JMicron JMB585 https://cdn.nfp.is/kisildalur/20240213_151103_SYA0017569.jpg.). Could that have fucked up everything? I recently changed all the SATA cables so I doubt that's the case. I've also tried xfs_repair without prevail. Can anyone here tell my where I went wrong and if there is a possibility to at least get one drive stable to parity one of the disks because I only have one parity disk. Here are 2 diags, one yesterday when all this happened and one today after all my tinkering where I hope I didn't break anything. Thank you all so much for your help. cybertron-diagnostics-20240405-2202.zip cybertron-diagnostics-20240406-2136.zip

I got no errors and normal speed so this case is closed. Thanks for your input @JorgeB. cybertron-syslog-20221009-2249.zip cybertron-diagnostics-20221009-2248.zip

Here are the diagnostics. After rebuilding the disk everything seems to be working correctly now. You see anything out of the ordinary? cybertron-diagnostics-20221009-1244.zip

I'm currently following this now, hopefully solves it. I'll mark it resolved if that's the case:

I'm baffled. I'm getting no errors or anything and the disk seems to be there (logs seem to say so as well) but the menu says the disk is disabled. Anyone know what's going on? New logs provided. cybertron-syslog-20221008-2057.zip

I updated the BIOS and it seems to have fixed one of the drives, but the original one is still out. This is the error I get now: Oct 8 18:15:12 Cybertron kernel: ata4.00: exception Emask 0x50 SAct 0x2000 SErr 0xb0802 action 0xe frozen ... Oct 8 18:15:18 Cybertron kernel: I/O error, dev sdd, sector 24 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

Hey guys. I have been having some trouble with parity checks lately, being really slow, taking 52 days to finish and so on and I saw on some forum post that swapping SATA cables might do the trick. Mine were really old from various other systems I had so I have no idea if they were bad or not so I swapped them all out for new ones. That's were the trouble starts, one of my drive stopped working after that. I try running xfs_repair but when I did that another disk started having problems. I have to admit I have little idea what I'm doing and I don't know what's happening. Sometimes my system feels like a house of cards. I noticed the disks with the error changed partition names, like in the Unassigned Devices they all of a sudden had sdb and sdd but they had a different ones when part of the array. Logs and screenshot of the disks are attached. I hope someone here can help. Thanks a lot! cybertron-syslog-20221008-1542.zip

I had one of the drives act up like that before and I just formatted it and it was fine after that. I just thought this was some conflict or something.

I will try it when I get off work. I have a SATA PCI-E card connected but I don't remember what disks are connected to it, could that have anything to do with this?

I tried to press the refresh arrows like you suggested but it only said "Success" but nothing happened. I just finished the parity check and I restarted the server (tried the arrow refresh thing again, still nothing). It booted up with the array offline and it looked like this: But when I tried to add them to the array they became like this again: I checked the logs on the disks and this is what comes up on the top one: The bottom one: Any ideas what's going on?

Hello there nice folks at Unraid. I have a problem that started when I replaced one of my drives without removing the old one from the array first. I of course turned everything off and all, but I should have done things differently. But when I did that two drives started acting out and I couldn't mount them back on and they had errors and hazzle and xfs_repair did nothing. I suspect it was some kind of conflict from the other drive. After some googling I saw a post where someone just made a new config, figuring I didn't have anything to lose I just did it. That didn't really do anything so I'm going to you guys with this. I have diagnostics from after the new config, maybe that can shed some light? Thank you so much guys. cybertron-diagnostics-20220714-1804.zip