Froberg

Came here for this.. Running nginx proxy manager to serve nextcloud.. do I need to take any action other than update when available? I'd rather not mess around with the core config files. I guess I can always take it offline until a fix is available.

I've just tried it and it appears to be working.. although I usually don't go for RC's. 🙂 Trusting ya here, Squid Actually scratch that. It's slightly improved, but not gone.

That'd be the idea, yes.

Hi all I'm pondering setting up my, ancient, mediasmart homeserver as a straight up datadump for array backups. I have some old Seagate Archive drives kicking around and figured I could use UnRaid for this secondary array and just drop parity altogether and use these totally raid-unsuitable drives. But that shouldn't matter since it's.. not RAID? Or am I missing the big picture altogether here?

I'd just like to reiterate that the issue isn't fixed, but the mover scheduler has removed my daily hassles. So, a workaround at least.

Can confirm CA Auto Update resolves everything.

Cheers! Auto-update installed and everything resolved.. and it also solved me having to update plugins and containers in future.. Appreciated!

So for a few weeks some, not all, of my containers are listed as "update available". Regardless of whether I update one, or all, they all check out fine and then I can check for updates again - and they all want to be updated again. I just tried rebooting my server, something I tend to avoid, and it didn't change anything. Any diagnostic tips to be had for this? Essentially they'll keep pulling down 0b and doing all the upgrade steps, it just seems to report incorrectly so now I don't know what to trust any more.

I understand that they are, but not in any great detail, no.

Are you referring to split-levels and allocation settings? Mine's set up to just throw data wherever with high-water and split any directory. I kind of wish I hadn't gone that route initially, now, since in the event of data-loss due to a drive or something else, I'd rather have a good idea of what data was lost.. but I didn't really understand how UnRaid functioned back then. Not really.

I can see your point. Unfortunately I took the "just throw stuff wherever" approach when setting up UnRaid, so the cold-storage stuff is scattered all over the place along with the more active stuff. Not sure I can change that at this point in time.

In my case I use my media server most of the day. It's running some dockers, but those are contained on the SSD's. As for the storage, well, it depends on the day.. but we usually listen to music via the Plex server on the Sonos system, or the kids will be watching cartoons on an ipad or something. I guess they could technically be spun down.. hmm. Won't it increase storage access times when whatever system requires whichever file?

Okay.. I have always prevented my drives from spinning down, because I heard that the fewer start/stops you have to do, the better it is for longevity. Is this not accurate for UnRaid? Because then I should be changing some settings ASAP.. Cheers.

Agreed. This appears to be the exact issue. I am experiencing all those same problems. My array-rebuild not withstanding.

Right you are. It was a bit more involved than I had expected. Not sure what I did to trigger this, but maybe the fact that I pulled the failed drive and inserted the new one in the slot the failing one was in, caused some confusion. I had to stop the array, remove the drive from the array, tried to stop the array again but it couldn't unmount the shares for whatever reason, rebooted, stopped the array, assigned the drive again, restarted array - partity check has begun. It's now back on-line and the speeds are looking much improved. Thanks for the assist, and apologies for thread hijacking as the mover issue is still pertinent.

I tried that first, but it just kept only showing me the option for read check. Just going to let it run, looks like it's all disks based on read activity and it's going fairly quickly;

Server did not enjoy it. I replaced the faulty drive-tray and put it in a different slot. Now I'm forced in to a disk read check of, it seems, all drives and the drive that was moved is listed as "Disabled". Haven't seen that before. It's going to take a day just for one drive to read check.. so I'm in for a long haul it seems.

The slot seems to have a dead diode anyway, so it's for the best probably. I'll try. Thanks.

Not possible I'm afraid. It's firmware updated (they implied that solved it) and hasn't been an issue though. Running the cache drives on that controller too. I guess I'll try and move disk 4. Do I wait for the rebuild or just throw it in a new slot after pausing?

How do I tell which drive is connected to ATA12? I have hot-swap bays, so might just try and move it to a new slot.

Here ya go. It's still working on rebuilding, so it's slow now. To be clear though. The system is usable right now. So it's not like the mover issue. I just get intermittent interruptions. fortytwo-diagnostics-20190806-0254.zip

All the drives are 6-10 TB WD Red's. Once the array is safe, I'll do another Parity check to rule out any cable fault.

Two different things. My REBUILD is going excruciatingly slow, but my regular parity check hasn't seen any performance degradation having been stable at 120-130'ish during the period. The Rebuild is much, much slower than it was a year ago, when I last replaced a failing drive.

No I meant what I wrote. My normal parity check, which runs monthly, hasn't been impacted in any way. The rebuild though.. major impact. I've even had trouble during this rebuild playing media. We're talking even having disruptions when playing a flac file over my Sonos system at home. And considering the speed it's going at, it's impacting my performance for almost a week.

I think the issue extends further. I'm doing a rebuild now, due to having to replace a failing drive, something I have done with UnRaid before. So far it's run for 24 hours and I haven't seen it get higher than 50MB/s. Usually it's in the 20's. That's significantly slower than I've seen before in this setup. Might be related. Here's how it's looking 23 hours in: And here's the parity check history.. Fairly consistent, IMO.