Boyturtle

That didn't fix the issue I'm afraid. Digging deeper, other users on Windows and Mac clients are experiencing the same problems, so it would appear that there is something at the server end that is causing this issue. Have you any suggestions how to address this?

Can someone please point me to what might be going wrong on my server? For a long time, I was exclusively using smb file shares to cater for the variety of clients that would access the server (Linux desktop, Apple Mac, Windows, iphone, Android). Recently I noticed that mover wasn't working for some files/folders and that they would remain in the cache drives. It would appear that this was being caused by file/folder ownership (not 99:100, but the file creator and users group eg 1000:100). Furthermore, folders that were being created had rwxr-xr-x permissions, while files had rw-r--r--. I fixed the problem with Docker Safe New Perms, but I noticed that issue persisted with new files after I ran it. Additionally, a couple of the shares started disappearing from my remote network mount list on my Linux desktop whenever I created a file or folder in the share, and I would need to unmount and remount it to gain access again. Thinking that it might be a samba issue, I enabled nfs and exported it on a few shares with private security and added my Linux desktop to the acl with the rules async,no_subtree_check,rw,sec=sys,insecure,anonuid=99,anongid=100,no_root_squash; when I created a file, it was 1000:1000 with rw-r--r-- and a folder was 1000:1000 and rwxr-xr-x. Changing the rules to async,no_subtree_check,rw,sec=sys,insecure,anonuid=99,anongid=100,all_squash; when I created a file/folder, it gave ownership to 99:100, but the permissions were still wrong with rw-r--r--/rwxr-xr-x. FWIW, I was mounting the SMB shares on my Linux desktop via systemd (now all disabled) and mounting the nfs shares with /etc/fstab. nabu-diagnostics-20260128-2145.zip

My nginx error.log is full of this line repeating itself FastCGI sent in stderr: "PHP message: PHP Warning: Undefined array key "dontlog" in /app/www/public/inc/Logger.php on line 35; PHP message: PHP Warning: Undefined array key "hidewarnings" in /app/www/public/inc/ErrorHandler.php on line 168; PHP message: PHP Warning: Undefined array key "samesitecookie" in /app/www/public/inc/auth.php on line 516; PHP message: PHP Warning: Undefined array key "hidewarnings" in /app/www/public/inc/ErrorHandler.php on line 168; PHP message: PHP Warning: Trying to access array offset on null in /config/dokuwiki/lib/plugins/move/action/rename.php on line 42; PHP message: PHP Warning: Undefined array key "hidewarnings" in /app/www/public/inc/ErrorHandler.php on line 168; PHP message: PHP Warning: Undefined array key "defer_js" in /app/www/public/inc/template.php on line 390; PHP message: PHP Warning: Undefined array key "hidewarnings" in /app/www/public/inc/ErrorHandler.php on line 168; PHP message: PHP Warning: Undefined array key "defer_js" in /app/www/public/inc/template.php on line 397; PHP message: PHP Warning: Undefined array key "hidewarnings" in /app/www/public/inc/ErrorHandler.php on line 168; PHP message: PHP Warning: Undefined array key "dontlog" in /app/www/public/inc/Logger.php on line 35" while reading response header from upstream, client: 192.168.52.134, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: I have added the lines display_errors = off and display_startup_errors = off to /dokuwiki/php/php-local.ini, but this has not stopped the errors. Can anybody help please?

I asked a question about logrotate and someone commented "this thread is user using logrotate incorrectly and not reading nextcloud docs", but no advice towards a fix nor where to look. Not helpful at all.

My server shutdown today without warning. It was not a graceful shutdown as it started a parity check immediately after restart. When I restarted the server it did not boot into unraid, but got stuck in the bios, I had to force it to choose the unraid flash drive to boot up correctly. I've set my unraid to be a syslog server, and looking at unraids own logs, the last entry before the restart (19:52) was at 04:10 today. Looking at the logs from other devices, I see that the last entry from them to the syslog server was at 14:16, so I guess it went down at about that time. We've not had any power outages here today and my server is on a UPS (the NUT server plugin is outdated and needs an upgrade, but this should not have caused the problem). We've had no electrical storms here today and nothing else in my home is affected. It may be that the flash drive (which is USB 3) is not happy, although it is just over a year old. I have found a Transcend JetFlash 600 USB 2 drive with MLC nand that I plan to migrate the OS to in due course. I've attached diagnostics and would appreciate any suggestions about what may have caused my server to shutdown nabu-diagnostics-20240117-2102.zip

I've had this docker up and running for a while now and I'm surprised how variable my connection speeds are and I'd like to raise this with my service provider. To support this, I'd like to be able to export the data to a .csv and I note in the github documentation that this is available. Can someone give me a step by step guide to set this up? I have the basic install (sqlite)

Ok, I'll just add it to the array then :-)

I completely missed this. I found the box and checked it and now it is all working, thanks. I will preclear the old parity 1 before adding it to the array. Thanks again for your assistance.

Using the process you mention above, I am unable to start the array after unassigning parity 1; the button option is greyed out and the disk is labelled as missing. My only option is to reboot the server and when I do, parity 1 is back again.

I have tried to upgrade my parity to a larger drive (12TB) and then add the old parity (8TB) to the array, but it is not working for me following the suggestions in this post. After preclearing the new drive and stopping the array, I added the new drive as Parity 2, brought the array back up and let the parity sync. I was able to disable VMs and Docker while I did this and the sync process took approximately 24 hours. I then stopped the array and tried to change the old parity drive (P1) to "no device" so that it would become unassigned, and I could preclear it, ready to add to the array, but it would not accept this after the restart and the old parity resumed as P1. I tried to remove P1 to "no device" and then adding it to the array, but after reboot, the old parity resumes as P1 again. I'm not sure if this is relevant, but when I unassign the old parity drive, it is listed in the Unassigned Devices as Dev 1, but there is already another Dev 1 device in that set of disks. I'm not sure what I'm missing here and I've attached my diagnostics. Thanks nabu-diagnostics-20230511-1421.zip

Thanks for this, it now works perfectly, as before. I have no idea how this setting changed!

I have a WD Purple drive that a remote PC writes to 24/7; it is in unassigned devices and has been set to share. I recently upgraded the Unraid hardware (CPU, mobo, RAM and the Unraid flash disk as it was showing signs of failure at about the same time) and since then (I think), it hasn't shown up on the available server shares on the network; so I'm unable to map to it from Windows clients nor mount it from other Linux devices. The drive mounts ok within Unraid and I'm able to read the contents. I have a workaround by creating a folder share that simlinks to the purple drive, but I'd rather have it working properly. I've attached the diagnostics and would appreciate any suggestions to fix this. Thanks nabu-diagnostics-20230301-1314.zip

I'm looking at upgrading my Unraid server to allow me an amount of future proofing, taking into account future VMs (including a Mac, up to 3 Windows and pfSense), the ability to hardware transcode for Plex and to run a number of dockers. My current setup, that has been running for about 5 years now, is a Xeon 1230v5, 48GB ECC RAM, 3 cache drives, 4 storage drives and a parity all nestled in a Define R6 on a Supermicro X11SSM-F-O Motherboard with a Corsair RM750X 80+ Gold PSU. When I have all my dockers and 1 windows VM running at the moment, the CPU can get pegged at 80-90% and things have a tendency to slow down considerably when this happens. I like having IPMI and running ECC RAM and would like to carry this forward to my next build. Having 2 NICs for aggregation is also preferable. I'd like to improve performance without upping my power consumption if possible. I'm considering getting a W680 motherboard from Supermicro (X13SAE-F), 32GB (for now) DDR5 ECC RAM and an i7 12700, I plan to keep the rest of the equipment as is. I've been holding off doing this for a while as I've not been able to get my hands on DDR5 ECC RAM until now; Kingston have recently announced that they have 16GB and 32GB variants that will work with this motherboard. I've also considered similar mobo offerings from Asrock Rack, Asrock Ind and Gigabyte, and these products use DDR4 RAM, but I have not been able to source any products from resellers in the UK, the Supermicro is available, albeit with a 4 week lead time. I'd appreciate any feedback about my choices and particularly if anyone has used a similar set up.

Thanks very much for the insight, this worked for me too. If only I'd found this thread and your post earlier, my partner would not be so upset with me for losing half a day trying to find a fix!

Schoolboy error. I had my firewall rules in the wrong order on pfSense; the open port rule was below on the list and it ran after the block VLAN rule. Moving it above the block VLAN rule resolved the issue I was having.