I copied openSUSE-13.1-DVD-x86_64.iso onto a virgin 16GB USB stick using SUSE Studio Imagewriter 1.10.
I change the boot order of my BIOS so that the USB device is first in the boot order
Nevertheless, my computer refuses to boot from the USB stick, but always boots instead from the hard disk (position 3 in the boot order) instead.
What am I doing wrong? :’(
Cheers
hn
I have always used UNetbootin to create my bootable USBs and use gparted to format my USBs to Fat32 first. I never had troubles. What works for me may not work for you.
It is not recommended to is special softwareto mod the image for openUSE. the basic idea is to simply do a binary copy.
On my machine I have to plug the USB in before the boot and go to the boot selection and move the USB to the top then continue every time since it does not remember the order if the USB is not in place.
So the problem could be just a bad BIOS.
How old is the machine? BIOS or UEFI?
Have you tried the USB boot on another machine?
Did you do the creation from Linux or Windows (which version?)?
On 2014-01-10 23:16, sammiev wrote:
>
> I have always used ‘UNetbootin’ (http://unetbootin.net/) to create my
> bootable USBs and use gparted to format my USBs to Fat32 first. I never
> had troubles. What works for me may not work for you.
That’s absolutely not recommended for openSUSE.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Don’t I need to put a boot loader on the USB stick(s) as well? But how and where? :\
Cheers
hn
Are you attempting to make a bootable Linux OS (like, say, OpenSUSE 13.1) USB? If so, you can try the (modified by you) dd command I’ll post as an example. If not a linux OS USB, then ignore me…
pat@Pats-Main:~$ sudo blkid
[sudo] password for pat:
/dev/sda1: UUID="f5dbf091-6f5d-6d15-6e95-5cdd99c2a3d4" UUID_SUB="c10affb5-10d9-d18b-2c93-ceffe1fa6b32" LABEL="Pats-Main:0" TYPE="linux_raid_member"
/dev/sda2: UUID="CB1D-5BFF" TYPE="vfat"
/dev/sdb1: UUID="f5dbf091-6f5d-6d15-6e95-5cdd99c2a3d4" UUID_SUB="c81bbcfa-f496-8e2b-a524-f36b5cd3db55" LABEL="Pats-Main:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="923456be-0667-4d81-acd0-94871c6352aa" TYPE="swap"
/dev/sdc1: UUID="935a295e-8ace-440e-ad48-e7b7f4f48481" TYPE="ext4"
/dev/md0: UUID="3bda19a1-88ba-4e83-8efb-5973c4a53f9e" TYPE="ext4"
/dev/sdd1: LABEL="Ubuntu-Server 13.10 amd64" TYPE="iso9660"
/dev/sdd2: SEC_TYPE="msdos" UUID="A671-24BC" TYPE="vfat"
This tells me that my USB is listed as /dev/sdd
pat@Pats-Main:~$ sudo dd if=~/Downloads/OS/openSUSE-13.1-DVD-x86_64.iso of=/dev/sdd bs=4096
1116416+0 records in
1116416+0 records out
4572839936 bytes (4.6 GB) copied, 590.043 s, 7.8 MB/s
This tells the system to copy the OpenSUSE 13.1 iso I have to the /dev/sdd in block sizes of 4096. It completely overwrites what is already there (as you can see, it was Ubuntu Server) with the iso.
pat@Pats-Main:~$ sudo blkid
[sudo] password for pat:
/dev/sda1: UUID="f5dbf091-6f5d-6d15-6e95-5cdd99c2a3d4" UUID_SUB="c10affb5-10d9-d18b-2c93-ceffe1fa6b32" LABEL="Pats-Main:0" TYPE="linux_raid_member"
/dev/sda2: UUID="CB1D-5BFF" TYPE="vfat"
/dev/sdb1: UUID="f5dbf091-6f5d-6d15-6e95-5cdd99c2a3d4" UUID_SUB="c81bbcfa-f496-8e2b-a524-f36b5cd3db55" LABEL="Pats-Main:0" TYPE="linux_raid_member"
/dev/sdb2: UUID="923456be-0667-4d81-acd0-94871c6352aa" TYPE="swap"
/dev/sdc1: UUID="935a295e-8ace-440e-ad48-e7b7f4f48481" TYPE="ext4"
/dev/md0: UUID="3bda19a1-88ba-4e83-8efb-5973c4a53f9e" TYPE="ext4"
/dev/sdd1: SEC_TYPE="msdos" LABEL="BOOT" UUID="BED8-013D" TYPE="vfat"
/dev/sdd2: LABEL="openSUSE-13.1-DVD-x86_640091" TYPE="iso9660"
As you can see, The info changes and OpenSUSE 13.1 was copied successfully. I don’t have any issues booting from my USB’s created this way.
WARNING- dd is a potentially destructive command, capable of destroying an entire harddrive. Use with caution
On 2014-01-11 11:26, hnimmo wrote:
> 3. I did the creation on OpenSUSE
> 13.1 / Gnome 3.10 using SUSE Studio Imagewriter 1.10 Don’t I need to
> put a boot loader on the USB stick(s) as well? But how and where? :\
Certainly not!
The openSUSE images already contain the appropriate boot loader. If you
attempt to add a bootloader yourself you destroy the image.
You create the USB stick per the instructions on the webpage. Do not
even try to use unetbootin or any such thing. You just do a raw copy
of the image (which you have to verify it is a correct download), using
imagewriter or ImageUSB from ‘Tools for OSForensics -
ImageUSB - Write an image to multiple USB Flash Drives’
http://www.osforensics.com/tools/write-usb-images.html
If you have a Linux machine, just do:
cp imagefile.iso /dev/sdX
making sure you have the correct “/dev/sdX” or you will destroy
completely another disk.
MIND: The step to verify that the downloaded image file is crucial, do
not skip it. If there was an error during the download (and they are
frequent on large files such as these), the installation will fail at
some point.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I did all that (as per instructions on the webpage) including verifying the checksum of the the iso file(s). My systems both refuse to boot from the ‘bootable’ USB stick although USB is at the top of the list in each case. How do I find out where the problem lies?
cheers
hn
On 2014-01-11 20:26, hnimmo wrote:
> I did all that (as per instructions on the webpage) including verifying
> the checksum of the the iso file(s). My systems both refuse to boot from
> the ‘bootable’ USB stick although USB is at the top of the list in each
> case. How do I find out where the problem lies?
I have not tried to modify the permanent boot list telling it to use the
USB. Instead, while the bios is doing the memory check, I press a
certain key and I get a list of the currently available boot media, and
I choose the usb one - which displays the brand name of the usb plugged
on it.
If you have tried different computers, that stick is obviously bad -
either that brand or model is bad (I have heard of such a case), or
something was not correct on the image “burning” or download.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I do not suspect the quality of the load files, since both check sums were OK, both USB sticks (one with 32-bit OS 13-1 and one with 64-bit OS 13.1) exhibit the same behaviour and both files were used successfully to install OpenSUSE 13.1 on respective machines. There must be something wrong with the procedure I am using, or perhaps the BIOSs (both different)
What I have discovered on the 32-bit configuration is that I can put ‘USB HDD’ (instead of ‘USB key’ at the top of the boot list and it works!
The 64-bit BIOS has no similar possibility.
Cheers
hn