XiMA4

I have solved my problem, so that ends the question. First I moved my Syno server to a different subnet and one problem was solved, but the intermittent disappearance of the user directory as described here was still happening, so I moved my array to another server, TueNAS Core. Now the problems are gone and hopefully won't come back. Now my unRAID only works for docker containers. upd. I shouldn't have hoped for anything. Some problems remained though. Several times I noticed that I could not access the web interface. If you leave it for a while, the control comes back. Honestly - I'm getting tired of looking for solutions to problems, 6.13 is coming soon and new problems. The system should just work for me, but in this case I am working for it. I'm moving the main docker containers to other servers. UnRAID will be a test environment, I will wait for the developers to fix the bugs.

My unRAID is running ESXi, so not a problem, I'll just have to take the time to reconfigure. Before 6.12.x I had a very stable server, I restarted only when I updated OS or hardware, extremely rarely when there was a power outage. After I bought a UPS and upgraded to 6.12. I guess you are right, it would be smarter to use a file server (OMV for example) and the second part of unRAID. There are various recommendations to fix the problems (I have another one besides this one), but many of the recommendations boil down to disabling something. Of course, if you disable NFS, and at the same time SMB, you disable XMP, the problem will be solved, but who needs such a NAS, where for stability you need to degrade the performance or even give up the functionality. I really like unRAID, but it turned out that stability is more important.

Thank you! I confirm, it works. but the command in my case was "fusermount3" (I have 6.12.6), maybe restarting the OS will be faster I'm so sick of this problem. If I'm not home, all users suffer and wait for my return. In my opinion, this is unacceptable for NAS. I'm seriously thinking about changing unRAID to something stable. Or split my setup into two parts, one unRAID just the file server and the other unRAID for add-ons, docker, etc. But I'm not sure it will work consistently in this case. I'm very disappointed with version 6.12.x

thanks for the reply This is not an issue, but a consequence of the issue, and I can't figure out the cause. It happens only once when I turn on the device, no matter Synology or unRAID. If I turn it on automatically according to Syno schedule, then unRAID freezes, then I turn off unRAID and start it up, it freezes again. If I leave both running, the problem does not recur. Something burns up all the memory, the system closes some process, from what processes are closed and depends on whether the system will work further and when the control will return, it happens that 10 minutes, it happens that an hour, and it happens that the system hangs intentionally. On Syno I did not make any changes, unRAID is updated - hence the problem is in the update.

syslog-10.1.1.20.log I tried repeating the situation during the day, just manually running my Syno. The unRAID hung as expected. I rebooted it and after about five minutes it booted up, I started the array and almost immediately lost access to the GUI, I should note that docker has no effect on the situation, I had previously tried disabling docker autostart but I still lost control of the server after starting the array. I couldn't connect via ssh either, but the server was pinging. After about ten minutes I got control back. Ten minutes is a long time, during this period of time many network connections are dropped and Plex clients' buffers are emptied.

Hey, unriders. My problem is that the unRAID server freezes after the Synology NAS is turned on. It's just mind blowing. My setup: Syno NAS is just a backup device, automatically turns on every night at 2:10 and turns off at 9:10. The unRAID server has been running 24/7 for years. Both servers are on the same subnet. Normally I don't upgrade to a fresh release but wait for .1, in the case of 6.12 I upgraded later, surely .4 will be fine, I thought. But that was a mistake, after upgrading from 6 .11.5 to 6.12.4 I started having 40-50 minutes of freezes at night. I started experimenting with network settings (bridge, macvlan and stuff). But periodically the freezes would happen, it wasn't every night, but several times a week the CPU load would increase to 100% and access to the GUI would become very difficult, but would persist. It was hard to find a reason why this was happening, it was always at night and not all the time. After upgrading to 6.12.5 and then 6.12.6 it got really bad. The server would always stop responding, even over ssh, after SynoNAS automatically started. Does anyone have any ideas, I would be grateful for any hints. I had to temporarily disable the backup server. unraid-diagnostics-20231202-1249.zip

I have a similar problem, not the first time. The server freezes after midnight. CPU is consuming 100%. I can monitor the work of unRAID virtual machine. After about an hour it lets up. ver. 6.12.4 / Docker Image btrfs / ipvlan

Exactly! It was turned off. Now I am satisfied. Great plugin! Thanks for the help.

Disastrously low write speed is it ok for iSCSI Target on unRAID? I am using FileIO 300GB in Array.

Wow! Works! Many thanks, didn’t know it needed to add the name of the initiator. This is not required at Synology.

Thanks for the answer, how to do this? Or where can I find information about this?

I created initiator and LUN from fileIO, but client on macOS asks for CHAP details, when I enter username and password from unRAID, I get a message that the password must be 12 to 16 characters. And it is impossible to disable it. client: DAEMON tools macOS: 11.5.2 (20G95) unRAID: 6.9.2 When I create such an initiator on the Synology NAS, everything works without any problems.