Arch Linux

MickeyRat

Member

Registered: 2011-11-15

Posts: 135

(SOLVED] Encrypted container suddenly write protected

I have a raspberry PI running raspbian with nfs.  That serves up several mountpoints that contain encrypted containers.  The commands I use to access these containters are as follows:

mkdir /tmp/backup
mount <raspberry PI>:/mount/nfs/backup /tmp/backup
losetup /dev/loop0 /tmp/backup/backup
cryptsetup luksOpen /dev/loop0 backup
<prompt for password>  <password>
mlkdir /tmp/backup_crypt
mount /dev/mapper/backup /tmp/backup_crypt

The problem is that /dev/mapper/backup mounts readonly and adding a -w to the mount command won't make it mount read write.  I've been using this setup for over a year.  So, something has changed recently but, I don't know what.  I do keep this system up to date.  Any pointers?

Last edited by MickeyRat (2016-02-27 20:22:39)

---

Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde

Scimmia

Fellow

Registered: 2012-09-01

Posts: 12,418

Re: (SOLVED] Encrypted container suddenly write protected

I have a raspberry PI running raspbian ...

So why are you here?

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,349

Re: (SOLVED] Encrypted container suddenly write protected

https://wiki.archlinux.org/index.php/Fo … pport_ONLY

Closed.  Dust binned.

After corresponding with the original poster, I have restored the thread.  The Raspberry pi is a server that apparently is functioning as expected.  The problem is with an Arch Linux system acting as a client.

Last edited by ewaller (2016-02-25 14:54:20)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

MickeyRat

Member

Registered: 2011-11-15

Posts: 135

Re: (SOLVED] Encrypted container suddenly write protected

Okay I owe those that looked at this an apology.  The problem was a hard drive failure.  The file system had gone into read only mode on the host.  It threw me off because it never indicated that it was read only until I mounted the encrypted container even if I mounted the nfs file system with a -w.  It would be entirely fair to delete this thread.  OTOH it might be a lesson to others that haven't seen a failure that looked like this.  I certainly hadn't.

---

Some cause happiness wherever they go; others whenever they go.
- Oscar Wilde