Tag Info

New answers tagged

-3

This sequence allowed me to access the data cryptsetup luksOpen /dev/sdb1 disk2 modprobe dm-mod vgchange -ay mount /dev/disk2/disk2 /disk2 So I offer the reward to the one who'll tell me how to make this change permanent.


4

You have to remember there are two layers of abstraction involved here. You don't "mount" an encrypted disk. You open the encrypted disk with cryptsetup (if you have the correct password). This will create a mapping of the de-crypted partition at /dev/mapper/foo. Then you can mount /dev/mapper/foo to your desired mountpoint (such as /disk2). These are two ...


0

To mount an encrypted drive you just have to identify your encrypted drive and partition (lets say it is sdb1). Run the command cryptsetup luksOpen /dev/sdb1 EncHDD You will have to introduce your passphrase and a new device will be created under /dev/mapper called EncHDD. After that mount /dev/mapper/EncHDD /mnt and you will be ready to go. Your ...


1

Try not using /dev/sdX to idendify your devices, instead use its UUID and you should always be safe. Use the blkid command to identify your device's UUID and modify your fstab using UUID=YourDevicesUUID replacing /dev/sdX. You will also need to modify your /etc/grub/grub.cfg to set your root device as the UUID of the drive you want to boot from.


1

To get things back to where they should be, I: Highlighted 'Ubuntu' at the boot menu hit 'e' to edit the configuration in the line starting with linux=, I switched the 'ro' to 'rw' and added the word 'single' at the very end of the line hit f10 to boot once it booted, as root, I did: mount -o remount,rw / as root, I edited /etc/fstab to get it where it ...


2

You are confusing the rw option with the umask. The rw option merely dictates that the partition is not mounted read-only. The umask option dictates what permission that not set on files and directories. Your current umask of 022 sets the permission bits to 755 which translates to rwxr-xr-x. Change the umask to 000, which should give you 777 or rwxrwxrwx ...


0

It looks to me you have write permission as root. Il you want write permission as pi user (or whoever ) sudo chown pi /mnt/data sudo chmod g+w /mnt/data The rw option in /etc/fstab allow proper user to write on filesystems. It is however seldom use. I once in a while mount a FS ro (read-only) due to migration or backup.



Top 50 recent answers are included