| Optional Certifications Available for ToughArmor MB601VK-1B | |
| TAA | Trade Agreements Act Compliance |
| UL | Safety Standard Certification |
| UL94 | Flammability of Plastic Materials |
| FCC | Federal Communications Commission Compliance |
| Wide Temperature | MIL-STD-810H - Method 501.7 & 502.7 |
| *IEC 60529 (IPX5) | Protection against water jets |
| • | Fits 1x 2.5” U.2 NVMe SSD, up to 15mm in height |
| • | Installs into any standard external 3.5” device bay or floppy bay |
| • | Uses a U.2 port (SFF-8639) to connect, requires NVMe host |
| • | Supports the full NVMe bandwidth specification of 64 Gbps |
| • | Ruggedized full-metal enclosure meeting flammability requirements |
| • | 2-segment key lock for additional physical security |
| • | Eagle-hook tray latch securely holds the tray inside the enclosure |
| • | EMI Grounding – protects hard drives from electrical damage |
| • | Anti-Vibration Technology (AVT) reduces noise and protects against environmental damage |
| • | Active Power Technology (APT) saves power by shutting the device down when no drive is installed. |
| • | Industry leading 3-year warranty against all defects |
| Model Number： | MB601VK-1B |
| Color： | Black |
| Support Drive Size： | 1 x 2.5" U.2 NVMe SSD (up to 15mm height) |
| Compatible Drive Type： | U.2 NVMe |
| Number of Drives： | 1 |
| Drive Bay： | 1 x external 3.5" drive bay |
| Host Interface： | 1 x U.2 SFF-8639, pin-out defined by SFF-9402 Rev 1.1 (Tri-mode HBA/RAID card compatible) |
| Power Input： | Via U.2 (SFF-8639) |
| Transfer Rate： | PCIe 3.0 up to 32Gbps / PCIe 4.0 up to 64Gbps |
| Support HDD Capacity： | No limitation |
| Drive Cooling： | Metal heat dispersion with passive cooling |
| Structure / Material： | Full metal |
| Support Hot-Swap： | Yes |
| Drive Security： | 2 segment key lock |
| Product Dimension (L x W x H)： | 168.7 x 101.2 x 25.4mm |
| Product Net Weight： | 441g |
| Package Gross Weight： | 506.4g |
| Drive Activity LED Indication： | Drive power: solid green; HDD access: flashing green |
| Package Contents： | 1 - device, 1 - user manual, 10 - screw, 2 - key |
| U.2 Connector Insertion Rate： | 10,000 |
| Humidity： | 5%~65% RH |
| Operating Temperature： | 0°C to 60°C (32°F to 140°F) |
| Storage Temperature： | -35°C to 70°C (-31°F to 158°F) |
| Compliance： | CE, RoHS, REACH |
| Warranty： | 5 years limited warranty |
Compatible Drive Tray (Caddy):
Related Products Series:
Quick Link:
Q: Can you recommend an add-on card that is compatible with MB601VK-1B?
A: To ensure compatibility with MB601VK-1B, please make sure that your add-on card or motherboard’s BIOS/UEFI supports PCIe Bifurcation when using a PCIe 16x or 8x slot. Additionally, set up the PCIe splitter in the BIOS/UEFI with the configuration of x4, x4, x4, x4 for a PCIe 16x slot or x4, x4 for a PCIe 8x slot.
Please click the icon below to view the compatibility of your motherboards or add-on cards that support PCIe Bifurcation mode. For the best compatibility, we highly recommend using the cables recommended or manufactured by the motherboard or add-on card manufacturer.
We are currently in the process of certifying our NVMe enclosure with major add-on card and motherboard manufacturers. We will keep updating the list to include compatible accessories.
To report a compatible add-on card, cable, or motherboard, or to check the compatibility of add-on card(s) or motherboards that are not listed, please click here.
Q: I've completed the installation of the hard drive and device as per the instructions in the product manual, but the system still can't detect the drive. How can I troubleshoot this issue?
A: Please first confirm the compatibility of your hardware, and make sure that the drive, drive enclosure, cable, and host interfaces are compatible. Try connecting the drive directly to the host to see if the system can detect the drive. If it still doesn't detect it, this can rule out issues with the drive enclosure. You can also try connecting the drive enclosure with different drives, cables, or systems to see if the issue can be resolved. If the system still can't detect it, here are some possible issues:
| • | Insufficient PCIe lanes in the system: Whether you're connecting the drive enclosure to the motherboard or add-on card, It is important to note that the number of available PCIe lanes is limited. This includes understanding the number of lanes provided by the CPU and chipset, as well as their allocation method. Failure to do so may result slower transfer speeds, unstable connections, or even the inability to detect the drive. |
| • | Incompatible interface protocols: It is crucial to verify whether the Mini-SAS HD, OCuLink, or SlimSAS interface on the motherboard or add-on card is capable of supporting NVMe. |
| • | Incompatible interface pinout standard: Prior to connecting the drive enclosure to the Mini-SAS HD, OCuLink, or SlimSAS port on the motherboard or add-on card, please verify that the port utilizes the same pinout standard as the port on our drive enclosure. To check the pinout standard of our drive enclosure, you can refer to the specification table on our product page, where it specifies whether the pinout standard is Legacy or SFF-9402 1.1. |
| • | Excessive length of the connecting cable: To ensure optimal performance, it is advised to use a connecting cable that is no longer than 50cm. Using longer cables can lead to excessive signal loss, resulting in slower transfer speeds, unstable connections, or even the inability to detect the drive. Additionally, we recommend using the same interface connector for both the device and the host to prevent any potential compatibility issues. |
Q: I'm using Intel/Broadcom Tri-Mode HBA and RAID cards with the MB601VK-1B, but the drives do not show up in my system?
A: The issue is caused by RAID card manufacturers using a different pinout for Tri-Mode cards than is typically used for U.2 connections. When using these cards with U.2 NVMe drives and cables, a U.2 enabler cable must be used for compatibility, which reverts the pinout back to standard U.2 specifications. For more information, please click here.
Q: My NVMe drive did not detect after inserting it back into the device while powered on?
A: For systems that support hot-plug function, while your system is powered on, each drive insertion and removal cycle will require a manual refresh from the operating system in order for the system to recognize the drive.
If you are unable to detect the drive after performing the manual refresh, your system might not support hot-plug functions. We suggest you check with the motherboard/add-on card manufacturer to see if it supports the NVMe hot-plug function.
Windows 11 / Windows 10 / Windows 8 – In the search box on the taskbar, type Device Manager, then select from the menu, right-click on the disk drive and then select scan for hardware changes.
Windows 7 – Right-click on computer icon on desktop and select properties, click Device Manager, right-click on the disk drive and then select scan for hardware changes.
Q: Is the ICY DOCK NVMe enclosure supporting the PCIe 4.0 standard?
A: Yes, all ICY DOCK NVMe enclosures support the PCIe 4.0x4 standard, with up to 64Gbps transfer rates.
Q: I feel that the drive tray's upper and lower metal spring is stuck when inserting the drive tray. What should I do?
A: Remove the drive tray from the enclosure and reinsert the tray without putting excessive pressure on the metal mesh sheet in front of the tray. Excessive force on the front metal mesh sheet may bend the top and bottom metal spring, causing difficulties when inserting the drive tray. Therefore, please do not forcingly insert the drive tray when this happens as it may cause damage to the metal spring.
 |
| Please DO NOT put excessive pressure on the metal mesh sheet as shown |
3.5” Mobile Racks for 2.5" SATA/SAS SSD/HDD
With ICY DOCK’s 3.5” drive bay enclosure series, we can maximize the unused 3.5" drive bay of any workstation with an easily removable drive enclosure in the frontal bay. We believe this is critical for most industries that are transitioning to be more efficient, frequently require more drive swap than others, and the ability to transport data from one system to another when drives are in the frontal bay as opposed to being stored internally.
