trurl

Go to Main - Array Operation and Move Now. Wait for it to complete then post new diagnostics.

Never had any "cool" lighting. Maybe the BIOS can make that work without anything. Maybe a VM could do something with it. Unraid itself isn't going to know or care about any of that. Unraid is a NAS OS with docker and VM hosting and doesn't try to do anything else. Dockers and VMs can add a tremendous amount of capabilities, and Unraid only has to host them.

As mentioned, parity isn't a backup. And in fact, it is probably less important than your other drives, since it doesn't contain any of your data, and by itself is useless, whereas the data disks do at least contain data. In fact, one of the advantages of Unraid is each disk can be read by itself without needing parity or the other disks, unlike RAID. Single parity will allow a single disk to be reconstructed from the parity calculation using the bits on parity combined with the bits on all the other disks. That wiki overview I linked explains parity and I suspect that video I linked does also though I haven't looked at it lately. As I said, parity is just an extra bit that allows a missing bit to be calculated from all the other bits. That is all parity ever is whether talking about Unraid, RAID, or just data transmitted on whatever. And parity can't help recover deleted files, for example. Parity is NOT A BACKUP. Parity doesn't even know anything about your files. It is just bits. It just allows you to reconstruct a failed disk. That will get you going again a lot easier and faster than getting everything from backups.

You will need a monitor and keyboard to configure BIOS so it boots the Unraid flash drive. Unraid doesn't really "install". The OS is unpacked fresh from the archives on the flash drive into RAM at each boot, and it runs completely in RAM. Think of it as firmware. You don't install drivers in Unraid but if you run a VM that uses the GPU then the VM will install drivers. Some dockers such as plex can also use GPU for transcoding or other GPU-type processing. There are currently 822 dockers and plugins listed on the Apps page. I'm sure there would be a few that would serve for cloud storage. I have NextCloud docker running on mine.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

The motherboard, CPU, RAM, drives, you can expect Unraid to know what to do with these. The GPU, it will use as a simple video output since it doesn't require any more than that. And you can run "headless" where Unraid is managed from other computers on the network through its webUI. That would allow the GPU to be used by dockers or VMs. yes, but no, parity doesn't contain any of your data. Parity is a very common concept in computers and communications. It is simply an extra bit that allows a missing bit to be calculated from all the other bits. If you lose a drive, parity allows it to be reconstructed from the data on all the other drives. Parity by itself can't do anything. Don't know if you started with the Unraid Basics playlist at that YouTube link or not. That is probably a good place to start: There is also the wiki Overview: https://wiki.unraid.net/UnRAID_6/Overview

yes, docker and libvirt img deleted/not enabled. Trying to clean up the setup so those things that belong on cache are all on cache. Then we can go from there.

Did you do this before posting those latest diagnostics? If so you must have done a lot more than that since your dockers and VMs are still enabled in those diagnostics. And your system share still has files on disk1.

Do you have backups? Parity (which you don't have yet) is not a substitute for backups. You must always have another copy of anything important and irreplaceable.

Simpler to just get us the Diagnostics. Diagnostics contains SMART for all disks plus many other useful things which give a more complete understanding of your configuration and situation, all in one neat ZIP download for us. . Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Go to Settings - VM Manager, disable VMs, then delete libvirt image from that same page. Go to Settings - Docker, disable Dockers, then delete docker image from that same page. Then post new diagnostics.

Normally you will want ssh (or at least telnet) available, but only on your LAN, not on the internet. Instead of OpenVPN you might consider using the built in WireGuard VPN: https://forums.unraid.net/topic/84226-wireguard-quickstart/

Plex should be fine. Port 22 definitely should not be open. Disable ftp. Your system share has files on disk1. Do you have any VMs?

I was talking about your shares. If you have the docker configured to write to a share then it will be using whatever allocation method the share is set for. Your docker won't even know disk1 exists unless you have mapped it. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. Also post the docker run command for the docker in question, as explained in this very first link in the Docker FAQ:

The end of your syslog Jun 30 10:54:24 unMHN sshd[15251]: Failed password for root from 87.251.74.48 port 46684 ssh2 Jun 30 10:54:24 unMHN sshd[15252]: Failed password for root from 87.251.74.48 port 46682 ssh2 Jun 30 10:54:24 unMHN sshd[15251]: Connection closed by authenticating user root 87.251.74.48 port 46684 [preauth] Jun 30 10:54:24 unMHN sshd[15252]: Connection closed by authenticating user root 87.251.74.48 port 46682 [preauth] https://www.abuseipdb.com/check/87.251.74.48 Also some ftp logins from various. Are these expected? Jun 30 10:33:26 unMHN sshd[10227]: Accepted none for ftp from 167.71.222.119 port 58092 ssh2 ... Jun 30 10:34:04 unMHN sshd[12055]: Accepted none for ftp from 68.183.180.132 port 59740 ssh2 ... Jun 30 10:34:31 unMHN sshd[13178]: Accepted none for ftp from 104.248.156.167 port 34192 ssh2

Most likely it is just the default highwater allocation method of the share you are writing to. Once enough data has been written to disk1 it will go to the next disk. The first highwater is at half-full.

Looks like you are being hacked. Close all ports immediately. Why is your server on the internet?

Looks like there are USB2 headers on the motherboard. Some people find they have issues with USB3 disconnects with some hardware. Doesn't seem to affect everyone.

Be sure to boot from USB2 port

Not correct. See here for the different btrfs raid configurations available: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421 Also, latest beta allows multiple cache pools.

Since you can't get diagnostics, post syslog. Do you have a backup of flash?

And that would also apply to replacing a data drive. Simply assigning the new disk to the slot is all that is required to get Unraid to rebuild to that disk, whether parity or data.

It might be possible to do basic NAS, but some things may not work well. Can you add RAM? Also, do you have a link to that specific wiki you quoted?

Diagnostics are compiled in RAM before saving to flash. And you don't have enough RAM.

Those diagnostics don't contain anything. Possibly your flash drive has disconnected. Be sure you are booting from a USB2 port.