Solved Lost access to BIOS after adding a 2nd M.2 SSD

Megahertz said:

Only MBR has a limit of 4 Primary partitions and (using a 512-byte sectors) a drive size of 2.2T (one or multi partitions)

Master boot record - Wikipedia

en.wikipedia.org

Click to expand...

I can only speak from personal experience. Here is MS community link addressing this problem:

My friend, who is light years ahead of me in his knowledge and expertise, had an old SATA II Seagate external hard drive. He could not get it to keep the full 3TB as a single partition until he converted it to GPT. However, it kept on reverting back to 2.2 TB and leaving the rest unallocated even after he converted the drive to GPT. It refused to hold the configuration. I was perplexed about it as I had not heard of such a thing before. I dismissed it as an anomaly.

About a year later, I had a WD "My Book" that began to behave the same way but it was 4TB. Converting it to GPT made no difference. I could go through the process but it would always revert to an unallocated partition. So the problem wasn't in Seagate architecture or design and it wasn't exclusive to Western Digital external hard drives either. The problem is with older mechanical hard drives. Since then I've run into this issue many times, especially with older WD "My Book" type drives and my solution to the problem is to break open the enclosure and remove the drive from the bridge (which often goes defective anyway) and pop it into a newer external enclosure. I still have an old WD drive like this and even with the replacement enclosure and after converting to GPT it won't keep the partitions unless I limit them to 2TB. That has been my personal experience. Key words: Older hard drives.

kanenas said:

You said GPT handles only up to 3TB partitions?!

I had no idea that GPT is also limited with such low partition sizes (in today's disk market).
This explains why after I converted the 4TB to GPT (as a single partition), the system wouldn't recognize it.

Until I resolve the BIOS problem, I can try convert it to GPT (after splitting it in two), using the Win 10 in my laptop.

There goes my weekend :)

Click to expand...

@kanenas I have only found this to be the case with older mechanical hard drives of the external variety. Should you decide to remove it from the enclosure you might be able to remedy this problem somewhat. It could very likely be a bad bridge in the original enclosure as this is a common issue with many older external drives. Of course I have no clue what you are using for an external enclosure so I could be barking up the wrong tree. All I know is that this problem is NOT exclusive to MBR drives. Perhaps it only happens to old external hard drives that have been converted to GPT. Anyway, that has been my personal experience.

My advice is to attempt to make your repairs one drive at a time. Physically disconnect all drives that you are not currently working on before booting up your PC. Make sure you have your boot order established each time you add a new drive to work on. If you have two operating systems using the same license key you will definitely have a recipe for trouble on your hands. You do not need two versions of Windows 11 running on the same PC anyway, do you? If you plan on running dual boot on your PC please specify. Freebooter and others here are very capable with helping in this regard. BUT we need to address these issues one at a time.

Concerning the MBR->GPT conversion, something is missing somewhere...
I retried the process using Win 10 in the laptop (it runs in MBR mode) and got the same results.

For screen cap 1:
I connected the external 4TB USB disk (in its original enclosure) to the laptop (Win 10). It showed as MBR.
I converted it to GPT using Minitool. It converted fine.
I rebooted Win 10, checked the USB and it was still in GPT mode. Windows Explorer could see and access any the files in it.

For screen cap 2 and 3:
I connected the 4TB USB (in GPT now but still using its original enclosure) to Win 11 (that runs in GPT mode).
Error 1: it wanted to initialize the disk
Error 2: (properties): shows the same thing.

This is getting frustrating (but still interesting).

Why Win 10 has no problems reading a GPT disk even though that system is set up for MBR, whereas Win 11 looks and finds something missing?

I'll plug the disk again in the new USB 3 enclosure but I've tried it before and don't expect miracles.

Screen cap 1:



Screen cap 2:



Screen cap 3:

Thank you Scannerman. Sorry, I hadn't seen your last post earlier.

The disk is certainly old but in perfect shape. I add backup files to it for years and it never had any errors.
But its age or the way they used to utilize a single 4TB partition, might have thrown off the "modern" systems.

I'll try and get rid of some stuff that's in it to reduce its "used space" size. At its current load, I hate to think how long it will take to split its partition in two :)
I'll try it after I can get to the BIOS, correct the USB settings and see if anything changed.
I'll post any updates sometime next week.

Enjoy the rest of the weekend.

kanenas said:

Thank you Scannerman. Sorry, I hadn't seen your last post earlier.

The disk is certainly old but in perfect shape. I add backup files to it for years and it never had any errors.
But its age or the way they used to utilize a single 4TB partition, might have thrown off the "modern" systems.

I'll try and get rid of some stuff that's in it to reduce its "used space" size. At its current load, I hate to think how long it will take to split its partition in two :)
I'll try it after I can get to the BIOS, correct the USB settings and see if anything changed.
I'll post any updates sometime next week.

Enjoy the rest of the weekend.

Click to expand...

I've already been to the farm and back today. It's shaping up to be a good weekend. Yeah, I'm thinking the older firmware might be the cause. Hard to say. Still, it shouldn't take that long to partition the drive into two separate partitions. The thing that will take time is ripping the files off the drive first. MiniTool makes partitioning easy. Anyway, that's what I would do with it.

If disk 3 is the drive we are talking about (see: screen cap 3) then it can't be read because it isn't initialized. If you initialize it you will loose all the data. So if you have any data you need to recover on disk 3 the time to act is now, before you initialize and reformat. Either way, that drive won't be showing up as usable until it is initialized. Of course, if you already have a back up of disk 3 you can initialize this drive and reformat right away. But after that you'll be back to square one as you will still have yet to partition the drive.

I have a question. Is your UEFI/BIOS set to RAID?

There were some MBR drives that use a 4096-byte sectors instead of using a 512-byte sectors. They were called AF (Advanced format)
This AF enabled MBR drives bigger than the 2.2 T
They had a different electronic control (512-byte Emulation (512e) Disk) and could have a strange behavior if formatted or initialize as a regular drive.

Megahertz said:

There were some MBR drives that use a 4096-byte sectors instead of using a 512-byte sectors. They were called AF (Advanced format)
This AF enabled MBR drives bigger than the 2.2 T

Advanced Format - Wikipedia

en.wikipedia.org

They had a different electronic control (512-byte Emulation (512e) Disk) and could have a strange behavior if formatted or initialize as a regular drive.

Click to expand...

Indubitably those would cost a fair dollar and would probably be used predominantly in the commercial/industrial field. My friend's Seagate was just your average external drive. I believe these sorts of drives come pre-configured so that the standard user could just start saving data to them directly without having to know much about the process of backing up data. The market for these things really exploded back in 2007, if I'm not mistaken, But they were notorious for developing bridge problems with the USB conversion. Often times there was really nothing wrong with the actual hard drive itself. People would crack open the cases, reformat the drive, and hook them up to SATA and they would work fine for years to come BUT anything over 3TB would present problems even if they were converted to GPT without being partitioned afterwards. I'm guessing the issue lies somewhere in the firmware. Perhaps some sort of shadow memory?

I don't suggest that all external hard drives are like this. The old Western Digital "My Books" were and my friend's old Seagate also had this problem. At first I thought it might be a thing that was exclusive to Western Digital SMR drives but that proved to be not the case. I'm having zero issues in this regard with my Seagate Backup Plus drives.

No RAID. I've used it ages ago at work on long-dead computers. The current desktop is to kill time pleasantly.

As for Advanced Format, I don't know. I was under the impression that its enclosure's chips pulled the trick.

Yes, we are talking about Disk 3.
When converted to GPT, Win 11 says it's uninitialized but why Win 10 has no problem with the same disk?
When set up as MBR (as it was initially), both used to recognize it just fine.

In the last iteration of this back-and-forth to MBR, Win 11 doesn't even see the disk when it's in MBR mode. Win 10 has no problems.

Which is why I blame myself for changing in the desktop BIOS the option on how to handle legacy USB. Either I set the wrong option or the BIOS programming didn't treat properly.
But that's an assumption... It could just be Win 11's handling of the oldie disks.

I'll know in a couple of days after I can get in and correct the BIOS setting.
As is, I can't even split the disk before Win 11 can see it. I have extra SSD storage to back up things in Win 11, but nothing in Win 10.

On the Advanced Format, something crossed my mind and I'll try it.
I'll put the disk in the new USB 3 enclosure I got for it and check if Win 10 still sees the full disk. Having only USB 2 on Win 10 shouldn't make a difference. I'll try it in its current GPT mode or convert it back to MBR if needed.
If the disk is working as 4TB, it can't be a trick of its enclosure.

Take care.

kanenas said:

No RAID. I've used it ages ago at work on long-dead computers. The current desktop is to kill time pleasantly.

Click to expand...

Just thought I'd check. Sometimes if this is changed it can throw older drives a real loop. It really shouldn't as we are talking about an external USB drive but stuff happens. Best to just leave as is then.

kanenas said:

As for Advanced Format, I don't know. I was under the impression that its enclosure's chips pulled the trick.

Click to expand...

The enclosure's chips pull the trick until they don't. I can almost guarantee you that you're struggling with a failing bridge in the enclosure and that there is nothing wrong with the drive itself. In fact, if you remove the drive from the enclosure and hook it up to SATA you'll likely have no issue with it after ward. Admittedly, I'm only speculating here but this is starting to look mighty familiar. Of course there is the off chance that the bridge in that enclosure just doesn't play well with Windows 11 but if you plan on using Win 11 the rule of thumb is that your drives should be in GPT. Yes, there are exceptions but the exceptions only prove the rule.

kanenas said:

Yes, we are talking about Disk 3.
When converted to GPT, Win 11 says it's uninitialized but why Win 10 has no problem with the same disk?
When set up as MBR (as it was initially), both used to recognize it just fine.

Click to expand...

You may be able to get your data back simply by switching the disk back to MBR in MiniTool. This of course assumes you haven't tried to do anything else with it since but it's worth a go. There could be a number of reasons why your Win 10 isn't encountering this issue. Firstly, it's running on SATA, I'm assuming. Secondly, it's an OS. Third, it's not 4TB.

kanenas said:

Which is why I blame myself for changing in the desktop BIOS the option on how to handle legacy USB. Either I set the wrong option or the BIOS programming didn't treat properly. But that's an assumption... It could just be Win 11's handling of the oldie disks.

Click to expand...

My personal experience is that Win 11 is not that forgiving of older drives. I'm not saying this is a bad thing as over time drives do need to be replaced. Your BIOS is not the problem. Nobody can tell you to keep your BIOS in CSM or Secure Boot but that's not the fault of the BIOS. Ideally, with Windows 11 you will want your settings to boot UEFI first. Legacy is for MBR, older operating systems, and other operating systems. If you're dual booting you still want UEFI because you're using Windows 10. (Windows 7 is another matter.) Select which drive you want to give boot priority to, save, and move on.

kanenas said:

'll know in a couple of days after I can get in and correct the BIOS setting.
As is, I can't even split the disk before Win 11 can see it. I have extra SSD storage to back up things in Win 11, but nothing in Win 10.

Click to expand...

You should be able to get into your UEFI/BIOS without issue if you have only the basic peripherals (keyboard and mouse) connected and all other drives disconnected. You need to tackle this one drive at a time. Just keep tapping the 'delete' key after you see the logo when you boot up. Myself, I disable "fast boot" when I'm in UEFI/BIOS because those couple of seconds are handy to have when you need them. From there you can go to your boot tab and set the boot priority. There shouldn't be much to choose from if all other drives are disconnected. The moment you introduce a new operating system to your PC it will default to that drive in boot priority so be ready to switch it if you want to keep the original boot priority. Again, I can't stress the importance of working on one drive at a time.

I hope this helps.

The original enclosure's chip is the only one working properly :). All the rest could drive me up a wall.

BIOS access is not a problem. Doing anything there, is. No mouse or keyboard is active while in the BIOS.

And some things of interest:

The original enclosure's chip is the one that did all the magic with the 4TB partition in MBR.

Using the original enclosure and as I mentioned earlier, the Disk 3 converted to GPT, works fine in Win 10, but shows as unallocated in Win 11.

Until I read a suggestion in a Minitool article for disks shown as unallocated:

I applied that in Win 11. My Win 10 was already set up properly)

Basically, go to Customize Power Plan -> Change Advanced Power Settings, then USB Settings -> USB selective suspend setting.
Make sure it's set to Disabled.
Save and reboot.

New Win 11 and I haven't fooled around with settings like that yet. So this setting might be the default.

I rebooted Win 11 and there's the full Drive 3 in GPT mode :)





I thought 'great!' but not quite there yet (:

I transferred the USB disk to a USB 3 enclosure and tried it again.

Without the funky original enclosure, the disk shows its true MBR face, so Win 11 (and Win 10), see only the first 2TB as a partition. Even that, shows a couple of folders for a total of 250GB.




It looks like I'll have to live with the original enclosure or buy another huge disk to backup Disk 3 before reformatting it.

Ah well, at least we learn something new every day...

It looks like we are making progress! As I suggested, the problem or 'trick' as you call it lies in the bridge of your enclosure. This is what I meant when I stated that it kept 'reverting' back in an earlier post. There is a chance that you will be able to use your mouse and keyboard in the UEFI/BIOS now that you disabled the 'selective USB settings'. I thought originally that you had four disks. Is there any chance that you have enough room on one of those to move enough of the files from the 4TB drive to make a permanent 2TB partition with your funky enclosure while you are in Windows 10? MiniTool will usually allow for this. You could strip the files while you're in Win 10. I'm assuming of course that the last screen shot at the bottom of the page was taken when you were in Windows 11. Just a thought.

Myself, I would strip off the data, pull the disk out of the enclosure, hook it up to SATA, completely format the drive in Disk Management, then look at it in MiniTool to ensure that I got everything and that it was in GPT, reformat it anyway and save that enclosure for use with an older PC. BUT that's me. Obviously Windows 11 insists that anything in that enclosure should be set to MBR. I suppose another work around would be to just use a newer drive in the enclosure that has been formatted in GPT and is less than 3TB — preferably 2TB to stay on the safe side. This would still provide ample space for backups.

Anyway, I'm sure you'll sort it out eventually. One more thing: Get rid of all that unallocated space. IMO you have too many recovery partitions and this could wreak havoc on your system. There are better ways of setting up multiple recovery options.

Truthfully, given that a decent USB enclosure can be had for $20-$30, I'd just pitch that ancient one and upgrade.