Open willscott opened 8 years ago
I can't reproduce. Just mounted an encrypted disk (after installing cryptsetup-bin, which was indeed missing), I am able to access the files (outside of oz) without any difficulty. Inside oz is a separate issue. Can you elaborate on how we can repro this?
Steps were just to plug in a 4tb luks encrypted disk, and mounting once cryptsetup was installed. Got I/O errors when trying to navigate in the file browser or list the directory from the gnome terminal.
ls from a root shell didn't result in i/o errors, but the mounting still seemed to not have fully worked. I'll try again after a reboot and see if it had gotten in a weird state from partially starting before cryptsetup was installed.
On Tue, Feb 2, 2016 at 4:55 PM, David Mirza Ahmad notifications@github.com wrote:
I can't reproduce. Just mounted an encrypted disk (after installing cryptsetup-bin, which was indeed missing), I am able to access the files (outside of oz) without any difficulty. Inside oz is a separate issue. Can you elaborate on how we can repro this?
— Reply to this email directly or view it on GitHub https://github.com/subgraph/subgraph-os-issues/issues/49#issuecomment-178927959 .
Ok. Will keep this tentatively open.
@willscott Do you still have this error on recent releases?
I have experienced similar issues. Any encrypted thumbdrives and/or USB hard drives that I have formatted on other machines (Ext4 usually), are mounted as read-only in SGOS. However, disks I format + encrypt from SGOS do not seem to have this problem.
I've noticed several strange disk behaviors including LVM volume oddities, like a duplicate mount explosion, probably related to this bug, and gnome-disks
and dd
not making USBs bootable. In fact, any .iso
put onto a USB stick with the subgraph alpha seemingly cannot be used to boot and install a Linux distribution.
ls: cannot access Dropbox: Input/output error
for all files on the mounted disk. accessing as root works, but seems like a bad solution.