I haven’t gotten as far as gongalov71 in another recent thread.
Holding down F12 at post up, My Toshiba (UEFI) laptop is set to boot from:
1 USB
2 Optical Drive
3 HDD
4 Network
5 <Go To Settings>
My fat32 USB with Leap 15 .iso on it will not boot, nor will another Linux ‘live’ fat32 USB. Windows Fast Boot is off. BIOS secure boot is disabled.
I am not sure about UEFI to CSM, but I will check it.
Additional info, HDD is 500 GB split into two partitions approximately 250GB each, plus the usual system and whatever small partitions at the beginning of the drive.
There are ‘recovery’ partitions I will likely delete, as I am not concerned about them as I do have a recovery USB if I need it (yeah it works).
My question is, IF I have to set BIOS to CSM, and get Leap Installed, will I still be able to have Win10 in the boot menu?
I am not sure I understand this. An USB mass storage device is either partitioned (often in only one partition) and may then have a fat32 file system on that partition, or it has an ISO on it.
Thus either you copied the ISO to the partition, which then does no longer contain a fat32 file system, or you copied it to the device, which then no longer has any partitions on it.
BTW the second method is the correct one. do not copy to /dev/sdx1, but to /dev/sdx (with the cor5rect x of course).
I agree with the rest of your post, and the most likely reason for not seeing a bootable USB device is copying the ISO image to a partition. But copying a Leap-15.0 .iso to a USB device does produce a vfat partition. This bootable USB flash memory stick was produced with
“dd bs=4K if=openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso of=/dev/sdb”
rayh@y3:~> sudo /usr/bin/lsblk --fs /dev/sdb
NAME FSTYPE LABEL UUID MOUNTPOINT
sdb iso9660 openSUSE-Leap-15.0-DVD-x86_64258 2018-05-15-13-58-33-06
├─sdb1 vfat CDBA-175B
└─sdb2 iso9660 openSUSE-Leap-15.0-DVD-x86_64258 2018-05-15-13-58-28-09
rayh@y3:~> sudo /usr/sbin/parted /dev/sdb p
Model: TOSHIBA USB FLASH DRIVE (scsi)
Disk /dev/sdb: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Number Start End Size Type File system Flags
1 1333kB 5333kB 4000kB primary esp, type=ef
2 5333kB 3916MB 3911MB primary boot, hidden, type=17
In any case, talking about a “fat32 USB” makes no sense. I know that many people try to type less and less, but leaving out words that count does not help increasing knowledge. My first interpretation of “fat32 USB” would be “an USB device with a fat32 file system directly on the device (no partitioning)”, which is possible to create, but not many people do this.
Same as your “vfat partition”, which in fact is “a partition with a vfat file system” (it is in fact a partition of type ef). It makes things shorter and many will understand what is meant, but at the same time, those who are uneasy at what all these words like “mass-storage device”, “partition”, “file system” really mean will probably never learn to understand. And then, when the documentations say “copy to the device”, it is easy to make the error and copy to the partition.
Because of surrounding context, I took it to mean USB with an EFI partition. I’m guessing that the EFI partition is probably FAT16, not FAT32.
In any case, the OP should recheck how he created that USB. He will need to be able to boot the installer in UEFI mode to properly install openSUSE in a way that is compatible with the already installed Windows.
Life story of the Leap 15 USB stick.(and then some)
Leap 15 .iso was put on the stick on my MRB desktop, using Universal USB Installer(UUI for future reference) within the Win10 system.
IIRC the 16GB stick was not formatted but may have had a single partition(I could be wrong, too long ago when I did it).
UUI informed me the stick would be formatted to fat32 before writing the .iso to the USB stick.
UUI then proceeded to copy the .iso to the stick.(Not dd image).
UUI finished that, and I could boot it on my MRB desktop as the boot sequence is the same as I described in my OP.
I could burn the .iso to a DVD(if I had one), but I am not sure if the UEFI system would boot from it either, even if it was burned using the UEFI laptop.
I could re-do the stick in openSUSE(on my desktop), and hope it will boot on the UEFI laptop. Another learning process for me.
More later as needed, or it just may not be worth the trouble!
Life story of the Leap 15 USB stick.(and then some)
Leap 15 .iso was put on the stick on my MRB desktop, using Universal USB
Installer(UUI for future reference) within the Win10 system.
IIRC the 16GB stick was not formatted but may have had a single
partition(I could be wrong, too long ago when I did it).
UUI informed me the stick would be formatted to fat32 before writing the
…iso to the USB stick.
UUI then proceeded to copy the .iso to the stick.(Not dd image).
UUI finished that, and I could boot it on my MRB desktop as the boot
sequence is the same as I described in my OP.
I could burn the .iso to a DVD(if I had one), but I am not sure if the
UEFI system would boot from it either, even if it was burned using the
UEFI laptop.
I could re-do the stick in openSUSE(on my desktop), and hope it will
boot on the UEFI laptop. Another learning process for me.
More later as needed, or it just may not be worth the trouble!
Hi
In linux you can see what the partitions are…;
/usr/sbin/fdisk -l openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso
Disk openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso: 3.7 GiB, 3916431360 bytes, 7649280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7e5278e3
Device Boot Start End
Sectors Size Id Type
openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso1 2604 10415 7812 3.8M ef EFI (FAT-12/16/32)
openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso2 * 10416 7649279 7638864 3.7G 17 Hidden HPFS/NTFS
I just use dd to lay the image down (as root user)… eg
The medium will boot either UEFI or legacy, note you may need to check
the system BIOS for the likes of CSM or UEFI to boot in UEFI mode.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
That is undoubtedly the easiest option. Microsoft software is designed to make technical stuff hard – it keeps their certifiable distribution network in business.
Note the iso must be copied without changes or modification. Some “Linux” copy programs mode the image. If you must use Windows to make the installer use one that is binary only copying. Like https://www.osforensics.com/tools/write-usb-images.html or be sure any option that may mode the iso is not used. ie binary copy only to the device not to a partition.
As stated in OP, Fast Boot is OFF, BIOS Secure Boot is Disabled.
I checked UEFI while trying to get it to boot, and it is and has been UEFI.
This is what I get for fdisk -l when the stick is inserted.
Disk /dev/sdd: 15 GiB, 16079781888 bytes, 31405824 sectorsUnits: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x040ebc23
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 31405823 31403776 15G c W95 FAT32 (LBA)
If I put the iso image in the command line as you stated, fdisk -l errors out
'fdisk: cannot open openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso: No such file or directory
Gparted shows it as
Partition File System Label Size Used UnUsed Flags
/dev/sdd1 fat32 openSUSE LE 14.97GB 130.02MiB 14.85GB boot,LBA, type
OpenSUSE LE is just the USB stick label, not the version on the stick.
The Windows download directory for Leap 15 has both the DVD(3.6GB) and the NET(118MiB) versions, so I am guessing I used the NET version when writing the USB stick with UUI.
A qualifier, I probably also used the NET version for my original install of Leap 42.3. <<< Confirmed only the disk label is UUI instead of openSUSE LE. >>>
In my mind it should make no difference if DVD or NET version. I could be wrong.
It will likely come to that if I decide to carry forward with it. Now that I know the Linux command to do it.
I have tried imageUSB in the past, and all I ever got was ERROR, Failure to write image AFTER the long, long process of writing the image(a waste of time IMO when it could just say CAN’T DO IT!)). This regardless if ISO or dd in the selection. Which is why I use YUMI for making live versions, and UUI for writing as ISO or dd image for install.
Thanks to all that once again responded and to those that use these ‘newbie posts’ as teaching moments.
From experience here any modification to the ISO will break it for openSUSE. Some distros may need mod or tolerate it but openSUSE must be a unmodified binary copy to the disk. It appears the program you used modified it to live on a FAT partition which of course breaks it.
This is what a proper functional install drive looks like
Disk /dev/sdd: 14.6 GiB, 15698231296 bytes, 30660608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x135a2181
Device Boot Start End Sectors Size Id Type
/dev/sdd1 4084 11643 7560 3.7M ef EFI (FAT-12/16/32)
/dev/sdd2 * 11644 8562687 8551044 4.1G 17 Hidden HPFS/NTFS
Hi
No you point it at the raw device (in my case /dev/sdb), not a partition… the device is overwritten by the image and will lay down it’s own partitions as per the iso image.
Personally I use cp command but dd works fine too but to the device not a partition on the device. Point is to do an unaltered binary copy to the device.
Can you please post complete between CODE tags, that is with the line that has the prompt and the command before and the line that has the new prompt after the output. Then you do not have to type things like “Gparted gives:”, and we can be 100% sure about what command you gave, etc.
