ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - X370 Taichi SATA SSD goes missing
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

X370 Taichi SATA SSD goes missing

 Post Reply Post Reply Page  <1234 6>
Author
Message Reverse Sort Order
Peter13779 View Drop Down
Newbie
Newbie


Joined: 13 Apr 2017
Status: Offline
Points: 39
Post Options Post Options   Thanks (0) Thanks(0)   Quote Peter13779 Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2017 at 3:45pm
Originally posted by mchilds83 mchilds83 wrote:


When I switch to any of the other SATA ports, the computer operates perfectly fine with no troubles. Is the SATA controller for SATA3_1 and SATA3_2 different somehow, or is it perhaps broken?




I still think that Asrock designed the first two SATA ports on this Board as direct connected ports to the CPU while the other ports come from the x370 chipset:

https://rog.asus.com/media/14878984098.gif

I hope they fix this with a new Bios cause replacing the Taichi in my ATX case is a pain in the ass.


Back to Top
mchilds83 View Drop Down
Newbie
Newbie
Avatar

Joined: 19 Apr 2017
Location: Canada
Status: Offline
Points: 4
Post Options Post Options   Thanks (0) Thanks(0)   Quote mchilds83 Quote  Post ReplyReply Direct Link To This Post Posted: 19 Apr 2017 at 12:36pm
EDIT: After further testing, I noticed the problem is recurring on the other SATA ports. In the absence of a known driver solution, I'm preparing to RMA the SSD.


I found this thread because I'm having a similar issue. On my X370 Taichi (P2.00 BIOS) while plugged into either of the SATA3_1 and SATA3_2 ports (The two top ports nearest the memory):


My ADATA SP550 SSD with latest firmware shows Active Time 100% while neither reading nor writing in the Performance Monitor. Every 5-10 minutes the cpu cycles drop to < 1% and all hard disk activity is zero. The computer mostly freezes up, but performance monitor keeps graphing and some games keep running but maybe with limited audio effects while other games will disconnect from online matches and others just freeze completely until the 30 second limit is up. Once the computer resumes, it operates like nothing happened, but it logs 2 warnings into the System Event Log:


Warning, Disk, Event ID 153: The IO operation at logical block address 0xe7b3350 for Disk 0 (PDO name: \Device\00000036) was retried.


Warning, storahci, Event ID 129: Reset to device, \Device\RaidPort0, was issued.


I swapped SATA cables, went into the BIOS and disabled Aggressive Sleep mode in FCH Common Options and in Promontory Common Options. I also enabled High Performance Mode in Windows 10, and tried the Ryzen Balanced Performance Mode. I installed the latest AMD chipset drivers from AMD's website, as well as the latest Asrock All In One Driver (tried that before AMD's). I even tried some registry hacks to enable Active AHCI Power Management in the Advanced Power Plan options but none of this worked.

When I switch to any of the other SATA ports, the computer operates perfectly fine with no troubles. Is the SATA controller for SATA3_1 and SATA3_2 different somehow, or is it perhaps broken? I'm not overclocking the CPU and I'm running my 2x16GB 3200mhz TridentZ CAS14 memory kit at 2666 with loose timings in A2/B2 configuration.


I have zero stability issues otherwise and it appears all other SATA ports run my system without any problems at all. I haven't bothered to test the bottom ports 9 and 10 which I understand to be the AsMedia ports, but I've spot checked a few in the SATA3_3-SATA3_8 range and all was fine.


In Device Manager, IDE ATA/ATAPI controllers: All 3 "Standard SATA AHCI Controller" entries use the same Microsoft Driver, Version 10.0.15063.0, Date: June 21, 2006


Should the AMD chipset driver or the Asrock All In One driver have overwritten this with something else?


System Specs:

AsRock X370 Taichi BIOS P2.00

Ryzen 1800X at stock frequency

ADATA SP550 SSD with latest firmware (BIOS set to AHCI prior to clean install)

ASUS ROG GeForce GTX 1070 STRIX-GTX1070-O8G-GAMING G.SKILL TridentZ 32GB (2 x 16GB) DDR4 3200mhz (PC4 25600) F4-3200C14D-32GTZ

Windows 10 Pro x64


Is this an RMA or some weird chipset incompatibility or driver problem? Thanks




Edited by mchilds83 - 19 Apr 2017 at 3:29pm
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2017 at 11:00am
Originally posted by AYUNES5 AYUNES5 wrote:

I'm having a similar issues with a toshiba RD400 m2.   The BIOS does not pick up the device when the os is rebooted, has been happening since the board (Fatal1ty X370 Professional Gaming) was released.  A  complete system shutdown fixes the issues.  Definitely happens with the Toshiba/OCZ driver.  I will test with the included MS nvme driver.

By the way, I also have an OCZ Vertex 4 and have not had any issues with the device.


The only time you lose the RD400 is after a Window restart, or say a press of the Reset button on the PC case?

When the RD400 is not recognized, is that both in Windows and the UEFI/BIOS, Storage Configuration screen?

I assume you are using the M2_1 slot for the RD400? Is that your Windows/OS drive? Which version of Windows are you using?

Which UEFI/BIOS version are you using?

Please try the MSoft NVMe driver, although I have no idea if it will make a difference.

The Ultra M.2 slot (M2_1) on Ryzen boards does not use the SOC (chipset) resources, as the SATA interface does, it uses PCIe lanes from the CPU. So your issue should not be related to any issue with the SOC.
Back to Top
JohnV View Drop Down
Newbie
Newbie
Avatar

Joined: 14 Apr 2017
Location: NC, USA
Status: Offline
Points: 6
Post Options Post Options   Thanks (0) Thanks(0)   Quote JohnV Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2017 at 10:55am
Originally posted by AYUNES5 AYUNES5 wrote:

I'm having a similar issues with a toshiba RD400 m2.   The BIOS does not pick up the device when the os is rebooted, has been happening since the board (Fatal1ty X370 Professional Gaming) was released.  A  complete system shutdown fixes the issues.  Definitely happens with the Toshiba/OCZ driver.  I will test with the included MS nvme driver.

By the way, I also have an OCZ Vertex 4 and have not had any issues with the device.


With regards to your M.2 issue Ayunes5, I had the same issue with my M.2 drive (BPX), It seems to have been fixed with updating to the 2.0 bios. I had the issue with the 1.5 bios (original). No problems at all since updating.  Note, i used the DOS update, seems safest.
Back to Top
AYUNES5 View Drop Down
Newbie
Newbie
Avatar

Joined: 18 Apr 2017
Status: Offline
Points: 1
Post Options Post Options   Thanks (0) Thanks(0)   Quote AYUNES5 Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2017 at 9:46am
I'm having a similar issues with a toshiba RD400 m2.   The BIOS does not pick up the device when the os is rebooted, has been happening since the board (Fatal1ty X370 Professional Gaming) was released.  A  complete system shutdown fixes the issues.  Definitely happens with the Toshiba/OCZ driver.  I will test with the included MS nvme driver.

By the way, I also have an OCZ Vertex 4 and have not had any issues with the device.


Edited by AYUNES5 - 18 Apr 2017 at 9:47am
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996
Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2017 at 8:49am
Originally posted by GenesisDoes GenesisDoes wrote:

Originally posted by ljt ljt wrote:

Update 2:

Ok. So I've plugged the BX100 into the ASMedia ASM1061 ports on the board (SATA3_A1/A2) and it detected it perfectly and is now showing up in windows and is fully useable.

I've ran some benchmarks and the drive is slightly under performing due to the fact it's on a 3rd party chip rather than native like the rest. 

However it's now proven it isn't the drive itself at fault.

I also did a little bit of digging regarding the 2 drives mentioned having compatibility issues with SATA ports 1-8 (AMD native) i.e. BX100 and the Mushkin Reactor drives and noticed they both have the same controller in common i.e. - Silicon Motion SM2246EN

The MX100 uses a Marvell controller and the Samsung EVO 850 uses its own samsung controller.

Perhaps it's an issue with the main SATA ports not liking this certain controller?

Looks like an issue with this particular controller and X370, maybe something like Z87 and Sandforce controller issues, didn't detect unless you restart just like I'm having now.


Thanks for providing the information about the Reactor and BX100's SSD controller, I was not aware of that.

It was the Sandforce 1200 series SSD controllers that have the problem with the newer Intel SATA ports. The OCZ Vertex II is an example of an SSD that used the Sandforce 1200 series controller.

Just being clear about this, since the Sandforce 2000 series SSD controllers do not have the same problem. I don't want people with SSDs that have the 2000 series Sandforce controller (many Intel SSDs, 520 and 530 models) wondering if they will have problems.

I believe it was never clear whether or not the problem was a hardware issue (the chip design itself) or a firmware problem. I vaguely recall it was the chip itself, but I may be wrong.

But I believe at least part of the problem with the 1200 series controllers was they did not support a new revision to the SATA specification, that was not backwards compatible. The new Intel SATA ports supported that new SATA revision. Whom would we say is at fault in a situation like that? Or is it not a fault, just a compatibility reality?

It might be the case that the Silicon Motion controller does not work well with the Ryzen SATA chipset. I'm not comfortable saying that is true at this point, and I'm not saying that you are. But things like this have happened, such as the example above.

I've used an older Samsung 830 with the first two AMD SATA ports, an Intel 530, and the MX100. Those work fine. I'll try an OCZ Vertex 4 next.


Back to Top
GenesisDoes View Drop Down
Newbie
Newbie
Avatar

Joined: 10 Apr 2017
Status: Offline
Points: 54
Post Options Post Options   Thanks (0) Thanks(0)   Quote GenesisDoes Quote  Post ReplyReply Direct Link To This Post Posted: 18 Apr 2017 at 4:33am
Originally posted by ljt ljt wrote:

Update 2:

Ok. So I've plugged the BX100 into the ASMedia ASM1061 ports on the board (SATA3_A1/A2) and it detected it perfectly and is now showing up in windows and is fully useable.

I've ran some benchmarks and the drive is slightly under performing due to the fact it's on a 3rd party chip rather than native like the rest. 

However it's now proven it isn't the drive itself at fault.

I also did a little bit of digging regarding the 2 drives mentioned having compatibility issues with SATA ports 1-8 (AMD native) i.e. BX100 and the Mushkin Reactor drives and noticed they both have the same controller in common i.e. - Silicon Motion SM2246EN

The MX100 uses a Marvell controller and the Samsung EVO 850 uses its own samsung controller.

Perhaps it's an issue with the main SATA ports not liking this certain controller?
< ="chrome-extension://hhojmcideegachlhfgfdhailpfhgknjm/web_accessible_resources/index.js">

Looks like an issue with this particular controller and X370, maybe something like Z87 and Sandforce controller issues, didn't detect unless you restart just like I'm having now.
Taichi X370, Ryzen 1700 @ 4ghz, 32GB G.Skill TridentZ Ram, Samsung 960 EVO nvme, Intel 600P nvme, 2TB Seagate HDD, 2TB Hitachi HDD, 1TB Mushkin SSD, GTX 1080
Back to Top
ljt View Drop Down
Newbie
Newbie


Joined: 16 Apr 2017
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote ljt Quote  Post ReplyReply Direct Link To This Post Posted: 17 Apr 2017 at 5:09am
Update 2:

Ok. So I've plugged the BX100 into the ASMedia ASM1061 ports on the board (SATA3_A1/A2) and it detected it perfectly and is now showing up in windows and is fully useable.

I've ran some benchmarks and the drive is slightly under performing due to the fact it's on a 3rd party chip rather than native like the rest. 

However it's now proven it isn't the drive itself at fault.

I also did a little bit of digging regarding the 2 drives mentioned having compatibility issues with SATA ports 1-8 (AMD native) i.e. BX100 and the Mushkin Reactor drives and noticed they both have the same controller in common i.e. - Silicon Motion SM2246EN

The MX100 uses a Marvell controller and the Samsung EVO 850 uses its own samsung controller.

Perhaps it's an issue with the main SATA ports not liking this certain controller?


Edited by ljt - 17 Apr 2017 at 5:10am
Back to Top
GenesisDoes View Drop Down
Newbie
Newbie
Avatar

Joined: 10 Apr 2017
Status: Offline
Points: 54
Post Options Post Options   Thanks (0) Thanks(0)   Quote GenesisDoes Quote  Post ReplyReply Direct Link To This Post Posted: 17 Apr 2017 at 3:10am
Originally posted by parsec parsec wrote:

Originally posted by Peter13779 Peter13779 wrote:

Originally posted by ljt ljt wrote:

A little update after some testing;

I've managed to try both a Crucial MX100 and a Samsung EVO 850 ssd using the same sata cable on the same port (sata3_1) that the BX100 was disappearing from and they both seem ok and were showing as an option when I ran the windows install via USB.

edit: I also shifted the BX100 down to SATA port 2 and left the MX100 on port 1 (where the BX100 was disappearing from to begin with) and and the BX100 disappeared from SATA port 2 just like it did on port 1. Yet the MX100 remained ok on port 1. So it's not the port or cable.

For some reason after first reboot the system just doesn't like the Crucial BX100 and it disappears into nowhere.


Better description than mine with my poor english Big smile

The BX100 is still disapearing sometimes when I soft-reset the system. Since it is on SATA3_4 while SATA3_3 has an normal HDD connected it is working fine when the system is runnig and it is BIOS-found. Not usind SATA3_3 and BX100@SATA3_4 it is still disapearing every soft-reset. This has to be some crazy energy-saving stuff or powerdelivery detection problem ...

The Taichi BIOS is a bitch LOL


From my post on page 1:

I'm not sure if your board's UEFI has these options, or what version you are using, I hope the latest 2.00 version. In the Advanced screen, do you see the AMD CBS screen?

If so, in that screen find the Promontory Common Options screen, and in there the PT SATA Configuration screen.

Two options in this screen, PT Aggressive SATA Device Sleep Port0 and Port1. Set both to Disabled.

In the AMD CBS screen, there is also the FCH Common Options screen. The FCH is the X370 chipset, which can support up to eight SATA III ports. It also has a SATA Configuration screen. Why there are both Promontory and FCH SATA screen options, I am not yet clear about. Both Promontory and FCH are terms for the X370 chipset.

Regardless, this SATA Configuration screen has Aggressive SATA Device Sleep options, again try disabling them.

I can't guarantee disabling these options will fix your problem.
< ="chrome-extension://hhojmcideegachlhfgfdhailpfhgknjm/web_accessible_resources/index.js">

These settings didn't work. It appears only certain SSD's disappear like the Mushkin Reactor and Crucial BX100. Other SSD's seem to be working fine and the HDD's never disappear.
Taichi X370, Ryzen 1700 @ 4ghz, 32GB G.Skill TridentZ Ram, Samsung 960 EVO nvme, Intel 600P nvme, 2TB Seagate HDD, 2TB Hitachi HDD, 1TB Mushkin SSD, GTX 1080
Back to Top
ljt View Drop Down
Newbie
Newbie


Joined: 16 Apr 2017
Status: Offline
Points: 9
Post Options Post Options   Thanks (0) Thanks(0)   Quote ljt Quote  Post ReplyReply Direct Link To This Post Posted: 16 Apr 2017 at 11:13pm
Originally posted by parsec parsec wrote:

Originally posted by Peter13779 Peter13779 wrote:

Originally posted by ljt ljt wrote:

A little update after some testing;

I've managed to try both a Crucial MX100 and a Samsung EVO 850 ssd using the same sata cable on the same port (sata3_1) that the BX100 was disappearing from and they both seem ok and were showing as an option when I ran the windows install via USB.

edit: I also shifted the BX100 down to SATA port 2 and left the MX100 on port 1 (where the BX100 was disappearing from to begin with) and and the BX100 disappeared from SATA port 2 just like it did on port 1. Yet the MX100 remained ok on port 1. So it's not the port or cable.

For some reason after first reboot the system just doesn't like the Crucial BX100 and it disappears into nowhere.


Better description than mine with my poor english Big smile

The BX100 is still disapearing sometimes when I soft-reset the system. Since it is on SATA3_4 while SATA3_3 has an normal HDD connected it is working fine when the system is runnig and it is BIOS-found. Not usind SATA3_3 and BX100@SATA3_4 it is still disapearing every soft-reset. This has to be some crazy energy-saving stuff or powerdelivery detection problem ...

The Taichi BIOS is a bitch LOL


From my post on page 1:

I'm not sure if your board's UEFI has these options, or what version you are using, I hope the latest 2.00 version. In the Advanced screen, do you see the AMD CBS screen?

If so, in that screen find the Promontory Common Options screen, and in there the PT SATA Configuration screen.

Two options in this screen, PT Aggressive SATA Device Sleep Port0 and Port1. Set both to Disabled.

In the AMD CBS screen, there is also the FCH Common Options screen. The FCH is the X370 chipset, which can support up to eight SATA III ports. It also has a SATA Configuration screen. Why there are both Promontory and FCH SATA screen options, I am not yet clear about. Both Promontory and FCH are terms for the X370 chipset.

Regardless, this SATA Configuration screen has Aggressive SATA Device Sleep options, again try disabling them.

I can't guarantee disabling these options will fix your problem.

Hi. 

I've tried that but no success with those options. I'll try the BX100 in the 2 sata ports from the ASMedia chipset later and see if that recognises the drive without it disappearing and report back
Back to Top
 Post Reply Post Reply Page  <1234 6>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.156 seconds.