Install script fails with "Failed to access /dev/sdb, maybe root privilege is needed!"

[klasrocket]

When running the install script for v 1.0.15 I get the following message; Failed to access /dev/sdb, maybe root privilege is needed! both using the -i and the -I flags, regardless using sudo or sudo su for proper root permissions. My sdb has following properties; brw-rw---- 1 root disk 8, 16 jul 22 11:23 sdb My machine is amd_64 with ubuntu20.04 but I also got the same results while running at a fresh ubuntu20.04 live disk.

Got it working after writing a new msdos partition table using gparted. Maybe this could be described more clearly in the documentation or in the error message it self. Hope this could to some help.

[rmpel]

switch to the superuser with sudo su - and rund the script there. That worked for me (after having the same issue, of course).

[kutear]

root@xxx-ubuntu:/home/xxx/Downloads/ventoy-1.0.29# ./Ventoy2Disk.sh -i /dev/sdd

**********************************************
      Ventoy: 1.0.29
      longpanda admin@ventoy.net
      https://www.ventoy.net
**********************************************

Failed to access /dev/sdd, maybe root privilege is needed!

I had same problem on ubuntu 20.04

[malgam]

I had the same problem when running Ubuntu 20.10. The destination usb drive is automatically mounted when plugged in and has to be unmounted before running Ventoy2Disk.sh. When this is done from Nautilus file manager using the unmount button, the install fails with the above error. I found that this is caused by the dd command in tool/VentoyWorker.sh returning a "No Media Found" error.

To get around this, I unmounted the usb drive partitions from the command line rather than using Nautilus. The install then completed successfully.

[aalaap]

@malgam is right. These are the commands that worked for me:

$ sudo umount /dev/sdb1
$ sudo ./Ventoy2Disk.sh -i /dev/sdb -g

You can get a list of your disks like this:

$ sudo fdisk -l

[tkrafael]

After little experiment, if you do "eject" the mount path from nautilus, the issue above happens. By doing "umount /dev/sdx[n]" (where x is the device and n is the partition number) you get rid of this issue.

[ventoy]

What about the linux GUI installer? https://www.ventoy.net/en/doc_linux_webui.html

[OHboy-jpg]

Ventoy "write-protected" feature doesn't let you make edit to the usb...So if you had Ventoy files on usb and copied them over to your linux machine. Just do one thing: Format the usb drive & retry.

[ke1g]

Similar on mint 20.1. Indeed using eject (up arrow thing in Nautilus) is the issue. It not only unmounts the partition, but "powers down" the device (safest for remove), in which state the kernel no longer sees it, so close Nautilus if inserting the drive popped it up, then umount the partition, e.g. /dev/sdb1, which does not power down the drive, and only then run e.g.; Ventoy2Disk.sh -i /dev/sdb (without the 1).

Another way to find the disk is, after you plug it in, run mount without arguments. The last item in the list will typically be the last mounted, so the partition shown will be on the USB drive, but you can also not that it is mounted "on", at least on Debian derived distributions, on /media// .

[solarkraft]

Formatting and manually unmounting worked for me.