Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#47832 - [linux] LUKS partition created with Gnome Disks fails to mount with 4.4-4

Attached to Project: Arch Linux
Opened by AaronP (Bellum) - Wednesday, 20 January 2016, 15:24 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 27 January 2016, 15:10 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This was working in 4.4-3. I unlock the partition just by clicking on it in Nautilus and typing in my password.

Nautilus gives the following error:
Error unlocking /dev/sdd: Command-line `cryptsetup luksOpen "/dev/sdd" "luks-936da53e-0d91-4b09-8ae6-3f398b888508" ' exited with non-zero exit status 1: device-mapper: reload ioctl on luks-936da53e-0d91-4b09-8ae6-3f398b888508 failed: Invalid argument

And this shows up in the journal:
Jan 20 09:16:41 arch-tower0 kernel: device-mapper: table: 254:0: crypt: unknown target type
Jan 20 09:16:41 arch-tower0 kernel: device-mapper: ioctl: error adding target to table
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 27 January 2016, 15:10 GMT
Reason for closing:  Not a bug
Comment by AaronP (Bellum) - Wednesday, 20 January 2016, 23:47 GMT
Hum. I'm not able to reproduce this right now for some reason. Possibly PEBKAC, but I don't think so given the error messages.
Comment by Doug Newgard (Scimmia) - Wednesday, 27 January 2016, 05:16 GMT
Is it possible this happened after updating the kernel without rebooting?
Comment by AaronP (Bellum) - Wednesday, 27 January 2016, 15:01 GMT
Huh. I'd like to think I wouldn't do something that stupid, but I can't rule it out, actually. I'll check.

...

Yep, I did something that stupid; you figured it out. Looks like the update happened at about 9:00, and the next reboot wasn't until 17:34, after which I reported that I couldn't reproduce this. There was a reboot immediately before the update. Probably I was a little distracted and I thought I rebooted when I didn't.

Loading...