0

I want to create a bootable USB and to put drivers folder beside my .iso image. Firstly, I wrote zeroes on my USB drive using this command: sudo dd if=/dev/zero of=/dev/sda bs=4096 conv=fsync oflag=direct status=progress, got this output:

1907201+0 records in 1907200+0 records out 7811891200 bytes (7.8 GB, 7.3 GiB) copied, 2188.11 s, 3.6 MB/s 

then I unmounted and formatted it:

sudo umount /dev/sda sudo mkfs.vfat /dev/sda 

Then I created a partition on it using gparted, and got this output in lsblk:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 7.3G 0 disk └─sda1 8:1 1 7.3G 0 part 

Then I wrote an .iso file into my USB using sudo dd bs=4M if=/home/alex/Downloads/Win10_22H2_EnglishInternational_x64v1.iso of=/dev/sda conv=fsync oflag=direct status=progress command and got this output:

1462+1 records in 1462+1 records out 6135633920 bytes (6.1 GB, 5.7 GiB) copied, 1396.19 s, 4.4 MB/s 

As I understood later, dd command overwrites partition table, so now my partition is gone. I'm still need to put a folder with drivers on to my USB drive beside .iso image. I don't know how to do it, because I can't copy my folder into USB drive, or create a new folder inside it. My partition sda1 is disappeared, and when I try to mount sda itself, it says "source write-protected, mounted read-only". I heard I can use Ventoy for this kind of things, but is there any other way? I don't know what to do now and where is the problem. Would be thankful for your help.

1 Answer 1

4

None of this makes sense.

  1. You mustn't write something to the raw device while there is still a mounted file system on it
  2. luckily, 1. is not a data loss problem here, because the writing of zeros was superfluous anyways
  3. No, dd-ing a windows DVD image to a USB drive does not make a bootable USB drive. It doesn't work like that – unlike some Linux distro installer .iso images, Windows installer .iso images are not hybrids that work as both a bootable optical drive image and bootable USB image.
  4. you can't "put some files next to an ISO" if you're not putting the ISO as a file on your drive.

So, you need to create a bootable Windows installer image differently, in a way that actually works, and that the windows installation process understands afterwards. Here's but a pointer.

1
  • 3
    Thank you for your answer. I decided to use Ventoy and succeeded, but I think, your explanation and link can be a good alternative. Commented Jul 2 at 13:30

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.