Dell E5580 Bios doesn't see bootable usb drive containing iso of 17.10
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I'm trying to install ubuntu 17.10 onto a Dell Latitude E5580 from a usb stick onto which I've burned the 17.10 iso using gnome-disks. I've done exactly the same thing with the 16.04 iso and it worked fine (and still does). The problem is that when I hit F12 and boot options come up, the stick containing the 17.10 iso is not seen. When I do exactly the same thing with the usb stick containing the 16.04 iso, bios sees the stick under UEFI options, and I can boot to the stick. As far as I can tell the two sticks have the same structure. I've tried the same thing on two almost identical Dells, and the problem is the same on both. I've also loaded the 17.10 iso onto a different usb drive, with the same problem.
One difference that I do notice is that the 17.10 iso is on a usb3 drive while the 16.04 iso is on a usb2 drive. Could that possibly be the source of the problem, and if so, why? Isn't usb3 supposed to be better?
Here's the output of fdisk -l. sdb1 contains the 17.10 iso, and sdb2 contains the 16.04
Disk /dev/sdb: 28.9 GiB, 31004295168 bytes, 60555264 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: 0x97f903c8
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 60555263 60547200 28.9G c W95 FAT32 (LBA)
Disk /dev/sdc: 3.8 GiB, 4007657472 bytes, 7827456 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: 0xc3072e18
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 8064 7827455 7819392 3.7G c W95 FAT32 (LBA)
When I mount the drive sdb1 containing the 17.10 iso, all of the ingredients for booting seem in place. Here's the content of the mount point:
simon@E5580:/mnt/usb>lt
total 76
-r--r--r-- 3463 Jan 5 12:55 md5sum.txt
dr-xr-xr-x 2048 Jan 5 12:55 boot/
dr-xr-xr-x 2048 Jan 5 12:55 EFI/
dr-xr-xr-x 4816 Jan 5 12:55 isolinux/
dr-xr-xr-x 2048 Jan 5 12:55 casper/
dr-xr-xr-x 2048 Jan 5 12:55 install/
dr-xr-xr-x 2048 Jan 5 12:55 .disk/
dr-xr-xr-x 2048 Jan 5 12:54 dists/
dr-xr-xr-x 2048 Jan 5 12:54 pics/
dr-xr-xr-x 2048 Jan 5 12:54 pool/
dr-xr-xr-x 2048 Jan 5 12:54 preseed/
-r--r--r-- 229 Jan 5 12:54 README.diskdefines
lr-xr-xr-x 1 Jan 5 12:54 ubuntu -> ./
Could somebody please suggest why my BIOS is not seeing the sdb1 drive?
boot system-installation usb
asked Feb 26 at 5:25
Leo Simon
5101721
add a comment |Â
up vote
0
down vote
favorite
I'm trying to install ubuntu 17.10 onto a Dell Latitude E5580 from a usb stick onto which I've burned the 17.10 iso using gnome-disks. I've done exactly the same thing with the 16.04 iso and it worked fine (and still does). The problem is that when I hit F12 and boot options come up, the stick containing the 17.10 iso is not seen. When I do exactly the same thing with the usb stick containing the 16.04 iso, bios sees the stick under UEFI options, and I can boot to the stick. As far as I can tell the two sticks have the same structure. I've tried the same thing on two almost identical Dells, and the problem is the same on both. I've also loaded the 17.10 iso onto a different usb drive, with the same problem.
One difference that I do notice is that the 17.10 iso is on a usb3 drive while the 16.04 iso is on a usb2 drive. Could that possibly be the source of the problem, and if so, why? Isn't usb3 supposed to be better?
Here's the output of fdisk -l. sdb1 contains the 17.10 iso, and sdb2 contains the 16.04
Disk /dev/sdb: 28.9 GiB, 31004295168 bytes, 60555264 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: 0x97f903c8
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 60555263 60547200 28.9G c W95 FAT32 (LBA)
Disk /dev/sdc: 3.8 GiB, 4007657472 bytes, 7827456 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: 0xc3072e18
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 8064 7827455 7819392 3.7G c W95 FAT32 (LBA)
When I mount the drive sdb1 containing the 17.10 iso, all of the ingredients for booting seem in place. Here's the content of the mount point:
simon@E5580:/mnt/usb>lt
total 76
-r--r--r-- 3463 Jan 5 12:55 md5sum.txt
dr-xr-xr-x 2048 Jan 5 12:55 boot/
dr-xr-xr-x 2048 Jan 5 12:55 EFI/
dr-xr-xr-x 4816 Jan 5 12:55 isolinux/
dr-xr-xr-x 2048 Jan 5 12:55 casper/
dr-xr-xr-x 2048 Jan 5 12:55 install/
dr-xr-xr-x 2048 Jan 5 12:55 .disk/
dr-xr-xr-x 2048 Jan 5 12:54 dists/
dr-xr-xr-x 2048 Jan 5 12:54 pics/
dr-xr-xr-x 2048 Jan 5 12:54 pool/
dr-xr-xr-x 2048 Jan 5 12:54 preseed/
-r--r--r-- 229 Jan 5 12:54 README.diskdefines
lr-xr-xr-x 1 Jan 5 12:54 ubuntu -> ./
Could somebody please suggest why my BIOS is not seeing the sdb1 drive?
boot system-installation usb
asked Feb 26 at 5:25
Leo Simon
5101721
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to install ubuntu 17.10 onto a Dell Latitude E5580 from a usb stick onto which I've burned the 17.10 iso using gnome-disks. I've done exactly the same thing with the 16.04 iso and it worked fine (and still does). The problem is that when I hit F12 and boot options come up, the stick containing the 17.10 iso is not seen. When I do exactly the same thing with the usb stick containing the 16.04 iso, bios sees the stick under UEFI options, and I can boot to the stick. As far as I can tell the two sticks have the same structure. I've tried the same thing on two almost identical Dells, and the problem is the same on both. I've also loaded the 17.10 iso onto a different usb drive, with the same problem.
One difference that I do notice is that the 17.10 iso is on a usb3 drive while the 16.04 iso is on a usb2 drive. Could that possibly be the source of the problem, and if so, why? Isn't usb3 supposed to be better?
Here's the output of fdisk -l. sdb1 contains the 17.10 iso, and sdb2 contains the 16.04
Disk /dev/sdb: 28.9 GiB, 31004295168 bytes, 60555264 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: 0x97f903c8
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 60555263 60547200 28.9G c W95 FAT32 (LBA)
Disk /dev/sdc: 3.8 GiB, 4007657472 bytes, 7827456 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: 0xc3072e18
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 8064 7827455 7819392 3.7G c W95 FAT32 (LBA)
When I mount the drive sdb1 containing the 17.10 iso, all of the ingredients for booting seem in place. Here's the content of the mount point:
simon@E5580:/mnt/usb>lt
total 76
-r--r--r-- 3463 Jan 5 12:55 md5sum.txt
dr-xr-xr-x 2048 Jan 5 12:55 boot/
dr-xr-xr-x 2048 Jan 5 12:55 EFI/
dr-xr-xr-x 4816 Jan 5 12:55 isolinux/
dr-xr-xr-x 2048 Jan 5 12:55 casper/
dr-xr-xr-x 2048 Jan 5 12:55 install/
dr-xr-xr-x 2048 Jan 5 12:55 .disk/
dr-xr-xr-x 2048 Jan 5 12:54 dists/
dr-xr-xr-x 2048 Jan 5 12:54 pics/
dr-xr-xr-x 2048 Jan 5 12:54 pool/
dr-xr-xr-x 2048 Jan 5 12:54 preseed/
-r--r--r-- 229 Jan 5 12:54 README.diskdefines
lr-xr-xr-x 1 Jan 5 12:54 ubuntu -> ./
Could somebody please suggest why my BIOS is not seeing the sdb1 drive?
boot system-installation usb
asked Feb 26 at 5:25
Leo Simon
5101721
I'm trying to install ubuntu 17.10 onto a Dell Latitude E5580 from a usb stick onto which I've burned the 17.10 iso using gnome-disks. I've done exactly the same thing with the 16.04 iso and it worked fine (and still does). The problem is that when I hit F12 and boot options come up, the stick containing the 17.10 iso is not seen. When I do exactly the same thing with the usb stick containing the 16.04 iso, bios sees the stick under UEFI options, and I can boot to the stick. As far as I can tell the two sticks have the same structure. I've tried the same thing on two almost identical Dells, and the problem is the same on both. I've also loaded the 17.10 iso onto a different usb drive, with the same problem.
One difference that I do notice is that the 17.10 iso is on a usb3 drive while the 16.04 iso is on a usb2 drive. Could that possibly be the source of the problem, and if so, why? Isn't usb3 supposed to be better?
Here's the output of fdisk -l. sdb1 contains the 17.10 iso, and sdb2 contains the 16.04
Disk /dev/sdb: 28.9 GiB, 31004295168 bytes, 60555264 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: 0x97f903c8
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 8064 60555263 60547200 28.9G c W95 FAT32 (LBA)
Disk /dev/sdc: 3.8 GiB, 4007657472 bytes, 7827456 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: 0xc3072e18
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 8064 7827455 7819392 3.7G c W95 FAT32 (LBA)
When I mount the drive sdb1 containing the 17.10 iso, all of the ingredients for booting seem in place. Here's the content of the mount point:
simon@E5580:/mnt/usb>lt
total 76
-r--r--r-- 3463 Jan 5 12:55 md5sum.txt
dr-xr-xr-x 2048 Jan 5 12:55 boot/
dr-xr-xr-x 2048 Jan 5 12:55 EFI/
dr-xr-xr-x 4816 Jan 5 12:55 isolinux/
dr-xr-xr-x 2048 Jan 5 12:55 casper/
dr-xr-xr-x 2048 Jan 5 12:55 install/
dr-xr-xr-x 2048 Jan 5 12:55 .disk/
dr-xr-xr-x 2048 Jan 5 12:54 dists/
dr-xr-xr-x 2048 Jan 5 12:54 pics/
dr-xr-xr-x 2048 Jan 5 12:54 pool/
dr-xr-xr-x 2048 Jan 5 12:54 preseed/
-r--r--r-- 229 Jan 5 12:54 README.diskdefines
lr-xr-xr-x 1 Jan 5 12:54 ubuntu -> ./
Could somebody please suggest why my BIOS is not seeing the sdb1 drive?
boot system-installation usb
boot system-installation usb
asked Feb 26 at 5:25
Leo Simon
5101721
asked Feb 26 at 5:25
Leo Simon
5101721
edited Feb 26 at 12:52
asked Feb 26 at 5:25
Leo Simon
5101721
asked Feb 26 at 5:25
Leo Simon
5101721
asked Feb 26 at 5:25
Leo Simon
5101721
5101721
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51
add a comment |Â
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009828%2fdell-e5580-bios-doesnt-see-bootable-usb-drive-containing-iso-of-17-10%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Copied == burned?
– TheOneAboveAll
Feb 26 at 6:39
sorry, I've edited the original, yes burned
– Leo Simon
Feb 26 at 12:51