How to remove referenced disks?

You need to undo any service that is using it (e.g. if you have a Samba share remove the Samba share in the Shares TAB). Then go trough your users, in access rights management, and make sure no user has a share on that drive as it's home directory. Highlight the user and then click on the Settings TAB. If you user has a shared folder as it's home directory change it to None. Then remove any shared folder on the drive.

A command not, but the config.xml might help.

One spot that most people overlook is the home folder section. Even if disable the reference for the shared folder still exists.

Greetings
David

Grab PuTTY to connect to your NAS and if you like you can install Teamviewer and I'll show you a bit. (PM me your credentials)

Greetings
David

You will learn these little things over time and they will become easy.

So I'm running into this same issue and was hoping for some direction. I've got a disk that went bad, I've RSYNC all the data to a new disk replacement. I've swapped out where this disk was used in the MergerFS setup and the SnapRAID setup. Everything else references either Disk1 (not the one that went bad) or Storage1 which is the MFS pool.

I've dropped down to CLI and grepped through the config.xml to look for entries of disk3, sdc1, or the UUID of the disk in question holding the Filesystem assigned. I'm not finding any traces. Any other places to look? I'm hoping to properly get this bad boy unmounted/deleted from the system before I pull the physical disk.

Checked both. Good ideas, but still coming up short. I just really don't want something to get messed up if I pull the disk and it's still referenced from some config in OMV. I have an issue a long while back when I first started out with it that caused me havoc in a config that needed to be "redone" and removed again to get rid of the errors I kept getting making changes to other non-relevant things. Long story short, I know OMV can be temperamental in some instances if the config has a reference to something that doesn't exist.

Any other ideas? All I found in fstab is the regular mount call for the actual mounting of the drive at this time. So I'm pretty sure that's supposed to be there at the moment, and should give me the option to unmount the filesystem if it wasn't referenced somewhere else.

One hunch I'll ask - is it possible that the UFS function is causing this? Since there was some reference at one point to Disk3 being part of the Storage1 pool, that it's somehow still linked with all the instances of Storage1 being used? This could be extremely problematic if it's the case, since Storage1 is what's used ALL over my system. But I've already switched out Disk3 for Disk4 in the pool setup.

delete disk on fstab and config.xml and reboot.

PD: Full path is:

/etc/openmediavault/config.xml

and

/etc/fstab

But because is a manual intervention, be carefull do not delete other information otherwise OMV can fail.

@raulfg3 - I'll of course be making a backup copy before editing core files.

If there are leftover dependencies, will OMV still choke or complain though? If so, I guess I'll have to hold on to the backups for quite some time!! (just in case)

no dependencies, I do several times when change mainboard or Disk.

Good to know. Thank you, I'll give it a try this afternoon and see if I can't get the disk removed and sent back so I don't get a fee from WD for the RMA!

Well, as I was working on trying to quickly via the UI discover the UUID of the new disk, I found the culprit!! Turns out in my SnapRAID config, there are exclusion rules that call out the individual disks instead of the main pool. This was suggested as the best way to go I think somewhere. So it seems these leftover rules, were what was being seen as the reference! Now that I updated those rules to apply to Disk4, and Disk3 has now been listed at Not referenced, and I can unmount and remove it properly. So just wanted to share this here in case anyone else stumbles upon this issue as well.