MowMdown

Make sure you get a fan for that HBA, they run hot and are meant to be installed in server chassis with high pressure airflow. They cannot be passively cooled.

Give the tailscale plugin a try. Unraid's wiregurd VPN is a bit rudimentary (albeit it does work for me)

That's probably more/less due to the cpu driver in the kernel controlling that. you are disabling the cores in the BIOS right? You're not doing that in urnaid are you?

Yes

Probably should run a 24 hour memtest from the unraid boot menu. RAM can cause crashes. Other faulty hardware can too, like a bad PSU. You basically erased the "map" that pointed to the data. There is no way to recover this map, you will instead need to use something like UFS explorer file recovery software to see if you can recover any data. The trial is free and will show you what may be possible to save. Parity is not a backup. It's a real-time computation of your current drives. Anything you do to your disks, parity is updated along with it right then and there. Parity can only save you from a disk failure, not data loss/erasure/corruption.

SWAG is the equivalent of Nginx Proxy Manager but more sophisticated than NPM and no GUI.

That's because you can use the remaining space as a data partition/pool storage. Whereas you couldn't really use the USB for anything other than booting. Most users will take their two 1TB SSDs and carve out a small 4-8GB boot partition leaving 990+GB of usable space rather than dedicate two drives to only booting unraid.

Appdata backup takes /boot and makes a copy(archive) of it. It doesn't care nor needs to care about filesystems or anything else. And the only thing you actually need to backup is the /boot/config folder and /boot/extra (if you have this) everything else on the boot drive(s) is replaceble by making a new install, to which you then just need to put your backed up config (and extra) folder back in place.

No. SWAG is Nginx Proxy/Webserver + Fail2Ban + LetsEncrypt rolling into a single application. Cloudflare is a CDN+DNS provider who has some small reverse-proxy like features like CF Tunnels. However you have no local control over it. You need Nginx to host a webserver from your machine.

Like Itimpi said, /mnt/user0 is a special FUSE path that just represents all your Array Disk shares & data w/o the cache(pools) data being included. You should generally ignore it unless you have a special use case for writing to the array only manually.

Yeah it was just something to try as a way to troubleshoot if something was keeping the disk from unmounting. Sorry to hear it didnt work.

You would want to host it by using SWAG or similar or even in a VM to further isolate it from unraid

Looks like root:root for the owner:group on the share. you will want to change this to nobody:users instead. You can do it from the built in file-manager or typing in chown nobody:users /mnt/cache/Peliculas in the terminal.

unraid no longer runs on c0/t1. it should be safe to run all E-cores

open terminal and type in lsof /mnt/cache/appdata and it will spit out a process, then type in kill -9 <process_ID> replace <process_ID> with the actual number. might have to repeat this depending on how many processes are accessing appdata.

You can always go create a feature request

Just curious what does windows device manager show when the usb is attached to the windows pc?

I just use the appdata backup plugin to make scheduled backups of my boot device. I then just copy the archive somewhere remote.

Add new disks to the system, mount them with the Unassigned Devices plugin. Format disks and copy (not move) all data from array disks to the unassigned devices plugin. I would suggest using another plugin for this called "Unbalanced" Remove all disks from array, run a new config, and assign new disks (that contain the copied data) to the disk slots. Build parity if you are going to have parity. I think this way might be a good approach because your old array disks will still contain data in the even you need to add them back in in-case of a new disk failure before the new parity is finished syncing.

Your old Disk11 might actually still be healthy but due to the read errors (likely a faulty cable/HBA overheating) it was disabled by unraid. Hopefully you still have the disk and can mount it as an unassigned device and run an extended smart test on it to see what's up once you get your situation stabilized.

you will need to delete the folder /mnt/cache_two and then reformat. unraid is weird and will not finish the format if the folder exists prior to the format. (or use a different name other than "cache_two") May 18 13:23:20 Tower emhttpd: shcmd (4096): /usr/sbin/zpool create -f -o ashift=12 -O dnodesize=auto -O acltype=posixacl -O xattr=sa -O utf8only=on -m /mnt/cache_two cache_two /dev/nvme0n1p4 May 18 13:23:20 Tower root: mountpoint '/mnt/cache_two' exists and is not empty May 18 13:23:20 Tower root: use '-m' option to provide a different default May 18 13:23:20 Tower emhttpd: shcmd (4096): exit status: 1

It is a point release, edge cases like yours might slip through the cracks... The solution is a easy fix. My advice is wait for the X.X.1 update if you really want to be safe.

Something to keep in mind, if you dont have active cooling on your HBA it could also be overheating, these things are meant for a server chassis with high airflow and if you are running one of these in a consumer case, it will need a dedicated fan for itself.

Sounds like a cabling issue honestly. Bunch of your disks have UDMA CRC errors which indicates a faulty connection between he disk and the CPU. Double check all the cables are connected properly. Please reboot post new diagnostics. the syslog is 0bytes and the previous syslog is full of disk read errors on disk11 (presumably the old one)

worst case is you delete the network.cfg and network-extra.cfg from the USB and reboot unraid