Public bug reported: Hi,
I have a Samsung 990 Pro in my system for data that is protected with self-encryption. I use a shadow MBR with a PBA (pre-boot authentication) that should unlock it, but sometimes my motherboard boots into my OS directly and skips the PBA. In case that happens I just manually run sedutil to unlock the drive. When unlocking the drive by setting MBRDone to yes, the contents of the drive completely change and a new GPT table is provided. The Ubuntu GUI picks up these new drives, I can see them pop up in the bar on the left side of my screen (as you see with all drives). However when I try to open it from there or in my files app, I see the error "No object for D-Bus interface". The drive is not mounted. If I run "systemctl --user restart gvfs-udisks2-volume-monitor", the drives flashes (disappears and re-appears) in my UI and I can now successfully mount the drive. This problem does not occur when unlocking the drive before booting ubuntu. What I expect to happen is that after running the SED command to unlock the drive, mounting can be done without the error, and without having to restart the gvfs-udisk2-volume-monitor service. Description: Ubuntu 25.10 Release: 25.10 gvfs: Installed: 1.57.2-2ubuntu5 Candidate: 1.57.2-2ubuntu5 Version table: *** 1.57.2-2ubuntu5 500 500 http://nl.archive.ubuntu.com/ubuntu questing/main amd64 Packages 100 /var/lib/dpkg/status Disk /dev/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: Samsung SSD 9100 PRO 4TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: <REDACTED> Device Start End Sectors Size Type /dev/nvme0n1p1 2048 69631 67584 33M Microsoft basic data /dev/nvme0n1p2 69632 7814035455 7813965824 3.6T Microsoft basic data Steps to reproduce: - Take an NVME drive with OPAL 2 support - Add some partitions on the drive - Enable SED with sedutil-cli --initialSetup - Enable PBA with sedutil-cli --setMBREnable - Optionally also flash a PBA with --loadPBAimage (I don't think this is required to reproduce the bug) - Relock drive or cold reboot system to put drive in PBA mode. (The COLD reboot part is important to let the drive lock itself!) - Check that drive is in MBRDone=n mode using sedutil-cli --query - Run sedutil-cli --setMBRDone - See created partitions appear in the UI - Click on one of the partitions to mount it - See error message instead Thank you. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, I have a Samsung 990 Pro in my system for data that is protected with self-encryption. I use a shadow MBR with a PBA (pre-boot authentication) that should unlock it, but sometimes my motherboard boots into my OS directly and skips the PBA. In case that happens I just manually run sedutil to unlock the drive. - When unlocking the drive by setting MBRDone to yes, the contents of the drive completely change and a new GPT table is provided. The Ubuntu GUI picks up these new drives, I can see them pop up in the bar on the left side of my screen (as you see with all drives). However when I try to open it from there or in my files app, I see the error "No object for D-Bus interface". The drive is not mounted. + When unlocking the drive by setting MBRDone to yes, the contents of the drive completely change and a new GPT table is provided. The Ubuntu GUI picks up these new drives, I can see them pop up in the bar on the left side of my screen (as you see with all drives). However when I try to open it from there or in my files app, I see the error "No object for D-Bus interface". The drive is not mounted. If I run "systemctl --user restart gvfs-udisks2-volume-monitor", the drives flashes (disappears and re-appears) in my UI and I can now successfully mount the drive. This problem does not occur when unlocking the drive before booting ubuntu. What I expect to happen is that after running the SED command to unlock the drive, mounting can be done without the error, and without having to restart the gvfs-udisk2-volume-monitor service. - Description: Ubuntu 25.10 Release: 25.10 gvfs: - Installed: 1.57.2-2ubuntu5 - Candidate: 1.57.2-2ubuntu5 - Version table: - *** 1.57.2-2ubuntu5 500 - 500 http://nl.archive.ubuntu.com/ubuntu questing/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.57.2-2ubuntu5 + Candidate: 1.57.2-2ubuntu5 + Version table: + *** 1.57.2-2ubuntu5 500 + 500 http://nl.archive.ubuntu.com/ubuntu questing/main amd64 Packages + 100 /var/lib/dpkg/status Disk /dev/nvme0n1: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors - Disk model: Samsung SSD 9100 PRO 4TB + Disk model: Samsung SSD 9100 PRO 4TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: <REDACTED> Device Start End Sectors Size Type /dev/nvme0n1p1 2048 69631 67584 33M Microsoft basic data /dev/nvme0n1p2 69632 7814035455 7813965824 3.6T Microsoft basic data Steps to reproduce: - Take an NVME drive with OPAL 2 support - Add some partitions on the drive - Enable SED with sedutil-cli --initialSetup - Enable PBA with sedutil-cli --setMBREnable - Optionally also flash a PBA with --loadPBAimage (I don't think this is required to reproduce the bug) - - Relock drive or cold reboot system to put drive in PBA mode + - Relock drive or cold reboot system to put drive in PBA mode. (The COLD reboot part is important to let the drive lock itself!) - Check that drive is in MBRDone=n mode using sedutil-cli --query - Run sedutil-cli --setMBRDone - See created partitions appear in the UI - Click on one of the partitions to mount it - See error message instead Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2137391 Title: Mounting partitions in UI on OPAL drive not working after setting MBRDone to yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2137391/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
