Baregills

Just a note to confirm that the problem was indeed Mac related, although I was unable to find any reason for the dropouts, but within a day or two the problem became much more frequent and also began to affect USB connected devices. This made Time Machine unusable once again because I had set it up on a USB disc which was disconnecting every few minutes. I had to stop taking back ups, but today, for no apparent reason, the fault has gone away and I am again able to back up to the array. I wonder if the source of this problem is Time Machine but I am at a loss to understand why it would cause a transient issue when there has been no change made to the OS.

You are not wrong. I'm still having dropouts. I'm beginning to suspect the Mac is the problem. Thanks again for your input.

So I just set the share option to yes from auto and there is now a share.cfg file on the flash drive so that's something. It contains the following:- # Generated settings: shareDisk="yes" shareUser="e" shareUserInclude="" shareUserExclude="" shareUserExclusive="no" shareSMBEnabled="yes" shareNFSEnabled="no" shareNFSFsid="100" shareInitialOwner="Administrator" shareInitialGroup="Domain Users" shareCacheEnabled="yes" shareCacheFloor="2000000" shareMoverSchedule="40 3 * * *" shareMoverLogging="no" fuse_remember="330" fuse_directio="auto" fuse_useino="yes" shareNOFILE="" shareAvahiEnabled="yes" shareAvahiSMBName="%h" shareAvahiSMBModel="Xserve" I hope that will have some effect but even if not, thank you for your help. I really appreciate it.

No. Neither of those files are on the flash drive. I'll do some digging on those and investigate the Samba errors too.

My apologies. I replied using my phone and it's not here! The connection drops out and the server disappears from my desktop but when I look on finder it is connected and when I double click it in the finder it reconnects. At no point does the server actually stop working as far as I can see,

Thanks for the response. I have replaced the appropriate cables but it hasn't helped.

I have always had the odd server dropout but have lived with it. It has now become a real issue with dropouts happening too frequently. I had to abandon my Time Machine backups as a result of many dropouts in the course of a backup. Other than this, everything seems fine. On checking the system log I see no record of any problems so am stuck. Any ideas please? Diagnostics attached. tower-diagnostics-20250824-1104.zip

Yes, it appears you are correct. Safari has an option to open files after download. That's news to me. I don't recall this happening before so it may have been set active in OS Sequoia which I recently installed.

Thank you so much. I've been puzzling over this for ages. As for the diagnostics, I uploaded exactly what appeared in my downloads folder. I wondered if I had done something to alter the output, so I just ran it again with the same result. Whilst the program clearly displayed that it intended to download a ,zip, that's not what I ended up with. Perhaps my Mac is becoming too smart.

Thank you. Here they are. unraid-7.1.4.txt domain.cfg cache.cfg tempo.cfg docker.cfg editor.cfg super.dat network-rules.cfg ident.cfg network.cfg go.txt favorites.cfg disk.cfg listen.txt Sabrent_0546079B11F300654799-2025-06-04 tempo (nvme0).txt HGST_HUH728080ALE604_VKJBD9DX-2025-06-04 disk1 (sdd).txt SPCC_Solid_State_Disk_MP49W23228263-2025-06-04 cache (sdb).txt nvme.1987-3035343630373942313146333030363534373939-53616272656e74-00000001-2025-06-04 tempo (nvme0).txt USB_SanDisk_3.2Gen1_01010d3b4049c090dcd29f7efc6aadea0679845b44f2cfd07c4d76513779a9ddfdc500000000000000000000438651ecff81420083558107c82e1294-0-0-2025-06-04 flash (sda).txt TOSHIBA_MG08ADA800E_X3N0A30KFCXH-2025-06-04 disk2 (sde).txt HGST_HUH728080ALE604_VKJWP1MX-2025-06-04 parity (sdc).txt cmdline.txt btrfs-usage.txt drm.txt plugins.txt motherboard.txt iommu_groups.txt ntp.txt aspm-status.txt ethtool.txt folders.txt sshd.txt lsmod.txt lsscsi.txt loads.txt testparm.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt servers.conf.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt graphql-api.txt syslog-previous.txt syslog.txt appdata.cfg m---a.cfg a------p.cfg j---y.cfg system.cfg o------f.cfg shareDisks.txt tm.cfg b----p.cfg

I am receiving regular messages about one of my drives showing ata4 needing to be reset. I cannot find anywhere how to identify which drive this is since ata doesn't seem to appear anywhere in the tools. Thanks in anticipation.

Well, today I wrote some changes to the array and they went to the pool drive and not the array. I then initiated a move and the changes were written to the array and deleted from the pool. I changed nothing to facilitate this. I wonder if the change to the capitalization of there media folder was somehow delayed, though I can't see how. I rebooted after making the change and checked after that. Anyway, it is now fixed. Thank you for your help and as always, it is much appreciated.

Yes. I am looking from Main at the array and the pool. They both show the file I am using as a test file. Time to reflect and try to think how this could have happened and perhaps a new load of Unraid and see if that clears it. I'll leave it for a day or two before doing anything silly/brave!

Yes. I fixed that but I'm still writing to both the pool and the array.

I just noticed the media.cfg is capitalized!!