oliver

So I have an old mac that I just finally replaced with a brand new one. On the old mac this command worked to prevent writing of .DS_Store files: defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true On my new mac running Tahoe, even though the boolean is true, the OS still is attempting to write the file and it's failing because I have it veto'd in unraid. In MAC logs I see: 2026-05-13 19:00:31.133147-0400 0x3a61a98 Error 0x0 41442 0 Finder: (DesktopServicesPriv) [com.apple.DesktopServices:CopyEngine] Error -8062 at path: /.nofollow/Users/user/Desktop/<private>/.DS_Store on write 2026-05-13 19:00:31.133551-0400 0x3a609cc Error 0x0 41442 0 Finder: [com.apple.Finder:General] Task::GetStandardErrorMessage error=-8062 operationType=2 '.DS_Store' Unraid settings (7.2.6) are below. I set this many years ago so might be time to update them: Enable SMB: Yes (Workgroup) Hide "dot" files: Yes Enable SMB Multi Channel: No Enhanced macOS interoperability: Yes Enable NetBIOS: No Enable WSD: Yes WSD options [experimental]: veto files = /._*/.DS_Store/ aio read size = 1 aio write size = 1 strict locking = No use sendfile = No server multi channel support = Yes readdir_attr:aapl_rsize = no readdir_attr:aapl_finder_info = no readdir_attr:aapl_max_access = no fruit:posix_rename = yes fruit:metadata = stream Presumably I can remove the veto and then everything will work. But I use something in house to index my array and then I have to deal with the crapload of files that I really prefer not to exist to begin with.

I have 18 drive split out amongst two power supplies but it's just not great, I get random drops. I was looking to see if there is any consumer grade PSU that can handle it, primarily the voltage. Now here is what chatgpt has recommended spec-wise for my hardware: Components Component 12V amps Watts 15× Seagate ST8000DM004 30A 360W 3× WD 8TB 5.4–5.7A 65–69W LSI SAS3008 HBA 1.0–1.5A 12–18W 5 fans 1.0–2.0A 12–24W i7-6700K CPU peak 8–10A 95–120W Motherboard/RAM/misc 2–4A 25–50W TotalsRequirement Estimate 12V current needed ~48–53A 12V wattage needed ~575–635W Total PSU size recommended 850W bare minimum, 1000W safer, 1200W ideal Now, im fine with the wattage but the whole 12v rail thing confuses me, especially because I think that is what is causing me issues now. Can anyone recommend a PSU that has strong rails and wont randomly drop drives? It is reccomending Corsair RM1200e 1200W PSU but I really wanted to get some non-ai opinions.

Most of the time my server is hidden away so I don't know how long this has been going on for but I noticed an on-again off-again noise from a hard drive. If I run a smart (short) test, it happens during the test, although not the entire time. Drive itself seems to perform as normal when accessing files and writing to it. The smart report itself looks good but the sound is not encouraging. I've attached the smart report and the audio of the drive noises. I have other identical drives that don't do this. It's late at night right now but tomorrow I will investigate for vibrations and such that could be causing it but I wanted to get another opinion on if this noise sounds like the drive itself or a vibration from it. output.mp3 SMART.txt

Hi, i've seen this one or twice when booting my array. I get this notification event: Event: Unraid Primary_cache disk message Subject: Warning [NAS] - Cache pool BTRFS missing device(s) Description: NE-1TB_2280_0025695000052 (nvme0n1) Importance: warning But it looks fine on the device page: Logs for the drive (full diags attached) text error warn system array login Mar 20 17:15:13 nas kernel: nvme0n1: p1 Mar 20 17:15:30 nas emhttpd: online: NE-1TB_2280_0025695000052 (nvme0n1) 512 2000409264 Mar 20 17:15:30 nas emhttpd: import 32 pool device: (nvme0n1) NE-1TB_2280_0025695000052 Mar 20 17:15:30 nas emhttpd: read SMART /dev/nvme0n1 Mar 20 17:20:57 nas emhttpd: shcmd (377): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards Mar 20 17:21:02 nas emhttpd: import 32 pool device: (nvme0n1) NE-1TB_2280_0025695000052 Mar 20 17:21:06 nas emhttpd: #011devid 1 size 953.85GiB used 2.03GiB path /dev/mapper/nvme0n1p1 Mar 20 17:21:46 nas kernel: block nvme0n1: the capability attribute has been deprecated. Press ANY KEY to close this window BRTFS stats: root@nas:~# btrfs dev stats /mnt/primary_cache root@nas:~# btrfs dev stats /mnt/primary_cache [/dev/mapper/nvme0n1p1].write_io_errs 0 [/dev/mapper/nvme0n1p1].read_io_errs 0 [/dev/mapper/nvme0n1p1].flush_io_errs 0 [/dev/mapper/nvme0n1p1].corruption_errs 0 [/dev/mapper/nvme0n1p1].generation_errs 0 [/dev/mapper/nvme3n1p1].write_io_errs 0 [/dev/mapper/nvme3n1p1].read_io_errs 0 [/dev/mapper/nvme3n1p1].flush_io_errs 0 [/dev/mapper/nvme3n1p1].corruption_errs 0 [/dev/mapper/nvme3n1p1].generation_errs 0 Is this safe to ignore or could it be a sign of an impending failure? nas-diagnostics-20260320-1721.zip

this seems nice, i do wish there was the ability to recursively go into directories though, trying it out.

bumping this as i also noticed this in my log. @bmartino1 is not understanding the problem correctly. it doesnt seem to always occur. most of the time email notifications go to where they are configure correctly. but today, while upgrading to 7.2.1, i noticed it was indicating send to [email protected], which is NOT configured on my side. if i had to guess, its a non-gui setting somewhere for the root user?

the interesting this is it's doing this even without a switch in the middle. i tried connecting a different NIC to both computers and going NIC -> NIC with no router/switch in between and it stills tends to drop

i did try NFS as well and saw similar behavior, it eventually dropped the connection and FFS also errored out. i even tried rsync instead of FFS and unfortunately the same behavior. it just freezes when the error happens instead of gracefully reconnecting. i can't trace down WHY this is happening, is it just stressed under constant load?

Hi all, im having problems getting a reliable SMB connection. I have two unraid servers, NAS and NASBACKUP. I am trying to move all data from NAS -> NASBACKUP by mounting the backup server as a SMB mount on NAS. Then using FreeFileSync docker to move the data. There is a large amount of data to move, about ~100 TB. The problem is the connection is not reliable. I get random CIF drops all the time like this: Nov 14 16:51:58 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL sends on sock 0000000032302d62 stuck for 15 seconds Nov 14 16:53:00 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL Send error in SessSetup = -11 Sometimes I can go 24 hours without an error, sometimes I get them within minutes of mounting. I can't tell what server the problem lies in, but i've attached diags from both of them. Even giving each server a separate NIC and directly attaching them gives the same behavior. Unfortunately, FreeFilySync does not gracefully recover from this and requires manual intervention every time this happens. It's greatly slowing down my backup progress. nas-diagnostics-20251114-1653.zip nasbackup-diagnostics-20251114-1654.zip

HI, I have two unraid servers, NAS and NASBACKUP. I am trying to move all data from NAS -> NASBACKUP by mounting the backup server as a SMB mount on NAS. Then using FreeFileSync docker to move the data. There is a large amount of data to move, about ~100 TB. The problem is the connection is not reliable. I get random CIF drops all the time like this: Nov 14 16:51:58 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL sends on sock 0000000032302d62 stuck for 15 seconds Nov 14 16:53:00 nas kernel: CIFS: VFS: \\NASBACKUP.LAN.LOCAL Send error in SessSetup = -11 Sometimes I can go 24 hours without an error, sometimes I get them within minutes of mounting. I can't tell what server the problem lies in, but i've attached diags from both of them. Even giving each server a separate NIC and directly attaching them gives the same behavior. Unfortunately, FreeFilySync does not gracefully recover from this and requires manual intervention every time this happens. It's greatly slowing down my backup progress. nas-diagnostics-20251114-1653.zip nasbackup-diagnostics-20251114-1654.zip

Hi, so im trying to move files off multiple drives with the goal of ultimately removing them from the array entirely. 1. I need to run unbalance to move files off 2. I need to prevent new files from being to said disks written until #1 is complete. My question is regarding how to use these settings while the above steps. Inside of the share settings, theres these two options: Included disks: Excluded disks: So it seems like I can accomplish what I want either way? I still want the files to still be accessible while this is happening, just dont want new things added to them.

was hoping to avoid an unclean shutdown but did it and the array is up again, i'll have to try to setup a syslog server. hoping it was just a random gremlin, but there were no changes made to the array. thanks

I get a connection refused via ssh, webgui, shares. However, even though my shares are unavailable, my docker containers seem to be working, at least some of them, including plex. But my VM's are down. After checking my pikvm, I see this on the screen: I can't even seem to login from the console, typing root won't take me to the pass prompt. What could cause even the console itself fail to login? Attached screenshot

thanks, ill look at it, a client side index is interesting. i have a massive array and think server side would be nice. im gonna fork the repo and see if i can get it to work with an everything database file serverside, which is basically a csv file for all files. and search that instead, it would be nice

how does search work, index or realtime?

I seem to randomly get this error when writing files to the array. As far as I can tell there is no problem with the file itself, it writes correctly and reads correctly but im curious if anyone has seen this before. Googling around hasn't helped much. I am writing to a cache drive, i've never seen this when mover invokes. I tried Tools-> repair permissions but I still sporadically get the error. I'm on 6.12.14. It seems the new file permissions are the username of my SMB account, shouldn't they be 'nobody'? EDIT: I don't think the above is the issue, it seems all new files I write are using my smb username. Still not sure where this error is coming from since it's sporadic.

autofan seems to be stuck running, how do i stop it? i've disabled it in the ui but it remains running. i also tried this UI command but it won't stop

ugh, i give up on this for now, it's so weird. After doing a bunch of testing and downloading, I found Brave is the only browser I can reproduce this with, which is what I use for my desktop/laptop. I installed Chrome itself and could not reproduce. I then installed two virtual machines with fresh linux/windows and installed Brave on those and could NOT reproduce the issue. such a bizarre bug

Can you try the steps below? (additional step added) i can 100% reproduce this across 2 separate arrays and 3 different computers. 1. Go to Main 2. Click a disk 3. Click on a different tab, e.g. 'Attributes' 4. Click back button if you can't do it once, try doing it a few times but it's very important to change the active tab from step 3 in between tries. that seems to trigger the glitch the most.

if copying packages to /boot/extras/ is complicated, you have no business using something like nerdtools to begin with

is the nerdtools plugin even needed if you don't use the default included packages? it's just a matter of finding compatible slackware packages and dropping them into /boot/extras right?

i can reproduce this bug 100% of the time on chromium based browsers. 1. Go to Main 2. Click a disk 3. Click back button There is some kind of 'refresh' that happens and it disappears. I see the same refresh on firefox/webkit but it doesn't disappear. interestingly, even clearing cache will not fix it once this happens. if you wait on the blank page a few minutes, it just comes back.

just bought a brand new and more reputable new power supply instead of reusing another older one. ordered a new sas card as well for good measure. i just dont understand why it's the same drives that remain problematic. smart tests are all good though. i wonder if the physical drive connector might be damaged. re buiild: i just unassign -> start array -> stop -> resassign and that should rebuild parity?

woke up today to see a parity drive dropped out. looks like another random power/data failure? sigh, it ran for a good week before just resetting. i did notice this happened when mover was running, which i guess makes sense since there was writing happening is there any way to see from logs if it's data vs power issue? i suppose now a parity rebuild is required nas-diagnostics-20241221-0546.zip

all went well but i got an interesting notification after shutting down the system to remove the old drive and rebooting. it sent me a notification saying a drive drive is missing from another, unrelated pool although array shows everything there. everything appears to look fine in the ui though. notification received: drive seems fine in the pool: diags attached but i dont see any errors in the logs or ui missing cache pool nas-diagnostics-20241217-2303.zip