If the disk was part of an MDADM RAID set, there's a good chance that the md superblock might still be present on that disk...
Note that the tools and methods below can absolutely annihilate any and all data, so make sure any essential data is backed up somewhere outside of the NAS...
How to disassemble an old MDADM Raid Array
MD Admin can be
very persistent on mounting/locking a former member of a RAID set - so sometimes we have to get brutal about it and zero out the persistent superblock that defines that disk as being a member of a collective RAID.
Find out your arrays (md0, md1, etc..) using - this command just lists any and all disks on the system.
sudo fdisk -l
Query your arrays to find out what disks are contained using - assuming that /md0 is something of interest.
sudo mdadm --detail /dev/md0
Shut down the array using
mdadm --stop /dev/md0 <-- or whatever md array the disk thinks it's part of - look for md127 sometimes...
And here's the magic key …… zero the superblock FOR EACH drive - make sure you know the target on this one, if in doubt, check
fdisk -l to confirm - below are just examples - in the example below, /dev/sdb was the device with the persistent superblock...
mdadm --zero-superblock /dev/sdb
mdadm --zero-superblock /dev/sdX...