Nirvash

I was watching this Jeff Geerling video, searched if unraid could run on that thing and found this thread... Looks like that ARM NAS hardware is finally starting to appear, but it's still very far to be consumer hardware.

Could this script be turned into a plugin? That way it could be downloaded through the CA store and have a convenient button to run it, or schedule it. I'd also add a log of locked files and maybe (if it's not too difficult) a log of files that have been tried to be modified but were locked by the plugin. And I was wondering... has this been "field tested"? With this I mean, did someone get a ransomware infection and their unraid data survived?

Yup, I would have used DFM initially but since it's too manual I decided to give unbalanced a go. I also find very weird that unbalanced is crashing the server. No, buy I ought to, really. I didn't think about running it so I'm going to do that right now! Edit: It passed the first tests but I'm going to let it run all night. Edit 2: More than 8 hours later, 11 test passed, I'm willing to call them good.

It just happened again. The computer has been working perfectly since friday, I've precleared a new drive, added it to the array and parity-checked without any issue, yet the moment I use unbalanced to "gather" a couples of shares into that drive, unraid reboots. This leads me to believe that unbalanced is the issue here, I'm certain about it. I never had any problem with my server until I start using that plugin. It cannot be Power related because I just have a 4670K and 6 drives with a 650W PSU, no GPU. It's plenty. And it cannot be thermally related because I've run way more intensive loads on it and it took it like a champ. It's also being watercooled. There must be something wrong with unbalanced that's not being shown in the logs. I believe it's time to open an issue in their repository.

It just happened again. New diagnostics with the syslog-previous included! unraid-diagnostics-20240126-2014.zip

Alright, thank you!! I'm going to enable the Mirror to Flash option and wait for a new crash.

Hello, my server has been rebooting by itself about every 2 hours, and I don't know why. This problem has been happening since my SanDisk Ultra Fit 32G died, and I replaced it with a random 2Gb USB 2.0 thumb drive. Could it be related? Also this is happening while I'm trying to unbalance a drive to remove it. Diags attached. unraid-diagnostics-20240126-1853.zip

Remember to do a backup first! docker exec -i postgres14 /usr/bin/pg_dumpall -U root > postgres-backup.sql

Thank you very much, I though as much but it's good to have confirmation.

Today I got an MCE event and the "Fix common problems" suggested me to post the diagnostics. I tried to look at the logs myself and there are 3 lines that contain the MCE string but they don't make any sense to me. Thanks for the help! unraid-diagnostics-20231129-1209.zip

My Warrior is always stuck at uploading, and never completes any task. I'm using atdr.meo.ws/archiveteam/warrior-dockerfile:latest without any changes. Edit: https://github.com/ArchiveTeam/seesaw-kit/issues/145#issuecomment-1728304787 Servers are full.

Output: nslookup homeserver Servidor: pi.hole Address: 192.168.1.20 Nombre: homeserver.casa Address: 192.168.1.215 It's as I was saying in the previous post. .215 is not the correct IP! Thank you very much, I didn't know about nslookup. I'll keep it in mind for the next time. Edit: Yes, that was it. I changed my Unraid hostname and everything works as normal again. Thank you very much, @Mainfrezzer.

I realized that my (stopped) LinuxMint VM (the one that lives in Unraid) was also named Homeserver. Maybe that's the issue, a good ol' conflict. I'm going to try to rename unraid's shares to just unraid and see what happens.

I've been using unraid for a while now and so far it's been working good. I have my shares and I could access them just fine at \\HOMESERVER. Context bit: Today I added drives to the array and to my cache pools, so before I did that I had to disable VMs, Docker, move everything out of the cache and re-enable it when I was done adding drives. My issue: And now \\HOMESERVER is not accessible on Windows (Android and a Linux Mint VM on VMWare finds that path). If I want to access my shares I have to either use \\homeserver.local or the IP, \\192.168.1.130. Also, on Windows, if I go to the Network "folder" in the Explorer, it finds my old WD Nas as "NAS", my router and other stuff, and all is reachable, unraid is shown as "HOMESERVER" but is NOT reachable. The other two paths I mentioned earlier are not discovered. Why is my SMB share not working anymore on Windows? This seems entirely a Windows problem because as I said I can access shares from other non-Windows OSs. EDIT: By the way, there's a PiHole on my network acting as a DNS. homeserver-diagnostics-20230919-2205.zip

I feel that, even though I stopped a file transfer between a SMB share and a local share, the transfer is till happening. I see both disk activity and 3 rsync processes still running even though I cancelled the file transfer: Attached are the diagnostics. Another "issue" I have is related to the previous post. According to this post, the scheduler functionality doesn't really schedule anything, I feel like the name is a bit misleading, as all it really does it queue a list of jobs, but you can't really schedule it with trigger like time, array status, disk activity or something like that. homeserver-diagnostics-20230915-1825.zip