Squid

It's actually hard to occur once you've got the cabling right. Reason why the drive keeps getting disabled is because during a read from the drive it dropped offline momentarily, so the OS tried to correct the read error by writing the appropriate information back to the drive and it failed.

USB while supported isn't recommended (ever wonder why on occasion your windows system does the sounds for a device disconnect and reconnect when nothing changed?)

Mar 26 12:00:21 statiknas kernel: ata9: EH complete Mar 26 12:00:21 statiknas kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 26 12:00:21 statiknas kernel: ata9.00: irq_stat 0x40000000 Mar 26 12:00:21 statiknas kernel: ata9.00: failed command: READ DMA EXT Mar 26 12:00:21 statiknas kernel: ata9.00: cmd 25/00:08:00:2a:81/00:00:a3:03:00/e0 tag 8 dma 4096 in Mar 26 12:00:21 statiknas kernel: res 53/04:08:00:2a:81/00:00:a3:03:00/e0 Emask 0x1 (device error) Mar 26 12:00:21 statiknas kernel: ata9.00: status: { DRDY SENSE ERR } Your issue is cabling. SATA connections are terrible, and depending upon the type of drives, the non-locking cables are better than the locking ones (eg: on WD drives) Reseat the cabling at both ends, along with the power, avoid splitters at all costs, and do not try and make cable runs look pretty -> the prettier it is the more susceptible to cross talk it is and never, never, never tie power cables to data cables. When doing this, take care not to disturb any adjacent cables. Whenever I'm in my system I always give a little push to every single sata cable everywhere.

First thing to do is reboot. The OS runs automated file system check on the flash drive during boot up. If that doesn't fix it, turn off the server and run the file system check in another computer (chkdsk). If this still happens, replace the flash drive https://wiki.unraid.net/Manual/Changing_The_Flash_Device (An "unclean" parity check will result because the flag won't be able to be written to the flash when rebooting the system)

The drive is failing SMART and needs to be replaced SMART overall-health self-assessment test result: FAILED! - available spare has fallen below threshold - media has been placed in read only mode SSDs / HDD keep spare sectors so that when a sector goes bad it's automatically mapped to one of the spares That spare pool has no been exhausted.

If the banner disappears after refreshing the page or going to a different page, then it's simply a race where one of the files it wanted to check wasn't available to read (being updated concurrently?) and is nothing to worry about. We'll check it out. Thanks.

I don't see how that's possible TBH Does it reappear as soon as the server is rebooted? If you delete it and then refresh the folder is it still there?

Type in the path

If the GUI gives you the option to cancel (I really have no idea) I would. Since it's unmountable, it's going to tell you to remove the -n anyways. Do that and re-run Saves some time.

You have to let it finish with the continual dots. Assuming you didn't remove the "-n" flag, that'll be the next thing you do and run it again.

Only the settings which are stored on the flash drive (eg: any templates for apps installed since then) I would however when trying the backup to first make a copy of the existing /config folder if it's readable on any system and then restore it after restoring your backup

Disable mover logging in Settings - Scheduler Also, generally the appdata share should be set to use cache: Prefer. Mover keeps trying to move it to the array (and the logs fill up because most of the files are in use) You will get far far better performance by setting it to Prefer, running mover (with the entire docker service disabled in Settings Docker). Use the appdata backup plugin to make weekly backups of it to the array

Pretty much nothing. Never hurts to make a backup of the flash first though no What problems do you have?

Only for new containers you install. Change it back

Unraid 6.10 has some improvements on how the dashboard is handled with regards to this, especially if the dashboard is left open for long periods of time

First I would try closing all browser tabs on all devices which may be open to the OS Then a reboot

You should post your diagnostics

Looks like a bad flash. Replace

Varies massively depending upon the app. Within a config file, within the settings in the app's GUI, via an environment variable. No one answer fits all here.

uninitialized csrf_token Rebooting and going from there is your only recourse at the moment

Don't use the symbolic links and instead export the pool via Unassigned Devices if you can or manually export the shares via appropriate editing of smb-extra.conf

You need to install it within the container itself, not on Unraid. For that your best bet is to talk to the container authors on how to do this. (Or try apt-get within the container itself, but that'll need to be redone after every update to the container)

The mce itself appears to be harmless and happened at processor initialization which occurs on certain hardware combinations. As for why it turned off during a preclear, I'd say it has nothing to do with the mce, but something else (power outage etc)

Quick googling suggests to blow out all the accumulated dust etc on the motherboard, reseat the power connections to it and reseat any add on cards / RAM

Management settings. Use SSL: no