No Boot to bios or windows with 4 tb usb ext HD connected

frazld

Reputable
Nov 26, 2014
6
0
4,510
Sorry if this is a repeat I cant find my original post.

Toshiba Lap top i3, Windows 7 64bit, 8 gb ram, updated bios and drivers
Seagate Back up Plus desktop 4 tb, usb, hard drive, external power.

System will not boot to bios or windows with this drive connected no mater which usb port is connected.
In Bios boot to usb is disabled.

With it disconnected I can boot to both bios & windows.

In windows it shows up in computer management as 3.726 tb I can read and write to it.

After booting to bios and connecting the drive, bios doesn't pick it up.

It was original formatted as NTFS and did the same,
I reformatted to exFAT and still the same.

Any suggestion to recognize the drive at boot up.

Update:
I ran diskmgmt.msc, right clicked on left drive tab, and the convert to GPT Disk
is greyed out.
I'm assuming that it is allready initialized as a GPT.
Also from http://support.microsoft.com/kb/2581408

It's not supported if not 64 bit, but with limitations.
Boot Volume
UEFI + GPT
Supported; requires a 64-bit version of Windows
BIOS + GPT
Boot volume not supported
UEFI + MBR
Boot volume not supported

non-booting data volumes
>2 TB single disk – MBR = Supports up to 2 TB of addressable capacity
>2 TB single disk – Hybrid-MBR = Not Supported
>2 TB single disk – GPT = Supports full capacity

Ok I think I got it.
Windows will read the drive if it id GPT, but wont boot to or with it.
and the bios could read it supports GPT, but will still hang on boot due to above.

But I'm not trying to boot off the drive.
So I'm assuming that they also mean that there will be no boot what so ever.

Does that make sense?



 

frazld

Reputable
Nov 26, 2014
6
0
4,510



Thanks for replying. I updated my orig post with what little knowledge I have on the subject.
Could you look at the lower part and see if I'm close to the answer?
 

DataMedic

Honorable
Nov 22, 2013
384
0
10,960
I get what you're suggesting, but the issue is unrelated to how the drive is formatted or partitioned. It's almost certainly related to the UEFI secure boot which locks the computer to only be able to boot to the specific hard drive it's linked with. Anything which the UEFI views as an attempt to boot from USB is blocked. The only way around this (if you want to boot from something else) is to disable secure boot and enable legacy boot in the BIOS (if those options are available).

I had a Toshiba laptop here a while back where the user had forgot their password and the BIOS was missing the toggles to enable legacy boot (a bios update fixed that, but the update would only run in Windows). I ended up having to hack the ease of access tools to get into the computer just to update the bios and fix it.

The whole secure boot thing is an attempt to prevent being able to use a linux live CD to gain access to files you shouldn't be able to get to. But it's more of a hassle than anything else. Sure taught me to never buy a Toshiba laptop.
 

frazld

Reputable
Nov 26, 2014
6
0
4,510



LOL.
I'll check that out see if my bios will do that.
Seagate could saved me a lot of time if they said if might only be used as a non boot device.
Which I don't mind should have let me know.
Nothing on their support sit about this.
 

DataMedic

Honorable
Nov 22, 2013
384
0
10,960
Actually in your case, since you're not looking to boot from USB I'd disable "legacy USB" and just make sure that your internal HDD is at the top of the boot priority.

Try that both ways, with "secure boot" enabled, and with it disabled.
 

DataMedic

Honorable
Nov 22, 2013
384
0
10,960
It's nothing to do with your Seagate drive. It absolutely can be used as a boot device (on all computers that don't use secure boot). Problem is Toshiba wants you to have to buy replacement hard drives from them instead of aftermarket, so they lock the computer to it.
 

frazld

Reputable
Nov 26, 2014
6
0
4,510



LOL.
I'll check that out see if my bios will do that.
Seagate could saved me a lot of time if they said if might only be used as a non boot device.
Which I don't mind should have let me know.
Nothing on their support sit about this.