scottcru

You legends! that worked. Thank-you.

Hi, I have just upgraded my unraid system to v7.2.0 from the previous version. I am now having problems with some of my shares (not all). In some of the shares set-up page I am getting an error 'Case-insensitive Share name is not unique'. I can confirm each of my shares has a unique name. In addition for the shares where this error exists the SMB Windows share doesn't work on my PC with the error 'Microsoft Windows Network: The local device name is already in use'. Can anyone assist me please, your help would be appreciated? scott-nas-diagnostics-20251108-1833.zip

Thank-you will do this evening and post

Thank-you for the guidance, diagnosis run and now attached. Just to note, parity check not running when diagnosis just run, and if it was, I then wouldn't be able to access the WebGUI to then run the diagnosis. scott-nas-diagnostics-20240623-2124.zip

Hi, I've had a problem with my parity check scheduling recently (now solved by a very helpful user on this forum), but helped to highlight a problem I have had pretty much since setting my unraid server up. When the parity check is running my server becomes unresponsive via the WebGUI or the CLI. When I hard reset and get access to the WebGUI and turn off the Docker and VM service the server remains responsive when the parity check restarts. Is there any advice or experience others have had they can share. Is there a way to limiting the amount of processor capacity used by parity check? can the docker service be shutdown prior to a parity check being commenced? could I have a resource hungry Docker container? I'm still quite new to seeking support via these forums, so if there are any diagnosis reports I can run please do let me know. Many thanks for your help in advance.

Hi, it was indeed the scheduler, I had installed the 'Parity Check Tuning' app to try it, but uninstalled it. However, it changed the frequency of my parity check schedule. Turning the parity schedule off and then resetting back on seems to have solved it. Thanks for your advice.

Hi, I have been running an Unraid server successfully for the last 18 months. However, for the last month I am finding the server is commencing an unscheduled parity check which in turn makes the server unresponsive from both the GUI and the command line interface. I am new to requesting support and help, what logs should I provide for someone to guide or help me? Many thanks in advance. Unraid system:Unraid server Plus, version 6.12.10 Model:Custom Motherboard:ASUSTeK COMPUTER INC. PRIME Z690M-PLUS D4, Version: Rev 1.xx, s/n: 211194560801764 Processor:12th Gen Intel® Core™ i5-12600K @ 3700 MHz HVM:Enabled IOMMU:Enabled Cache:L1 Cache = 288 KiB (max. capacity 288 KiB) L1 Cache = 192 KiB (max. capacity 192 KiB) L2 Cache = 7680 KiB (max. capacity 7680 KiB) L3 Cache = 20 MiB (max. capacity 20 MiB) L1 Cache = 128 KiB (max. capacity 128 KiB) L1 Cache = 256 KiB (max. capacity 256 KiB) L2 Cache = 2 MiB (max. capacity 2 MiB) L3 Cache = 20 MiB (max. capacity 20 MiB) Memory:32 GiB DDR4 (max. installable capacity 128 GiB) Controller0-ChannelA-DIMM0: Corsair CMK16GX4M2B3200C16, 8 GiB DDR4 @ 3200 MT/s Controller0-ChannelA-DIMM1: Corsair CMK16GX4M2B3200C16, 8 GiB DDR4 @ 3200 MT/s Controller1-ChannelA-DIMM0: Corsair CMK16GX4M2B3200C16, 8 GiB DDR4 @ 3200 MT/s Controller1-ChannelA-DIMM1: Corsair CMK16GX4M2B3200C16, 8 GiB DDR4 @ 3200 MT/s Network:bond0: fault-tolerance (active-backup) eth0: 2500 Mbps, full duplex, mtu 1500 eth1: interface down Kernel:Linux 6.1.79-Unraid x86_64 OpenSSL:1.1.1v P + Q algorithm:32125 MB/s + 49587 MB/s

You superstar, I missed the lock! currently re-ordering as I type. Thank-you.

Have just installed and setup, everything went perfectly with one exception that is probably more likely to be user error rather than a fault of the plug-in. Found how to sort dockers within a folder, but just can't sort / re-order the folders based on my personal preference. The order just looks like the latest folder I created being on the top of the folder list. Any help would be appreciated.

Hi, I'm a bit of a newbie on Unraid, but have everything all up and running and am loving it. I was researching photo management applications on Unraid and Photonix seems well regarded. I followed all the above excellent instructions but just get a server error when trying to run the Photonix docker. I have checked the logs on the redis and the postgres and these dockers seem to be running fine and awaiting connections. Turning to the Photonix docker the only area I wanted to check was the line: docker network create --subnet=192.168.255.0/24 photonix_net Is the IP address used the one I should use or is there a local address I should be using e.g. the IP of my server, my gateway etc.? Thanks in advance for your help.