- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Coaching Changes
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
UEFI, Win11 and storage
Posted on 6/1/24 at 6:31 pm
Posted on 6/1/24 at 6:31 pm
This is the second time in a year I've been forced to reinstall Win11 due to UEFI and Win11. This time is extra-inexplicable. The first time I updated AMD drivers and Windows in the same reboot, so I count that as my fail. This time has me vexed.
Boot drive is an NVMe drive, which was not touched. The *only* thing I did was replace a Samsung 840 (which was blank, and not the boot drive) 256GB, with a Samsung 870 1TB (both SATA.) Turned PC back on, I end up in an endless BIOS loop where it can't find the Windows boot drive (which again, was not touched.) Even when I unplugged the new 870, it still couldn't find a boot device. Windows re-install required. I switched from UEFI to Legacy, turned off secure boot, etc., and nothing. Win repair from USB couldn't find an installation to repair, even though the boot NVMe was clearly displayed in the BIOS.
I replaced a drive that I use to store games (not O/S), and everything goes to shite.
I don't upgrade often, but can someone help me with what may be going on? MSI X570 Tomahawk, if it matters.
Boot drive is an NVMe drive, which was not touched. The *only* thing I did was replace a Samsung 840 (which was blank, and not the boot drive) 256GB, with a Samsung 870 1TB (both SATA.) Turned PC back on, I end up in an endless BIOS loop where it can't find the Windows boot drive (which again, was not touched.) Even when I unplugged the new 870, it still couldn't find a boot device. Windows re-install required. I switched from UEFI to Legacy, turned off secure boot, etc., and nothing. Win repair from USB couldn't find an installation to repair, even though the boot NVMe was clearly displayed in the BIOS.
I replaced a drive that I use to store games (not O/S), and everything goes to shite.
I don't upgrade often, but can someone help me with what may be going on? MSI X570 Tomahawk, if it matters.
3
Posted on 6/2/24 at 2:00 am to LemmyLives
I think MSI is the problem. I just built a new system using the 670E Tomahawk. Total CF! I tried to use my drives from my old computer and it wouldn't boot. Tried cloning old drives to NVMe drive, nothing. The bios is very confusing, and in Linux it won't recognize my second monitor. At first I chalked it up to the build being so cutting edge that Windows, and especially Linux, needed to catch up, but no, it's MSI, and I'll never buy another product from them.
This post was edited on 6/2/24 at 2:02 am
Posted on 6/2/24 at 10:59 am to LemmyLives
Are any of the programs you use Winblows only with no substitute?
If you don't absolutely need Winblows, install Linux over it.
If you don't absolutely need Winblows, install Linux over it.
Posted on 6/2/24 at 5:21 pm to LsuFan_1955
I've been an MSI fanboi (Intel and AMD) for 15+ years (which is maybe 3 mobos, cause I'm cheap). I tried an Asus or Gigabyte? once in that period and had to RMA it before it ever booted. But if the BIOS sucks, since it's AMI, isn't that going to extend to the other brands that use AMI at least?
Thanks for the warning on the 670E, that was actually what I was going to buy in early 2025 to upgrade to AM5.
Thanks for the warning on the 670E, that was actually what I was going to buy in early 2025 to upgrade to AM5.
Posted on 6/3/24 at 7:19 am to LemmyLives
I was Gigabyte and Asus upto 2007, that was when I built my last computer. It was a 1st. generation i7, and really ran fine. There was nothing wrong with it. I never had a problem with this computer, but over the years I read, and watched videos, of how bad Asus and Gigabyte were becoming. I just wanted a new computer. I just wanted a highend machine, with the Rysen 9 processor and a really good graphics card. I wish I could go back.
Posted on 6/3/24 at 11:25 pm to LsuFan_1955
I guess that leaves ASRock, who also uses AMI. The dice shall roll in a few months.
Posted on 6/6/24 at 6:12 pm to LemmyLives
quote:
Boot drive is an NVMe drive, which was not touched. The *only* thing I did was replace a Samsung 840 (which was blank, and not the boot drive) 256GB, with a Samsung 870 1TB (both SATA.) Turned PC back on, I end up in an endless BIOS loop where it can't find the Windows boot drive (which again, was not touched.) Even when I unplugged the new 870, it still couldn't find a boot device. Windows re-install required. I switched from UEFI to Legacy, turned off secure boot, etc., and nothing. Win repair from USB couldn't find an installation to repair, even though the boot NVMe was clearly displayed in the BIOS.
I've had a similar issue with Win10 drives which were partitioned to MBR but in a UEFI environment.
Pull your primary drive and USB it to another system to see if you can pull the data off. If so, do it. If not, you may still be able to recover your data but you'll have to do some interwebz searching.
When in the Windows PE environment during the Win11 install, you should have an option to go to a troubleshooting/repair section where you can access the command prompt. There's supposed to be a MBR2GPT tool you can access to change the partitioning, but I haven't done it with Win11 (used diskpart during the Win10 install).
For the MBR2GPT tool, type:
mbr2gpt /convert /disk:0 (or whatever your disk number is)
For diskpart:
list disk
select disk (whatever the disk # is)
clean
convert gpt
Once this is done, install Windows as normal then migrate your data back. If being partitioned as MBR in the UEFI environment was your issue, this should fix it.
Posted on 6/6/24 at 11:17 pm to Bard
quote:
Win10 drives which were partitioned to MBR but in a UEFI environment.
I did a clean format/reinstall last year on the boot drive on the same mobo on Win11 (I think I've been on Win11 since it was available on the release view channel years ago.) I was in UEFI the last two times I installed Win11, and was on UEFI mode when I installed Win10 before that. I never use compatibility mode settings in UEFI/BIOS unless out of desperation.
All of my data lives on a spinning HDD that is replicated to a NAS and the cloud, so my main annoyance is that it should have been a reboot and installing stuff on the new SSD, and instead I had to format the boot drive and reinstall a bunch of utilities and move OneDrive local locations, etc. FFS, I've never had more than two partitions on a boot drive (basic, not dynamic, at least in the last 20 years,) and one of those is the recovery partition which has never served any purpose. "Can't repair," ad nauseum.
I don't know if it means anything, but mbr2gpt /validate /disk:x /allowFullOS on multiple drives results in validation failed (not from PE, but admin terminal.)
Posted on 6/13/24 at 9:52 am to LemmyLives
quote:
I don't know if it means anything, but mbr2gpt /validate /disk:x /allowFullOS on multiple drives results in validation failed (not from PE, but admin terminal.)
Hrrmmmm... bad firmware update on the drive? Physical issue?
Page 1 of 1
Popular
Back to top
Follow TigerDroppings for LSU Football News