trurl

I've personally never done more than one. I think the rationale for more is to try to get the disk past infant mortality. Like most electronics, if it doesn't fail early, it may last until obsolete. But if the rest of your array is healthy and you are diligent you should be able to survive a single disk with infant mortality. Do you have Notifications setup to alert you by email or other agent as soon as Unraid detects a problem? Do you have backups of anything important and irreplaceable? The original purpose of preclear was to allow you to clear (zero) a disk so it can be added to a new data slot without invalidating parity. If you try to add an unclear disk to a new data slot, Unraid will clear it so parity is maintained. Older versions of Unraid took the array offline while it cleared a disk, so preclear was invented to clear the disk before adding it to a new data slot. Later version of Unraid clear the disk without taking the array offline, so that original purpose isn't really necessary anymore. And, note that except for adding a disk to a new data slot, Unraid doesn't need a clear disk for any other scenario. Such as replacing a disk, since the disk contents would be completely overwritten by the rebuild anyway. Additional functionality of preclear includes some things that also test the disk. but it is possible to test a disk using other tools, such as badblocks or one of the utilities provided as free downloads by the disk manufacturer.

Your plugins are way out-of-date, including the preclear plugin.

Where are you seeing the speed you are reporting? (Also, there is a difference between MB/s and Mb/s, and no such thing as mb/s) You would have to post a diagnostic for us to have any idea what the problem might be.

👍

So, how to reformat that disk. Stop the array. Click on the disk in Main to get to its page. Change its filesystem. Start the array to format to the new filesystem.

Actually that IS what format means. Many people have a pretty vague idea about formatting, thinking it is just something you do before you can use a disk. But the key part of that is "a file system format was written to the disc". Format is a write operation. Unraid updates parity in realtime on ANY write operation. So if you format the disk when it isn't in the array obviously parity will be invalid. And, in fact, Unraid won't let you do that without going to an awful lot of trouble, which is why I said trying to stress that disk would greatly complicate your life

No, in fact it is critical that the disk remain in the array while it is reformatted or you will invalidate parity. You likely have some misunderstandings about formatting and how parity works. Do you know exactly what "format" means?

SMART for Disk4 looks fine. Nothing to be gained by stress testing it, and you will greatly complicate your life if you try to.

What do you mean "while it's out". You haven't unassigned or removed the disk have you?

I have crossed out everything you absolutely must not do. If the disk is empty you just need to change its filesystem to XFS by making Unraid reformat it. Since you are so confused though, before I go into detail about how exactly you make Unraid reformat that disk to XFS, go to Tools - Diagnostics and attach the complete diagnostics zip to your next post so I can take a look and make sure you aren't overlooking something important.

Could you give us a screenshot of this? Sounds like it. Don't do anything without further advice.

Looks like you left out something

Do you mean stripe?

The orphaned containers won't grow but of course they will take up space until they are removed.

Almost certainly a browser problem then. Whitelist your server in your adblocker, clear browser cache, etc. Let us know if that works for you so we can close this report.

Just in case you didn't see this. Mappings themselves aren't the cause of docker image filling

Have you tried the plex forums?

If I remember correctly this is a bug parsing crontab if you have your schedule set for Sunday. You might try changing that until the fix is released.

I expect you are still getting hack attempts on ssh then. You do know there are bots that automatically seek out and relentlessly try to break into systems don't you? You will probably have to get physical access to make any progress.

yes

Take your server off the internet. Then maybe we can work together to get things working again, including perhaps VPN. Lots of people have made this work.

The Need Help link I gave earlier has the information on how to get the syslog or better yet the diagnostics even if the network isn't working. Maybe you didn't read it.

Your syslog is full of hack attempts from all over. Don't put your server on the internet.

Looks like your server name is simply "the"

Please don't link to unknown external sites. Just attach your syslog directly to your post. Or better if you could get us the complete diagnostics zip.