Victor Ivanov wrote: > From what I gather, taking into account your other email as well, there > are two separate things going on which may or may not be related: > > 1) The (now open) filesystem isn't being mounted where it should as per > fstab > > 2) Even then, there appears to be a bogus 'private' parent directory: > /run/media/private/<uid>/<volume> as opposed to /run/media/<uid>/<volume>
When I named it, I named it private. It could be that is where it got that word from. It could be DN picked it up, it could be other things picked it up as well. Basically, that's the LVM name for the group thingy. I named the partition privatepart. I added part so I would know it is a partition. Sometimes the names LVM uses can be confusing. I try to avoid naming a LVM group and a partition with the same name. If nothing else, I add 'part' for partitions or something that I can tell what they are more than what they are called. Example, I have a internal backup drive that has a LVM group named backup. The partition is also named backup. Yea, now which is which? If I ever redo that, I'll name the partition backuppart or something. Then I know which is a LVM group and which is a partition. > On 11/06/2020 23:17, Dale wrote: >> This is my fstab entry: >> >> UUID="7f0cf585-57c8-4a50-808b-987fc13ceee0" >> /home/dale/Desktop/Videos/Private ext4 defaults,users 0 0 >> ... >> You notice anything off about that? I make a error somewhere? Miss a >> option maybe? > fstab doesn't like quotes. The correct syntax would be: > UUID=7f0cf585-57c8-4a50-808b-987fc13ceee0 > > Re (1) above, given that /etc/conf.d/dmcrypt is only used by the dmcrypt > service through OpenRC its contents are irrelevant when using KDE. So, > from the perspective of DN updating fstab with the correct syntax should > be a two birds, one stone solution to both (1) and (2). > > Unless your encrypted volume is always connected to the system and you > would like it to be automatically unlocked (via means of being asked to > enter your password), there is no need to enter anything into > /etc/conf.d/dmcrypt and you can leave the file blank/commented out. > > Re (2), frankly, I have no idea but I'm curious as to where that > "private" parent directory might come from. The only possible source for > this that I can guess is from your entry in /etc/conf.d/dmcrypt in the > value for "target": I copied that method from a wiki. I also have this in fstab. The first one has been there for several years. It mounts when booting up. UUID="13d4bec9-1271-490c-b718-d8b1c68ae1e6" /backup ext4 defaults 0 2 UUID="7f0cf585-57c8-4a50-808b-987fc13ceee0" /home/dale/Desktop/Videos/Private ext4 defaults,users 0 0 It has quote marks and it works fine. Maybe that is a new thing?? That said, I'll remove them since on a Gentoo wiki, it doesn't show them. I commented out the entries in dmcrypt. I saved them in case I need to refer back later tho. It took me a while to figure out what all I needed and what I didn't tho. Poor google. >> ## 3TB private drive external >> target='private' >> source=UUID='107be33c-b31c-44b8-b4e7-400ee19fb440' > While this should only affect the name of the block device created under > "/dev/mapper" it seems too much of a coincidence that the bogus parent > directory bears the same name. I've tried to reproduce your set-up but I > still don't get such a parent under /run/media. Perhaps you can try > changing the value to something else and see if it creates a directory > with the new name? If so, this would confirm the theory, but it still > shouldn't be doing that. At least it would be a starting point for > diagnosis, if it's worth going into that at all. > > Also, note that, as I mentioned, when mounting a crypto container > through KDE DN or Dolphin your dmcrypt config is irrelevant and > disregarded. You should hence expect upon opening the container to have > the filesystem's block device appear as "/dev/mapper/luks_abcd1234". > > - Victor > I been doing it manually. I open the drive on the command line, make sure it is open and then mount it manually. It uses fstab and mounts where I want it that way. The DN tool just doesn't work. Actually, trying to use it to handle encrypted drives sort of screwed up my normal drives and such. Now it's mounting those things wrong. I'm concerned it is going to break some thing such as my SDHC cards that I put in a card reader. I started a new thread on that. How do you mount something within Dolphin? I've looked through the menus and I can't find anything on mounting listed. I haven't got my new glasses yet so maybe I'm not seeing it??? lol Thanks. I had to read this twice to make sure I got where you were going here. I think I got it tho. ;-) Dale :-) :-)
