This is just a guess. Maybe you have two devices with the same UUID?
If so, you can change it with: $ cryptsetup --uuid="<some_uuid>" luksUUID "/dev/sdx1" -Ramon On 05/07/2021 05:19, Dale wrote:
Dale wrote:Dale wrote:After staring at it a while, it hit me that lsblk is showing it as still mounted, even tho I umounted already without error. So, I just ran the umount command again. After that, it closed just fine. So, it seems to be mounted twice, not once. I mount using this command 'mount /mnt/8tb' which uses fstab to mount the correct UUID device to that mount point. Surely it only mounts once. Always has in the past. So why is it being mounted twice now? None of my scripts used for backups includes any mounting commands. There's also only one entry in fstab as well. Anyone have any idea while it gets mounted twice? Does the cryptsetup open command mount it in some way and then I mount it manually as well?? When I opened it just now, it didn't show anything as mounted. So it doesn't appear to be the open command. What else could it be?? Ideas? Dale :-) :-)The same drive just did it again. I had to reboot to get it to reset. This is Linux not windoze. Rebooting to reset something like that is plain ridiculous. I also checked, this time it was mounted only once. When I tried to umount it again, it said it wasn't mounted. The thing that really gets me, nothing can tell me what it is that is using the device. It says it is in use but no clue what it is using it. To test a theory, I changed fstab to mount by label instead of UUID. Maybe that will change something. I dunno. I do know, if this doesn't improve soon, I'm going to erase the drive and either find another encryption tool or just not encrypt it at all. I'm not rebooting every time this thing wants to act ugly. I'm used to rebooting like every 6 months or so. Usually when the power fails. If anyone has any ideas, please post. In the meantime, I'm going to try this mounting by label idea. Dale :-) :-)Here's a update. I'm doing my weekly updates which means I close web browsers, to conserve memory mostly. While I'm doing updates, I update my backups. As usual, the 6TB drive did fine. I ran the usual commands, got the proper response and everything worked fine. The 8TB drive did the same. It ran every command from decrypting it to unmounting and closing without a single problem. I even opened it, mounted it, unmounted it and closed it again. Still, no problems at all. The only thing I changed, I mounted by label instead of UUID. Can someone explain to me why that should matter? It's the same thing being mounted so one would think it wouldn't matter at all. Heck, most even say mounting by UUID is the best way. Dang near impossible to have two of anything with the same UUID. So why does it work fine with labels but not UUID? I'm looking forward to someone having a clue on this. I'm very confused, happy it works but confused for sure. This makes no sense. Dale :-) :-)
-- GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF
OpenPGP_signature
Description: OpenPGP digital signature
