Xfce Hide a system volume in XFCE new mount system ?

Jaekelsson

New Member

Reaction score: 6
Messages: 14

Hi,

I would like to know if it is possible to hide a system volume in
the XFCE new mount system.

I have updated my Freebsd 12.2 laptop with latest repos, and now XFCE uses
- bsdisks (UDisks2 service implementation for FreeBSD)
- gvfs-udisks2-volume-monitor
to show and mount volumes

It dont use hald any more (was using gvfs-hal-volume-monitor)

I don't use automount from Vermaden
I don't use autofs from base

On the screen here i would like to hide only the "120 GB Volume", not the 15 GB USB stick.

Screenshot_2020-11-17_17-36-00.png


I tried some solutions like
create a file /usr/local/lib/udev/rules.d/99-hidevolume.rules
KERNEL=="ada0s1", ENV{UDISKS_IGNORE}="1"
or
KERNEL=="ada0s1a", ENV{UDISKS_IGNORE}="1"

without success

Thanks to help
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,106
Messages: 39,696

There are some examples here: https://github.com/GNOME/gvfs/blob/master/monitor/udisks2/what-is-shown.txt

You basically add the x-gvfs-hide to the disk's fstab entry. But I don't know if this works for FreeBSD, I don't use XFCE.

You could also try ENV{ID_SERIAL}=="<some serial code from the disk>", ENV{UDISKS_IGNORE}="1" instead of KERNEL=="<disk>"

And another thing, are you sure you're using MBR with slices and bsdlabels? If you have a GPT partitioned disk it's probably ada0p2, check with gpart(8).
 
OP
J

Jaekelsson

New Member

Reaction score: 6
Messages: 14

There are some examples here: https://github.com/GNOME/gvfs/blob/master/monitor/udisks2/what-is-shown.txt

You basically add the x-gvfs-hide to the disk's fstab entry. But I don't know if this works for FreeBSD, I don't use XFCE.
Thanks ! I already have read that page.

I put "x-gvfs-hide" in fstab and system was not booting at all. Seems a Linux thing.

Can't make it work. I'm not sure if it works with FreeBSD.

Need someone who really knows bsdisks and udisks2.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,106
Messages: 39,696

I put "x-gvfs-hide" in fstab and system was not booting at all. Seems a Linux thing.
I was afraid something like that would happen. I was hoping FreeBSD's mount would simply ignore those x-* options.

Can't make it work. I'm not sure if it works with FreeBSD.
Can you post a gpart show output from that disk?
 
OP
J

Jaekelsson

New Member

Reaction score: 6
Messages: 14

I was afraid something like that would happen. I was hoping FreeBSD's mount would simply ignore those x-* options.


Can you post a gpart show output from that disk?
of course yes :

Code:
gpart show
=>       63  234441585  ada0  MBR  (112G)
         63          1        - free -  (512B)
         64  234441584     1  freebsd  [active]  (112G)

=>        0  234441584  ada0s1  BSD  (112G)
          0  226492416       1  freebsd-ufs  (108G)
  226492416    7949168       2  freebsd-swap  (3.8G)

diskinfo -v ada0
ada0
    512             # sectorsize
    120034123776    # mediasize in bytes (112G)
    234441648       # mediasize in sectors
    4096            # stripesize
    0               # stripeoffset
    232581          # Cylinders according to firmware.
    16              # Heads according to firmware.
    63              # Sectors according to firmware.
    Crucial CT120M500SSD1    # Disk descr.
    xxxxxxxxxxxx    # Disk ident.
    id1,enc@n3059712457366d30/type@0/slot@1/elmdesc@Slot_00    # Physical path
    Yes             # TRIM/UNMAP support
    0               # Rotation rate in RPM
    Not_Zoned       # Zone Mode

geom disk list
Geom name: ada0
Providers:
1. Name: ada0
   Mediasize: 120034123776 (112G)
   Sectorsize: 512
   Stripesize: 4096
   Stripeoffset: 0
   Mode: r2w2e5
   descr: Crucial CT120M500SSD1
   lunid: 500axxxxxxxxxxxx
   ident: xxxxxxxxxxxx
   rotationrate: 0
   fwsectors: 63
   fwheads: 16

camcontrol identify ada0
pass0: <Crucial CT120M500SSD1 MU05> ACS-2 ATA SATA 3.x device
pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)

protocol              ACS-2 ATA SATA 3.x
device model          Crucial CT120M500SSD1
firmware revision     MU05
serial number         xxxxxxxxxxxx
WWN                   500axxxxxxxxxxxx
additional product id
cylinders             16383
heads                 16
sectors/track         63
sector size           logical 512, physical 4096, offset 0
LBA supported         234441648 sectors
LBA48 supported       234441648 sectors
PIO supported         PIO4
DMA supported         WDMA2 UDMA6
media RPM             non-rotating
Zoned-Device Commands no

Feature                      Support  Enabled   Value           Vendor
read ahead                     yes    yes
write cache                    yes    yes
flush cache                    yes    yes
Native Command Queuing (NCQ)   yes        32 tags
NCQ Priority Information       yes
NCQ Non-Data Command           no
NCQ Streaming                  no
Receive & Send FPDMA Queued    yes
NCQ Autosense                  no
SMART                          yes    yes
security                       yes    no
power management               yes    yes
microcode download             yes    yes
advanced power management      yes    yes    254/0xFE
automatic acoustic management  no    no
media status notification      no    no
power-up in Standby            no    no
write-read-verify              yes    no    0/0x0
unload                         yes    yes
general purpose logging        yes    yes
free-fall                      no    no
sense data reporting           no    no
extended power conditions      no    no
device statistics notification no    no
Data Set Management (DSM/TRIM) yes
DSM - max 512byte blocks       yes              8
DSM - deterministic read       yes              zeroed
Trusted Computing              yes
encrypts all user data         yes
Sanitize                       yes        block, crypto
Sanitize - commands allowed    no
Sanitize - antifreeze lock     no
Host Protected Area (HPA)      yes      no      234441648/234441648
HPA - Security                 yes      no
Accessible Max Address Config  no

fdisk -s
/dev/ada0: 484521 cyl 16 hd 63 sec
Part        Start        Size Type Flags
   1:          64   488397104 0xa5 0x80
a bit long......
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,106
Messages: 39,696

The gpart(8) output would have been enough ;) It's the partitioning and therefor the naming convention I was interested in. That was to verify it should indeed be ada0s1a. Lots of people appear to get confused between the MBR and GPT naming of the partitions, I just wanted to rule that out.
 
OP
J

Jaekelsson

New Member

Reaction score: 6
Messages: 14

I have found an other log. May be usefull ;

bsdisks.log :

Code:
Nov 18 07:49:36 test bsdisks[1226]: Not probing ZFS, the kernel module isn't loaded
Nov 18 07:49:36 test bsdisks[1226]: Created drive  "cd0"
Nov 18 07:49:36 test bsdisks[1226]: Created block  "cd0"
Nov 18 07:49:36 test bsdisks[1226]: Created drive  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: Created block  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: Created block  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: Created block  "ada0s1a"
Nov 18 07:49:36 test bsdisks[1226]: Created block  "ada0s1b"
Nov 18 07:49:36 test bsdisks[1226]: Finished GEOM probe on  "cd0"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/drives/cd0"
Nov 18 07:49:36 test bsdisks[1226]: Finished GEOM probe on  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/drives/ada0"
Nov 18 07:49:36 test bsdisks[1226]: Finished GEOM probe on  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: Finished FS probe on  "cd0"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/block_devices/cd0"
Nov 18 07:49:36 test bsdisks[1226]: Finished FS probe on  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1"  waits for partition table  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: Finished FS probe on  "ada0s1a"
Nov 18 07:49:36 test bsdisks[1226]: Finished GEOM probe on  "ada0s1a"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1"  waits for partition table  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1a"  waits for partition table  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: Finished FS probe on  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1a"  waits for partition table  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1"  waits for partition table  "ada0"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/block_devices/ada0"
Nov 18 07:49:36 test bsdisks[1226]: "ada0s1a"  waits for partition table  "ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/block_devices/ada0s1"
Nov 18 07:49:36 test bsdisks[1226]: Pop  "ada0s1"  from m_postponedRegistrations
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/block_devices/ada0s1a"
Nov 18 07:49:36 test bsdisks[1226]: Pop  "ada0s1a"  from m_postponedRegistrations
Nov 18 07:49:36 test bsdisks[1226]: Finished GEOM probe on  "ada0s1b"
Nov 18 07:49:36 test bsdisks[1226]: Finished FS probe on  "ada0s1b"
Nov 18 07:49:36 test bsdisks[1226]: "Registering /org/freedesktop/UDisks2/block_devices/ada0s1b"
 
Top