[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
[Expired for cryptsetup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cryptsetup (Ubuntu) Status: Incomplete => Expired -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
This is not your bug. Do not touch its status! ** Changed in: cryptsetup (Ubuntu) Status: Invalid => Incomplete -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
OK -- I discovered the root cause of my problem and it is not a bug in Ubuntu or cryptsetup. In my case, it was that an update on February 12 provided a new version of /sbin/blkid. This new version added a colon to the device name for increased readability (my guess) and it broke my script. I failed to notice the colon in log file, my test commands, and in the strace. Sorry for wasting your time. I may file an issue with blkid. ** Changed in: cryptsetup (Ubuntu) Status: Incomplete => Invalid -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
This is not your bug. Do not change its status. Read what I've written, and fix your usage of cryptsetup. LimCore, can you provide the information that I've asked for in order to continue tracking down this bug? ** Changed in: cryptsetup (Ubuntu) Status: New => Incomplete -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
** Changed in: cryptsetup (Ubuntu) Status: Incomplete => New -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
I deleted the attachment from post #3 to help eliminate the confusion. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
Post #3 contains the attachment of the output of the mistaken command "strace sudo cryptsetup". Post #7 holds a new attachment that contains the output from "sudo strace cryptsetup " Or are you saying the attachment in post #7 is also wrong somehow? ** Attachment removed: "crypt_trace.txt" http://launchpadlibrarian.net/39582676/crypt_trace.txt ** Attachment removed: "crypt_trace.txt" http://launchpadlibrarian.net/39582681/crypt_trace.txt -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
That's the trace I replied to telling you you were passing the wrong argument as the device name. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
See post #7 -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
I've already told you that your strace showed you were getting an error because you were *running the command wrong*. Have you fixed the command you were running? -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
The following command "sudo cryptsetup luksDump /dev/sdc1" produced the following output which tells me that the system recognizes it is a luks partition: LUKS header information for /dev/sdc1 Version:1 Cipher name:aes Cipher mode:cbc-plain Hash spec: sha1 Payload offset: 2056 MK bits:256 MK digest: 06 ea 71 86 9f 40 6d 98 c1 2f cd aa f8 da de fd 0c 18 24 f9 MK salt:df d5 b7 90 be d9 1f bc 49 b1 7a 26 aa cc b4 7f a7 4a 6b db 26 30 31 d3 0b 64 b8 6b 38 c1 e6 58 MK iterations: 10 UUID: 6631660b-7c99-4b00-8191-345b3a749de4 Key Slot 0: ENABLED Iterations: 353970 Salt: da 0f b2 e4 b7 db f5 07 7b b9 3f f3 50 e4 a8 8b 04 ad 8c e3 9a c7 66 cc 3a ad fe 8e 5e 0e 77 11 Key material offset:8 AF stripes: 4000 Key Slot 1: ENABLED Iterations: 383771 Salt: ef 49 65 a8 11 b7 e7 5b 44 e1 86 1c 61 01 7a b2 72 39 0b 09 0a 6d c4 40 b9 89 61 b2 38 82 e0 97 Key material offset:264 AF stripes: 4000 Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
no, it is not. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
sorry -- i mean 433051. https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/433051 -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
This bug may be a duplication of 485624. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
This log shows you're calling cryptsetup with an argument of '/dev/sdc1:' which indeed will not exist. The correct name is '/dev/sdc1'. I don't think you have the same bug as the submitter. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
Sorry about that -- here is the proper one -- with the attachment this time. DOH! ** Attachment added: "crypt_trace_fixed.txt" http://launchpadlibrarian.net/39586591/crypt_trace_fixed.txt -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
Note that I get the "Command failed: Can not access device" error message regardless of wether I try the keyfile or the password. Also note that I get the error before even being prompted for a password. The device in question has only one partition and it shows up in /proc/partitions -- but is (as expected) not already under /dev/mapper -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
Sorry about that. Here is the proper one I believe. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
This shows an attempt to strace sudo. That doesn't help, you can't run sudo under strace. If you want to run this as a single command, you need to run 'sudo strace' instead of 'strace sudo'. -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
I have this same error: Here is the output of the strace: ** Attachment added: "crypt_trace.txt" http://launchpadlibrarian.net/39582681/crypt_trace.txt -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
I have this same error: Here is the output of the strace: ** Attachment added: "crypt_trace.txt" http://launchpadlibrarian.net/39582676/crypt_trace.txt -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
Please show the output of 'strace cryptsetup luksOpen /dev/sda11 abc'. ** Changed in: cryptsetup (Ubuntu) Status: New => Incomplete -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485624] Re: cryptsetup can not access device - Command failed: Can not access device
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35869547/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/35869548/XsessionErrors.txt -- cryptsetup can not access device - Command failed: Can not access device https://bugs.launchpad.net/bugs/485624 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
