Interesting.I have some other ideas, but this is really grasping at straws. Create a backup of the backup drive before doing any tests, since you have to move it a lot for this:
1. Connect the hard drive to a different eSATA port 2. Try another eSATA cable 3. Try to mount the hard drive on different devices 4. Try different hard drive cases with different connection types (Maybe you have a better enclosure with USB or even FireWire, which does not damage your drive?) 5. Connect it internally via SATA and try to mount it 6. Mirror the hard drive to a second hard drive and try to mount the second one I think, this would entirely cover Layer 1 of the OSI Layer Model[1]. :) -Ramon [1] https://en.wikipedia.org/wiki/OSI_model On 07/07/2021 20:08, Dale wrote:
Dr Rainer Woitok wrote:Ramon, Dale, On Tuesday, 2021-07-06 20:40:32 +0200, Ramon Fischer wrote: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"Good idea. But to find out whether or not this is the cause of Dale's problems I would suggest to first run "cryptsetup" without the "--uuid" option (in order to get the UUID listed) and to then compare this with the output from "ls /dev/disk/by-uuid". Sincerely, RainerWell, it's midweek and I wanted to test this theory even tho it is early. Plus, it's raining outside so I'm a bit bored. I pulled the backup drive from the safe and did a backup. While it was backing up new stuff, I ran this: root@fireball / # blkid | grep dde669 /dev/mapper/8tb: LABEL="8tb-backup" UUID="0277ff1b-2d7c-451c-ae94-f20f42dde669" BLOCK_SIZE="4096" TYPE="ext4" root@fireball / # ls /dev/disk/by-uuid | grep dde669 0277ff1b-2d7c-451c-ae94-f20f42dde669 root@fireball / # I just grepped the last little bit of the UUID to see if anything else matched. It didn't. I tried both methods just in case. It was grasping at straws a bit but hey, sometimes that straw solves the problem. I might add, I unmounted the drive and cryptsetup closed it first time with not a single error. It didn't even burp. Given I've done this several times with no problem after doing the UUID way with consistent errors, I think it is safe to assume that changing from UUID to labels solves this problem. The question now is this, why? It's not like one mounts something different or anything. It's the same device, just using a different link basically. This is thoroughly confusing. It just doesn't make sense at all. Either way should work exactly the same. I'm open to ideas on this. Anybody have one? I'll test it if I can even if it is a serious grasp at a small straw. ;-) Dale :-) :-)
-- GPG public key: 5983 98DA 5F4D A464 38FD CF87 155B E264 13E6 99BF
OpenPGP_signature
Description: OpenPGP digital signature
