https://bugzilla.novell.com/show_bug.cgi?id=841695 https://bugzilla.novell.com/show_bug.cgi?id=841695#c0 Summary: /dev/mapper is read-only in rescue mode preventing LUKS and LVM from working Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ingham@i-pi.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Firefox/24.0 My production system using encrypted partitions holding LVM volumes suffered a filesystem problem and I downloaded and booted from 13.1. cryptsetup failed with a "read only filesystem" error. /dev was read-write, but /dev/mapper was a symlink to a read-only filesystem. Reproducible: Always Steps to Reproduce: 1. Boot 13.1 beta 2. cryptsetup luksOpen foo bar 3. see the error message Actual Results: I had to track down what filesystem was read-only that was interfering with cryptsetup. It was /mounts/mp_0001. /dev/mapper was a symlink to a dir on that filesystem. Expected Results: cryptseup should have updated /dev/mapper to allow me to then do a vgscan and then a mount. I was able to work around the problem by moving /dev/mapper and creating a new one in /dev (which was rw). I am not sure it was needed, but I used mknod to create /dev/mapper/control. Unless there is a good reason otherwise, why not let /dev/mapper be part of /dev and not a symlink? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.