How to access an attached partition in Gnome File manager

User Support
1

Hi to All,

i succeeded to attach a partition to the appropriate app. After startup of the app the Gnome desktop will be available, but I can’t access the attached partition from the gnome file manager. I kindly ask to guide me towards a working solution.

best regards, hitam

2

If you’ve attached just one partition (and not a whole drive), you’ll need to mount it manually, through the terminal in an AppVM.

See: How to Mount and Unmount Drives on Linux | GeeksforGeeks

3

Thank you for your advice and the link for handling partitions.

I reinstalled the damaged Office app successfully.

However i am still confused with the mouting of the assigned partition inside the gnome desktop.

This is content of the startup script for assigning the different partitions to the different apps:

20250420_102528
20250420_1025281920×1074 223 KB

This is the content of the /etc/fstab file in debia-12-clone-office:

20250420_101137
20250420_1011371920×848 127 KB

How to put things together, to make the partition acccesible within the gnome desktop.

Please, please advise.

i investigated the situation further and found out, that there is no xvdi device present.

lsblk and sudo fdisk -l returned no information about such a device in debian-12-clone-office template and in the Office app as well. However, the partition ist attached to the app successfully. What happened and where i am able to find the /dev/xvdi and mount it correctly to be able to access my data on the rigt partition e.g. nvme1n1p1 ??

My notebook holds 2 M.2 SSD’s from the same vendor and the same size.
However on startup of Qubes, the M.2 SDD holding the boot partiton gets named nvme0n1p1 OR nvme1n1p1 without any rule. How can i force the system to name the M.2 SSD, holding the boot partition: nvme0n1p1 ONLY ???

Otherwise I have to boot the system so many times until the naming of the M.2 SSDs fits my startup script.

Please advise.

Regards, hitam

4

It’s difficult to say. You haven’t said “which” of the menu items work
and which not.
I cant see the images so I’m not sure what you want to convey with them

  • it’s always helpful for people to add a brief description when posting
    images.
    You could try to open a terminal from dom0 - qvm-run -p QUBE uxterm
    might do.
    Or you can get a console by running qvm-console-dispvm, and then
    trying to run applications from there. This will help to show you any
    errors that are stopping these applications from starting.

    I never presume to speak for the Qubes team.
    When I comment in the Forum I speak for myself.