myplaybox

I have no idea why but I just tried it again and it worked. Before I used Chromium which gave me those results, Firefox seemed to have no problem. It of course still said the site is unsecure and my certificate is invalid, but after clicking continue anyways it just loaded up on the 3001 (HTTPS) port. Both browsers can load unsecure sites after clicking away the warning, they have the same permissions and run on the same machine. I have no idea why it makes a difference. Maybe someone can explain why. So if anyone here is still having problems, try Firefox (if running Chrome). Thought I might give an update even if this thread is dead.

Having the same problem but with Ungoogled Chromium. Guessing this belongs here too then. Even after setting the variables CUSTOM_USER and PASSWORD I still get the HTTPS required message on port 3000 and the waiting for stream one on port 3001. I thought HTTPS was not required when using CUSTOM_USER? (https://github.com/linuxserver/docker-ungoogled-chromium/pkgs/container/ungoogled-chromium) Anyone found a fix for that yet? Nothing in here seems to be working. Edit: What I noticed when I try port 3001 is this. It says not secure.

Yeah for that I am building another server as a backup. Probably running TrueNAS or something so I am not solely relying on Unraid. Just to back up the data automatically once a month or something.

Thanks, I was thinking way too complicated. Sorry for getting back to it so late, I was at work until now. I did it exactly that way and it is rebuilding now. The content all seems to be there, I was just a little scared. Rebuild will take around 5 hours now, so I will just wait and see. Thanks you are a lifesaver. I do not have a good backup strategy in fact. My only "backup" is this Unraid system. I am planning another server (nothing too crazy) with the sole purpose of backing up all data from my Unraid once every 2 months or something. Is having two parity disks overkill? Since I mainly use old and recycled drives (sometimes bought second hand) I thought it would make sense to have two. A brand new 8 TB drive is ordered and on its way now. I planned on installing it as a second parity again. Do you really think it is unnecessary? Also thanks, I didn't know about the parity swap feature, will read into it a little more.

Oh I see. So is it not possible to downsize a setup in a case like this? When I buy a replacement right now, I would buy a larger one. But that would mean I have to change the parity drive too. Isn't that a problem having two drives replaced? Because when I buy let's say another 8 TB drive now I would have to use it as the second parity disk (because parity needs to be the largest one). Which means I would have to put the current parity 2 disk into the array. That would mean two disks have to rebuild at the same time right? Is that a problem or does that just work? Am I thinking wrong?

Yeah, I knew that drive was on its way out because they are all used and old. I just don't have a replacement right now and when I buy one, I also have to upgrade my second parity disk (because parity needs to be the largest one I think?). Could I pull it out and rebuild the data from parity without losing data or do I have to do something first? I would do it with the new config tool. This is the first time I have to do something like this and I don't want to lose anything.

Hello, I wasn't sure where to ask correctly so I try here. I noticed something weird when my scheduled parity check has been running for two days and hasn't moved past 35%. When I checked I saw that it was running at between 0.3 and 2 MB/s. When I checked the drives one of them showed a reallocated sector count error and it has been going up since. It now says failing now in capital orange letters. (Ignore UDMA CRC error count, that was because of bad SATA cables I have used previously. I have replaced those, I just don't know how to clear that statistic.) I stopped the parity check and spun down all drives as I don't want to annoy the failing drive more than necessary. I am not sure what my next move should be. I do not have a replacement drive right now and I am not sure if I should back up the failing drive as it also says something about corruption errors. Don't want to overwrite good data with corrupted ones. Should I just yank it out, make a new config and rebuild the data from parity? (I have 2 parity disks because I use recycled and usually older drives.) I wasn't really 100% sure so I wanted to ask before I do anything dumb. I also have a SMART test done yesterday and current diagnostics here if that helps in any way.littleboi-diagnostics-20250804-1744.ziplittleboi-smart-20250804-1741.zip Thanks in advance

Update: So the new SATA cables arrived. I threw out the old ones and put in the new (supposedly good ones). Starting up, the system still shows parity 2 as disabled. To make sure the system even recognizes that drive, I did a short SMART test. It completed without errors. littleboi-smart-20250604-1742.zip I am not really sure where to go from here. Is this something with the config of my system? Is the drive just toast? Edit: I found comment on a 3 year old Reddit thread that fixed it. Guess I was just dumb not thinking of this. Rebuilding parity now. The comment: Stop the array, unassign the disk, start the array in maintenance mode, stop it again, reassign the drive to the same slot. The idea is to start the array temporarily with the drive “missing” so it changes from “disabled” to “emulated” status, then to stop it and “replace” the drive to get it back to “active” status. Thanks for all the help. You have been amazing.

Got it, thanks. Always wondered how that works. I just moved all the system and appdata files over to the cache manually. I could have probably done it with the mover in hindsight, but that would have required to set the shares up for secondary storage. It seemed to have worked that way, thanks. I also adjusted the spindown timer for all drives to 30 minutes and set up appdata backup for doing weekly backups to the array.

Yup, I acknowledged it. Now all drives show the green thumb up again. I do want to keep the second parity disk, even if it might not be the fastest thing to do. I am using recycled drives so that lets me sleep at night. The disk still shows up as disabled, I tried reseating, restarting but it still shows as disabled. To make sure the system even recognizes the drive, I ran a small SMART test which completed without errors.

System and appdata combined are 23.7 GB and I have a 128 GB m.2 here. So it would totally fit without a problem. I also have a 256 GB one but that is currently used to run the VM from. If I copy the virtual disk from there I could use the 256 GB one. Since I would like to put some other files on the SSD pool as well. Everything I want won't fit until I have a bigger one but it's fine for now. I think. If I tell a share to be saved on another disk or the pool will Unraid just move the files there?

Yes, parity 2 shows the UDMA CRC errors that are common. After clicking on attributes for that disk: I also ran a short SMART test for that drive but I can do a long one too if that helps. littleboi-smart-20250530-1548.zip

Interesting, I might consider that then. I have a spare SSD laying around but it's small. I just thought it was not worth it having important data like that unprotected. How would that work? With setting up the mover? Also I have my VM on a SSD connected with a USB adapter. I just use this plugin, unassigned devices that lets me do this outside of my array.

I do know this, but it helps me sleep at night. Having to rebuild parity won't have me sweating bullets that way. I am trying to fix these for good, waiting for the new (supposedly) good SATA cables to arrive. I don't think it should be a power issue since I have a 600 W Be Quiet power supply and the entire system usually never consumes more than 60 W. Will have to see how the new cables do once they arrive. Please correct me if I'm wrong but pool devices are protected with RAID1 right? How does parity work with just one HDD as a pool device?

I shut it down, reseated all the sata power and data cables and here are the diagnostics. It still shows the red X. But the drive seems to be working because I did a small SMART test to see if the system even recognizes it. That worked.littleboi-diagnostics-20250530-1527.zip I must say that UDMA CRC errors are normal, I have those all the time. From my research it is usually a bad connection. The SATA cables I currently use are just whatever I could get in a pack of 6 off Amazon. I bought new ones that are supposed to be good ones. Those are on the way. For power I have them all on the same PSU, if the new SATA cables don't fix that someone said that I should use a second power supply. So the drives are split and not on the same cable. Not sure if that helps. But these are really old and used drives. I bought them used and I am aware of that. They might fail in the future, that's why I decided to have 2 parity disks. I know, this is very much not optimal. I do not have a cache pool, currently don't have the money to buy 2 SSDs either. The drives are usually always spinning due to that and qBittorrent doing whatever it does (seeding mostly).