apandey

Knowing all this is additional Metadata which needs to be guaranteed to be correct at all times, including instances like those that cause the failure to write one file. Also it needs to be stored somewhere where it's immune to the failures its trying to overcome. Just taking care of first point takes you into the territory of trying to write your own filesystem, which unraid isn't. The recovery part isn't that hard. It's knowing those assumptions leading to that recovery which are not so easy

Have you tried running with a single RAM stick at a time to try and eliminate any bad ones. Normally, if it's stable in memtest, it should not cause problems. I hope you ran the latest downloaded memtest, not the one bundled with unraid

Maybe should look for this ipv6 address and see if it's spamming unraid server with requests PROPFIND is a custom http method commonly used by webdav clients. It can be something like a webdav client with wrong credentials continuously trying to connect back

That was some response, I may have to read it a few times to pick my favourite OCDs to follow 😆 This is pretty much what has been happening. The usual things over time are slight rise in temps, and more annoyingly the fan hum becoming annoying. I cannot significantly control the dust in the environment, so I have settled down on trying to reduce its flow into the case to increase the time between cleaning cycles Filters, yes, that is one obvious one. But I am not sure what type of stuff I should be looking at, where to procure it etc. More importantly, if there is something readymade I can buy or adapt, of if not, any ideas on DIY solutions. I learn better from looking around and seeing what else is happening Any other ideas / inputs from people in a similar boat?

I have a norco style 24-bay 4u case. The drives are hotswap caddies in front, followed by a fanwall into the ATX compartment at the rear. Airflow is front to back All is good, except I see a lot of dust build up within a week accumulating in drive bays. At lest this shows that airflow is working, but cleaning is tedious as I have to pull out drives and open the case etc Do others have this issue? What solutions have you deployed? Is there a 4u mesh cover type things available? I am happy to DIY things if needed Any real world advise will be appreciated EDIT: my case for reference - https://www.macase.hk/4U-Servers-case/28875.html

If chatgpt is smart enough, it would base its answers off the unraid manual in this case. Seems it doesn't use the right source when answering questions.

Usually it says what type of error. Was there a corresponding green notification saying disk error returned to normal? If it happens again, take note. For now, let's see the result of extended test

If the other disk is spun down, there will be a slight lag. But that's it. I don't worry about this for a use case like streaming a show. Single files are self contained on a single disk, so it's not like reads are randomly jumping disks in real time As for managing across drives, you should look at user shares documentation here: https://wiki.unraid.net/Manual/Shares#User_Shares Specifically, allocation method, free space strategy and split levels and how they work together to manage storage across drives

It is for you to decide. The factors are any organizational preferences you may have, and any disk spindown preferences you may have (like if you have music files spread across all disks, playing them in a Playlist will keep all disks spinning) I personally have individual movies and TV show same seasons stay on same disk, which gives me a balanced array for now (my drives are uniformly sized 8TBs). But I know others who have a different preference I have an extra level of nesting for movies to use same split-level setting for both movies and shows

Download and run memtest86 to start with

What exactly was the error? How did you notice it, was there a message? Cables / Connectors can be a culprit for random IO errors even on healthy disks At this point, I would just run an extended smart test to be sure. If that passes, it should be ok

If none of your pools are named cache_nvme and there is no data there, you should simply be able to delete it

The banner is just to bring to your attention there is something to do, typically that something is an update available to some of your installed apps In the left navigation menu, a new action center item will show up and the banner is just pointing that out. It's not the greatest UX, with a global message disconnected from relayed UI item As for the freeze, not sure. Usually, I would just click on action center menu item to proceed

Try running with kernel boot argument This isn't unraid's doing, you will probably see the same on other Linux distros too. You can Google those errors and find other solutions too. It's best to solve the underlying issue then to mute the logs, who knows if the drives are dying for same underlying cause

It looks like one of your pcie devices is producing lots of errors (which is what irq/xxx is processing) which are then being written to syslog. You can disable syslog server to reduce first one, but instead you should be looking at the root cause. Look into your syslog and see if there are lots of AER (Advanced Error Reporting) events logged. Or post diagnostics so someone here can check

Wifi is still a no go Power line, depends. But it does bring uncertainties into the mix based on your home wiring. It might work for you though, so it's an option A more reliable solution can be a wifi bridge - basically a wireless uplink to ethernet

Remove the drive you added from the pool. Then add it as a new pool https://wiki.unraid.net/Manual/Storage_Management#Removing_disks_from_a_multi-device_pool

It cannot be done with the way how unraid is coded today. It's not a support issue, you are asking for a feature request from unraid developers As far as I see, coding it is effort for a very niche use case. Anyone having a bigger disk can do a parity swap and end up with same amount of storage that you are proposing. With additional benefit that every subsequent disk addition can benefit from larger parity Smaller faster disk has some merit, but again, write speeds are limited to combination of parity+data disks, so marginal utility If you can convince enough people, it might get added. If not, you need biggest disk as parity today because of how parity works and unraids decision to allow people to be able to use all of their data disks (assuming there are always equal or more data disks than parity disks in most cases anyway)

Install the fix plugin mentioned in this thread -

HA is very subjective, depending on what failures you are willing to accept Since these are stateful workloads, let's start with HA on storage (shared nfs) - if you want to protect against individual disk failures, any raid or unraid setup is enough. If you want protection against controllers or servers themselves, you will need to look at a distributed storage solution. Then again, are they in same rack or share power distribution etc is something you need to further decide. At this point, it is already a problem beyond unraid which is limited to a single server. Mostly, you will need to look at individual application and decide based on its HA architecture too You also mention running one instance at a time, so sounds you are looking for automated failover rather than HA. In that case, you should also consider how much switching downtime you can tolerate. If it's not too tight, sometime it's cheaper to reinstall from a backup than to have a full HA solution

Looks like a hardware fault. I would start by running a memtest to rule out memory, followed by looking at disk controller You can also try setting up remote syslog server and see logs leading up to the crash EDIT: seems you already did a mem test. Try running extended smart tests on your disks one by one. What is your disk / controller configuration? Perhaps post diagnostics so someone can see details

Does running ssh in verbose mode help?

Seeing a lot of core plug-ins updated in last few days to support 6.12. That must be a good sign. Sooner

You can reset the network by deleting /config/network.cfg from the USB boot drive using another computer

Would it help if you managed your custom exports under /etc/exports.d/ instead? That way no conflict with whatever unraid might be managing in /etc/exports