I think its a general failure with more Nuc´s , i have a D54250WYKH and are having the same problem that you do, except the one with loosing connection to the drive, but if my 1 tb drive is connected to the Nuc and i start it it do not find the drive before i make a reboot, but another way that Works most of the times is to start without the drive connected and wait until its up and running and then connect the drive, then my Nuc finds the drive most of the times, but there is for sure something quite wrong with the Nuc to behave like that, so sometimes when Intel fixes stuff in bios updates somethings kinda get broken in the bios, so hopefully they find a fix for that as it has worked before.
But can you get your drive to Work if you connect it to the Nuc after you have turned it on and is up running ?
Thank's for answer.
I've already tried this version. I tried also version 220.127.116.11 (https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23734&lang=eng) wich seems more recent.
Disconnections occure with both of them.
Thank's Joe_intel to work on this issue.
I have two questions :
1) is the USB 3.0 driver version 18.104.22.168 suitable for D34010WY ?
2) Is the NUC USB power good enough for USB 3.0 external disk ? I have another D34010WY NUC with an USB 2.0 western digital external disk and I have no problem with it.
I was able to replicate the issue with a similar USB 3.0 1TB WD* external drive, it was not accessible after a cold boot until I restart the system. A possible workaround in my system was connecting the drive to the other USB port.
Just to make sure we are on the same track; this is the type of smaller external drive that is not self powered, is it yours too?
The USB 3.0 driver version 22.214.171.124 is listed for the Intel® NUC Kit DN2820FYKH, it is indicated at the end of the download page.
I am not quite sure this is a power related issue because my USB 3.0 flash drive had similar issues but it worked randomly. Furthermore, you mentioned this did not happen in earlier BIOS 022.
See if the workaround I mentioned above works for you, just in the meantime. For a permanent solution I suggest you creating a service ticket with your local Intel support team and request to escalate it by making reference of this community thread.
yes my drive is not self powered. It's the same as yours.
I've bought an USB 3.0 powered hub (amazon basics), I will receive it tomorrow or monday. I want to know if the nuc power is the cause of disconnections. I will tell you.
Tomorrow I will test bios version 030 and reinstall usb3.0 driver version 126.96.36.199.
Thank's for help.
I upgrade bios version 30 WITH windows 7 USB3.0 controller version 188.8.131.52 : no change. After a cold start, nuc doesn't see the disk. If I unplug/replug the disk, even after 5 minutes nuc is started, the disk is not available. If I plug the disk into another usb port, the disk is still not seen by the NUC. If I restart NUC, the disk is OK.
I keek this configuration to see I disconnections still occur.
Ok I did it.
Some news : disconnection of my usb3.0 disk after one day of use. Config : bios version 030 + USB3.0 controller version 184.108.40.206.
The P/N of my WD Disk : WDBUZG0010BBK. See this page : Support WD / Téléchargements / Eléments WD
some new tests :
I bought this usb hub : http://www.amazon.fr/gp/product/B00E4J7PTM
Despite the hub alimentation : no change about disconnections. But sometimes the disk is mounted after a cold boot. Without the hub, it's never mounted, I have to reboot to see it.
I've uninstalled USB3.0 controller intel driver because it was very unstable (disconnections).
With windows native usb driver, I confirm that the disk is in USB2.0 mode (slow transfer) but the disk is always mounted after a cold boot and there are far fewer disconnections.
I am very surprised that this problem has persisted for so long :
I hope a solution from technical support.