Southweave

Follow up on this topic. I changed a lot of settings ~1 month ago and I haven't had any issues since then. Actions I took: Deleted preclear plugin (I don't think this had any effect) Deleted Tips & Tweaks plugin (I don't think this had any effect) Deleted Nerds plugin (I don't think this had any effect, it wasn't suppose to be used anyways) Dynamix File Integrity I set to disabled: "Automatically protect new and modified files:" Allowed incremental (not only full and differential) backups with Macrium Allowed writing backups to cache drive This couldn't be done with Acrium because they file into a single large file, while Macrium creates a new file for every backup I believe the Dynamix File Integrity changes or directing backups to cache drive fixed the issue. But because I decided to go nuclear and try everything once, then I can't be sure.

I compared our testparm results and there are only a few differences: You seem to have syslog on Your casesensitive is Yes while mine is Auto You show dot files Your max log size is 5 000 while mine is 10 000 And some naming differences Doesn't seem anything substantial. Must be something else... It does seem like finding a way around the problem would be quicker by now... Thank you for your help!

Yes, if the backup fails then you can repeat it by reattempting. I'd guess that the odds of second backup failing is ~50%. Usually the process to reattempt: Check if SMB lock is still active (smbstatus) If yes, then kill the process (kill {PID}) Restart the backup Fails? Start again from #1 No, but that's a good suggestion. But because the odds of second backup also failing are ~50% it would take a while to actually conclude that it works. Because it would take a while to actually validate this I think it would be simpler for me to simply revert Unraid to previous version. However if reverting proves to be okay then I'm still not any closer to the actual solution. EDIT: The backup has failed the whole day and I just attempted to backup to another drive on the PC itself. It was successful. Correct, first full image backup and then differential image backups. Both types fail I'm also going to include "testparm -v" global output, can you please verify this against yours or just check it over? It is entirely possible I've changed something in the bast when attempting to get 10Gb connection between Unraid and other systems

While it does seem logical that a local file is blocking the actual backup, I believe that's not the case. If I remember correctly then Acronis logs stated that there was an error locking SMB share file (because it was already locked by the same process) Macrium states "An unexpected network error occured" Today for the first time I also got an error "Backup aborted! - Open file failed - \\SMB_SHARE... - Error - The process cannot access the file because it is being used by another process This probably occured because the 09:00 backup failed and left the SMB locks up I can imagine how the issue could start occurring at the same time I updated Unraid and cause the issue, but I believe it would be a leap - and for two PC's to start having the issue. If the consensus is that it's not my Unraids configuration problem, then I'll just try to revert back to 6.10.3 and run it for a month again. The probability that the issue occurs within a month is high if the cause is not my Unraid's configuration. Also Acronis & Macrium don't seem to care about locked files. I mean you can literally restore your computer from the image. I don't know what black magic is going on there.

While I do agree that it's not Unraids fault I do believe it has something to do with my specific configuration. I just don't know what and I don't have any more ideas how to debug this mess, thus why I created this topic. The reasons why I think it's related to my Unraid setup: The issue started occuring on 6.11.5 If I revert to 6.10.3 then the problem does not reoccur (but because it's not consistent I can't be 100% sure) The issue occurs on both Windows 10 and Windows 11 The issue occurs with both Acronis and Macrium Reflect While that doesn't necessarily mean it's my Unraid setup which causes it, it sure does seem like it. But of course it's not the first time that even though everything seems to point at Unraid - it's not actually Unraid's fault.

Sadly Macrium Reflect logs don't show the time of exception (or anything useful at all). However the backup start time is 13.02.2023 10:43:56 I guess the backup lasted couple of minutes at best. The temporary file is also gone by now so I can't verify last modified date time.

Sadly it is already disabled and has been for over a year. Settings are also visible in pictures, i'll remove them from hidden content to make them more visible

Description After updating Unraid from version 6.10.3 to 6.11.5 windows backups occasionally fail, which root cause seems to be that SMB locks are not properly handled. When backing up the required disks are all spun up and transfer works properly. Data is transferred to Unraid and everything is fine until the end, there something goes wrong and the process never finishes. For example today it backed up 17GB of data but the file has suffix .tmp which will probably be deleted the day after tomorrow. I never had the issue on 6.10.3 and if I reverted to 6.10.3 then problem didn't reoccur If I kill the process which locks SMB lock then sometimes backup works sometimes it doesn't. There have been times where the problem didn't occur for a week and then there have been times where the whole week backups failed. Pictures of smbstatus, smb settings and tips & tweaks have been included. smbstatus picture shows the locked file which shouldn't be locked anymore (the process already failed) Also I included server diagnostics. The server was restarted this morning after which I attempted to backup once again. I'll gladly answer any questions, this problem has been driving me nuts Systems Unraid Version 6.11.5 Supermicro X9DR3-F Intel E5-2680 v2 (2x) 40Gib DDR3 ECCS memory 40Gib NIC Windows #1 Windows 10 10Gib NIC Intel system Windows #2 Windows 11 10Gib NIC Intel system Backup software: Acronis Macrium Reflect I initially used Acronis however I thought the issue was Acronis specific and migrated to Macrium Reflect. Macrium reflect has the same issue What I've tried: Enabling & Disabling SMB Multi channel Resetting Tweaks And Tricks plugin settings Removing all custom samba configuration (which included RSS & Multi channel prior to update) Changing backup software Switching backing up to rotational, as in one Windows systems backs up a day so there isn't a possibility of a conflict Creating separate Unraid users for backing up Changing "ulimit -Hn" and "ulimit -Sn" to 80000, it used to be 40960 Turn SMB share to public (not hidden) Googled the same issue over and over within last month with different wording and attempted to find same issue described. I couldn't find anything that would help me Definitely something more Backup schedule Both windows attempt to backup at 09:00, if computer is not on then it is initiated on boot Windows #2 is usually always on at 09:00 so that's when it backs up Windows #1 is usually not on at 09:00 and usually backup occurs later on in the day Both Windows systems have issues This issue has occurred for a while now and if my memory serves me right then it occurred the very day I upgraded to 6.11.5 Unraid now has SMB version which supports Multi Channel and with multi channel there's also a bug: https://bugzilla.samba.org/show_bug.cgi?id=11897 It seems like similar issue but I am not knowledgeable enough to Assert that it has the same root cause How to fix it Why does it occur to me server-diagnostics-20230213-1110.zip

Alright, thank you for helping. The parity rebuild was successful and right after completing I let it check the parity, everything seems to be fine. I'll swap out the power cable the next time I have to open the case. Thank you very much for your assistance.

Thank you for the response. If this will happen again, do you think I can use warranty to replace the disk? Because it passed the SMART test I am not very confident that I can get a replacement

Hello, Today (12.07) around 3.42 am my parity drive got disabled. (WD red 3TB) Other disks were not affected by it so no data was lost and the drive itself seems fine. I ran short SMART test and the extended one and both of them passed. There lies the problem, I can't seem to figure out what happened and why the drive got disabled (except that it couldn't be written on?). I will include the server-diagnostics (hopefully nothing private is there) and the mark to look at is 3.42 am, 12.07. I tried searching for the errors using google, however I don't really know exactly what to search for so here I am. Currently the drive is in use again and the parity is rebuilding without any complications. (about 5 hours till completion) The server is currently not UPS protected so maybe that could have something to do with it, however in the past 2 years I've had 1 outage, which wasn't notified about. And obviously the power did not go out, maybe just a drop in supply? Hopefully someone can shed light on this and help me out. Information about the system: Motherboard: Supermicro x9dri-f CPU: Dual E5-2620 V1 PSU: Seasonic M12II EVO (1 year old) Affected HDD: Western Digital Red (3TB) (sata 2 port) WD red is in the same PSU cable chain with 2 seasonic drives, none of which were affected. server-diagnostics-20180712-0650.zip

Update 1: I did some testing and I found that if I start unraid on GPU then the system shuts down properly. Is it a known problem or is there a way to fix it? I'd like to have VM and unraid terminal open at the same time.

Hello, I just recently acquired a new motherboard and CPU for my unraid setup and after upgrading unraid won't shut off. Whether I use power off function or the sleep plugin neither gets past "umount: /boot unmounted" text at shutoff. Hardware: Processor: Intel I7 8700k Motherboard: Asrock Z370 Fatal1ty Gaming K6 Graphics: AMD HD7970 Memory: 16GB DDR4 3000MHz Storage: Single SSD Four HDD's Previous hardware: Processor: AMD Ryzen 1600 Motherboard: Gigabyte AB350M Gaming 3 The issue is on both versions 6.4.0 and 6.4.1. Basically currently I am unable to shut off the unraid without having to smother it at the end. The unraid is booted on the IGPU and does not use the GPU (If that matters) The diagnostics are taken after booting up again so I am not sure if it holds any valuable information. It was stuck in that particular screen for over 4 hours (at night) so it won't shut itself off eventually... I will try to respond as fast as possible with any information requested. I currently do not know what else to add. Thank you for your time. server-diagnostics-20180208-0823.zip

I am having a problem with preclear- today I purchased 2 new disks and I can't clear either one of them. On the Script line it says following: "gfjardim - [strings] Please install it and try again. Line 49" The system is Ryzen 5 1600, Gigabyte AB350M gaming 3, 16GB ddr4 ram, WD and Seagate drives. I've tried to reboot and reinstall several times, nothing has worked. OS version is- 6.4.0_rc10b

Aren't all threads passed through as 'real' cores though? That's what XML says. I have always passed through 3 'real' cores and 3 'hyper' threads and I have yet to see any downside to it.

As much as I've read then people say that KVM does not scale well with core count. I personally haven't seen an issue with passing more cores than 4. About RAM- it's basically however much you can and want give the VM, I give 6GB currently (16GB total in system) and I will give it more later after I've made sure everything is working just as a normal PC. If you need better performance then don't forget to add <emualtorpin cpuset='#-#'/> # being the core(s) you want to use to emulate your VM cpu. I use last 6 cores in VM and two before that for emulating. -> (6-11) = VM & (4-5) = Emulator TL:DR - 6 Cores seems to be the sweet spot for my Ryzen and choose however much RAM you think your VM needs. (Just leave some for Unraid also).

Update on the NPT patch: Everything seems to be working great! No more spikes, 3Dmark score is just around where it should be compared to other peoples scores and games run as intended. If anyone is still holding back on buying Ryzen then the time to buy is now. From the top of my head the only reason not to buy one is ECC memory but AMD performance killing bugs are now fixed. Now I only wish I would've gotten r7 1700 instead of r5 1600. Thank you LimeTech for releasing the fix so fast after it was discovered!

Thank you for giving us the patch so fast. I was about 2 weeks off from buying Intel x299 chipset and I even had everything chosen but luckily the fix came. I will switch my main pc for the server today (I use Ryzen on my main system because of the NPT bug and Intel as server) so once the the next rc comes I can give feedback. The NPT patch is out for unraid! Everyone who worked on this patch thank you very much, you are heroes!

Well, lets just hope that they will make AMD (Including TR and Ryzen) owners happy and manually include the patch then. 6.4 is still in beta so it would be a good time to include it. At least that's what I'd think.

Can't they manually override the code or is it too much of a hassle? (I have never worked with kernels)

Is it possible to manually fix that issue on unRaid? As in can I go into the proper file and edit it to fit the description of this post: https://marc.info/?l=kvm&m=150891016802546&w=2 (The same topic that Tuftuf linked) I am inexperienced with linux so I am unable to find the proper location for it and I know even less about the KVM setup. It's only recently that I started tinkering around with Linux based systems. I don't believe that we will get this fix in the current unraid version so maybe we can make due with it ourselves? I'd really like to get back my Intel CPU for my main system and use Ryzen CPU for the server once again. Edit #1: I just realized that it requires editing kernel? If so then I will just wait

I have the same problem. I reverted back to the previous version and it started working again. Reinstalled FileBot using Docker Hub URL: https://hub.docker.com/r/coppit/filebot/builds/b3qovrz4qankwgbssrzgamm/