Nirvash

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

Hi! The user manual pdf in the first posts is unavailable. Can you fix it, please? I'm trying to figure how what the job / scheduler does and how it works (how to actually schedule a job) and maybe that pdf explained it. Basically my goal is to start a copy job after the current disk rebuild is completed, as I don't want to tax the system too much by doing multiple stuff at the same time.