The problem is that the installer does not offer to choose Flash drive as the target device. Those. if the computer does not have a screw, then the installation is simply impossible to continue.

It was possible to launch it by modifying the LiveUSB image with the help of a third-party tool, but this is not a complete installation — just LiveUSB allows you to save data, but the possibilities for managing users and software are severely limited.

Tell me what to fix in the Live image or how to fix the flash drive itself, so that the installer would perceive it as a HDD?

  • it is clear that mint is a distribution kit that focuses on “hamsters” at all, but it cannot be that the installation program is distorted to such an extent that it cannot be installed where you want // in the step of selecting a target device "Breakdown. - aleksandr barakin
  • What is flash? Is that what you call a key chain? And from what goes installation? Do you have two of them inserted into the computer? Intel machine architecture? Used EFI? Are these devices visible there? Is the key chain itself a quality one? (These are the first questions that come to mind) - 0andriy
  • @ alexander-barakin if not a "hamster" - do an experiment, find a solution and give an answer. The question clearly states that the installer does not offer other devices as targets other than HDD, respectively, and no "manual" methods with emptiness. You know the "nehomyachno" solution - offer - SynCap
  • @ 0andriy no, not a key fob, but a Flash drive, and yes, there are more than one, and yes one of them is SD-USB, the others are a direct USB Flash, and yes, the system sees them all, and yes, they are quality, use or non-use of the EFI interface does not impress the installer. - SynCap
  • @SynCap, OK, I understand correctly that all devices work via USB? Is it possible in the installer to go to the command prompt as root? Try to study the situation in it with the help of lsusb , gdisk , dmesg . But something intuition tells me that there is most likely PP (the pottery section), and it is to blame for the situation. - 0andriy

1 answer 1

nothing needs to be fixed. the possibility of a “manual” selection of the target block device is present in the installation program.

demonstration with pictures.

On the step of choosing the type of installation, you must select the last item (in Russian translation - “another option”):

enter image description here

then there will be a dialogue with the choice of where to install the system, and where to install the bootloader:

enter image description here

At that moment I connected a block device to usb, and in order for it to be displayed in the dialog, I had to go back and choose the same item again:

enter image description here

As you can see, I chose the newly appeared block device /dev/sdc as the target and chose it as the target for installing the bootloader.

then this device will need to be tagged according to your tastes / needs.

  • Try with an SD / MMC drive. The block device should be / dev / mmcblkX , sections, respectively / dev / mmcblkXpY . - 0andriy