I’ve just installed a new 22TB Red drive into my computer. The drive seems to work fine. But when I run WD Drive Utilities or Kitfox I get a “No Device Detected” message. I’ve been working on fixing this problem for 1/2 a day now, and there doesn’t seem to be any fixes available.
Does anyone here know how to fix this problem?
Does CDI detect it?
https://www.reddit.com/r/datarecoverysoftware/wiki/index/smart/
Yes. The HDD is found by Crystaldiskinfo, and GSmartControl and even by the old WD Digital Dashboard (DD), but since WD DD is depreciated and is being replaced by KitFox I would like to know why the latest and greatest new software doesn’t work, including WD Drive Utilities!
If the drive is working but WD Drive Utilities and Kitfox don’t detect it, try connecting it to a different SATA port or using a different cable. Ensure the drive is initialized and formatted correctly in Disk Management (Windows) or Disk Utility (Mac). Also, check if your motherboard’s BIOS and SATA drivers are up to date. If the issue persists, try running WD Drive Utilities as an administrator or testing the drive on another computer to see if the software detects it there.
Try initializing the drive in Disk Management and ensuring the correct drivers are installed.
Yes Also check if the drive appears in Device Manager under Disk Drives.
Yes. I’ve done all the easy things. Yes it appears in device manager.
I am kind of hoping that someone from the software development team might see this and give some deep knowledge on this topic.
Yes, I’ve tried all the easy things. The only thing that I have not tried is running it on a different computer. I have it installed on my NAS (its a NAS drive after all) and all my other computers are not in the same location. MY NAS is running on an HP computer (Windows 10 pro with all of the current updates) if that makes any difference. (yes, yes, I know HP do things weirdly, but still why won’t the new WD software run properly?)
@mcconkeyb Would you mind sharing the drive’s exact model with us so we can test it internally?
@mcconkeyb It would be helpful to know configuration info as well like how many drives and whether said drives are in a RAID. Are there any other drives connected to this system? Can you verify which Windows version you have? For example, the latest Windows 10 verison is 22H2. Kitfox only supports WD drives. A quick and easy thing you could check is in Windows Services to see if KitfoxService is running.
The model number is WD221KFGX-68CJNN0
I’ll attach a photo of the name plate on the drive for those playing along at home.
Cheers,
Brian
Currently it is the only HDD in the system. There is an SDD for the OS to boot from, and then this 22TB drive. I’ve set up this drive with 2 x 11 TB partitions. There is currently no RAID, that might come later.
Cheers,
Brian
PS. WD Dashboard, called out for an update the old version was 4.?.?. and it updated to 5.0.2.3 and the name changed from WD Dashboard to SanDisk Dashboard. This new version of Dashboard can no longer see the drive. But all of my other 3rd party tools and utilities can, and the drive seems to be working fine, with about 4.5 TB of data currently being stored there. It seems that SanDisk wants to close out the WD division, bye-bye WD, you had a good run…
It’s probably the NAS that is preventing WD’s tool from seeing the drive. That said, CDI and GSmartControl would both be facing the same problem. Were they able to report the drive’s SMART attributes?
Yes CDI, and GSmartControl, and also Seagate’s tools can see the drive, its just the WD sub contracted software that can not see the drive!
PS. Currently its not running special NAS OS, it just runs Windows 10 Pro, with all the updates.
@mcconkeyb Were you able to verify if KitfoxService was running?
To check, you can type “Services” in the windows search bar and scroll through the list to find KitfoxService. It should look the same as below.
Well buckm, I’m not on the development team, and thus am not paid to debug their software. So currently I don’t know the answer to this question and its not a priority to work on this problem.
I will say, that if this new KitFox software is so bad that it will open a window and report that it can not find any WD drives, and is not aware if the background services are running or not, well then this is some very very poor software.
I’ll get the real answer when I have the time to check…
OK, I’ve had the time to do some playing around with my computer where this drive lives.
Yes, KitfoxService is running and is set to start “Automatic”. But still not detecting the drive!
I have this problem, too. I went to test a WD Red Pro drive (WD2002FFSX-68PF8N0) that I just received back from warranty replacement, and the former Dashboard program upgraded to Sandisk, which referred me to install Kitfox. After installing Kitfox and rebooting, the WD Red Pro drive is not being detected. The cables are good, BIOS detects the drive successfully, and Windows 10 Drive Management detects the drive just fine. Any updates on a resolution? Thanks.
Good Luck. It seems that SanDisk who purchased WD, does not care at all about WD. I have not received any updates on this problem. I recommend that you use either CrystalDiskInfo or Seagate’s HDD utilities (oddly they mostly work better that WD utilities, they just don’t know what to do with WD’s proprietary SMARTDISK values).
That’s unfortunate. I’ve got a workbench PC with all the different HDD utilities installed (Seatools, WD, CrystalDisk, etc), and the WD Dashboard had been working just fine up until this “KitFox” transition. I was considering re-installing the last working version again, but guess I’ll just revert to using smartmontools and ShredOS on WD HDDs now.
I suggest a modern USB box for the disk which is usually transparent to the OS and I found disk tools all recognize the disk.
I have several USB boxes and USB-C is my preference as cables are cheap and abundant,. My Orico 5-disk box is top load making JBOD easy.
