github/Ventoy

Fork 0

mirror of https://github.com/ventoy/Ventoy.git synced 2026-04-03 00:28:39 -06:00

[issue]: Call `dmsetup rename` to give the mapped iso partition a name #262

New issue

Open

opened 2025-10-14 18:14:03 -06:00 by navan · 0 comments

navan commented

2025-10-14 18:14:03 -06:00

Owner

Originally created by @Korkman on 2/12/2025

Official FAQ

I have checked the official FAQ.

Ventoy Version

1.1.01

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

Legacy BIOS Mode

Partition Style

GPT

Disk Capacity

512GB

Disk Manufacturer

PNY

Image file checksum (if applicable)

None

Image file download link (if applicable)

No response

What happened?

Thunar (and likely others) won't see the new /dev/mapper/X device for easy mounting, but with a simple dmsetup rename it appears as a duplicate in the list of drives and can be mounted with a click. I would also suggest to give the mapping a unified name so it is always in the same place. With "ventoy" being taken, I would make it "ventoy-remount" or smth.

# dmsetup rename sda1 ventoy-remount
= /dev/mapper/ventoy-remount

# dmsetup rename sda1 --setuuid ventoy-remount
= /dev/disk/by-id/dm-uuid-ventoy-remount

Technically a rename isn't strictly necessary, as dmsetup suspend sda1 and dmsetup resume sda1 trigger appearance of the partition as well.

*Originally created by @Korkman on 2/12/2025* ### Official FAQ - [x] I have checked the official FAQ. ### Ventoy Version 1.1.01 ### What about latest release Yes. I have tried the latest release, but the bug still exist. ### Try alternative boot mode Yes. I have tried them, but the bug still exist. ### BIOS Mode Legacy BIOS Mode ### Partition Style GPT ### Disk Capacity 512GB ### Disk Manufacturer PNY ### Image file checksum (if applicable) None ### Image file download link (if applicable) _No response_ ### What happened? Thunar (and likely others) won't see the new /dev/mapper/X device for easy mounting, but with a simple `dmsetup rename` it appears as a duplicate in the list of drives and can be mounted with a click. I would also suggest to give the mapping a unified name so it is always in the same place. With "ventoy" being taken, I would make it "ventoy-remount" or smth. ``` # dmsetup rename sda1 ventoy-remount = /dev/mapper/ventoy-remount ``` or ``` # dmsetup rename sda1 --setuuid ventoy-remount = /dev/disk/by-id/dm-uuid-ventoy-remount ``` Technically a rename isn't strictly necessary, as `dmsetup suspend sda1` and `dmsetup resume sda1` trigger appearance of the partition as well.

No labels

Fixed

Not an issue

USB Hardware Issue

【Tested Image Report】

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github/Ventoy#262

No description provided.

Rows
Columns

[issue]: Call dmsetup rename to give the mapped iso partition a name #262