Automounted Ext4 partition - Dolphin see it, why is it invisible to Veracrypt?

English Applications
#1

Hi there,

I have an up-to-date Tumbleweed system, with a standard BTRFS \ and \home setup.
The system also has a large HDD for storage, and I used Yast to format that as Ext4 and automount it.

*Dolphin see it fine - and is able to write to it after I installed “Root Actions Servicemenu” and then configured the folder “root as local user” (why was this nevessary!)
*
So, having copied my data as a veracrypt container over to the storage drive, I then tried to mount it with Veracrypt…
Only to find that Veracrypt is blissfully ignorant of the presence of a mounted Ext4 partition!

Any idea why this partition is stealthed?

Many thanks. Jbt

#2

Can we assume you mean / and /home?

Can you lease give us some data. Like (as root)

fdisk -l

lsblk

cat /etc/fstab

It maybe because I do not run Tumbleweed, but can you explain where in YaST > Partition Mangere you can define “automount”.

#3

Thank you, yes.

Will do, when i can get the PC back off PJ Masks…

https://www.admin-magazine.com/var/ezflow_site/storage/images/archive/2017/41/manage-logical-volumes-with-gui-tools/figure-13/142897-1-eng-US/Figure-13_reference.png

#4

Well, i the image you show there is nowhere the word “auto”.

On the right you can specify if you want it mounted (and indirect if you want the mount configuration put in /etc/fstab or not.
And when you want it mounted, you have to specify the mount point and you can specify additional mount options.

While i admit that the word “automount(ing)” is used in a variety of defintions, this hasn’t much to do with "automounting’ in most of the definitions I know of.

#5

i accept the newb level imprecision with terminology, but; having done ‘mounty’ thing when i did the formatty thing in the yasty thing… i know find that when i start the computer and open dolphin it shows me a happily mounted “Storage2” partition. :slight_smile:


linux-xxxx:/usr/storage2 # fdisk -l

Disk /dev/sda: 223.58 GiB, 240057409536 bytes, 468862128 sectors
Disk model: Crucial_CT240M50
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: **some stuff**

Device         Start       End   Sectors   Size Type
/dev/sda1       2048     18431     16384     8M BIOS boot
/dev/sda2      18432 464666623 464648192 221.6G Linux filesystem
/dev/sda3  464666624 468862094   4195471     2G Linux swap

Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000AS0002-1NA
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: **some stuff**

Device          Start         End     Sectors  Size Type
/dev/sdb1          34      262177      262144  128M Microsoft reserved
/dev/sdb2      264192  3808696319  3808432128  1.8T Microsoft basic data
/dev/sdb3  3808696320 15628053134 11819356815  5.5T Linux filesystem

Partition 1 does not start on physical sector boundary.

linux-xxxx:/usr/storage2 # lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 223.6G  0 disk 
├─sda1   8:1    0     8M  0 part 
├─sda2   8:2    0 221.6G  0 part /
└─sda3   8:3    0     2G  0 part [SWAP]
sdb      8:16   0   7.3T  0 disk 
├─sdb1   8:17   0   128M  0 part 
├─sdb2   8:18   0   1.8T  0 part 
└─sdb3   8:19   0   5.5T  0 part /usr/storage2
sr0     11:0    1  1024M  0 rom  
sr1     11:1    1  1024M  0 rom 

linux-xxxx:/usr/storage2 # cat /etc/fstab
UUID=675c15d5-ee71-441a-bcab-56216266db33  /                       btrfs  defaults                      0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /var                    btrfs  subvol=/@/var                 0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /tmp                    btrfs  subvol=/@/tmp                 0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /root                   btrfs  subvol=/@/root                0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /home                   btrfs  subvol=/@/home                0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=675c15d5-ee71-441a-bcab-56216266db33  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
UUID=f1fdf5c5-e385-4f37-bdd3-ce6dfe2c88c9  swap                    swap   defaults                      0  0
UUID=c70eca2a-5f87-47d8-9812-cf82ba8c9f40  /usr/storage2           ext4   data=ordered                  0  2
#6

You mean that you are satisfied and that you do not have the problem any more?
In that case: enjoy openSUSE.

#7

Thank you for your assistance to date.

I do still have the original problem - whereby despite the mounted partition being visible/available/usable without issue in dolphin - remains invisible to Veracrypt.
Veracrypt is perfectly able to see an unmounted windows NTFS partition, so i am confused as to why it is unable to see a mounted EXT partition…

#8

Is there any indication from the info requested as to why the drive is visible/available/usable to Dolphin, but Veracrypt cannot see it?

#9

Sorry for the bump, but ss there any indication from the info requested as to why the drive is visible/available/usable to Dolphin, but Veracrypt cannot see it?