X470 Taichi Nvme issue

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Okay,
       First I managed to revert the bios from 3.43 back to 2.00 using ami tools in an efi shell, did a clear cmos to reset everything, and the nvme showed up once again as offline in raid mode, but would no longer be stable in windows 10 in ahci mode.
  I went back to raid mode and tried to boot into windows to see what it would do,  and It wanted to do a reset of win 10.  I figured what the hell I was going to start over anyhow, and the reset went ok,  I got my raid 0 storage back and Its booting off of the nvme and is good to go. Somehow my win 10x64 install got trashed and I do not know how. But now my question is " Do all nvme drives show up as legacy offline in raid mode? Maybe it was always like that and I never noticed, but I thought it was the problem because it would not boot. What does everybody think on this? Am I missing something?  Thanks in advance

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Arax Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 12 Feb 2018 Location: Pittsburgh Status: Offline Points: 11	Post Options Post Reply Quote Arax Report Post Thanks(0) Quote Reply Posted: 06 Aug 2019 at 8:37am
	Okay, First I managed to revert the bios from 3.43 back to 2.00 using ami tools in an efi shell, did a clear cmos to reset everything, and the nvme showed up once again as offline in raid mode, but would no longer be stable in windows 10 in ahci mode. I went back to raid mode and tried to boot into windows to see what it would do, and It wanted to do a reset of win 10. I figured what the hell I was going to start over anyhow, and the reset went ok, I got my raid 0 storage back and Its booting off of the nvme and is good to go. Somehow my win 10x64 install got trashed and I do not know how. But now my question is " Do all nvme drives show up as legacy offline in raid mode? Maybe it was always like that and I never noticed, but I thought it was the problem because it would not boot. What does everybody think on this? Am I missing something? Thanks in advance

gizmic Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 13 Jun 2018 Location: Hong Kong Status: Offline Points: 677	Post Options Post Reply Quote gizmic Report Post Thanks(0) Quote Reply Posted: 06 Aug 2019 at 10:24am
	no the nvm shouldnt be in offline/legacy mode in raidexpert it shouldn't be visible there. and normally youre windows will be unstable in ahci because it is a broken raid drive. are you enabling nvm raid mode in the amd menus? because you dont have to do that unless you are using nvm raid


Arax Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 12 Feb 2018 Location: Pittsburgh Status: Offline Points: 11	Post Options Post Reply Quote Arax Report Post Thanks(0) Quote Reply Posted: 07 Aug 2019 at 9:34am
	No, I am not using nvme raid mode. I might just start all over again and go ahci because I can back up all the data on my raid 0 storage now, getting kind of fed up with this.

Arax Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 12 Feb 2018 Location: Pittsburgh Status: Offline Points: 11	Post Options Post Reply Quote Arax Report Post Thanks(0) Quote Reply Posted: 10 Aug 2019 at 8:46am
	Well, I installed the latest amd chipset drivers and the latest raid expert and drivers, and raid expert showed the legacy nvme drive twice, one online and one offline. I deleted the the offline drive and thought my problem was solved, but upon reboot, the raid sreen showed two legacy nvme drives, one online and one offline again, but the offline one does not show up in raid expert. Also, windows disk management showed the 240gb nvme drive as 512gb with 1 240gb partion and the rest unallocated space. Very strange. After trying to fix this for awhile now I changed everything to ahci and formatted all over again with a fresh install of win 10 and so far all is well. I have been building and using pc's since 1996 and have never ran into anything like this. Any thoughts would be appreciated.