* [dm-crypt] luks container write-protected and read-only, can't be mounted
@ 2018-05-01 14:17 cici-tor
2018-05-02 10:46 ` Milan Broz
0 siblings, 1 reply; 2+ messages in thread
From: cici-tor @ 2018-05-01 14:17 UTC (permalink / raw)
To: dm-crypt
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hello,
I hope you can help me.
I have a LUKS Container file called didi with files in it and mounted it (as didiOpen). While opening one file in the Container my Raspberry Pi crashed and made a reboot without closing and unmounting the Container.
Now I can open the Container but everytime when I want to mount the Container I get an Error, that the Container is read-only and cannot be mounted.
I use sudo mount -t ext4 /dev/mapper/didiOpen /mnt everytime.
Error:
mount: /dev/mapper/didiOpen is write-protected, mounting read-only
mount: cannot mount /dev/mapper/didiOpen read-only
When I check cryptsetup status OpenContainer it said:
type: LUKS1
cipher: aes-xts-plain64
keysize: 512 bits
device: /dev/loop0
loop: /media/user/vid/didi
mode: readonly
Closing and opening the Container does not help. There I get no Error, so opening/closing is not the problem, only the mounting of the opened container.
How can I get my write permissions back or copy all stuff without mounting in a new container?
I've read luks write some special datas by closing the volume regulary? That is maybe the failure at the moment.
Thanks a lot,
didi
Sent with [ProtonMail](https://protonmail.com) Secure Email.
[-- Attachment #2: Type: text/html, Size: 1947 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dm-crypt] luks container write-protected and read-only, can't be mounted
2018-05-01 14:17 [dm-crypt] luks container write-protected and read-only, can't be mounted cici-tor
@ 2018-05-02 10:46 ` Milan Broz
0 siblings, 0 replies; 2+ messages in thread
From: Milan Broz @ 2018-05-02 10:46 UTC (permalink / raw)
To: cici-tor, dm-crypt
On 05/01/2018 04:17 PM, cici-tor wrote:
> Hello,
>
> I hope you can help me.
>
> I have a LUKS Container file called didi with files in it and mounted it (as didiOpen). While opening one file in the Container my Raspberry Pi crashed and made a reboot without closing and unmounting the Container.
>
> Now I can open the Container but everytime when I want to mount the Container I get an Error, that the Container is read-only and cannot be mounted.
>
> I use sudo mount -t ext4 /dev/mapper/didiOpen /mnt everytime.
> Error:
> mount: /dev/mapper/didiOpen is write-protected, mounting read-only
> mount: cannot mount /dev/mapper/didiOpen read-only
>
> When I check cryptsetup status OpenContainer it said:
> type: LUKS1
> cipher: aes-xts-plain64
> keysize: 512 bits
> device: /dev/loop0
> loop: /media/user/vid/didi
> mode: readonly
>
> Closing and opening the Container does not help. There I get no Error, so opening/closing is not the problem, only the mounting of the opened container.
>
> How can I get my write permissions back or copy all stuff without mounting in a new container?
> I've read luks write some special datas by closing the volume regulary? That is maybe the failure at the moment.
Some of your underlying storage layer is read-only (I guess it is underlying file).
Run "lsblk" and check "RO" flag (I guess /media/user/vid/didi does not have read-write access).
LUKS obviously cannot map read-write over read-only device. And it does not write any metadata on close/open.
Milan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-05-02 10:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-01 14:17 [dm-crypt] luks container write-protected and read-only, can't be mounted cici-tor
2018-05-02 10:46 ` Milan Broz
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.