Hi everybody,

 

I feel like I have kind of a stupid problem over here. I did remove a disk from my array, headed over to „tools - new config“ to reflect the removal in the config and rebuild parity. So far so good. Fix common problems plugin now states that I have a share which uses the removed disk. So I followed the guidance fix common problems gave me:
 

Quote

disk2 is not defined / installed in the array. This will cause errors when writing to the array. Fix it here:  NOTE: Because of how the UI works, disk2 will not appear in on this page. You will need to make a change (any change), then revert the change and hit apply to fix this issue

 

However, I am not able to make any change in the affected share. No matter what I change in its config I only get the „done“ button activated, the „apply“ button will remain grey at all time. I did restarts of the array as well as restarts of the whole unraid server without any change. I tried disabling the vm and docker service just in case I missed a mount of the share into a docker container or vm but without any change in the error. 

 

I also tried to delete the share. I made sure that there is no single file remaining on the share via ssh and checked via „ls -la /mnt/user/affected-share“ but I can not select the delete checkbox in the share‘s config as it feels like the config of this share is stuck or something.

 

So now I am hoping for a hint from the community. Hopefully one of you can help me out. I would appreciate if I won‘t need to add the removed disk again, rebuild parity, remove the share, remove the disk again, rebuild parity again. 

 

Thanks in advance and have a great day!

 

 

Best regards

 

Wolfgang

If the disk no longer exists, you cannot include/exclude it using the GUI, post the output from:

 

cat /boot/config/shares/<share name>.cfg

 

1 hour ago, JorgeB said:

If the disk no longer exists, you cannot include/exclude it using the GUI, post the output from:

 

cat /boot/config/shares/<share name>.cfg

 

 

Thanks for the hint. I tried to find the config in /etc/samba/smb.conf and /etc/samba/smb-config.conf

 

# Generated settings:
shareComment="omitted"
shareInclude="disk2"
shareExclude=""
shareUseCache="no"
shareCachePool=""
shareCOW="auto"
shareAllocator="highwater"
shareSplitLevel=""
shareFloor="97700000"
shareExport="eh"
shareCaseSensitive="auto"
shareSecurity="private"
shareReadList=""
shareWriteList="user1,user2"
shareVolsizelimit=""
shareExportNFS="-"
shareExportNFSFsid="0"
shareSecurityNFS="public"
shareHostListNFS=""

 

Since the GUI does not show any disk in the dropdown (see screenshot in first post) is it safe to set „shareInclude“ to „“? I would stop the array before changing the config. 

Edited January 28, 20251 yr by laest

52 minutes ago, laest said:

shareInclude="disk2"

Change this to shareInclude="" and save the changes.

Solved my problem. Thank you very much for the assistance! Is this expected behaviour of the GUI or is it a bug? After changing the share.cfg the GUI worked as expected and I could make changes to the share as well as delete the share. 

 

Did I miss kind of an alert when creating the new array config or is there no check if there are shares left which make use of the removed disk?

Ideally, Unraid would remove automatically any mention of included/excluded disks that no longer exist, but not sure how feasible that is to implement, for now, you should correct that before removing the disk.

Possibly the create new config tool could make a diff of the included disks in the old and new array config and check usage of removed disks in existing shares. But since the disk names/numbers are not unique that may not be precise enough. I don't know the mechanism behind the create new config tool. 

 

However, my problem is solved. Thank you very much for enlightening me and helping me out!

Edited January 29, 20251 yr by laest