Çözüldü Kubuntu'dan Windows 10'a Geçme

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.

Arch or Not

Hectopat
Katılım
29 Mayıs 2020
Mesajlar
1.129
Makaleler
7
Çözümler
14
Yer
İzmir/Alsancak
Daha fazla  
Cinsiyet
Erkek
Meslek
Öğrenci, Beginner Web Programmer
@Dengesiz Kokarca Hocamın YouTube'da paylaştığı videoda ventoy ile denerken hata aldım aldığım hata şu şekilde:
[

[CODE lang="bash" title="Hata"]acar@Root:~/Ventoy/INSTALL$ sudo sh Ventoy2Disk.sh -I /dev/sdb
[sudo] acar için parola:
Üzgünüm, yeniden deneyin.
[sudo] acar için parola:

**********************************************
Ventoy: x86_64
longpanda [email protected]
https://www.ventoy.net
**********************************************

Don't run Ventoy2Disk.sh here, please download the released install package, and run the script in it.
[/CODE]

Ayrıca başka nasıl geçebilirim? Unebootin de denedim fakat hata aldım, şu anda uygulama bile açılmıyor.
 
Son düzenleyen: Moderatör:
Çözüm
Şuradan Ventoy'un son sürümünü indirip çıkart. Release Ventoy 1.0.38 release · ventoy/Ventoy

Sonra çıkarttığın dizin içine girip, burada uçbirimi aç. Ardından aşağıdaki komutu çalıştır.

sudo ./VentoyWeb.sh

Ardından web tarayıcısını aç ve adrese şunu yaz ve aç http://127.0.0.1:24680.

Bu şekilde Ventoy'un Web arayüzünü Linux'ta kullanabilirsin.

webui_en.png
Hata verdi maalesef.
Kod:
    [CODE=bash]check_runtime_parameters: Error: source media "Windows_10.iso" not found or not a regular file or a block device file!

    WoeUSB 5.0.8 Help Information

    ======================================

    WoeUSB can create a bootable Microsoft Windows(R) USB storage device from an existing Windows optical disk or an ISO disk image.


    Currently two creation methods are supported:


        --device, -d


            Completely WIPE the entire USB storage device, then build a bootable Windows USB device from scratch.

            WARNING: All previous data on the device will be gone!


            woeusb-5.0.8 --device <source media path> <device>

            Examples:

            - woeusb-5.0.8 --device Windows7_x64.iso /dev/sdX

            - woeusb-5.0.8 --device /dev/sr0 /dev/sdX


        --partition, -p


            Copy Windows files to an existing partition of a USB storage device and make it bootable.  This allows files to coexist as long as no filename conflict exists.

            WARNING: All files that has the same name will be overwritten!


            woeusb-5.0.8 --partition <source media path> <partition>

            Examples:

            - woeusb-5.0.8 --partition Windows7_x64.iso /dev/sdX1

            - woeusb-5.0.8 --partition /dev/sr0 /dev/sdX1


    ## Command-line Options ##

        --verbose, -v

            Verbose mode


        --help, -h

            Show this help message and exit


        --version, -V

            Print application version


        --about, -ab

            Show info about this application


        --no-color

            Disable message coloring


        --debug

            Enable script debugging


        --label, -l <filesystem_label>

            Specify label for the newly created file system in --device creation method

            Note that the label is not verified for validity and may be illegal for the filesystem


        --workaround-bios-boot-flag

            Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled


        --debugging-internal-function-call <function name> (function_argument)...

            Development option for developers to test certain function without running the entire build


        --target-filesystem, --tgt-fs <filesystem name>

            Specify the filesystem to use as the target partition's filesystem.

            Currently supported: FAT(default)/NTFS


        --for-gui

            No longer supported, reserved for compatibility with the wrapper programs


    Unmounting and removing "/tmp/woeusb-source-20210317-182826-Wednesday.FCkHxc"...

    umount: /tmp/woeusb-source-20210317-182826-Wednesday.FCkHxc: not mounted.

    cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-source-20210317-182826-Wednesday.FCkHxc".

    Unmounting and removing "/tmp/woeusb-target-20210317-182826-Wednesday.wRomcE"...

    umount: /tmp/woeusb-target-20210317-182826-Wednesday.wRomcE: not mounted.

    cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-target-20210317-182826-Wednesday.wRomcE".

    Some mountpoints are not unmount/cleaned successfully and must be done manually

Güncelleyip ekledim linki, orada .bash dosyası var zaten.[/CODE]
Sonradan düzenledi.
 
Windows_10.iso yazan yeri kendi dosya adınla yazacaksın. Dosyanın yolunu da belirtmeyi unutma.
Hocam dosya yolunu mu yanlış belirtiyorum anlamadım 😞
Kod:
acar@Root:~/İndirilenler$ sudo bash woeusb-5.0.8.bash --device --partition sda5/home/acar/Desktop/Win10.iso /dev/sdb
ERROR: Unknown command-line argument "/dev/sdb"
WoeUSB 5.0.8 Help Information
======================================
WoeUSB can create a bootable Microsoft Windows(R) USB storage device from an existing Windows optical disk or an ISO disk image.

Currently two creation methods are supported:

    --device, -d

        Completely WIPE the entire USB storage device, then build a bootable Windows USB device from scratch.
        WARNING: All previous data on the device will be gone!

        woeusb-5.0.8 --device <source media path> <device>
        Examples:
        - woeusb-5.0.8 --device Windows7_x64.iso /dev/sdX
        - woeusb-5.0.8 --device /dev/sr0 /dev/sdX

    --partition, -p

        Copy Windows files to an existing partition of a USB storage device and make it bootable.  This allows files to coexist as long as no filename conflict exists.
        WARNING: All files that has the same name will be overwritten!

        woeusb-5.0.8 --partition <source media path> <partition>
        Examples:
        - woeusb-5.0.8 --partition Windows7_x64.iso /dev/sdX1
        - woeusb-5.0.8 --partition /dev/sr0 /dev/sdX1

## Command-line Options ##
    --verbose, -v
        Verbose mode

    --help, -h
        Show this help message and exit

    --version, -V
        Print application version

    --about, -ab
        Show info about this application

    --no-color
        Disable message coloring

    --debug
        Enable script debugging

    --label, -l <filesystem_label>
        Specify label for the newly created file system in --device creation method
        Note that the label is not verified for validity and may be illegal for the filesystem

    --workaround-bios-boot-flag
        Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled

    --debugging-internal-function-call <function name> (function_argument)...
        Development option for developers to test certain function without running the entire build

    --target-filesystem, --tgt-fs <filesystem name>
        Specify the filesystem to use as the target partition's filesystem.
        Currently supported: FAT(default)/NTFS

    --for-gui
        No longer supported, reserved for compatibility with the wrapper programs

Unmounting and removing "/tmp/woeusb-source-20210317-183656-Wednesday.586PBP"...
umount: /tmp/woeusb-source-20210317-183656-Wednesday.586PBP: not mounted.
cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-source-20210317-183656-Wednesday.586PBP".
Unmounting and removing "/tmp/woeusb-target-20210317-183656-Wednesday.ad70rk"...
umount: /tmp/woeusb-target-20210317-183656-Wednesday.ad70rk: not mounted.
cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-target-20210317-183656-Wednesday.ad70rk".
Some mountpoints are not unmount/cleaned successfully and must be done manually
Ek olarak belirteyim lsblk -l çıktısını USB belleğin takılıyken atar mısın?
Kod:
lsblk -l
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0   7:0    0 156,7M  1 loop /snap/code/59
loop1   7:1    0  99,2M  1 loop /snap/core/10859
sda     8:0    0 465,8G  0 disk 
sda1    8:1    0   100M  0 part /boot/efi
sda2    8:2    0    16M  0 part 
sda3    8:3    0 217,1G  0 part 
sda4    8:4    0 168,5G  0 part 
sda5    8:5    0    80G  0 part /
sdb     8:16   1  29,3G  0 disk 
sdb1    8:17   1  29,2G  0 part 
sr0    11:0    1  1024M  0 rom
 
Bash:
sudo bash woeusb-5.0.8.bash --device sda5/home/acar/Desktop/Win10.iso /dev/sdb1
Bunu dene bir bakalım.
Maalesef;
Kod:
acar@Root:~/İndirilenler$ sudo bash woeusb-5.0.8.bash --device sda5/home/acar/Desktop/Win10.iso /dev/sdb1
WoeUSB v5.0.8
==============================
check_runtime_parameters: Error: source media "sda5/home/acar/Desktop/Win10.iso" not found or not a regular file or a block device file!
WoeUSB 5.0.8 Help Information
======================================
WoeUSB can create a bootable Microsoft Windows(R) USB storage device from an existing Windows optical disk or an ISO disk image.

Currently two creation methods are supported:

    --device, -d

        Completely WIPE the entire USB storage device, then build a bootable Windows USB device from scratch.
        WARNING: All previous data on the device will be gone!

        woeusb-5.0.8 --device <source media path> <device>
        Examples:
        - woeusb-5.0.8 --device Windows7_x64.iso /dev/sdX
        - woeusb-5.0.8 --device /dev/sr0 /dev/sdX

    --partition, -p

        Copy Windows files to an existing partition of a USB storage device and make it bootable.  This allows files to coexist as long as no filename conflict exists.
        WARNING: All files that has the same name will be overwritten!

        woeusb-5.0.8 --partition <source media path> <partition>
        Examples:
        - woeusb-5.0.8 --partition Windows7_x64.iso /dev/sdX1
        - woeusb-5.0.8 --partition /dev/sr0 /dev/sdX1

## Command-line Options ##
    --verbose, -v
        Verbose mode

    --help, -h
        Show this help message and exit

    --version, -V
        Print application version

    --about, -ab
        Show info about this application

    --no-color
        Disable message coloring

    --debug
        Enable script debugging

    --label, -l <filesystem_label>
        Specify label for the newly created file system in --device creation method
        Note that the label is not verified for validity and may be illegal for the filesystem

    --workaround-bios-boot-flag
        Workaround BIOS bug that won't include the device in boot menu if non of the partition's boot flag is toggled

    --debugging-internal-function-call <function name> (function_argument)...
        Development option for developers to test certain function without running the entire build

    --target-filesystem, --tgt-fs <filesystem name>
        Specify the filesystem to use as the target partition's filesystem.
        Currently supported: FAT(default)/NTFS

    --for-gui
        No longer supported, reserved for compatibility with the wrapper programs

Unmounting and removing "/tmp/woeusb-source-20210317-184506-Wednesday.U6N4aH"...
umount: /tmp/woeusb-source-20210317-184506-Wednesday.U6N4aH: not mounted.
cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-source-20210317-184506-Wednesday.U6N4aH".
Unmounting and removing "/tmp/woeusb-target-20210317-184506-Wednesday.LunKtD"...
umount: /tmp/woeusb-target-20210317-184506-Wednesday.LunKtD: not mounted.
cleanup_mountpoint: Warning: Unable to unmount "/tmp/woeusb-target-20210317-184506-Wednesday.LunKtD".
Some mountpoints are not unmount/cleaned successfully and must be done manually
 
Belirttiğiniz dosya yolunda hata olabilir. Bir daha kontrol edin.
Kod:
acar@Root:/$ cd home
acar@Root:/home$ cd Masaüstü
bash: cd: Masaüstü: Böyle bir dosya ya da dizin yok
acar@Root:/home$ cd acar
acar@Root:~$ cd Desktop
bash: cd: Desktop: Böyle bir dosya ya da dizin yok
acar@Root:~$ dir
Belgeler  etcher  Genel  İndirilenler  Masaüstü  Müzik  Resimler  snap  Şablonlar  Ventoy  Videolar  WoeUSB
acar@Root:~$ cd Masaüstü
acar@Root:~/Masaüstü$ dir
Win10.iso  wwwroot
acar@Root:~/Masaüstü$
Belirttiğiniz dosya yolunda hata olabilir. Bir daha kontrol edin.
Hocam Teamviewer'dan bağlanma şansınız varsa müsaitim.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Technopat Haberler

Geri
Yukarı