# IODD Chatbot Training Material This document is a self-contained training source for general users and chatbot usage. It combines the deduplicated IODD manual, model reference, safety warnings, troubleshooting flows, and support-response guidance. It intentionally avoids outbound links or dependency on other files so the material remains complete when converted to PDF. --- ## Part 1. Deduplicated IODD Manual # ๐Ÿค– IODD All-in-One Documentation ## 1. ๐Ÿ˜ƒ Welcome to IODD Guide Image note: IODD Brand Main 2025 - Experience the ultimate virtual drive and encryption solution. Image note: MINI PRO Comparison - IODD Series Comparison: Find the right model for your needs. ### ๐Ÿ”” Latest News Currently sold products use the latest firmware, so no additional update is required. If there is a new update after **May 29, 2024**, we will announce it here. ### โœจ What's New **IODD TRIM Tool Released** A new Windows utility designed to send TRIM commands to external USB SSDs, maintaining performance and extending lifespan. * **IODD TRIM Tool Manual** --- ### ๐Ÿ“˜ Introduction This documentation provides a comprehensive, step-by-step guide to effectively using your IODD device. While the instructions are primarily tailored for the **ST/LK series**, most information is applicable to the **MINI series** as well. #### โš ๏ธ Pre-use Checklist To ensure stable performance and data integrity, please review these requirements: * **Power Supply**: Connect the IODD to a **rear USB port** on your PC. Laptop users should use a **powered USB hub** for consistent voltage. * **Encryption Conflict**: Hardware encryption **cannot** be used simultaneously with OS-level encryption (e.g., **BitLocker**). * **Cable Length**: Use a USB cable **shorter than 50cm** to prevent signal degradation. * **Disk Compatibility**: * **ST300 / ST400 / LK100**: **2.5-inch** **7mm** HDD/SSD. * **2531 / 2541 (Legacy)**: **2.5-inch** HDD/SSD up to **9.5mm**. * **MINI (Legacy)**: M.2 SATA **2242** SSD. * **MINI PRO**: M.2 SATA **2280** SSD. ### ๐Ÿ“Š Hardware Model Comparison | Feature | ST400 / MINI PRO | LK100 | ST300 | 2541 (Legacy) | 2531 (Legacy) | MINI (Legacy) | | :--- | :---: | :---: | :---: | :---: | :---: | :---: | | **Encryption** | AES256 XTS | AES256 XTS | โŒ | AES256 XTS | โŒ | AES256 XTS | | **Virtual ODD** | โœ… | โŒ | โœ… | โœ… | โœ… | โœ… | | **Virtual HDD** | โœ… (3 LUN) | โŒ | โœ… (3 LUN) | โœ… (4 LUN) | โœ… (4 LUN) | โœ… (3 LUN) | | **Interface** | Type-C (USB 3.1) | Type-C (USB 3.1) | Type-C (USB 3.1) | Micro-B (USB 3.0) | Micro-B (USB 3.0) | Micro-B (USB 3.0) | | **Controls** | Tactile Keys | Tactile Keys | Tactile Keys | Touch Keys | Jog Dial | Tactile Keys | | **Max PIN** | 38 Digits | 38 Digits | N/A | 15 Digits | N/A | 15 Digits | | **2nd P.W.** | โœ… | โœ… | โŒ | โŒ | โŒ | โŒ | | **Admin App** | โœ… | โœ… | โŒ | โŒ | โŒ | โŒ | | **Internal Disk** | 2.5" 7mm / 2280 | 2.5" 7mm | 2.5" 7mm | 2.5" 9.5mm | 2.5" 9.5mm | M.2 2242 | {% hint style="warning" %} **Safe Removal (Mandatory)** To prevent data corruption, **always use the "Safely Remove Hardware" option in your PC's operating system.** The hardware button ejection on the IODD may not be sufficient depending on your OS configuration. {% endhint %} --- ### ๐Ÿš€ Getting Started #### First Time Using IODD? If you haven't assembled your device yet, start here: * **Disk Assembly Guide (ST/LK)** If your hardware is ready, follow these core functions: #### 1. Virtual Drive Feature Learn how to mount ISO, VHD, and RMD files. * **Drive Setup Guide** #### 2. Encryption Function Secure your data with AES-256 hardware encryption. * **Encryption Guide (ST/LK/MINI PRO)** * **Encryption Guide (MINI Legacy)** #### 3. Simultaneous Use (Encryption + Virtual Drive) For maximum security and utility, follow this specific order: 1. **Configure Encryption**: Set up your password first. 2. **Setup Virtual Drive**: Once encrypted, partition and copy your files. --- {% hint style="danger" %} **Encryption Compatibility Notice** Due to an upgrade in the encryption algorithm, disks encrypted with **2541 / SecureDock** are **NOT compatible** with the **ST400 / LK100 / MINI PRO**. **To migrate your disk to a newer model:** 1. **Back up** all data to a safe location. 2. **Initialize** the disk on the new IODD device. 3. Set a new password and restore your data. **Compatibility Map:** * ST400 โ†” LK100 โ†” MINI PRO (Fully Compatible) * **[NOT COMPATIBLE]** * 2541 โ†” Securedock (Legacy Compatibility Only) {% endhint %} --- ### ๐Ÿ› ๏ธ Need Help? If you encounter issues, please refer to these troubleshooting resources: * **Firmware Update Guide** * **Disk Initialization Guide** * **Error Messages Guide** * **FAQ** #### Terminal Verification You can check if your IODD is correctly recognized by the OS: ```bash # On Linux, verify the connected USB mass storage device $ lsblk -o NAME,MODEL,SIZE,FSTYPE ``` --- ### ๐Ÿ“ž Corporate Contact * **Email**: **webmaster@iodd.kr** (Technical Support & Business Inquiries). * **Official Parts Store**: **IODD Ewoda Store (AliExpress)** - Official worldwide distributor. --- ## 2. ๐Ÿงฐ Disk Assembly (ST/LK) ### Disk Assembly Guide Please refer to the images below and follow these steps carefully. This guide applies to **ST300, ST400, and LK100** models, which share the same exterior design and use **2.5-inch 7mm** HDD or SSDs. --- #### 1. Position the Device Hold the **IODD main body** and the **back cover** as shown in the picture. * **White:** Back cover * **Black:** Main body Image note: Positioning the IODD body and cover --- #### 2. Remove the Rear Cover While holding the main body firmly in place, **slide the rear cover** in the direction of the arrow. * Push it all the way to remove it completely. * **โš ๏ธ Warning:** Do not apply excessive inward pressure, as this may cause damage. **Be sure to push strictly in the direction of the guide.** Image note: Sliding the rear cover --- #### 3. Install the Disk Drive Install the disk in the following order: 1. **Connect the SATA port side first.** Ensure it is aligned correctly. 2. **Seat the disk** into the IODD main body securely. Image note: Inserting the SSD/HDD into SATA port --- #### 4. Reattach the Cover Slide the cover back on until you hear a **`"click"`** sound. Image note: Closing the rear cover {% hint style="warning" %} **Check the Latch** Verify that the rear latch is properly engaged and the cover is flush with the body. {% endhint %} --- ### What do you want to do now? If your hardware is ready, you must initialize the disk first: **Disk Initialization Guide** * **Use Encryption:** Learn how to secure your data with the Encryption Guide. (Note: **ST300** does not support encryption). * **Use Virtual Drive:** Learn how to use the **Bootable Virtual Drive** feature. Drive Setup * **Use Both Simultaneously:** To use encryption and virtual drives together, follow this order: 1. Complete the **Encryption settings** first. 2. Then, set up your **Bootable Virtual Drive**. #### Verification Tool After assembly, you can check if the drive is physically detected: ```bash # Verify the physical disk connection $ lsblk -d | grep -i "iodd" ``` --- ## 3. โŒจ๏ธ Disk Initialization #### 1. First-Time Setup Sequence If you are installing a new disk for the first time, follow this specific order: 1. **Detection:** Once the IODD is recognized, an initialization message will appear in your OS disk management tool. 2. **Encryption First (Optional):** * If you intend to use hardware encryption, you **must set the password on the IODD hardware first** before initializing the drive in Windows/Mac. * **ST400, LK100 & MINI PRO:** Set the **2nd Password first**, followed by the **1st Password**. 3. **Perform Full TRIM (Highly Recommended):** Before creating partitions, we strongly recommend running the **IODD TRIM Tool** to perform a **Full Device TRIM**. This ensures all flash memory blocks are properly initialized to a clean state, providing optimal write speeds and extending the SSD's lifespan. *(If you have already created partitions or are currently using the drive, you can use the **Free Space Only TRIM** feature to safely optimize it without losing data.)* 4. **Disk Initialization:** * **Modern Models (ST, MINI PRO, LK100):** Supports both **MBR** and **GPT**. GPT is recommended for drives over 2TB. * **Legacy Models (2531, 2541, MINI Legacy):** Supports **MBR only**. GPT is **not supported**. * **Note:** Legacy models have a hardware limit that only recognizes the first **2TB** of a drive. 5. **Partitioning & Formatting:** * Format using **NTFS, exFAT, or FAT32**. * **Note:** FAT32 has a 4GB file size limit. NTFS/exFAT is recommended for ISO/VHD files. * **VHD Tool++ note:** If you use VHD Tool++, **exFAT** is recommended. On some Windows versions/locale settings, NTFS may cause occasional time/timestamp format errors in the tool. * **ST/MINI PRO:** The IODD data partition does not have to be the first partition on the disk. 6. **Safe Removal (Crucial):** Always use **`"Safely Remove Hardware"`** before disconnecting. Failure to do so with NTFS can lead to the "ASSERT" error. 7. **Reconnect & Verify:** Reconnect the IODD. * **Modern Models (ST, MINI PRO, LK100):** If files are not visible, **hold the [4] key for 3 seconds** to manually select the correct partition. * **Legacy Models (2531, 2541, MINI Legacy):** This partition selection hotkey is **not supported**. Ensure your data is on the first primary partition. (For 2541, long-pressing [4] only rescans the current partition). --- #### 2. Fixing Initialization Failures (MBR โ†’ GPT โ†’ MBR Trick) If the drive fails to initialize or displays errors, try this cycle: 1. Connect the HDD/SSD directly to a PC (if possible) or via IODD. 2. Initialize it as **GPT**. 3. Then, immediately re-initialize it back to **MBR**. This process can often clear corrupted partition table metadata that simple formatting cannot fix. --- #### ๐Ÿ› ๏ธ OS Specific Guides * **Windows:** Microsoft Disk Management Guide. * **macOS:** Disk Utility User Guide. --- #### 3. Voltage Check Monitoring voltage is crucial for data integrity. Press **[3]** on the keypad to view the current **V-voltage**. * **Lowest/Minimum Voltage**: Some models (ST/2541) track the lowest voltage detected since connection. This is the most critical value for stability. * **Current Voltage**: Displays the real-time BUS voltage. {% hint style="danger" %} **Low Voltage Warning (< 4.65V)** This is critical. Large file transfers may fail, or the disk may disconnect randomly. You **must** move to a rear PC port or use a **powered USB hub** immediately to prevent data loss. {% endhint %} --- ## 4. ๐Ÿ“ Basic Control / Function Keys ### IODD ST300/400, MINI PRO, MINI (Legacy) The physical keypad on your IODD allows for quick navigation and advanced power-user shortcuts. Understanding these keys will significantly improve your workflow. ### 1. Basic Control (Press Key Once) #### โŒจ๏ธ For Models with Keypad (ST300/400, MINI PRO, MINI, LK100) | Key                  | Function | Description | | :--- | :--- | :--- | |  **[1]** | **Rescan** | Rescans the root folder for new files. | |  **[2]** | **Up** | Moves up in the file or item list. | |  **[3]** | **Voltage** | Displays the **VBUS minimum voltage** (Crucial for stability). | |  **[4]** | **Back** | Goes to the parent folder. | |  **[5]** | **Info** | View detailed file information (size, fragmentation, etc.). | |  **[6]** | **Select** | Selects a file to mount or enters a folder. | |  **[7]** | **Eject** | Ejects the most recently mounted virtual drive. | |  **[8]** | **Down** | Moves down in the file or item list. | |  **[9]** | **Save** | Saves the current mount state (Auto-mounts on next boot). | |  **[M]** | **Menu** | Enters or exits the system settings menu. | |  **[0]** | **Help** | Accesses the built-in Help menu or active error details. | |  **[Enter]** | **Select** | Same function as Key [6]. | ### 2. Advanced Hotkeys (Long Press - 3 Seconds) For the **ST300/400, MINI PRO, MINI (Legacy)**, holding a key for 3 seconds triggers advanced maintenance functions: | Key | Function | Description | | :--- | :--- | :--- | | **[1]** | **Reconnect** | Restarts the USB connection without physical removal. | | **[3]** | **WP Reconnect** | Reconnects with **Write-Protection** enabled for all drives. | | **[4]** | **Partition List** | Displays all partitions; allows manual selection of the default data partition. | | **[7]** | **Detach All** | Reconnects with all virtual drives (ISO/VHD/IMA) unmounted. | | **[9]** | **Sleep Mode** | Safely detaches the USB connection and enters power-saving sleep mode. | | **[0]** | **Temp Disable WP** | Reconnects with Write-Protection **temporarily disabled**. | ### 3. Startup Keys (Hold while connecting USB) These keys must be held **before and during** the insertion of the USB cable: | Key | Mode / Function | Description | | :--- | :--- | :--- | | **[1]** | **Factory Reset** | Resets all settings (LCD bright, standby time, etc.) to defaults. | | **[3]** | **WP Mode** | Starts the device in a global Write-Protected state. | | **[5]** | **Standalone** | Operates the IODD using external power without a PC connection. | | **[7]** | **Unmount All** | Ensures no virtual drives are loaded upon startup. | | **[M]** | **Standalone Menu** | Enters the system settings menu in Standalone Mode. | | **[0]** | **Key Info** | Displays a list of available startup keys on the screen. | | **[9] + [Enter]** | **Firmware Recovery** | **Force Recovery:** Hold both keys for 7s to re-flash the current firmware. | #### ๐Ÿ”˜ For IODD 2531 (Jog Dial) * **Jog Up/Down**: Moves the cursor through the file list or menu items. * **Jog Click (Center)**: Selects a file or enters a folder. * **Back Button (Side)**: Moves to the parent folder or exits the current menu. #### ๐Ÿ‘† For IODD 2541 (Touch Keys) The 2541 features a 12-button capacitive touch interface. Operation is identical to the physical keypad models, but requires a light touch rather than a press. * **[2] / [8]**: Up / Down navigation. * **[6] / [Enter]**: Select / Mount. * **[4]**: Back / Exit. --- {% hint style="info" %} **Correct Startup Sequence** 1. Hold the desired key firmly. 2. Plug in the USB cable. 3. Release the key once the IODD logo appears. {% endhint %} --- ### Terminal Verification ```bash # Monitor kernel messages for USB reconnects/errors $ dmesg -w | grep -i usb ``` --- ## 5. ๐ŸŒณ Menu Tree (MINI PRO/ST/LK) **Related Products**: ST300, ST400, LK100, MINI PRO This page outlines the hierarchical menu structure of the IODD ST/LK and MINI PRO series. ### โŒจ๏ธ Menu Control * **`2`** : Moves cursor **Up**. * **`8`** : Moves cursor **Down**. * **`6`** or **`โŽ`** : **Execution / Select** key. --- ### 1. Mode Setting Configure the device's operational mode. Learn more * **`5`** - Toggles **Write Protection** (On/Off). Icon changes accordingly. * **`6`** - Toggles **Fixed / Removable** drive type. Icon changes accordingly. * **`3`** - Moves selection **Up**. * **`9`** - Moves selection **Down**. **Enabled/Disabled Devices:** Toggle the following virtual drives: 1. **ODD**: Virtual CD Drive (*.iso) 2. **HDD**: Physical Internal Drive 3. **VHD**: Virtual Drive (*.vhd, *.ima) ### 2. AES256 Encryption (Administrator Mode) Manage hardware encryption settings. Encryption Guide {% hint style="danger" %} **When setting or deleting the Admin password, all disk data will be permanently deleted. Please back up your data before proceeding.** {% endhint %} * **Admin Menu:** 1. **Set 2nd P.W.**: Setup the **secondary password** (4-38 digits). This **must be done before** setting the 1st password. 2. **Set Password**: Set the **primary administrator password**. (Data is deleted, but can be restored if released immediately after setting). 3. **Del Password**: **Deletes the password** and **wipes all data**. 4. **Chg Password**: **Changes** the existing password. * **General User Management:** 1. **User1 - User4**: Individual user slots. * **Set Password / Del Password**: Set or remove user-specific passwords. * **โ˜‘Read-only**: Enables **Write-protection** for the specific user. * **โ˜‘User Change**: Allows the user to **change their own** password. * **โ˜‘User Delete**: Allows the user to **delete their own** password. 2. **Save Users**: **Saves** the configured user settings. ### 3. AES256 Encryption (User Mode) Settings available for standard users. User Guide 1. **Chg Password**: **Change** the current user password. 2. **Del Password**: **Delete** the current user password. ### 4. USB Control Manage connection and safety settings. 1. **Keep P.W. 2min**: Maintains the password for **2 minutes** after power-off for quick reconnection. Details 2. **Write Protect**: Enables **Write-protection** for all drives. Details 3. **Refresh**: Software-based **reconnection** of the device. 4. **Safe Removal (HDD only)**: * **Stops the spindle motor** and enters power-saving mode. * **Note for SSD Users:** Hardware-side safe removal may not work depending on the PC. **Always use "Safely Remove Hardware" within your PC's OS.** ### 5. Information View disk health and product details. S.M.A.R.T. Info 1. **S.M.A.T.**: Internal Drive status. * **HDD Health**: Shows **Good**, **Warning**, or **Bad**. * **HDD Model / Serial**: Displays drive identification info. 2. **Product Info**: * **Firmware Ver**: Current IODD firmware version. * **USB Speed**: Currently connected speed (Full/Hi/Super Speed). ### 6. Setting Customize device behavior. 1. **LCD Bright**: Adjusts the **LCD backlight brightness**. 2. **Screen Saver**: Dims the screen after **2 minutes** of inactivity. For encrypted drives, the screen will **lock for security**. 3. **Load Default**: Restores all settings to **factory defaults**. ### 7. Language Select the display language: * English / ํ•œ๊ธ€ / ็ฎ€ไฝ“ไธญๆ–‡ / ๆ—ฅๆœฌ่ชž / ะ ัƒััะบะธะน --- ## 6. ๐Ÿ–ฅ๏ธ Display/Status Bar Image note: IODD Main Display - Main Display Overview ### Status Bar The status bar at the top of the screen shows the current operational state of the device. Image note: Status Bar Indicator | Icons | Description | | :---: | :--- | | | Physical drive **Write-Protect** status (Enable/Disable). | | | **Global Write-Protect** (Protects all disks, including virtual drives). | | | **Mount / Unmount** status of the ISO file. | | | **Mode Status** (CD-ROM / Dual / HDD). | | | **Power Status** (Timer / Sleep mode). | | | **AES256 Encryption** is active (On). | | | **USB Connection Speed** (3.0 / 2.0 / 1.1). | --- ### Virtual Drive Indicators This section displays information about the currently mounted virtual media. Image note: Virtual Drive Information | Icons | Description | | :---: | :--- | | | Name of the **mounted file** (ISO / VHD / RMD). | | | Type of the virtual drive (**Removable** or **Fixed**). | | | **Write-Protect** status for virtual drives (VHD / RMD). | --- ### File/Drive List Image note: File List View * Displays folders and compatible files in the currently selected directory. * **To use a different partition:** 1. Unmount all active virtual drives. 2. Press and hold the **`4`** key for **3 seconds**. 3. Select the desired partition from the **[Partition Selection]** menu. ### Help Menu * Users can access context-sensitive help at any time by pressing the **`0`** key on most screens or items. --- ## 7. ๐Ÿ’ฝ Drive Setup ### Choose your configuration * **Virtual Drive Only:** If you only plan to use the virtual drive functions, follow the instructions below. * **AES Encryption Only:** If you will only use hardware encryption, you can skip this section and go directly to the Encryption Guide. * **Using Both (Encryption + Virtual Drive):** You **must** complete the encryption setup first. Please refer to the Encryption Guide before proceeding here. --- ### **Drive Structure & Requirements** To ensure the IODD virtual drive functions correctly, your internal disk must meet the following partition and format requirements: * **Partition Style:** Must be either **GPT** or **MBR**. * **Partition Type:** Must be a **Normal/Primary** partition. * **File System:** Supported formats include **NTFS**, **exFAT**, or **FAT32**. * **Partition Selection:** The location of the partition does not matter. If you have multiple partitions, you can select the one containing your ISO files by pressing and holding the **`4`** key for 3 seconds. --- ### ๐Ÿ“‚ File Management & Limitations {% hint style="warning" %} **Important: 32-Item Limit per Folder** To ensure the IODD can index your files correctly, the number of files or subfolders within any single directory (that contains ISO/VHD/IMA files) **must not exceed 32 items**. {% endhint %} #### Recommended File Tree Structure You can bypass the 32-item limit by organizing your files into subfolders. The limit only applies to the number of items *within* a single folder, not the total number of files on the entire drive. ```text J: (IODD Internal Drive Root) (Max 32 items) โ”œโ”€ _ISO (Folder for ISO images) (Max 32 items) โ”‚ โ”œโ”€ Hirenโ€™s BootCD 15.2.iso โ”‚ โ”œโ”€ ubuntu-22.04-desktop-amd64.iso โ”‚ โ”œโ”€ Windows 11.iso โ”‚ โ””โ”€ (Up to 32 files or subfolders) โ”‚ โ”œโ”€ IMA_Floppy (Max 32 items) โ”‚ โ”œโ”€ Bios_updater.ima โ”‚ โ””โ”€ MS-DOS_6.0.ima โ”‚ โ”œโ”€ VHD_Files (Max 32 items) โ”‚ โ”œโ”€ Windows_10_Win2Go.vhd โ”‚ โ”œโ”€ Linux_Mint.vhd โ”‚ โ””โ”€ Subfolders (Nested folders are allowed) โ”‚ โ”œโ”€ Your_Personal_Folder_01 (No limit - non-ISO path) โ””โ”€ Your_Personal_Folder_02 (No limit - non-ISO path) ``` --- ## 8. โš™๏ธ Mode Configuration {% hint style="warning" %} Ensure that your disk drive is properly initialized before proceeding. Drive Setup Guide {% endhint %} --- ### ๐Ÿ› ๏ธ How to Enter Mode Setting 1. Press the **`Menu`** (or **`*`**) button. 2. Navigate to and select **[Mode setting]**. | | | | :---: | :---: | | | .png>) | --- ### ๐Ÿ“‘ Item Descriptions | Item | Description | | :--- | :--- | | **HDD** | The internal physical drive of the ST400/LK100/MINI PRO. | | **ODD** | Virtual Optical Disc Drive (CD/DVD/Blu-ray) used for mounting **ISO** files.
*Note: ODD is always write-protected; manual toggle does not apply.* | | **VHD** | Virtual drive used for mounting **VHD/IMA/RMD** files. It can act as a removable/fixed drive or a USB memory stick. | --- ### โŒจ๏ธ Mode Setting Controls | Key | Function | Description | | :---: | :--- | :--- | | **`2` / `8`** | **Move Cursor** | Moves the cursor (โ–ถ) **Up** and **Down** to select a drive. | | **`3` / `9`** | **Change Order** | Moves the selected item's **priority order** (โ–ถ) Up and Down. | | **`5`** | **Write Protect** | Toggles **Write Protection** (On/Off) for the selected drive. | | **`6`** | **Drive Type** | Toggles the selected drive's property between **Fixed** and **Removable**. | {% hint style="warning" %} **Disabling Items:** Items placed below the **[----------Disable-----]** line will be deactivated. Use the **`3`** or **`9`** keys to move unwanted items below this line. {% endhint %} --- ### ๐Ÿ’ป Configuration Example .png>) If configured as shown in the image above, the PC will recognize the following devices: 1. **Physical HDD** 2. **Virtual ODD Drive** 3. **Removable Writable USB Drive** --- {% hint style="warning" %} **Error: [No Extra Devices]** If you attempt to mount an ISO or VHD file and receive this message, it means no virtual drive (ODD/VHD) is currently active. **At least one virtual drive must be enabled in the Mode Setting menu.** {% endhint %} --- ### โœ… Saving and Next Steps Once you have finished your configuration, press the **`Menu`** (**`*`**) key to **save**. The IODD will automatically reconnect, and your new settings will be applied. * **To mount an ISO file:** Proceed to Virtual ODD (ISO) Guide. * **To use Virtual USB/HDD:** Learn how to Create VHD files with VHD Tools. --- ## 9. ๐Ÿ’ฟ Virtual ODD (ISO)
Step 1: Pre-check before use (Important) * Are virtual drives enabled? Mode Configuration * Are you going to use encryption at the same time? If so, proceed with encryption first. Encryption Guide * The ISO file must be a bootable file. * Since IODD works the same as physical ODD, an ISO file that does not boot from an actual ODD will not boot from IODD. * If your PC only supports UEFI boot, you must boot using the Virtual Drive function. Some motherboards do not support ODD boot. * Even in special cases (when installing an older OS on the latest generation board), the installation operation may fail due to a driver conflict. In this case, VHD files are mostly bootable and installable.
For macOS Users * IODD cannot directly mount DMG/BIN/IMG files or disk images for MAC. Must convert to ISO file. * You can change it directly in Terminal as shown below: ```bash # 1. Start conversion (converts DMG to CDR format) $ hdiutil convert [input.dmg] -format UDTO -o [output.iso] # 2. Rename extension from .iso.cdr to .iso $ mv [output.iso.cdr] [output.iso] ```
--- ### **ISO file mount** 1. Prepare the ISO file. 2. Copy the ISO file to the IODD disk. 3. Safe removal and Reconnect, or **Long Press** the **`1`** key for 3 seconds. 4. Select the ISO file from the IODD screen and **Press** **`6`** or **`Enter`**. - If it is mounted normally, you can see that the virtual drive is recognized on the desktop or in the Finder. 5. **Save current state:** Reconnecting will bring up the virtual drive in its current saved state by **Pressing** the **`9`** key. 6. **No Booting Required:** If the installation does not require booting, double-click the virtual drive or autorun as it is to execute the operation. 7. **Booting Required:** If you need to boot from a virtual drive, continue with the BIOS settings below. {% hint style="warning" %} **File not visible?** Try selecting another partition by **Long Pressing** the **`4`** key (partition selection). {% endhint %} {% hint style="danger" %} **If Virtual Drive is not enabled** Please refer to the Mode Configuration to enable Virtual ODD. {% endhint %} --- ### CMOS/BIOS Boot Order Setting {% hint style="info" %} Boot setup menus may differ depending on the board manufacturer/chipset configuration. {% endhint %} Enter the PC's CMOS/BIOS screen (typically using **`F2`** or **`DEL`** keys during booting). Image note: BIOS Setup Entry - Enter BIOS setup to configure boot priority 1. **Select the BOOT section:** This may be in a submenu like "Advanced" depending on the manufacturer. 2. **Set Boot Mode:** Set the boot mode to **Legacy** if required. 3. **Set Order:** Select **IODD Virtual ODD Drive** as the first priority in **Boot Order**. Image note: Boot Order Priority - Set IODD Virtual ODD as the primary boot device {% hint style="info" %} **Multi-Lun Support:** Some boards do not support Multi-Lun. In that case, enable only IODD Virtual Drive as the bootable drive (disable other drives in the Boot order). {% endhint %} {% hint style="warning" %} **Legacy/UEFI:** If you are unable to select Legacy/UEFI, please contact the manufacturer or use VHD boot methods. {% endhint %} {% hint style="danger" %} **Important:** To prevent accidental formatting of the IODD during OS installation, **Long Press** the **`3`** key for 3 seconds to enable **Write Protection**. {% endhint %} **Save & Exit (usually F10)** If you have set the correct ISO at the top of the boot order, the PC will boot via the virtual ODD. * **Windows:** You will be prompted to press a specific key on the boot screen (e.g., F6). * **Mac:** For Intel or Silicon Macs, refer to Apple's official guide for booting from an external disk. --- ## 10. ๐Ÿ’ป Virtual Drive (VHD) --- ### 10.1 โš’๏ธ Create VHD file with VHD Tools #### Overview of Virtual Drive Creation The VHD Tool is a **Windows-exclusive application** designed to create fixed-size VHD files, allowing your IODD device to function as a virtual drive. {% hint style="info" %} **Supported File Systems** The VHD Tool supports both **NTFS** and **exFAT** partitions for VHD creation. **Recommended:** Use **exFAT**. VHD Tool++ relies on Microsoft's legacy `vhdtool.exe`, and on some Windows versions/region settings you may encounter occasional **time/timestamp format errors** when working on an NTFS partition. {% endhint %} #### Download VHD Tools
View Download Link Official IODD Download Center ( **Tip**: To force the English version of the application, run the **`VHD_Tool++(en).bat`** file instead of the standard EXE.
#### Step-by-Step VHD Creation 1. Launch the **VHD Tool** application. 2. Navigate to the top menu and select the **[Create]** tab. Image note: VHD Tool Create Tab - Initiate new virtual drive setup via the Create menu. 3. In the **[File name]** field, designate the save path (an NTFS or ExFAT partition on the IODD) and enter the desired filename. Image note: File Path Selection - Select the internal IODD directory where the file will be stored. 4. Enter the required capacity for the VHD file in the **[Size]** field. {% hint style="warning" %} The allocated size must be less than or equal to the **[Biggest linear Space]** (maximum contiguous free space) available on the disk. {% endhint %} Image note: VHD Size Configuration - Assign the appropriate capacity after verifying the available disk space. 5. Click the **[Create]** button at the bottom to begin generating the VHD file in the specified path. {% hint style="warning" %} **UEFI Installation Requirements** When creating a VHD for UEFI booting and installation purposes, the VHD file size must be larger than the size of the original ISO file. {% endhint %} {% hint style="info" %} **Disk Optimization Recommended** Creating a VHD requires contiguous disk space. If creation fails due to insufficient contiguous space, please perform a **disk defragmentation** and try again. {% endhint %} --- #### Mounting and Persisting the VHD State Once the creation process is complete, follow these steps to mount the VHD and ensure it remains loaded after a reboot. 1. Reconnect the IODD device to your PC. 2. Use the LCD screen on the IODD to locate and select the newly created VHD file. 3. Press the **[6]** button or the **[Enter]** key to mount the file. 4. **Important (Save State):** To maintain the mount status even after a reboot or reconnection, you must press the **[9]** key (or **[Enter]** for certain models) to **save the current state** before restarting your PC. {% hint style="warning" %} **Persisting Mount Status** If you do not save the state using the **[9]** key, the VHD will be unmounted when the device loses power or the PC reboots. Ensure you save the state before proceeding to the boot sequence. {% endhint %} {% hint style="danger" %} **Troubleshooting Mount Failures** The VHD will not mount if the Virtual Drive mode is disabled in the device settings. Please refer to the Mode Configuration Guide to verify your configuration. {% endhint %} --- ### 10.2 ๐Ÿ› ๏ธ Advanced VHD Tool++ Functions **VHD Tool++** is a **Windows-exclusive application**. Beyond simple creation, it provides several utility functions for managing virtual drives: * **[Convert]**: Converts a general disk dump image file into a fixed-size VHD file. * **[Extend]**: Increases the size of an existing fixed VHD file. * **[Defragment]**: Specifically defragments a single file on the IODD to ensure it is contiguous (0 fragments). * **[Upload]**: Copies a file from your PC to the IODD while ensuring it remains unfragmented during the transfer. * **[Write To HDD] (Expert Only)**: Performs a sector-to-sector physical duplication of an image file to the internal HDD. **Note**: This function only supports the **NTFS**, **exFAT** file system. {% hint style="danger" %} **WARNING**: This will permanently delete ALL data on the internal drive. It is only recommended for advanced users performing raw disk operations. {% endhint %} --- ### 10.3 ๐Ÿ—œ๏ธ Converting ISO to UEFI Bootable Drive {% hint style="info" %} This process converts an ISO file into a bootable virtual drive, functioning similarly to a USB flash drive or a Windows-To-Go (WTG) drive. {% endhint %} ### Prerequisites * **ISO File**: The source OS installation image. * **Mounted VHD (Empty)**: A VHD file created and mounted via IODD. * Related topic: Creating VHD Files * **Rufus Application**: Download from --- ### Step-by-Step Conversion #### 1. Mount the VHD File Mount the prepared empty VHD file on your IODD device. It will appear as a "Virtual Drive" on your PC. #### 2. Configure Rufus Run the **Rufus** application with **Administrator privileges**. Image note: Rufus Configuration Screen - Configuring Rufus for VHD installation 1. **[Device]**: Select the **mounted VHD drive** (Ensure it is the virtual drive, not a physical disk). 2. **[Boot selection]**: Click **SELECT** and choose your original ISO file. 3. **[Image Option]**: Select **Standard Windows installation** (or **Windows To Go** if you wish to run the OS directly from the drive). 4. **[Partition scheme]**: Set to **GPT**. 5. **[Target system]**: Set to **UEFI (non CSM)**. {% hint style="info" %} For better compatibility with certain **Win-To-Go** installations on older systems, using **MBR** / **BIOS (or UEFI-CSM)** may be required. {% endhint %} 6. **[File system]** & **[Cluster size]**: It is highly recommended to use the **default values**. 7. Click the **[START]** button to begin the bootable file creation. {% hint style="danger" %} **Verify Target Drive Selection** Always double-check that the target drive is the **VHD-mounted "Virtual Drive."** Never select the physical IODD drive itself, as this will lead to data loss. Enabling **Write-Protection** on the physical drive before starting is a recommended safety measure. {% endhint %} --- ### 3. Booting from the Virtual Drive Once the process in Rufus is complete, you must configure your PC to boot from this virtual drive. 1. Save the current state of the IODD by pressing the **[9]** key. 2. Follow the instructions in the **CMOS/BIOS Boot Order Setting** section: * Go to BIOS Setup Guide {% hint style="warning" %} To ensure the virtual drive is recognized during the boot sequence, some motherboards may require the IODD to be set to **VHD-only mode** or have the specific VHD file pre-selected and saved as the primary boot state. {% endhint %} --- ### 10.4 ๐ŸŽ WTG / Boot Camp (Mac OSX) {% hint style="danger" %} **Compatibility Warning** Boot Camp installation via this method is **not supported on Apple Silicon Macs** (M1, M2, M3, etc.). This guide applies only to Intel-based Mac models. {% endhint %} Image note: WTG and Boot Camp Support - Portable Windows environment for PC and Mac The combination of IODD's WTG (Windows To Go) capability and encryption features allows for a secure, portable booting solution on both standard PCs and Intel-based Macs. For the full setup process, please also refer to the UEFI Booting guide. {% hint style="info" %} **Prerequisites** Since the VHD Tool and Rufus are **Windows-only applications**, you must have access to a Windows environment for the initial setup. * **VHD Tool**: Download and Guide * **Rufus**: Download * **Windows ISO**: Windows 8.1, 10, or 11 (Professional / Enterprise recommended) {% endhint %} --- ### Preparations 1. **Boot Camp Support Software (Drivers)**: * Download the necessary drivers via the **Boot Camp Assistant** (Control Panel) on your Mac. * Store these drivers on an external USB drive or a separate VHD file. 2. **VHD File for Installation**: * A **Fixed-size VHD** is highly recommended for optimal performance. * Related topic: Creating VHD Files --- ### Rufus Configuration The basic configuration follows the standard UEFI boot settings. Refer to the ISO to UEFI Conversion Guide for details. Image note: Rufus Advanced Drive Properties - Configuring Rufus for VHD-based WTG installation 1. **Enable Advanced Options**: In Rufus, navigate to **[Advanced Drive Properties]** and check **[List USB Hard Drives]**. 2. **Select Target**: Choose the **mounted VHD drive** (the fixed-size virtual disk) as the target device. 3. **Partition & System**: Set the partition scheme to **GPT** and the target system to **UEFI (non CSM)**. {% hint style="danger" %} **Critical Selection Check** Ensure the target drive is the **VHD-mounted "Virtual Drive."** Never attempt installation directly onto the physical IODD disk, as this will result in total data loss. It is strongly recommended to enable **Write-Protection** on the physical IODD device as a safeguard. {% endhint %} --- ### Booting into Boot Camp 1. Ensure your Mac is completely turned off. 2. Connect the IODD to the Mac. 3. Press the **Power button** while holding down the **[Option] (Alt)** key. 4. When the boot manager appears, select the **Yellow EFI Boot icon**. {% hint style="info" %} During the first-time installation, hold the **[Control]** key while selecting the disk to set it as the default boot device. {% endhint %} 5. After the Windows setup completes, install the **Boot Camp Support Software (drivers)** prepared earlier. --- ### Additional Resources For official information regarding Apple Boot Camp, please visit: Apple Support: Install Windows on your Mac with Boot Camp --- ### 10.5 ๐Ÿ’ฝ Creating Virtual Drives for Apple Silicon Macs Since the Windows-based VHD Tool cannot be used directly on Apple Silicon Macs (M1, M2, M3, etc.), you can create a compatible virtual drive file using the macOS Terminal. ### Recommended Resources For more details on dummy file creation, refer to the following technical guides: * Creating Large Dummy Files via macOS Terminal * mkfile Command Reference (SS64) --- ### Step-by-Step Creation Guide You can create a dummy file using the `mkfile` command. The file extension must be set to **.DSK** to be recognized by the IODD as a virtual drive. {% hint style="info" %} **Command Syntax** Open the Terminal and use the following command structure: `$ mkfile [Size] [Path/Filename.DSK]` {% endhint %} #### Usage Examples: * **Create a 10GB Virtual Drive:** ```bash $ mkfile 10G ~/VirtualHDD.DSK ``` *(Creates a 10GB virtual drive file named "VirtualHDD.DSK")* * **Create a 100GB Virtual Drive:** ```bash $ mkfile 100G ~/ST400VD.DSK ``` *(Creates a 100GB virtual drive file named "ST400VD.DSK")* --- ### How to Prevent File Fragmentation (Critical for IODD) The IODD hardware requires virtual drive files (DSK, ISO, VHD) to be stored in **physically contiguous space** (unfragmented). macOS does not have a built-in defrag utility, so follow these methods to ensure compatibility: {% hint style="info" %} **Method 1: Create Directly on the IODD Drive (Recommended)** To prevent fragmentation from the start, execute the `mkfile` command directly onto the IODD drive's path. ```bash # Example: Creating directly on the IODD volume $ mkfile 20G /Volumes/Your_IODD_Name/NewDisk.DSK ``` {% endhint %} {% hint style="warning" %} **Method 2: Ensure Sufficient Free Space** Before creating a file, ensure the IODD has much more free space than the file size you intend to create. This allows the file system to allocate a single contiguous block of data more easily. {% endhint %} {% hint style="danger" %} **How to Fix "Defrag!" Errors on macOS** If the IODD displays a "Defrag!" error, macOS does not provide a tool to fix this in place. You must: 1. Copy the fragmented `.DSK` file to your Mac's desktop. 2. Delete the file from the IODD and **Empty the Trash**. 3. Copy the file back to the IODD. If the error persists, the most effective solution is to **backup all data, format the IODD, and copy all files back** at once. {% endhint %} {% hint style="warning" %} **Avoid Sparse Files** Do not use the `dd` command with `seek` to create files, as this creates "sparse files" that are highly likely to be fragmented and unrecognizable by the IODD hardware. Always use `mkfile`. {% endhint %} --- ## 11. ๐Ÿ”‘ Encryption Guide ### Hardware Model Comparison The IODD provides robust hardware-based encryption. The following table summarizes the encryption capabilities by model: | Feature | ST400 / MINI PRO | LK100 | IODD MINI | | :--- | :---: | :---: | :---: | | **Max Password Length** | 38 Digits | 38 Digits | 16 Digits | | **2nd Password Support** | O | O | X | | **Admin Mode** | O | O | X | | **Random Keypad** | O | O | O | | **Keep 2 Min. PW** | O | O | X | {% hint style="info" %} **ST300 Notice** The **ST300** model does not support hardware encryption features. For encryption support, please use the ST400, LK100, or MINI/MINI PRO series. {% endhint %} --- ### Core Encryption Features IODD employs **Full Disk Encryption (FDE)** on a hardware basis. This ensures that the entire disk is protected, and no data can be accessed or recovered without the correct password. {% hint style="info" %} **Random Keypad Security** For enhanced security, all encryption-related inputs utilize a **Random Keypad** system where the number positions change every time the screen is activated. This prevents fingerprint tracing on specific keys. **Always verify the keypad layout on the screen carefully** before entering or setting your password. {% endhint %} {% hint style="danger" %} **Data Initialization Warning** Enabling or disabling the encryption feature will **completely initialize (erase) all data** on the disk. You **must back up** all critical data to a separate storage device before making any changes to encryption settings. {% endhint %} {% hint style="warning" %} **Incompatibility & Conflicts** * Encryption formats between **IODD 2541** and **ST400/LK100** are **not compatible**. * Do not use IODD hardware encryption simultaneously with third-party software encryption solutions (e.g., **BitLocker**, VeraCrypt). Doing so may cause system instability or data corruption. {% endhint %} --- ### Getting Started To use the encryption features safely, set up the **2nd Password** first. It is the administrator key used during encryption initialization and when moving an encrypted disk to another ST400/LK100/MINI PRO enclosure. * **2nd Password Setup Guide** --- ### Terminal Tips for Advanced Users If you are managing drive paths or checking mount points on a Mac, you can use the following command: ```bash # List all connected disks to identify your IODD $ diskutil list ``` --- ### 11.1 Admin The administrator has all the rights of the device and can create or delete users 1\~4 and grant rights. --- ### 11.2 ๐Ÿ”‘ 2nd Password The **2nd Password** is a critical security layer required when initializing encryption on a drive or when migrating an encrypted drive to a different IODD ST/LK or MINI PRO device. This password can be up to 38 digits long and is strictly managed by the **administrator**. {% hint style="danger" %} **Irrecoverable Password** If the 2nd password is lost, it cannot be retrieved, reset, or recovered through any means. Ensure this password is stored in a secure location. {% endhint %} --- ### Why the 2nd Password is Essential {% hint style="info" %} **Enhanced Security Benefits** * **Anti Brute-Force**: Prevents unauthorized access via mass-cloning or brute-force attacks by adding a secondary hardware-level validation. * **Hardware Portability**: If your IODD enclosure is physically damaged, the 2nd password allows you to safely migrate your encrypted drive to a new IODD ST/LK or MINI PRO device. {% endhint %} --- ### Key Usage Guidelines {% hint style="warning" %} **Storage of the 2nd Password** The 2nd password is encrypted and stored within the **ST400/LK100/MINI PRO hardware**. You typically only need to set it once during the initial encryption setup unless you choose to change it later. {% endhint %} {% hint style="warning" %} **Drive Migration Requirement** When connecting an encrypted drive to a new IODD device, you must provide the existing 2nd password to gain access. Without it, the drive remains inaccessible. Related topic: Encrypted Disk Migration Guide {% endhint %} --- ### Setting the 2nd Password 1. Press the **Menu button** and navigate to: **[Encryption] - [Admin]**. Image note: Encryption Admin Menu - Access the Administrative encryption settings. 2. Select the **[Set 2nd P.W]** option. Image note: Set 2nd Password Screen - Input your desired 2nd password twice to confirm and set. 3. Once the 2nd password is successfully configured, proceed to set the **Admin Password**. Related topic: Setting the Admin Password {% hint style="warning" %} **Encryption Activation** Hardware encryption functionality cannot be activated or utilized without first configuring a 2nd password. {% endhint %} --- ### 11.3 ๐Ÿ”‘ Setting the Admin Password When multiple users share an IODD ST/LK device, the **Administrator Mode** allows for the management of individual user passwords and specific drive permissions. Administrators have the authority to reset user passwords and are the only ones capable of removing encryption from the entire device. ### Prerequisites {% hint style="warning" %} **2nd Password Requirement** You must configure the **2nd Password** before you can set the Admin Password. Related topic: 2nd Password Setup Guide {% endhint %} --- ### Step-by-Step Setup 1. Press the **Menu button** and navigate to: **[Encryption] - [Admin]**. Image note: Encryption Admin Menu - Accessing the Administrative encryption settings. 2. Select the **[Set Encryption]** option and review the caution message. {% hint style="danger" %} **Data Loss Warning** Enabling or deleting the Admin password will **initialize (erase) all data on the disk**. Ensure all important files are backed up before proceeding. {% endhint %} Image note: Encryption Caution Message - Read the warning carefully before initiating encryption. 3. Enter your desired **Admin Password twice** for confirmation. Image note: Admin Password Entry - Input the administrator password using the keypad. 4. Wait for the process to complete. Once finished, the disk is initialized, and the screen may display **[No appropriate partition]** because the drive is now unformatted. Image note: No Partition Message - Disk initialization successful; formatting is required for use. 5. Reconnect the IODD. You will now be prompted for the password. To log in as the administrator, you must enter the **prefix "0"** followed by your password. Image note: Admin Login Screen - Log in using the 0 + [Admin Password] format. --- ### Understanding the Password Structure The IODD login system uses a prefix to distinguish between the administrator and general users. {% hint style="info" %} **Login Format: [User ID] + [Set Password]** * **0**: Administrator Identification Digit * **1โ€“4**: User Identification Digits **Example:** If you set the administrator password to `55447788`, the final login code is **0**55447788. {% endhint %} {% hint style="warning" %} **Authentication Errors** If you receive a "Wrong Password" error despite entering the correct numbers, check if you omitted the **`"0"`** prefix. The system does not add the administrator ID automatically during the login prompt. {% endhint %} --- ### Next Steps After setting the password, you may need to format the drive or set up virtual drives. * Using Virtual Drives with Encryption --- ### 11.4 ๐Ÿ‘ฅ User Management Administrators have the authority to create multiple user profiles, each with distinct access rights to the encrypted drive. ### Administrator Authentication 1. Access the menu and navigate to: **[Encryption] - [User]**. Image note: Encryption User Menu - Navigate to the User settings under the Encryption menu. 2. Enter **0** followed by the **Admin Password**. {% hint style="info" %} The prefix `0` identifies the input as an administrative login. {% endhint %} Image note: Admin Password Entry - Example: 0 + [Admin Password] 3. Select the specific user index (1โ€“4) you wish to manage. Image note: User Selection - Choose one of the four available user slots. --- ### User Permissions and Password Setup Configure the following options and set a password for the selected user: Image note: User Permission Settings - Setting individual user rights. {% hint style="info" %} **Understanding User Options** * **Read Only**: The user can access files but cannot write, modify, or delete data on the drive. * **User Change**: Permits the user to change their own password without administrative intervention. * **User Delete**: Allows the user to delete their own account/password from the device. {% endhint %} --- ### Saving Changes After configuring the user profile, you must confirm the settings. Image note: Save Users Option - Finalizing the user configuration. {% hint style="warning" %} **Persistence of Settings** You must select **[Save users]** to commit the changes. If you exit the menu without saving, all modifications will be discarded. {% endhint %} --- ### Password Structure for Users (1-4) To log in as a specific user, the password must be prefixed with the corresponding **User Identification Digit**. {% hint style="info" %} **Login Format** **[User ID (1~4)] + [User Password (Up to 37 digits)]** * If **User 1** sets the password to `55447788`, the login code is **1**55447788. * If **User 4** sets the password to `55447788`, the login code is **4**55447788. {% endhint %} --- ### Advanced User Operations For more details on specific encryption menus available to Users 1โ€“4, Related topic: User Encryption Menu --- ### 11.5 Duress PIN The **Duress PIN** feature, also called a **decoy PIN**, lets an IODD **ST400** or **MINI PRO** present only a prepared `vhd4.vhd` virtual disk to the PC when the device is unlocked with the **User 4 PIN**. This allows a separate, shareable decoy volume to be exposed while the normal storage area remains hidden from that PC session, supporting a **plausibly deniable** access workflow. {% hint style="warning" %} **Supported Models and Firmware** Duress PIN with `vhd4.vhd` is supported on **ST400** and **MINI PRO** with firmware **version 82 or later**, updated using `iodd_firm_upd-0.8.2.0_xx.exe` or later. {% endhint %} #### How It Works | Unlock Method | Main Purpose | What the PC Sees | | --- | --- | --- | | PIN other than User 4 | File management, ISO/VHD management, `vhd4.vhd` setting update | Normal physical partition | | User 4 PIN | Duress PIN access | Disk sized to `vhd4.vhd` | When the device is unlocked with a PIN other than **User 4**, the PC sees the normal physical partition. Use this state to create, delete, or update `vhd4.vhd`. When the device is unlocked with the **User 4 PIN**, the PC sees only the disk mapped to `vhd4.vhd`; other files from the physical partition are not shown in that session. #### Preparing `vhd4.vhd` 1. Unlock the device with a PIN other than the **User 4 PIN**. 2. On the PC, create a file named exactly `vhd4.vhd` in the **root folder** of the first partition. 3. Make sure the file is in the root folder, not in a subfolder. 4. Return to the root folder list on the device screen. 5. Rebuild the root folder list by pressing **Key 1**, rebooting the device, or entering a subfolder and returning to the root folder. 6. When `vhd4.vhd` appears in the list, the device updates the VHD setting. 7. Unlock the device again with the **User 4 PIN**. 8. The PC shows a disk whose size matches `vhd4.vhd`. {% hint style="info" %} When creating `vhd4.vhd`, use **VHD_Tool++ v0.9.0.10 or later** from the IODD Download Center. VHD_Tool++ is a Windows-only tool. {% endhint %} #### `vhd4.vhd` Requirements | Item | Requirement | | --- | --- | | File name | `vhd4.vhd` | | Location | Root folder of the first partition | | Format | Fixed-size VHD file | | Unsupported formats | Dynamic VHD, VHDX | | Placement | Contiguous, without fragmentation | Select `vhd4.vhd` on the device and press **Key 5** to display the file information message. The `fragment` value must be `1`. {% hint style="danger" %} A fragmented `vhd4.vhd` cannot be used. If the LCD shows a defragmentation or `DEFRAG` message, recreate `vhd4.vhd` as a contiguous fixed-size VHD file, then unlock with a PIN other than User 4 and rebuild the root folder list. {% endhint %} #### Updating the VHD Setting The device checks whether `vhd4.vhd` exists when it builds the root folder list. | State | Device Behavior | | --- | --- | | `vhd4.vhd` exists and is not fragmented | Updates the VHD setting for use with the User 4 PIN | | `vhd4.vhd` exists but is fragmented | Does not apply the VHD setting | | `vhd4.vhd` does not exist | Deletes the saved VHD setting | {% hint style="warning" %} Rebuild the root folder list only while unlocked with a PIN other than the **User 4 PIN**. A user with disk write protection cannot update the `vhd4.vhd` setting. {% endhint %} #### Troubleshooting **The VHD Disk Does Not Appear After Unlocking With the User 4 PIN** 1. Unlock the device with a PIN other than the User 4 PIN. 2. Check that `vhd4.vhd` exists in the root folder of the first partition. 3. Rebuild the root folder list by pressing **Key 1**, rebooting the device, or entering a subfolder and returning to the root folder. 4. Check that `vhd4.vhd` is not fragmented. 5. Unlock again with the User 4 PIN. If the PIN used to update the setting has disk write protection enabled, the VHD setting cannot be updated. **The Device Does Not Recognize `vhd4.vhd`** - Make sure the file name is exactly `vhd4.vhd`. - Make sure the file is in the root folder of the first partition. - Make sure the root folder list was rebuilt after creating the file. - Make sure the file is a fixed-size VHD, not a dynamic VHD or VHDX file. - Make sure the file is not fragmented. **A Defragmentation or `DEFRAG` Message Appears** `vhd4.vhd` is not stored contiguously on the disk. Delete and recreate `vhd4.vhd` on the PC, or arrange it so it is stored in a contiguous area. Then unlock with a PIN other than the User 4 PIN and rebuild the root folder list. --- ### 11.6 Remove Encryption / Change Admin Password Modifying the fundamental encryption settings of your IODD device has different impacts on your data depending on the command. Please review the following impact table carefully before proceeding. {% hint style="info" %} **Password Change & Data Safety** Changing your Admin password **does not delete the files** stored on the internal drive. It only resets the secondary User (1โ€“4) profiles and administrative access credentials. {% endhint %} ### Impact Table by Command | Command | Administrator Settings | User 1~4 Settings | Internal Drive Data (Files) | | :--- | :---: | :---: | :---: | | **Set Encryption** | Initialized | Initialized | **โŒ All Data Lost** | | **Change Password** | Updated | **Removed** | **โœ… Remains Intact** | | **Remove Encryption** | **Removed** | **Removed** | **โŒ All Data Lost** | --- ### Step-by-Step Instructions 1. Press the **Menu button** and navigate to: **[Encryption] - [Admin]**. Image note: Encryption Admin Menu - Accessing the administrative security settings. 2. Select either **[Remove Encryption]** or **[Chg Password]** based on your objective. 3. **Review the Caution Message** on the screen before confirming: * **Change Password**: This will reset the administrative password and delete all User 1โ€“4 profiles. **The files on the drive will remain safe and accessible to the administrator.** Image note: Change Password Warning - Notice: User 1-4 data will be reset, but drive files are preserved. * **Remove Encryption**: {% hint style="danger" %} This will permanently delete all passwords, user profiles, and **all files stored on the internal drive.** This action is irreversible. {% endhint %} Image note: Remove Encryption Warning - Warning: All data and settings will be permanently erased. --- {% hint style="warning" %} **Verification After Action** * **After Removing Encryption**: The device returns to a standard (non-encrypted) state. You must format the drive again to use it. * **After Changing Password**: You must log in with the new password using the **0 + [New Password]** format upon reconnection. Your existing files will be available immediately. {% endhint %} {% hint style="warning" %} **Unrecoverable Actions** For "Set Encryption" or "Remove Encryption," the deleted data **cannot be recovered** by any software or hardware tools once confirmed. Always maintain a backup of critical files. {% endhint %} --- ### 11.7 User Standard user access and encryption management for non-administrative users. --- ### 11.8 User Menu (Encryption) Standard users (User 1~4) can manage their own security settings, such as changing or deleting their passwords, provided the Administrator has granted the necessary permissions. {% hint style="info" %} **Menu Visibility** If you cannot see the **Encryption** menu after pressing the Menu button, it means the Administrator has disabled your permission to change or delete your password. {% endhint %} --- ### Accessing the Menu 1. Press the **[Menu]** button on your IODD device. 2. Navigate to and select the **[Encryption]** menu. Image note: User Encryption Menu - Accessing the encryption settings as a standard user. --- ### Available User Functions Depending on the **Permissions** assigned to you by the Administrator, the following options will be activated: Image note: Activated User Options - The menu items shown will vary based on your specific user rights. {% hint style="info" %} **User Menu Options** * **Chg Password**: Allows User 1~4 to independently change their own login password. * **Del Password**: Allows User 1~4 to delete their own account and password from the device. {% endhint %} {% hint style="warning" %} **Administrative Authority** Even if a user has the rights to manage their own password, the **Administrator** retains full control and can change or delete any user's password at any time via the Admin Mode. {% endhint %} --- ### Security Recommendations {% hint style="warning" %} **Password Deletion** If you use the **Del Password** function, you will lose access to the encrypted drive immediately. You will need to contact the Administrator to have a new user profile and password assigned to you. {% endhint %} {% hint style="info" %} **Changing Passwords** It is recommended to change your password periodically. When changing your password, ensure you remember your **User Identification Digit (1-4)**, as it must be entered as a prefix every time you log in. {% endhint %} --- ### 11.9 Encrypted Disk Migration (MINI PRO / ST / LK) {% hint style="info" %} **Drive Compatibility** An encrypted HDD/SSD can be moved to another ST400/LK100 device while maintaining the existing encrypted data, provided you synchronize the security settings correctly. {% endhint %} ### Preparation To migrate your encrypted data to a new device, you will need: * **Existing Drive**: The original HDD/SSD containing your encrypted data. * **Temp Drive**: A secondary or temporary drive used only for the initial setup of the new IODD. * **New IODD**: The replacement ST400/LK100 enclosure. {% hint style="danger" %} **Safety First** **Do not install your Existing Drive** into the New IODD until you have completed the 2nd password configuration. This prevents any accidental data initialization during the setup phase. {% endhint %} --- ### Migration Procedure Follow these steps to synchronize your new hardware with the existing encryption: #### 1. Initial Setup with the Temp Drive Install the **Temp Drive** into your **New IODD** enclosure. This drive acts as a placeholder to safely initialize the encryption settings on the new hardware. #### 2. Synchronize the 2nd Password Navigate to the menu and set the **2nd Password** on the New IODD. Related topic: 2nd Password Setup Guide {% hint style="warning" %} **Password Consistency** You must set the **exact same 2nd password** that was used on the original device. If the drive is not recognized after the migration, you can simply re-run this process with the correct 2nd password to regain access. {% endhint %} #### 3. Hardware Swap After successfully setting the 2nd password, power off the device and remove the **Temp Drive** from the enclosure. #### 4. Final Migration Install your **Existing Drive** into the New IODD. The device will now recognize the encryption, and you can unlock your data using your original administrator or user passwords. --- {% hint style="info" %} **Troubleshooting Access Issues** If your Existing Drive is not recognized after migration, it is likely that the 2nd password was entered incorrectly. In this case, re-insert the **Temp Drive**, use the **[Chg Password]** menu in Admin mode to set the correct 2nd password, and then try the Existing Drive again. {% endhint %} {% hint style="warning" %} **Encryption Prefix** Remember to enter the identification digit when prompted for a password: * **0** + [Admin Password] * **1~4** + [User Password] {% endhint %} --- ## 12. ๐Ÿ–ฅ๏ธ Admin Manager Application The Admin Manager is a specialized Windows application that allows administrators to manage encryption settings, user permissions, and device locking/unlocking directly from a PC. ### ๐Ÿ” Security & Mutual Authentication The iODD Admin Manager performs Challenge-Response based mutual authentication upon device connection. It exchanges a non-reusable random number (Challenge) for each session and verifies the response calculated using the genuine key securely stored within the iODD hardware to mutually confirm the authenticity of both the device and the application. This process is designed to prevent replay attacks. Fake or modified devices that fail authentication cannot establish management communication, which ultimately helps verify hardware authenticity and minimize the attack surface. {% hint style="warning" %} **Supported Models Only**: ST400 / LK100 / MINI PRO. This application does **not** support: 2531, 2541, IODD MINI, ST300. {% endhint %} ### Download Link You can Use the latest available version of the Admin Manager from the official IODD Download Center. {% hint style="info" %} **IODD Download Center** {% endhint %} --- ### Application Layout The application is divided into several functional zones to facilitate efficient device management. Image note: Admin Manager Main Layout - Overview of the Admin Manager interface. --- ### ๐Ÿ›ก๏ธ Admin Panel Area This section allows the administrator to control the primary security state of the connected IODD. Image note: Admin Panel Interface - Controls for device lock/unlock and secondary password management. 1. **[Admin Password] Field**: All administrative actions require this password. Without it, changes will not be saved to the IODD hardware. 2. **[Secondary Password (2nd Password)] Field**: Used for initial encryption setup or when migrating the drive to new hardware. 3. **[Set] Button**: Commits the entered 2nd password (up to 38 digits) to the machine. 4. **[Unlock] Button**: Unlocks the connected IODD from the PC. 5. **[Lock] Button**: Manually engages the password lock on the device. 6. **[Password Configuration] Tab**: Allows saving current user settings as a file. {% hint style="info" %} **Master Password**: Saving or loading configuration files requires a "Master Password." This is independent of the Admin Password and is used solely for protecting the configuration files. {% endhint %} --- ### ๐Ÿ‘ฅ User Management Area Administrators can configure up to four individual user profiles with specific access rights. Image note: User Management Section - Detailed configuration for Users 1 through 4. * **User Selection [1]**: Check the box for the user (1-4) you wish to manage. * **Password [2] & Authority [3]**: Set the individual password and check the desired permissions. * **Read Only**: User cannot write data. * **User Change**: User can modify their own password. * **User Delete**: User can remove their own credentials. * **Execution Buttons**: * **[Set Password]**: Applies the settings to the IODD. * **[Do not reconnect]**: If checked, settings apply immediately without needing to physically reconnect the device. * **[Empty]**: Clears all input fields in the user area for a fresh start. {% hint style="warning" %} **User Password Structure** User passwords must start with their designated User ID (1-4). The total length can be up to 38 digits (1 digit ID + 37 digit password). {% endhint %} --- ### ๐Ÿ“Š Status & Utility Areas #### Current Status Area Provides a real-time overview of the encryption lock status and active user permissions. Image note: Current Status Display - Check the live status of the connected hardware. #### Log Area Displays a chronological log of all actions and progress. Use the **[Clear]** button to reset the view. Image note: Application Log - Monitor the progress of tasks and command results. #### Main Menu & Settings Located under **[Settings] - [Preferences]**, you can close the program or change the interface language. * **Supported Languages**: Korean, English, German, French, Chinese, Japanese, Russian. --- {% hint style="info" %} **Feature Availability** All encryption functions can be performed directly on the IODD device hardware. The Admin Manager application is required only for managing **Password Configuration Files** (.cfg) or for more convenient batch management via PC. {% endhint %} ### Related Documentation * Administrative Encryption Settings --- ## 13. ๐Ÿ”‘ IODD MINI Encryption The IODD MINI features hardware-based AES256 encryption, ensuring that your data is protected and inaccessible without the correct authorization. #### Hardware Model Comparison While the IODD MINI provides powerful encryption, its feature set differs from the ST/LK and MINI PRO series. Please refer to the table below: | Feature | ST400 / LK100 / MINI PRO | 2541 / MINI (Legacy) | | :--- | :---: | :---: | | **Max Password Length** | 38 Digits | 15 Digits | | **User ID Prefix (0, 1-4)** | โœ… Supported | โŒ Not Supported | | **2nd Password Support** | โœ… | โŒ | | **Admin Mode** | โœ… | โŒ | | **Random Keypad** | โœ… | โœ… | | **Keep 2 Min. PW** | โœ… | โŒ | --- #### Core Security Information {% hint style="info" %} **ST300 Notice** The **ST300** model does not support hardware encryption features. {% endhint %} {% hint style="info" %} **Random Keypad Entry** All password inputs utilize a **Random Keypad** system. The position of each number changes every time the screen is activated. **Carefully verify the keypad layout** on the IODD MINI screen before entering or setting your password. {% endhint %} {% hint style="danger" %} **Data Initialization** Enabling or disabling the encryption feature will **completely erase (initialize) all data** on the internal drive. It is mandatory to back up your important files before making changes to the encryption state. **Tip (Legacy MINI)**: On the older IODD MINI, if you perform **"Remove Encryption" immediately after "Set Encryption"** (before any new data is written to the drive), it is possible to return the drive to a standard state without destroying the original pre-encryption data. {% endhint %} {% hint style="warning" %} **Encryption Incompatibility** Encryption formats are **not compatible** between different IODD generations. Drives encrypted on **IODD 2541** or **ST400/LK100/MINI PRO** cannot be read by an **IODD MINI**, and vice-versa. {% endhint %} {% hint style="warning" %} **Third-Party Software Conflicts** Do not use IODD hardware encryption in conjunction with software-based Full Disk Encryption (FDE) solutions such as **BitLocker** or VeraCrypt. Simultaneous use may lead to critical system errors or data corruption. {% endhint %} --- #### Configuration Guide Since the IODD MINI does not utilize a 2nd password system, you can proceed directly to the encryption setup and removal guide: * **Setting or Removing Encryption on IODD MINI** --- ### 13.1 ๐Ÿ” Set/Remove Encryption(MINI) ### Set Password **1.**Press the Menu button to select the **\[Encryption] \[SetEncryption]** menu. **2.** Check Caution Message {% hint style="danger" %} **Data Deletion Warning** When setting or removing the password, all disk data will be deleted. Please back up all necessary data before proceeding. {% endhint %} **3.**enter the password **twice.** **4.** Enter the setup password twice and wait for a while to finish. The disk was initialized \ when setting the password, Displayed **\[no appropriate partition]** **5.**When IODD is reconnected, Require a _**password**_ ### Remove Encryption **1.**Press the Menu button to select the **\[Encryption] \[RemoveEncrypt]** menu. **2.** Check Caution Message {% hint style="danger" %} **Data Deletion Warning** When setting or removing the password, all disk data will be deleted. Please back up all necessary data before proceeding. {% endhint %} **3.**enter the password **twice.** **4.** Enter the setup password twice and wait for a while to finish. The disk was initialized \ when Remove the password, Displayed **\[no appropriate partition]** ### and Using a virtual drive with encryptionDrive Setup --- ## 14. Various Functions --- ### 14.1 ๐Ÿ›ก๏ธ Write Protection IODD provides robust write protection that can be applied **globally** to the entire device or **individually** to specific virtual drives. This ensures your data remains untampered when connected to external systems. {% hint style="danger" %} **Emergency Security Connection** When connecting the IODD to an **unverified or insecure system**, always **press and hold the [3] key while plugging it in.** This forces the device into Write-Protect mode immediately, preventing any malware or unauthorized system from modifying your data. {% endhint %} --- ### Quick Hotkeys | Action | Result | | :--- | :--- | | **Hold [3] for 3s** | Triggers a **reconnection** with **Write-Protection enabled**. | | **Hold [0] for 3s** | Triggers a **reconnection** with **Write-Protection temporarily disabled**. | | **Boot with [3] pressed** | Starts the device in **Write-Protection mode** from the moment of connection. | --- ### Global Write Protection Setup To apply write protection to the entire IODD device, follow these steps: 1. Press the **[Menu]** button and navigate to: **[USB Control]**. Image note: USB Control Menu - Access the hardware control settings. 2. Locate **[Write Protect]** and toggle it using the **[6]** key or **[Enter]**. Image note: Enable Write Protect - Activating the global write protection lock. 3. Press the **[Menu]** key to save the current configuration. Image note: Save Settings - Confirming and saving your changes. {% hint style="info" %} **Status Indicator** Once Global Write Protection is active, the **padlock icon** at the top of the IODD display will be **highlighted in red**, indicating the drive is in a read-only state. {% endhint %} --- ### Individual Drive Configuration If you need to set write protection for a specific virtual drive (VHD/DSK) rather than the whole device, please refer to the Mode Configuration guide: * **Individual Mode Configuration** --- ### Terminal Verification (macOS/Linux) You can verify the read-only status of your IODD via terminal: ```bash # On macOS, check the "Read-Only" status in the disk info $ diskutil info /dev/diskX | grep "Read-Only" ``` --- ### 14.2 ๐Ÿ“„ TXT Viewer The TXT Viewer is a highly convenient tool that allows you to read text files directly on the IODD's built-in display without needing to connect to a operating system. ### Supported Formats To ensure proper rendering of text on the small display, please check the encoding of your files: * **Supported Encodings**: **UTF-16 (UCS-2 LE)** and **ASCII**. * **Incompatibility**: Certain Asian character codes and complex encodings may **not be supported**. {% hint style="info" %} **Encoding Tip** If a text file appears garbled or shows broken characters, try re-saving the file on your PC using **UTF-16 Little Endian** encoding for the best compatibility. {% endhint %} --- ### How to Use 1. Navigate through your IODD's file list to find the desired `.txt` file. 2. Highlight the file and press the **[Enter]** (or **[5]**) key to open it. --- ### Navigation Controls Use the hardware keypad to scroll through and read your documents: | Key | Action | Description | | :---: | :--- | :--- | | | **Line Up** | Scroll up by a single line. | | | **Line Down** | Scroll down by a single line. | | | **Page Up** | Jump to the previous page. | | | **Page Down** | Jump to the next page. | | | **Exit** | Close the viewer and return to the file list. | | | **Open** | Open the selected TXT file. | --- {% hint style="info" %} **Practical Use Case** This feature is particularly useful for storing **Windows Serial Keys**, **IP addresses**, or **step-by-step installation instructions** that you need to reference while the host computer is being formatted or offline. {% endhint %} ### Advanced Maintenance If you need to manage many text files, you can verify their presence and encoding via your terminal before disconnecting the IODD: ```bash # Check file encoding on macOS/Linux $ file -I /Volumes/IODD/_ISO/notes.txt ``` --- ### 14.3 ๐Ÿ•’ Keep 2min.PW The **Keep 2min.PW** feature is designed to streamline the operating system installation process. When enabled, the IODD remains in an unlocked state for **2 minutes** after a power cycle or system reboot, eliminating the need to re-enter your password repeatedly. {% hint style="info" %} **How it Works** Once you unlock the device with your password, the IODD stores the "unlocked" state in its temporary memory. If the computer reboots and the IODD regains power within 120 seconds, it will bypass the password prompt automatically. {% endhint %} {% hint style="info" %} **Recommended Use Case** This feature is highly effective during **Windows or Linux installations**, where the system may need to restart several times to complete the setup or driver updates. {% endhint %} --- ### How to Enable the Feature 1. Press the **[Menu]** button on the IODD and navigate to: **[USB Control]**. Image note: USB Control Menu - Navigate to the hardware control settings. 2. Locate **[Keep P.W. 2min]** and toggle it using the **[6]** or **[Enter]** key. Image note: Enable Keep PW Feature - Activating the 2-minute password retention. 3. Press the **[Menu]** button again to save your settings. --- ### Operational Safety {% hint style="danger" %} **Security Reminder** While this feature is active, anyone who reboots your computer or reconnects the IODD within the 2-minute window can access your data without a password. **Disable this feature** once your installation work is complete to maintain maximum security. {% endhint %} {% hint style="warning" %} **Power Loss Limitation** If the IODD remains without power (unplugged) for more than 2 minutes, the temporary unlock state will expire, and you must enter your password again to gain access. {% endhint %} --- ### Related Troubleshooting If the device is not being recognized quickly enough during reboot to trigger this function, you can check the USB initialization speed in your PC's BIOS: ```bash # (Conceptual) Ensure 'Fast Boot' or 'USB Initialization' is set to Full in BIOS ``` --- ### 14.4 ๐Ÿ“Š S.M.A.R.T / Information Maintaining the health of your internal drive and staying updated with the latest firmware is crucial for data integrity. The IODD provides built-in tools to monitor these statuses directly on its display. ### S.M.A.R.T. Disk Information S.M.A.R.T (Self-Monitoring, Analysis, and Reporting Technology) allows you to check the diagnostic health of your internal HDD or SSD. 1. Press the **[Menu]** button and navigate to: **[Information] - [S.M.A.R.T]**. Image note: S.M.A.R.T Menu - Accessing the disk diagnostic tool. {% hint style="info" %} **Understanding Health Status** * **HDD Health**: * `<< Good >>`: The drive is healthy and operating normally. * `<< Warning >>`: Potential issues detected. Back up your data and consider replacement. * `<< Bad >>`: Critical failure imminent. Replace the drive immediately. * **HDD Model**: Displays the manufacturer's model name. * **HDD Serial**: Displays the unique serial number of the drive. {% endhint %} {% hint style="danger" %} **Power Stability Warning** If the **USB voltage is insufficient or unstable**, S.M.A.R.T. information may be displayed incorrectly or fail to load. Always ensure a stable connection. For more details, Related topic: Voltage Check {% endhint %} --- ### IODD Information You can check the specific details of your IODD hardware, including the current firmware version and hardware revision. 1. Press the **[Menu]** button and navigate to: **[Information] - [Product Info]**. Image note: IODD Information Menu - Checking the device hardware and firmware version. {% hint style="info" %} **Key Device Status Indicators** * **Firmware Ver**: Current IODD firmware version. * **USB Speed**: Currently connected speed (Full/Hi/Super Speed). * **USB Lowest Volt**: The absolute lowest voltage detected since the device was connected. This is the most important indicator of power stability. * **Current Voltage**: The real-time BUS voltage currently being supplied. {% endhint %} --- ### Advanced Hardware Check (Linux/macOS) If you need a more detailed diagnostic log while the IODD is connected to a computer, you can use terminal commands: ```bash # On macOS, check disk utility list for basic health info $ diskutil list # On Linux, use smartctl for detailed reports (requires smartmontools) $ sudo smartctl -a /dev/sdX ``` --- ### 14.5 ๐Ÿงน IODD TRIM Tool - User Manual **Version**: 0.2.0.4 **Platform**: Windows 64-bit **License**: Freeware --- #### 1. Overview The IODD TRIM Tool is a Windows-exclusive application designed to send TRIM commands to **external SSDs connected via a USB-SATA bridge**. {% hint style="success" %} **Universal Compatibility** This tool is **not limited to IODD products**โ€”it supports **all external USB SSDs** from any manufacturer, as long as the USB bridge supports **ATA Pass-Through** or **SCSI UNMAP**. {% endhint %} While Windows automatically performs TRIM on internal SATA/NVMe SSDs, this automatic function does not work for external SSDs connected through a USB bridge. This tool is designed to maintain the performance and extend the lifespan of such external SSDs. ##### ๐Ÿ“ฅ Download - **Use the latest available version of IODD TRIM Tool** ##### Key Features - **3-Step TRIM Strategy**: Automatic fallback from DSM TRIM โ†’ SCSI UNMAP โ†’ ATA Pass-Through. - **BOT/UASP Support**: BOT prioritizes ATA Pass-Through, while UASP prioritizes SCSI UNMAP. - **Full Device TRIM**: Sends TRIM commands to the entire SSD area. - **Free Space Only TRIM**: Performs TRIM only on empty space, preserving existing files. - **Real Test**: Verifies if TRIM is actually working by performing a file write/delete/verify sequence. - **Write Speed Chart**: Records speeds at 2-second intervals during the Real Test and displays them on a time-series chart. - **Drive Inspection**: Provides detailed information on disk partitions, volumes, and free space. - **Dry Run Mode**: Simulates the process without sending actual TRIM commands. - **Read-only Drive Detection**: Automatically disables file output when run on a read-only drive. - **8 Languages Supported**: Korean, English, Japanese, Simplified Chinese, Spanish, German, French, and Russian. ##### ๐Ÿš€ Quick Start Guide 1. **Select your device** from the dropdown menu at the top. 2. **Choose a TRIM Mode**: - **Full Device TRIM**: Completely wipes the SSD. **ALL data will be permanently deleted.** Use this only when initializing a new or repurposed drive. - **Free Space Only TRIM**: Only trims the unused empty space. **Your existing files remain safe.** Use this to optimize performance on a drive you are currently using. 3. Click the **Start** button to execute TRIM. --- #### 2. System Requirements | Item | Requirement | | :--- | :--- | | OS | Windows 10 / 11 (64-bit) | | Privileges | **Administrator privileges** required (needed for SCSI Pass-Through) | | Connection | SSD connected via a USB-SATA bridge | | Protocol | Supports both BOT (Bulk-Only Transport) and UASP (USB Attached SCSI Protocol) | {% hint style="danger" %} **Important**: You must run the application with **Administrator privileges**. Standard user permissions cannot send SCSI Pass-Through commands to the disk. {% endhint %} --- #### 3. What is TRIM? TRIM is an ATA command (DATA SET MANAGEMENT, 0x06) that tells the SSD which data blocks are no longer in use. ##### Benefits of TRIM - **Maintains Write Performance**: Pre-emptively secures empty blocks to prevent write speed degradation. - **Extends SSD Lifespan**: Reduces unnecessary write/erase cycles, minimizing NAND wear. - **Consistent Response Times**: Maintains stable performance even after long periods of use. - **Efficient Space Management**: Optimizes the SSD controller's internal garbage collection. ##### When should you use TRIM? - After deleting a large number of files. - When the SSD's write speed has noticeably slowed down. - After using a USB external SSD for a long time without TRIM. - When the OS does not support automatic TRIM for USB-connected SSDs. --- #### 4. UI Layout The app consists of a top toolbar and 3 main tabs. ```text โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ [IODD Products] [IODD Manual] [Usage] [License] [TRIM Info] [Language โ–ผ] โ”‚ โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค โ”‚ Execute TRIM โ”‚ Drive Inspect โ”‚ Real Test โ”‚ โ”œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค โ”‚ โ”‚ โ”‚ (Tab Content Area) โ”‚ โ”‚ โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ ``` --- #### 5. Top Toolbar | Button | Function | | :--- | :--- | | **IODD Products** | Opens the IODD product page (Amazon) in your browser. | | **IODD Manual** | Opens the IODD help site (help.iodd.kr) in your browser. | | **Usage** | Displays a usage guide popup. | | **License** | Displays a popup with freeware license information. | | **TRIM Info** | Displays a popup explaining the benefits and timing of TRIM. | | **Language Selection** | Changes the app's UI language (dropdown on the top right). | --- #### 6. Execute TRIM Tab This is the main tab where you send TRIM commands to the selected disk. ##### 6.1 Disk Selection Select the target disk from the dropdown menu at the top. Each item displays the following information: ```text PD8 | Samsung SSD 860 | 465.8 GiB | BOT | O:(FAT32) | TRIM:YES PD6 | Generic | 111.8 GiB | UAS | P:(NTFS), Q:(exFAT) | TRIM:YES ``` - **PD Number**: Physical Drive number - **Model Name**: SSD model - **Capacity**: Total disk capacity (GiB) - **Protocol**: BOT (ATA Pass-Through) / UAS (SCSI UNMAP) / Non-USB - **Volume**: Drive letter + File system - **TRIM Support**: TRIM:YES / TRIM:NO / APT:N/A > You can rescan the disk list using the **Refresh** button. ##### 6.2 Disk Info Memo When a disk is selected, detailed information appears in the memo box below: - Model, Serial, Capacity, Transfer Protocol - Volume info (File system, Cluster size, Offset, Partition length in GiB) - ATA Pass-Through support status - TRIM Capable status - ATA Model, Firmware info ##### 6.3 TRIM Mode | Mode | Description | | :--- | :--- | | **Full Device TRIM** | Sends TRIM to the entire disk. **ALL data will be permanently deleted.** | | **Free Space Only** | Trims only the empty space on the file system. Existing files are preserved. | {% hint style="danger" %} **Warning**: Full Device TRIM permanently deletes all data on the disk. Be sure to back up your data before using this mode. {% endhint %} ##### 6.4 TRIM Transmission Methods Depending on the disk's protocol, a 3-step automatic fallback strategy is applied: | Order | Method | Description | | :--- | :--- | :--- | | 1 | **DSM TRIM** | Windows Native TRIM (Attempted while the volume is mounted) | | 2 | **SCSI UNMAP** | For UASP devices. Attempted after Volume Lock/Dismount if DSM TRIM fails | | 3 | **ATA Pass-Through** | Default for BOT devices. Final fallback if SCSI UNMAP fails | - **BOT Devices**: Directly sends via ATA Pass-Through. - **UASP Devices**: Attempts DSM TRIM โ†’ SCSI UNMAP โ†’ ATA Pass-Through in order. - SCSI UNMAP attempts multi-descriptor mode first, then switches to single-descriptor mode if rejected. ##### 6.5 Options | Option | Description | Default | | :--- | :--- | :--- | | **Dry Run** | Simulates the operation without sending actual TRIM commands. | OFF | | **Flush Volumes** | Flushes the volume buffers before performing TRIM. | ON | | **Init after TRIM** | Initializes the disk to GPT/MBR after TRIM is complete. | None | ##### 6.6 Advanced Settings Checking the **Show Advanced Settings** box reveals additional options: | Setting | Description | Default | | :--- | :--- | :--- | | **Timeout (ms)** | SCSI timeout duration for each TRIM batch. | 5,000ms | | **Retry** | Number of retries upon failure. | 3 | | **Batch Entries** | Number of TRIM ranges to send at once. | 32 | | **Batch Limit** | Maximum number of batches (1, 10, 100, All). | All | | **Allow System Disk** | Allows TRIM on the OS system disk. | OFF | | **Mask Serial** | Masks the serial number in logs. | ON | ##### 6.7 Execution 1. Select the disk. 2. Select the TRIM mode. 3. Click the **Start** button. 4. Verify by entering the disk number in the warning confirmation dialog. 5. The progress will be shown on the progress bar and status bar. 6. A success/failure popup will appear upon completion. You can immediately stop an ongoing TRIM by clicking the **Cancel** button. ##### 6.8 USB Notice You can view guidance regarding the USB bridge device's protocol: - **BOT**: Sends TRIM via ATA Pass-Through. - **UASP**: Sends TRIM via SCSI UNMAP (falls back to ATA Pass-Through if failed). If TRIM fails: 1. Unplug and reconnect the device directly. 2. Try changing the USB hub or cable. 3. Refresh and check the Transport protocol. --- #### 7. Drive Inspect Tab Investigates detailed partition and volume information of the selected disk. ##### Features - **Run Inspection**: Retrieves detailed volume information for the selected disk. - **Export Free Space CSV**: Outputs the free space ranges as a CSV file. ##### Displayed Information โ€” Summary - Disk model, size (GiB + total sectors), number of volumes, list of file systems - Total space, free space, used space (bytes / clusters / sectors / ratio) - Additional info: Transport protocol, BusHint - Number of free fragments, Free sectors, Free GiB, Last used LBA ##### Displayed Information โ€” Volume Grid | Column | Description | | :--- | :--- | | Drive | Drive letter | | FS | File system (NTFS, FAT32, exFAT, etc.) | | Partition# | Partition number | | Style | Partition style (GPT / MBR) | | Type | Partition type | | Sec/Cluster | Sectors per cluster | | Total Sectors | Total number of sectors | | Size (GB) | Capacity (GB) | | Free Sectors | Free sectors count (Ratio %) | | Used Sectors | Used sectors count (Ratio %) | | Physical Start Sector | Physical starting sector | | Partition Length Sectors | Partition length (sectors) | | Cluster Bytes | Cluster size (bytes) | --- #### 8. Real Test Tab Verifies whether TRIM is actually functioning on the SSD through a file write/delete/verify process. {% hint style="info" %} **Note**: It is **not mandatory** to run the Real Test for standard TRIM usage. This feature is intended to verify if the USB bridge controller and this software properly execute TRIM on your specific SSD. If verification is needed, running it **once** is sufficient. The time required depends on the disk capacity and USB speed, taking approximately **6 hours** for a 1TB SSD. {% endhint %} ##### 8.1 Test Procedure (STEP 1~4) | Step | Action | Description | | :--- | :--- | :--- | | **STEP 1** | TRIM + Fill Files | First executes Free-space TRIM, then fills 1/3 of the remaining capacity with 500MB random files. | | **STEP 2** | Delete + TRIM | Deletes 1 in every 10 files โ†’ Flushes โ†’ Extracts Free Space CSV โ†’ Performs Free-space TRIM. | | **STEP 3** | Additional Fill | Fills the remaining capacity with 1GB random files (leaving about 1GB of free space). | | **STEP 4** | Integrity Verify | Verifies the CRC integrity of the 500MB files. | > In STEP 1, TRIM is executed before creating files to ensure the SSD starts the test in an optimal write performance state. ##### 8.2 Options | Option | Description | | :--- | :--- | | **Start Step** | The step number to start from (1~4). | | **End Step** | The step number to end at (1~4). | | **Target Drive** | Select the logical drive to use for the Real Test. | | **Wait on Drop** | Wait time (minutes) if write speed drops below 50% of the moving average. Set to 0 to disable. | ##### 8.3 Sudden Speed Drop Detection If the SSD cache is exhausted during writing, the speed may drop sharply. This feature: - Tracks the average speed based on an **EMA (Exponential Moving Average)**. - If the 2-second interval speed drops to **50% or less** of the moving average, it pauses for the set duration. - Speed is recorded as 0 while waiting, and automatically resumes afterward. ##### 8.4 Buttons | Button | Function | | :--- | :--- | | **Start** | Begins the entire test (STEP 1~4). A confirmation popup appears before starting. | | **Verify Only** | Only verifies the CRC integrity of existing files (corresponds to STEP 4). | | **Stop** | Immediately halts the ongoing test. | | **Delete Test Folder** | Deletes the temporary files/folders used for the test. | | **Export FileMap** | Exports the physical location map of the test files as a CSV. | | **Speed Chart** | Displays the time-series write speed chart of the last test (enabled after completion). | | **Clear Log** | Clears the log and redisplays the instructional message. | ##### 8.5 Write Speed Chart Clicking the **Speed Chart** button after a test is completed displays a time-series line chart: - X-axis: Elapsed time, Y-axis: Write speed (MB/s). - Speed data measured at 2-second intervals is shown as a blue line. - Dotted lines mark the boundaries of each STEP, allowing you to see performance changes per stage at a glance. - Waiting periods are recorded as 0 speed. - You can save the data as a CSV file using the **Save CSV** button. ##### 8.6 Status Display - **Status**: The currently executing step. - **Speed**: Real-time write speed (2-second interval average, MB/s). - **Elapsed**: Total elapsed time (updates every second). - **Step**: Elapsed time for the current step (updates every second). ##### 8.7 TRIM Result Log After each TRIM execution, the results are output to the log: ```text TRIM completed: batches=32/32, sectors=63,560,392 โ† Success TRIM failed: success=0, failed=32, planned=32 โ† Failure ``` ##### 8.8 Test Completion Upon completion, a success/failure popup appears: - **Success**: If all file CRCs match, it means TRIM is functioning correctly. - **Failure**: If a CRC mismatch occurs, there may be data corruption after TRIM. - **Cancelled**: If the user pressed the Stop button. --- #### 9. Multilingual Support You can change the language from the dropdown in the top right corner of the app. The OS language is automatically detected and set as the default. | Language | Display Name | | :--- | :--- | | Korean | ํ•œ๊ตญ์–ด | | English | English | | Japanese | ๆ—ฅๆœฌ่ชž | | Simplified Chinese | ็ฎ€ไฝ“ไธญๆ–‡ | | Spanish | Espaรฑol | | German | Deutsch | | French | Franรงais | | Russian | ะ ัƒััะบะธะน | --- #### 10. Frequently Asked Questions (FAQ)
Q: TRIM fails on a UASP device. On UASP devices, the tool automatically tries DSM TRIM โ†’ SCSI UNMAP โ†’ ATA Pass-Through in order. If all fail: 1. Try unplugging the device and reconnecting it directly. 2. Try changing the USB hub or cable. 3. Some USB bridges simply do not support TRIM commands.
Q: It says ATA Pass-Through is not supported. This happens when the USB bridge controller does not support ATA Pass-Through. However, if connected via UASP, TRIM is transmitted via SCSI UNMAP, so TRIM might still be possible even without ATA Pass-Through.
Q: It displays TRIM:NO. This means ATA Pass-Through is supported, but the SSD itself does not support TRIM. This happens with very old SSDs or traditional HDDs. TRIM is a command exclusively for SSDs.
Q: Free Space Only TRIM fails with a "No free-space bitmap ranges available" error. This occurs when the file system bitmap cannot be read. Ensure that you are using a supported file system (NTFS, FAT32, exFAT).
Q: The disk is not recognized after a Full Device TRIM. After a full TRIM, the partition table may be deleted. If you set the **Init after TRIM** option to GPT or MBR, it will automatically initialize the disk afterward.
Q: I am getting an error even though I ran it with Administrator privileges. Some antivirus software may block SCSI Pass-Through commands. Try temporarily disabling your antivirus and run it again.
Q: [WARN] DSM TRIM winerr=1 appears in the log. This is normal behavior. The USB bridge does not support Windows DSM TRIM, so it automatically fell back to SCSI UNMAP. As long as the final TRIM is successful, there is no issue.
Q: [WARN] SCSI UNMAP winerr=1117 appears in the log. This is normal behavior. The bridge rejected multiple descriptors, so it automatically switched to single-descriptor mode. As long as the final TRIM is successful, there is no issue.
Q: The Speed Chart button is disabled. Speed data is only collected after running the Real Test at least once. The button becomes enabled after a test is completed.
--- #### 11. Troubleshooting | Symptom | Cause | Solution | | :--- | :--- | :--- | | **Disk does not appear in list** | Bad USB cable or not connected | Check USB connection and refresh | | **"Admin Privileges Required" error** | Ran with standard user rights | Right-click app โ†’ "Run as Administrator" | | **APT:N/A displayed** | USB bridge lacks ATA command support | Handled automatically via SCSI UNMAP if UASP | | **TRIM batch failed** | Timeout or bridge compatibility issue | Increase timeout value, decrease batch size | | **DSM TRIM winerr=5** | Attempted while volume is dismounted | Automatic fallback will handle it (Normal) | | **SCSI UNMAP winerr=5** | Attempted while volume is mounted | Retries automatically after Lock/Dismount (Normal) | | **CRC mismatch in Real Test** | Data area corrupted after TRIM | Possible bridge/SSD compatibility issue | | **Wait on Drop doesn't trigger** | Wait time is set to 0 | Set the wait on drop value to 1 or higher | | **CSV/Log files are not created** | Ran on a read-only drive | Run from a writable drive | --- #### 12. License The IODD TRIM Tool is **Freeware**. - Anyone can use it for free, and it may be freely copied and distributed. - This software is provided "AS IS". - Commercial sales are strictly prohibited. - The developer assumes no responsibility for any damages, including data loss, resulting from the use of this software. - Reverse engineering, decompiling, and source code extraction are prohibited. Copyright (c) 2025-2026 IODD. All rights reserved. --- *This manual is based on IODD TRIM Tool v0.2.0.4.* --- ## 15. Troubleshooting --- ### 15.1 ๐Ÿ› ๏ธ Booting Error If your computer fails to boot from the IODD, please follow this troubleshooting checklist to identify and resolve the issue. ### ๐Ÿ“‹ Troubleshooting Checklist {% hint style="info" %} **ISO & Media Validation** * **Verify Bootability**: Ensure that the ISO file you are using is a bootable image. Non-bootable data ISOs will not trigger a boot sequence. * **Hardware Comparison**: If a bootable ISO fails, try testing it with a physical USB DVD-ROM to confirm if the issue is with the ISO file itself or the system's compatibility. {% endhint %} {% hint style="warning" %} **Drive & System Configuration** * **Multi-LUN Support**: Some older PCs do not support multiple Logical Unit Numbers (LUN). If the IODD is not recognized, configure it as a single drive in the **Mode Configuration** settings. * **Internal DVD Conflict**: If your laptop has an internal DVD-ROM, it may conflict with the IODD. Disable the internal drive in the BIOS settings or physically remove it if necessary. {% endhint %} {% hint style="danger" %} **Power Supply Issues** The IODD is a high-performance, bus-powered USB device. If your computer's USB port provides unstable power, the boot process may fail. * **Solution**: Use a **USB Y-Cable** to draw additional power from a second USB port. {% endhint %} {% hint style="warning" %} **OS & Platform Compatibility** Newer hardware platforms may lack the necessary drivers for older operating systems. * **Example**: You cannot install a genuine Windows 7 on the **Skylake** (or newer) platform using a USB DVD-ROM device without injecting proper USB 3.0/XHCI drivers into the ISO. {% endhint %} --- ### Advanced Hardware Check (Linux/macOS) You can check if the IODD is correctly being recognized as a bootable optical or mass storage device via the terminal: ```bash # On macOS, check if the disk is listed as external and bootable $ diskutil list # On Linux, check the device type and partitions $ lsblk ``` --- ### 15.2 ๐Ÿ’พ IODD Drive Initialization Before using your IODD, the internal drive must be initialized and formatted correctly. Selecting the right file system ensures that your virtual drives and ISO files work perfectly across different platforms. ### 1. Initialize the Disk Connect the IODD to your PC and initialize the drive using your operating system's disk management tool. * **Modern Models (ST, MINI PRO, LK100):** Supports both **MBR** and **GPT**. GPT is recommended for drives over 2TB. * **Legacy Models (2531, 2541, MINI Legacy):** Supports **MBR only**. GPT is **not supported** (Legacy models have a hardware limit that only recognizes the first **2TB** of a drive). #### Partition Styles: * **MBR (Master Boot Record)**: Best for maximum compatibility with legacy BIOS systems. Required for all legacy IODD models. * **GPT (GUID Partition Table)**: Recommended for modern UEFI-based systems and drives larger than 2TB (Modern models only). {% hint style="info" %} **Fixing Initialization Failures (MBR โ†’ GPT โ†’ MBR Trick)** If the drive fails to initialize or displays errors, try this cycle: 1. Connect the HDD/SSD directly to a PC (if possible) or via IODD. 2. Initialize it as **GPT**. 3. Then, immediately re-initialize it back to **MBR**. This process can often clear corrupted partition table metadata that simple formatting cannot fix. {% endhint %} {% hint style="danger" %} **For Encryption Users** If you plan to use AES256 encryption, you must first **[Set a New 2nd Password]** via the Admin menu. After setting the password, you **must repeat the initialization process**, as the hardware encryption changes the disk structure. * Related topic: 2nd Password Setup Guide {% endhint %} --- ### 2. Formatting Partitions (Recommended File Systems) For the best experience with IODD, we highly recommend using either **NTFS** or **exFAT**. Both support large files (over 4GB) and are fully compatible with IODD tools. | File System | Best For | Key Advantages | | :--- | :--- | :--- | | **NTFS** | **Windows-centric environments** | Highly stable, supports journaling (error recovery), and is the native Windows format. | | **exFAT** | **Cross-platform use (Mac/Win)** | Excellent compatibility between macOS and Windows without file size restrictions. | | **FAT32** | โŒ **Not Recommended** | **4GB file size limit** and **Incompatible with VHD Tool++**. | {% hint style="warning" %} **Comparison: NTFS vs. exFAT** * Both file systems are **fully supported by VHD Tool++** and IODD's virtual drive functions. * Choose **NTFS** if you primarily work on Windows and need robust data recovery features. * Choose **exFAT** if you frequently move the IODD between Windows and Mac computers. {% endhint %} --- ### 3. File Transfer and Safe Removal 1. **Copy Files**: Transfer your ISO, VHD, or document files to the IODD drive. 2. **Safely Remove**: This is **essential** for both NTFS and exFAT to prevent filesystem corruption. * Use the "Safely Remove Hardware" icon in your system tray before physical disconnection. --- ### 4. Reconnection and Refreshing After reconnecting the IODD, the screen should display your updated file list. {% hint style="info" %} **Manual Refresh (Force Scan)** If the file list on the IODD screen does not match what you copied: * **Modern Models (ST, MINI PRO, LK100):** **Hold the [4] key for 3 seconds**. This forces a re-scan and allows you to manually select the correct partition if multiple are present. * **Legacy Models (2531, 2541, MINI Legacy):** Manual partition selection via hotkey is **not supported**. * For **2541/MINI**, long-pressing **[4]** only rescans the current folder. * For **2531**, long-press **Jog Up** to rescan. {% endhint %} --- ### Technical Verification You can check the partition status and file system type using the following command: ```bash # On Windows (PowerShell), check partition and filesystem info $ Get-Volume | Where-Object {$_.DriveLetter -ne $null} | Select-Object DriveLetter, FileSystem, Size, HealthStatus ``` --- ### 15.3 ๐Ÿ“‘ Error Messages Reference ### ๐Ÿ’พ Partition & File System Errors **`"1st Partition: XX"`** / **`"Unsupported Partition"`** * **For 2541 / 2531 Models**: Check your firmware version (ending in **N** or **F**). * **N** version: Supports **NTFS** only. * **F** version: Supports **exFAT / FAT32** only. * **For ST400 / ST300 / MINI PRO**: Unified firmware supporting both MBR and GPT. **`"ChkDsk"`** / **`"gErr: xxx"`** (Legacy Only) * These are equivalent to the "Drive Error" or "Check HDD" messages on newer models. * **Solution**: Perform a **Disk Check (chkdsk)** on your PC to repair filesystem metadata. **`"Too Many Files"`** * The IODD supports a maximum of **32 files or subfolders** within a single folder. * **Solution**: Organize your files into nested subfolders. **`"Enc Ver Err ???"`** (2541 Only) * Encryption version mismatch (e.g., drive encrypted with 6.x firmware but device using 7.x). * **Solution**: Restore firmware to the matching version or re-initialize the drive (Back up data first!). {% hint style="info" %} **Multi-Partition Support** ST/MINI models can mount ISOs from any primary partition. **Hold the [4] key for 3 seconds** to manually select a different partition. {% endhint %} **`"ASSERT Fails ArrayOffset"`** * **Primary Cause**: This error typically occurs when the IODD is **unplugged without using "Safely Remove Hardware"** (Safe Ejection). Failure to eject safely can lead to corrupted filesystem metadata or unwritten cached data. * **First Action (Data Preservation)**: Connect the IODD to a PC and perform a **Disk Check (chkdsk)** to repair the metadata errors caused by improper disconnection. * **Second Action**: If the error persists, you must re-initialize the drive. Refer to Drive Initialization. {% hint style="danger" %} **Importance of Safe Removal** To prevent the "ASSERT" error, always use your operating system's **Safely Remove Hardware** or **Eject** function before physically disconnecting the USB cable. This is especially critical when using the **NTFS** file system. {% endhint %} --- ### ๐Ÿ›ก๏ธ Security & Access Errors **`"Not Match..."`** * The entered password does not match. * **Solution**: Ensure you are using the correct admin/user prefix. * **Admin**: `0` + `[Password]` (e.g., `01234`) * **User**: `1~4` + `[Password]` **`"No Extra Devices"`** * No virtual drives are active. * **Solution**: Use the Mode Configuration to enable VHD/ISO drives. --- ### โš™๏ธ Hardware & Performance Errors **`"Check HDD"`** / **`"Drive Error"`** * Communication failure with the internal drive. * **Causes**: Physical disk error or **Low Voltage** (unstable power). * **Solution**: Try a different USB port or a Y-cable for stable power. **`"DEFRAG"`** * The ISO/VHD file is too fragmented to load (Max 24 fragments for ISO; 0 for VHD). * **Solution**: Use defragmentation utilities like MyDefrag or Defraggler. --- ### ๐Ÿ–ฅ๏ธ LCD Status Message Table Below is a combined table of LCD status and error messages found across various IODD models (ST, MINI, 2541, 2531). | Message | Meaning / Action Required | Affected Models | | :--- | :--- | :--- | | **`"Please Wait"`** | Operation in progress. Wait for the message to disappear. | All | | **`"Plug Out / Disconnect"`** | Safely disconnect the device from the USB port. | All | | **`"Data Saving..."`** | Writing configuration or data to the internal drive. **Do not disconnect.** | All | | **`"Flash Update..."`** | Updating internal flash memory (Firmware/Font). **Do not disconnect.** | All | | **`"Reconnect USB"`** | Please disconnect and reconnect the USB cable. | Modern (ST/MINI PRO) | | **`"Replug USB..."`** | Connection error detected. Please disconnect and reconnect the USB cable. | 2541 | | **`"Check HDD"`** | Drive check required. A drive error has been detected. | All | | **`"1st partition"`** | Partition mismatch with firmware. The firmware version (NTFS/FAT32/exFAT) does not match the first partition's file system. | All | | **`"bad or N/S HDD"`** | Unsupported or faulty drive. The device cannot read the internal drive (check cable or HDD). | All | | **`"NO _ISO Folder"`** | The required directory named `_ISO` was not found in the root. | All | | **`"NO - DISC"`** | No compatible files or subfolders were detected inside the `_ISO` folder. | All | | **`"Disc Locked"`** | The operating system or an application has locked the virtual drive. | All | | **`"Already Hit"`** | The selected file is already mounted as a virtual drive. | All | | **`"Input Limit..."`** | PIN retry limit exceeded. Reconnect the device to try again. | 2541 / MINI | | **`"Not Match..."`** | The entered PIN does not match the stored credentials. | 2541 / MINI | | **`"NO DEVICE !!!"`** | Internal HDD/SSD not detected. Check the physical SATA connection. | All | | **`"HDD ERROR !!!"`** | Critical drive read error or hardware failure. | All | | **`"HDD WARNING ???"`** | Drive health warning. Bad sectors detected. **Back up data immediately.** | All | | **`"Enc Ver Err ???"`** | Encryption version mismatch (e.g., 6.x vs 7.x firmware). | 2541 | | **`"Too Many Files"`** | Maximum of 32 files/subfolders per folder exceeded. | All | | **`"vDISK Limit"`** | Maximum number of virtual drives (LUNs) exceeded. | 2531 / 2541 | | **`"Product Mismatch"`** | Incorrect firmware model selected during update. | All | | **`"DEFRAG"`** | File fragmentation detected (Max 24 fragments for ISO, 0 for VHD). | All | | **`"No Use Dynamic"`** | Dynamic VHD files are not supported. Only fixed-size VHD is allowed. | All | | **`"No Use Sparse"`** | Sparse files are not supported by the IODD system. | All | #### ๐Ÿ“ "Excep_code" Error Reference Some newer models (ST/MINI PRO) may display a red popup with an **`"Excep_code"`**. Follow the specific instructions in the message: | Exception Code | Meaning / Action Required | | :--- | :--- | | **`"Excep_code - Please Reconnect"`** | Often caused by poor connection or insufficient power. Try a different USB port. | | **`"Excep_code - Please Check Disk"`** | File system corruption detected. Run `chkdsk X: /f` on your PC. | | **`"Excep_code - Please update firmware"`** | Critical system error. Re-flash the firmware using the Firmware Update Guide. | --- ### Terminal Diagnostics (Windows) If you encounter the "ASSERT" error, run the following command in Command Prompt (Admin) to repair the filesystem: ```bash # Replace 'X:' with your IODD drive letter chkdsk X: /f ``` --- ### 15.4 โ“ FAQ (Frequently Asked Questions) ### ๐Ÿ” Password & Security
I entered the correct password, but it says "Incorrect." You must enter the user identification prefix before your password. * **Admin**: Enter **0** + [Your Password]. (e.g., if your password is '1234', enter '01234') * **Users**: Enter **1~4** + [Your Password]. Related topic: Encryption Guide
I forgot my password. Can I recover my data? **No.** It is absolutely impossible for anyone, including the manufacturer, to recover or find a forgotten password. The data is hardware-encrypted.
I forgot my password. How can I reuse the IODD? The only way to reuse the device is to **Reset Password**. All existing data will be permanently lost during this process. * 2541 : 2541 Reset Password * MINI : MINI Reset Password * ST400, LK100 : ST400 Reset Password
After entering my password, the screen shows "PLEASE WAIT" and then stops. For **ST300, ST400, MINI PRO, and MINI** models, if the device stops responding on the **PLEASE WAIT** screen after password entry, use the following procedure to re-flash the firmware: Hold **`9`** and **`Enter`** while connecting the USB cable. Continue holding both keys for **7 seconds** to force a re-flash. Refer to the Firmware Update Guide for the updater download and full procedure.
--- ### ๐Ÿ’ป Booting & Virtual Drive
The IODD will not boot from the PC. Please refer to the Booting Error Guide for detailed troubleshooting steps.
When I mount a VHD, the mode changes to CD-MODE automatically. This is often caused by the filename or default settings. Legacy models (2531/2541) use filename extensions like `.VHD` (Fixed) and `.RMD` (Removable) to control mode behavior. Refer to the VHD Advanced Naming Guide.
How can I unmount virtual drives? * **ST/MINI PRO**: Navigate to the file and press the select key, or use the **[7]** eject hotkey. * **Legacy**: Press and hold **[7]** for 3 seconds, or use the **Menu -> Advanced -> Umount VHDD** option.
--- ### ๐Ÿ› ๏ธ Hardware & Maintenance
My SSD write speed has become noticeably slow. If your SSD's write speed has degraded, performing a **TRIM** operation will greatly improve performance. * **Why TRIM?**: USB-connected external SSDs typically do not receive automatic TRIM commands from Windows. Running TRIM manually clears unused data blocks, preventing speed degradation and extending the SSD's lifespan. * **How to fix**: Use the **IODD TRIM Tool** to perform a "Free Space TRIM" (safely optimizes without losing data) or a "Full TRIM". * **SLC Cache Tip**: Most modern SSDs use an "SLC Cache" for fast initial writes. Once the cache is full, speeds drop significantly. After a large file transfer, **leave the IODD connected to USB power for about 10 minutes** before unplugging. This gives the SSD controller enough idle time to flush the cache and reorganize data, ensuring fast speeds for your next use.
The LCD only displays "IODD [Model Name]" and does not progress. This indicates a system hang or corrupted firmware. Please perform a Firmware Update or use the **Emergency Recovery Procedure** (Section 15.2 in the Appendix).
The touch sensitivity of the buttons is poor (2541). For older units, placing a thin piece of paper or plastic film between the internal drive and the front body (not the cover) can improve responsiveness.
The firmware update fails repeatedly. Ensure you are using a stable USB port (rear of the PC) and have only one IODD connected. Refer to the Firmware Update Guide.
--- ### 15.5 ๐Ÿ†™ Firmware Update {% hint style="info" %} **Current Firmware Status** Currently sold products use the latest firmware, so no additional update is required. If there is a new update after **May 29, 2024**, we will announce it here. {% endhint %} Keeping your IODD firmware up to date ensures the best compatibility with the latest hardware and fixes known bugs. Please read the version-specific warnings carefully before proceeding. ### ๐Ÿ“ข Release Notes {% hint style="info" %} **Version 0.8.1 Highlights** * **ST300**: Fixed slow reboot issues after mode changes and resolved Write Protect toggle bugs. * **ST400 / LK100**: Added a dedicated password reset feature. * ST400/LK100/MINI PRO Password Reset Guide {% endhint %} {% hint style="info" %} **Version 0.8.0.1 Update Log** * **SECURE 2.0 โžก 2.5**: Improved encryption hardware logic. * **LUN Fix**: Resolved an issue where setup could proceed without a Single LUN in mode settings. * **4TB Support**: Fixed errors for 4TB drives (NTFS/exFAT). * **NTFS Clusters**: Supports up to 62KB clusters. * Code optimization and general compatibility improvements. {% endhint %} {% hint style="danger" %} **Critical Warning for Encryption Users (ST400 / LK100)** Passwords created in **Version 0.7 or earlier** are NOT compatible with **Version 0.8 or later** due to the encryption logic upgrade (Secure 2.5). **You MUST back up all data and disable encryption before updating.** Failure to do so will result in total data loss. {% endhint %} --- ### ๐Ÿ› ๏ธ How to Update **Requirements:** Windows PC, USB Port, and a high-quality USB cable. {% hint style="info" %} **๐ŸŽฅ Video Guide** If you prefer a visual walkthrough, check out our **Firmware Update Tutorial Video** on YouTube. {% endhint %} {% hint style="warning" %} **Pre-Update Checklist** * **Single Connection**: Connect only **one** IODD device to your PC at a time. * **Model Match**: Ensure you have downloaded the exact firmware matching your IODD model. If you flash the wrong firmware, simply retry with the correct version. {% endhint %} 1. **Download** the latest firmware file from the Official Directory. 2. **Uncompress** the ZIP file to a local folder. **Do not run the updater directly inside the ZIP file.** 3. **Run the EXE** file as Administrator. 4. If the message **`"Device is Detected"`** appears, click the **Update** button. **If the device is not detected:** * Try a different USB port or cable. * **Manual Recovery Mode**: Hold **[9] + [Enter]** while connecting the IODD to your PC. Release the buttons once connected and run the updater again. **Finalizing the Update:** Once the transfer is complete, click **Exit**. Reconnect the IODD and **wait for 2โ€“3 minutes** for the internal processing to finish. {% hint style="warning" %} **Do NOT disconnect the IODD while the LCD is blinking.** This indicates the internal firmware is being written to flash memory. Interrupting this can leave the device unable to boot normally and may require a recovery/force-update procedure. {% endhint %} --- ### ๐Ÿ”„ Troubleshooting: Version Not Changing (ST300 / ST300 / LK100 / MINI PRO / MINI) If your version number remains the same even after a successful PC transfer, follow this mandatory "Force Update" procedure: 1. Run the firmware update on your PC. 2. After the transmission is finished, the IODD will reconnect and show a **white screen**. 3. **Force Mode**: Disconnect the IODD. Press and hold **[9] + [Enter]** for at least **6 seconds** while reconnecting it to the PC. 4. The firmware update will continue internally. 5. Reconnect once more and verify the version in the Information menu. --- ### 15.6 ๐Ÿ”“ ST400 / LK100 / MINI PRO: Password Reset These models share the same keypad interface and menu structure. If you have forgotten your password, use one of the three methods below. {% hint style="warning" %} **Total Data Erasure** All methods listed below will **permanently delete all data** on the drive. Recovery is impossible. Proceed only if you have a backup or do not need the existing data. {% endhint %} --- ### Method 1: Using IODD Admin Manager (Recommended) This is the simplest method and does not require disassembling the device or manual keypad cycles. 1. Connect your IODD to a Windows PC. 2. Launch the **IODD Admin Manager** application. 3. Navigate to the **Emergency** tab. 4. Follow the prompts to complete the **Confirmation Procedure** (Click counting). 5. Execute **Erase All Data**. * This will wipe the password, encryption keys, and all stored data, returning the device to its factory state. --- ### Method 2: Keypad Sequence (The "1 to 0" Cycle) *Supported Models: ST400 / LK100 / MINI PRO* If you don't have access to a PC with Admin Manager, you can force a hardware reset via the keypad. 1. Power on the device to the **Password Input Screen**. 2. Enter the sequence: `1` โ†’ `2` โ†’ `3` โ†’ `4` โ†’ `5` โ†’ `6` โ†’ `7` โ†’ `8` โ†’ `9` โ†’ `0`. 3. **Repeat this entire 10-digit cycle 15 times.** 4. If you make a single mistake during the 15 cycles, you must restart from the very beginning. 5. **Success**: When the screen displays **`"1st Partition"`** or **`"No Supported Partition"`**, the encryption has been successfully wiped. --- ### Method 3: Physical Wipe (Requires Disassembly) This method bypasses the keypad cycles by connecting the internal drive directly to a PC. 1. **Disassemble**: Open the case and remove the internal HDD/SSD. 2. **Connect**: Plug the drive into a PC via a SATA-to-USB adapter or internal SATA port. 3. **The "GPT-First" Principle**: * Encryption metadata is stored in the GPT area. You must initialize the disk as **GPT** first to clear the lock. * After the GPT wipe, you can re-initialize it to your preferred style (MBR or GPT). 4. **Format**: Create at least one partition and format it as **NTFS** or **exFAT**. #### **Terminal Command (Windows Diskpart)** ```bash # Run Command Prompt as Administrator $ diskpart $ list disk $ select disk N # Check the size to select the correct IODD disk! $ clean # Force wipe encryption by converting to GPT $ convert gpt # Optional: Re-convert to MBR if needed $ convert mbr $ create partition primary $ format fs=ntfs quick # or fs=exfat quick $ exit ``` --- ### ๐Ÿ“ Summary of Methods | Feature | 1. Admin Manager | 2. Keypad Cycle | 3. Physical Wipe | | :--- | :--- | :--- | :--- | | **Tools Needed** | PC + Software | None | Tools + SATA Adapter | | **Effort** | Very Low | High (150+ presses) | Medium (Disassembly) | | **Best For** | Most Users | No PC Access | Advanced Users | {% hint style="warning" %} **Post-Reset Setup** After the wipe, the device is in a factory-new state. You must set a new password and perform Drive Initialization before use. {% endhint %} {% hint style="danger" %} **Safe Removal** To prevent filesystem corruption (ASSERT errors) in the future, always use the OS **Safely Remove Hardware** function. {% endhint %} --- ### 15.7 ๐Ÿ”“ iodd MINI: Password Reset Procedures If you have forgotten your password for the iodd MINI, you must initialize the drive to reuse the device. There are two primary ways to achieve this. {% hint style="warning" %} **Total Data Loss** Both methods will **permanently erase all data** on the internal SSD. Data recovery is impossible once the process begins. {% endhint %} --- ### Method 1: Password Reset via Firmware (No Disassembly) This method allows you to reset the password using specialized firmware and hardware button inputs without opening the device. #### **Step 1: Install Reset Firmware** 1. Download the **Reset Firmware**: iodd MINI Password Reset Firmware 2. Run `iodd_firm_upd-0.1.0.11-Del-Password.exe` and complete the update. #### **Step 2: Execute Deletion** 1. Reconnect the iodd MINI to your PC. 2. On the password input screen, **press the [Menu] button repeatedly (at least 300 times)**. 3. Wait for the **`"Password is deleted"`** message. #### **Step 3: Restore Standard Firmware (Mandatory)** 1. Download the **Standard Firmware**: iodd MINI Standard Firmware 2. Run `iodd_firm_upd-0.1.0.13.exe` to return the device to its normal state. --- ### Method 2: Manual Initialization (Requires Disassembly) This method involves connecting the internal SSD directly to a PC to wipe the encryption metadata. This is a "Two-Step Wipe" process. #### **Step 1: Disassemble and Connect** 1. Open the MINI case and remove the internal SSD. 2. Connect the SSD directly to a Windows PC via a SATA/M.2 adapter. #### **Step 2: Initialize via GPT โ†’ MBR (Diskpart Recommended)** The encryption data is stored in the GPT area. You must initialize as GPT first to ensure the lock is cleared. ```bash # Run Command Prompt as Administrator $ diskpart $ list disk $ select disk N # CAUTION: Ensure N is the correct MINI disk $ clean # Step 1: Wipe encryption data by converting to GPT $ convert gpt # Step 2: Re-convert to MBR (Preferred for 2541/Compatibility) $ convert mbr # Step 3: Create partition and format $ create partition primary $ format fs=ntfs quick # You may also use 'fs=exfat quick' $ assign $ exit ``` --- ### ๐Ÿ“ Comparison & Summary | Feature | Method 1 (Firmware) | Method 2 (Disassembly) | | :--- | :--- | :--- | | **Effort** | Low (No tools needed) | High (Requires disassembly) | | **Complexity** | 300+ button clicks | Command line (Diskpart) | | **Success Rate** | Very High | Absolute (Hardware reset) | | **Admin Manager** | Not Supported | Not Supported | {% hint style="warning" %} **Post-Reset Setup** After either method is complete, reassemble the device (if needed) and reconnect it. You will be prompted to perform the **Initial Setup** and set a new password as if it were a brand-new device. {% endhint %} {% hint style="danger" %} **Always use "Safely Remove Hardware"** after copying files to prevent the "ASSERT Fails ArrayOffset" error in the future. {% endhint %} --- ### 15.8 ๐Ÿ”“ IODD 2541: Password Reset (Cross-Platform) If the password is lost, you must bypass the IODD controller and connect the internal drive directly to a computer to wipe it. **This will erase all data.** {% hint style="danger" %} **Hardware Support Notice** IODD Admin Manager does not support the 2541 model. Manual initialization is the only solution to reset a forgotten password. {% endhint %} ### 1. Hardware Preparation 1. Disconnect the IODD 2541. 2. Remove the internal 2.5" HDD/SSD from the 2541 case. 3. Connect the drive to your computer using a SATA-to-USB adapter or an internal SATA port. --- ### 2. Initialization by Operating System #### **Option A: Windows (GUI)** 1. Open **Disk Management** (`diskmgmt.msc`). 2. Delete all existing volumes on the target disk. 3. Right-click the Disk Name (left panel) and select **Initialize Disk** as **GPT**. 4. Right-click again and select **Convert to MBR Disk**. (2541 requires **MBR**). 5. Create a **New Simple Volume** formatted as **NTFS** or **exFAT**. #### **Option B: macOS (Terminal)** On macOS, perform a two-step wipe to ensure all encrypted security metadata is removed: ```bash # 1. List all disks to find the IODD drive identifier (e.g., /dev/disk4) $ diskutil list # 2. Step 1: Initialize as GPT first to clear metadata # Replace 'diskX' with your actual disk number! $ diskutil eraseDisk ExFAT TEMP GPT /dev/diskX # 3. Step 2: Re-initialize as MBR (Required for 2541) $ diskutil eraseDisk ExFAT IODD MBR /dev/diskX ``` #### **Option C: Linux (Terminal)** ```bash # 1. Identify the drive (e.g., /dev/sdb) $ lsblk # 2. Wipe and create GPT label first $ sudo parted /dev/sdX mklabel gpt # 3. Finalize with MBR (msdos) label $ sudo parted /dev/sdX mklabel msdos # 4. Format the partition $ sudo mkfs.exfat /dev/sdX1 ``` --- ### 3. Reassembly & Verification 1. Place the drive back into the IODD 2541 case. 2. Connect it to your PC. The IODD will now act as a "New" device, prompting you to set a fresh password. {% hint style="warning" %} **Final Checklist for 2541** * **Partition Style**: The final state must be **MBR**. * **File System**: **NTFS** or **exFAT** is highly recommended. * **Safe Removal**: Always use "Safe Eject" to prevent the **`"ASSERT Fails ArrayOffset"`** error. {% endhint %} --- ## 16. Wiki Archive The wiki material is retained here as a compact product reference. Repeated usage procedures, virtual drive rules, error handling, FAQs, and firmware update steps are consolidated into shared reference sections so each model entry can focus on model-specific facts. --- ### 16.1 Common Product Capabilities Most IODD products combine an internal storage drive with virtual media features. Depending on the model, the device can expose ISO optical media, fixed VHD/VMDK disks, removable RMD media, floppy images, and the internal physical drive at the same time. | Capability | Meaning | Model Notes | | :--- | :--- | :--- | | Virtual ODD | Mounts ISO images as a USB optical drive for OS installation or boot media | Supported by ST300, ST400, 2531, 2541, MINI, MINI PRO | | Virtual HDD / VHD | Mounts fixed-size VHD or VMDK images as USB disks | Supported by ST300, ST400, 2531, 2541, MINI, MINI PRO | | Virtual RMD | Mounts removable virtual disks | Legacy filename extension is `.RMD`; modern models use the virtual drive menu | | Virtual FDD | Mounts IMA floppy images; IMG, BIF, or VFD should be renamed to `.IMA` for compatibility | Primarily documented for legacy workflows | | Multi-LUN | Exposes multiple USB logical units at the same time | Modern ST/MINI PRO family supports up to 3 VHDs, 1 ODD, and 1 physical HDD; 2531/2541 support up to 4 virtual drives, 1 ODD, and 1 physical HDD | | Write Protection | Makes a selected disk or device read-only | Key `5` toggles write protection on modern keypad models; legacy models also support filename and hotkey based behavior | | Safe Removal | Stops device access before unplugging | Always use OS safe removal/eject to prevent filesystem corruption and `ASSERT Fails ArrayOffset` errors | | Loading State Retention | Remembers selected/mounted media after reconnect | Automatic on newer firmware; older legacy firmware may require power-down or save actions | | S.M.A.R.T. / Information | Shows disk health, model, serial, firmware, USB speed, and voltage | Low or unstable USB voltage can cause incorrect readings or disk communication errors | --- ### 16.2 Model Matrix | Model | Controls | Internal Drive | Encryption | Virtual Drive Capacity | Key Limits / Notes | | :--- | :--- | :--- | :--- | :--- | :--- | | IODD 2531 | 3-way jog dial plus Back/Up button | 2.5-inch SATA HDD/SSD up to 9.5 mm; 7 mm drives need a spacer | No hardware encryption | Up to 4 virtual drives, 1 ODD, 1 physical HDD | Shares ZM-VE300 architecture; MBR-oriented virtual drive workflows; first 2 TB limit for virtual drive partition use | | IODD 2541 | 12 touch keys | 2.5-inch SATA HDD/SSD up to 9.5 mm | AES256 XTS, 4-15 digit PIN | Up to 4 virtual drives, 1 ODD, 1 physical HDD | Based on ZM-VE400 architecture; 6x/7x firmware encryption families are not interchangeable without backup/reinitialization | | IODD MINI Legacy | 12 tactile keys | M.2 SATA 2242 SSD | AES256 XTS, 4-15 digit PIN | Up to 3 virtual drives, 1 ODD, 1 physical HDD | Micro-B USB 3.0; legacy password reset uses reset firmware workflow | | IODD MINI PRO | Tactile keypad | M.2 SATA 2280 SSD | AES256 XTS, 4-38 digit passwords, 2nd Password support | Up to 3 VHDs, 1 ODD, 1 physical HDD | Compatible encryption family with ST400 and LK100; supports Admin Manager and Duress PIN on firmware 82 or later | | IODD ST300 | Tactile keypad | 2.5-inch 7 mm SATA HDD/SSD | Not supported | Up to 3 VHDs, 1 ODD, 1 physical HDD | Modern color LCD and Type-C interface; virtual drive focused model | | IODD ST400 | Tactile keypad | 2.5-inch 7 mm SATA HDD/SSD | AES256 XTS, 4-38 digit passwords, 2nd Password support | Up to 3 VHDs, 1 ODD, 1 physical HDD | Compatible encryption family with MINI PRO and LK100; supports Admin Manager and Duress PIN on firmware 82 or later | | LK100 | Tactile keypad | 2.5-inch 7 mm SATA HDD/SSD | AES256 XTS, 4-38 digit passwords, 2nd Password support | No virtual ODD/VHD function | Encryption-focused model; compatible encryption family with ST400 and MINI PRO | --- ### 16.3 Model-Specific Notes #### IODD 2531 - Appearance assets in the original wiki include `Iodd2531-01.jpg`, `Iodd2531-03.jpg`, `Iodd2531-04.jpg`, and `Iodd2531-contents.png`. - Materials: aluminum and polycarbonate. - Controls: jog dial up/down/click plus Back/Up button. - Navigation: jog up/down browses files, jog click selects, Back/Up moves to the parent directory. - Long-press hotkeys: Jog Up refreshes/rescans files, Jog Down enters power-saving mode, Jog Center opens the menu, Back/Up detaches all virtual drives. - Startup keys: Jog Up starts CD-MODE, Jog Down starts HDD-MODE, Jog Center starts DUAL-MODE and resets loading state, Back starts write-protected mode. - Firmware note: firmware 1558 or higher saves loading state automatically; older versions require manual save through power-down behavior. - Partition/file-system note: legacy firmware may be separated into NTFS (`N`) and FAT/exFAT (`F`) branches. #### IODD 2541 - Appearance assets in the original wiki include `Iodd2541-01.jpg`, `Iodd2541-03.jpg`, `Iodd2541-04.jpg`, and `Iodd2541-contents.png`. - Controls: 12 touch keys. - Navigation: `2` and `8` browse, `5` selects a file, `6` selects while maintaining loading state on supported firmware, `4` moves to the parent directory. - Long-press hotkeys: `1` power down, `3` reboot, `4` rescan files, `7` detach all virtual drives, `0` temporarily disables write protection after reboot. - Firmware note: key `6` loading-state retention requires firmware 6(7)9-05 or higher. - Encryption note: 6x and 7x firmware families differ; changing between them requires data backup because encryption compatibility changes. - Recovery note: if the device fails to initialize or firmware update fails, open the back cover, hold the internal tact switch while connecting USB for about 7 seconds, release, and wait approximately 1 minute. - Touch sensitivity note: on older units, a thin plastic or paper sheet between the HDD and front body can improve key responsiveness. #### IODD MINI Legacy - Appearance assets in the original wiki include MINI product images and contents images. - Uses 12 tactile buttons and a Micro-B USB 3.0 connector. - Internal drive is M.2 SATA 2242. - Supports hardware AES256 XTS encryption with 4-15 digit password behavior. - Password reset is handled through a reset firmware procedure and results in data loss. - Legacy virtual drive workflows remain MBR-oriented and should respect the first 2 TB limit for virtual drive partition use. #### IODD MINI PRO - Appearance assets in the original wiki include MINI PRO product and contents images. - Internal drive is M.2 SATA 2280. - Uses the modern keypad/menu family with color LCD behavior. - Supports AES256 XTS, 2nd Password, Admin Manager, user management, and encrypted disk migration with ST400/LK100/MINI PRO compatible devices. - Supports Duress PIN with `vhd4.vhd` on firmware 82 or later. - Supports text viewer, bitmap viewer, standalone mode, modern error popups, and multi-LUN virtual drive operation. #### IODD ST300 - Appearance assets in the original wiki include ST300 product and contents images. - Internal drive is 2.5-inch 7 mm SATA HDD/SSD. - Does not support hardware encryption. - Supports modern virtual drive operation, ISO/VHD workflows, write protection, text viewer, bitmap viewer, standalone mode, and multi-LUN operation. #### IODD ST400 - Appearance assets in the original wiki include ST400 product and contents images. - Internal drive is 2.5-inch 7 mm SATA HDD/SSD. - Supports AES256 XTS, 2nd Password, Admin Manager, user management, and encrypted disk migration with ST400/LK100/MINI PRO compatible devices. - Supports Duress PIN with `vhd4.vhd` on firmware 82 or later. - Supports modern virtual drive operation, text viewer, bitmap viewer, standalone mode, modern error popups, and multi-LUN operation. --- ### 16.4 Shared Usage Reference #### Recommended Folder Layout Create a folder named `_ISO` in the root directory. Files and subfolders inside `_ISO` can contain ISO, VHD, RMD, IMA, and related images, but a single directory should not exceed 32 files or subfolders. ```text J:\ +-- _ISO | +-- ISO files | +-- IMA for floppy images | +-- RMD for removable virtual disks | +-- VHD for bootable virtual disks +-- User data folders ``` #### Virtual Optical Drive (ISO) - ISO files are mounted as a USB optical drive for OS installation and boot media. - If boot fails, verify that the ISO itself supports the target boot mode, especially UEFI. - Disable Secure Boot when an unsigned or incompatible boot image is blocked by firmware. - Use ODD Mode when a system is unstable with multi-LUN Dual Mode. - Fragmented ISO files may trigger `DEFRAG`; defragment or recopy the file so it is contiguous enough for the device. #### Virtual Hard Disk (VHD / VMDK) - Use fixed-size VHD files. Dynamic VHD, sparse files, and VHDX are not supported by the IODD virtual drive loader. - VHD files must be contiguous. VHD files generally require zero fragmentation; recreate or defragment the file if `DEFRAG` appears. - IODD also supports fixed-size VMDK files when used in the documented virtual disk workflow. - Bootable VHD workflows should use compatible partition style and boot files for the target computer. #### Virtual Removable Disk (RMD) - `.RMD` files mount as removable virtual media. - RMD is useful when software expects USB removable media instead of a fixed disk. - Legacy models distinguish `.VHD` as fixed media and `.RMD` as removable media. #### Legacy Filename Mode Tags For IODD 2531 and 2541 only, filenames can control the mount mode: | Filename Pattern | Behavior | | :--- | :--- | | `filename.VHD` or `filename.VMDK` | Mounts as fixed virtual disk | | `filename.RMD` | Mounts as removable media | | `filename&D.VHD` | Mounts in Dual Mode with the physical HDD write-protected | | `filename&DW.VHD` | Mounts in Dual Mode with the physical HDD write-enabled | These filename tags are not supported on ST400, LK100, MINI PRO, or newer modern models. --- ### 16.5 Shared Menu And Key Reference #### Modern Keypad Models - `2` / `8`: move up or down in lists. - `5` or Enter: select the highlighted item. - `4`: move back or to the parent folder. - Long-press `1`: refresh/rescan or power-related behavior depending on model context. - Long-press `3`: reboot or toggle relevant mode behavior. - Long-press `5`: toggle write protection for the selected drive where supported. - Long-press `7`: detach or unmount virtual drives. - Hold `5` or `M` while connecting USB to use standalone mode on supported modern models. #### Legacy 2531 Use jog dial up/down/click for navigation and the Back/Up button for parent navigation. Startup mode is selected by holding the jog direction or Back button while connecting USB. #### Legacy 2541 Use the numeric touch keys for navigation and long-press actions. There are no 2541 startup hotkeys; emergency reset uses the internal tact switch. --- ### 16.6 Shared Error And Status Reference | Message / Alias | Meaning | Action | | :--- | :--- | :--- | | `Please Wait` | Operation in progress | Wait until the message disappears | | `Plug Out` / `Disconnect` | Device is ready to disconnect | Remove the USB cable after OS safe removal | | `Data Saving...` | Configuration or state is being written | Do not disconnect | | `Flash Update...` | Firmware/font flash is being updated | Do not disconnect | | `Reconnect USB` / `Replug USB...` | USB reconnection is required | Disconnect and reconnect the cable | | `Check HDD` / `Drive Error` / `ChkDsk` / `gErr` | Disk or filesystem problem, sometimes caused by low voltage or unsafe removal | Use a stable USB port and run filesystem check on the PC | | `1st Partition` / `Unsupported Partition` | Partition or file system does not match firmware expectations | Check MBR/GPT and firmware file-system branch on legacy models | | `Too Many Files` | More than 32 files/subfolders in one folder | Move files into subfolders | | `DEFRAG` | ISO/VHD file is too fragmented | Recopy, recreate, or defragment the image file | | `No Use Dynamic` | Dynamic VHD is unsupported | Create a fixed-size VHD | | `No Use Sparse` | Sparse file is unsupported | Use a normal fixed-size image file | | `Enc Ver Err ???` | 2541 encryption firmware family mismatch | Restore matching firmware or back up and reinitialize | | `Input Limit...` | PIN retry limit exceeded | Reconnect device before retrying | | `Not Match...` | Password or user prefix does not match | Use `0` for admin or `1`-`4` for users before the password | | `Product Mismatch` | Wrong firmware model selected | Run the updater again with the correct model firmware | | `Excep_code - Please Reconnect` | Connection or power issue | Try another USB port/cable and ensure stable power | | `Excep_code - Please Check Disk` | Filesystem corruption detected | Run a disk check on the PC | | `Excep_code - Please update firmware` | Critical system error | Re-flash firmware using the firmware update procedure | | `ASSERT Fails ArrayOffset` | Usually caused by unsafe removal or corrupted filesystem metadata | Run filesystem check first; reinitialize only if repair fails | --- ### 16.7 Shared FAQ Reference #### The correct password is rejected. Check the login prefix. Administrator login uses `0` plus the admin password. User login uses the user number `1` through `4` plus that user's password. #### A forgotten password must be recovered. Encrypted data cannot be recovered without the password. Password reset or encryption removal procedures erase data. Always warn the user about permanent data loss before explaining reset steps. #### The PC cannot boot from ISO or VHD. Check boot mode, Secure Boot, whether the image supports UEFI or legacy BIOS, device mode, fragmentation, and whether the internal disk uses a compatible partition layout. #### The drive is slow. For SSDs, run the IODD TRIM Tool first where applicable, then check USB 3.x connection, power stability, free space, filesystem errors, cable quality, and hub power. #### The LCD only shows the model name or the system appears frozen. Perform a firmware update or use the model-specific emergency recovery procedure. For ST/MINI PRO force recovery, hold `9` and Enter while connecting USB for at least 7 seconds. For 2531/2541, use the internal tact switch procedure. #### Virtual drives will not unmount. Use the device detach/unmount hotkey or the menu. Modern keypad models commonly use long-press `7` for detach-all behavior; legacy models have model-specific detach controls. --- ### 16.8 VHD Tool++ User Manual Summary VHD Tool++ is a Windows utility for creating and managing fixed-size virtual disk images for IODD devices. It can create, convert, extend, defragment, upload, and write images to disk. | Function | Purpose | Notes | | :--- | :--- | :--- | | Create | Creates fixed-size VHD files directly on the IODD drive | Designed to avoid fragmentation | | Convert | Converts raw disk dump images to fixed-size VHD | Use compatible image sources | | Extend | Increases fixed-size VHD capacity | Preserve data only when the tool supports the workflow | | Defragment | Checks and defragments individual files | Important for ISO/VHD mounting | | Upload | Copies files while reducing fragmentation risk | Useful for large images | | Write To HDD | Sector-by-sector clone to a physical drive | Expert-only; erases existing target data | Legacy IODD 2531/2541 filename behavior is summarized in the shared usage reference above. Use VHD Tool++ v0.9.0.10 or later when preparing `vhd4.vhd` for Duress PIN workflows. --- ## 17. Appendix & Historical Reference ### 17.1 Corporate History & Patents #### **Company Timeline** * **1996**: Co-founded **CNS Co., Ltd.** * **2011**: Spun off as **CNS Korea**. * **2013**: Established **IODD Co., Ltd.** #### **Intellectual Property** * **Patent (2nd Password)**: "Device password setting for preventing duplication of encrypted devices." (Patent-2022-0021783). Supports 4-38 digit passwords. * **Patent (Virtual ODD)**: "Memory device recognizable as an optical disk drive and its driving method." (No. 0993935). Valid until September 9, 2028. --- ### 17.2 ๐Ÿ“œ Legacy Device Details (2531 / 2541 / MINI) The legacy models use different physical controls and firmware structures compared to the modern ST/MINI PRO series. #### **Hardware Characteristics** * **Modern Series (ST300/400, MINI PRO)**: Feature a color LCD (128x160 dots) and support **Multi-LUN** (Mount up to **3 VHDs**, **1 ODD**, and **1 Physical HDD** simultaneously for a total of 5 devices). * **Legacy Series (2531, 2541, MINI Legacy)**: Support up to **4 Virtual Drives**, **1 ODD**, and **1 Physical HDD** simultaneously. * **IODD 2531**: Uses a **3-way Jog Dial** (Up/Down/Click) and a side back button. Supports 2.5-inch SATA HDDs up to 9.5mm. It shares the same architecture as the **ZM-VE300**. **Material**: Aluminum and PC (Plastic). * **Tip**: If installing a thinner **7mm** drive in a 2531, a spacer is required for a secure fit. * **IODD 2541**: Uses **12 Touch Keys**. Based on the **ZM-VE400** architecture but with improved hardware. * **IODD MINI (Legacy)**: Uses **12 Tactile buttons** and a Micro-B USB 3.0 connector. Uses M.2 SATA **2242** (42mm) SSDs. * **Tip**: For older 2541 units with touch sensitivity issues, placing a thin sheet of plastic or paper between the HDD and the front body (not the cover) can improve responsiveness. #### **Additional Modern Features (ST/MINI PRO)** * **Bitmap File Viewer (Experimental)**: Supports viewing small bitmap images (under 128x160 resolution, **1/16/24-bit** color depth). * **Text Viewer**: Supports reading `.txt` files in UTF-16 (UCS-2 LE) and ASCII formats. * **Standalone Mode**: Allows users to configure settings or browse files using a USB power bank without connecting to a PC (Hold key **[5]** or **[M]** during connection). * **Admin/User Login**: When encryption is active, the first digit of the password entry identifies the user: **`0`** for Administrator, **`1`** through **`4`** for standard users. (e.g., if the admin password is `1234`, enter `01234`). #### **Legacy-Specific Features (2531 / 2541)** * **Force USB 3.0**: A menu option to force the device to maintain a USB 3.0 connection even in harsh conditions where it might otherwise downshift to USB 2.0. * **Instant Save**: Quickly saves the current configuration and loading state. * **Fixed/Removable filenames**: Use `.VHD` for fixed disks and `.RMD` for removable media (Legacy only). #### **Emergency Recovery Procedures** | Device Type | Procedure | Description | | :--- | :--- | :--- | | **ST / MINI PRO** | **Force Recovery** | Hold **[9] + [Enter]** for 7 seconds while connecting. Re-flashes current firmware. | | **2541 / 2531** | **Tact Switch** | Open back cover, hold internal tact switch for 7s while connecting. | #### **Emergency Reset For 2541 (Tact Switch)** If the device fails to initialize or becomes unresponsive during a firmware update, follow this hardware reset procedure (requires opening the device): 1. **Open the back cover** of the IODD. 2. Locate and **press the tact switch** (reset button) on the internal PCB. 3. While holding the switch, **connect the USB cable** to the PC. 4. Continue holding the switch for about **7 seconds**. 5. **Release the switch** and wait for approximately **1 minute** for the system to recover. #### **Specific Hotkeys (Legacy)** | Device | Action | Hotkey | | :--- | :--- | :--- | | **2531** | Rescan Files | Long press **Jog Up** (3s) | | **2531** | Power Down | Long press **Jog Down** (3s) | | **2531** | Enter Menu | Long press **Jog Center** (3s) | | **2531** | Detach All | Long press **Back/Up** (3s) | | **2541** | Select File | **[5]** or **[6]** (**[6]** maintains loading state on newer firmware) | | **2541** | Power Down | Long press **[1]** (3s) | | **2541** | Reboot | Long press **[3]** (3s) | | **2541** | Rescan Files | Long press **[4]** (3s) | | **2541** | Detach All | Long press **[7]** (3s) | | **2541** | Disable WP | Long press **[0]** (3s) - Reboot and temporarily disable Write-Protection | * **Tip (2531)**: On firmware 1558 or higher, the loading state is saved automatically. For older versions, use the Power Down hotkey to save the state manually. * **Tip (2541)**: Button **[6]** for maintaining loading state requires firmware 6(7)9-05 or higher. #### **Startup Keys (2531 Only)** During startup (when connecting the USB cable), holding the following keys will force a specific mode: | Key | Resulting Mode | | :--- | :--- | | **Jog Up** | Start in **CD-MODE** | | **Jog Down** | Start in **HDD-MODE** | | **Jog Center** | Start in **DUAL-MODE** (Resets loading state) | | **Back Button** | Start in **Write-Protected** mode | #### **Firmware & Partition Limits (Legacy)** * **NTFS vs FAT**: Separate firmware versions exist (ending in **N** or **F**) depending on the first partition's file system. * **6x vs 7x Versions (2541)**: `7x` versions include enhanced security against brute-force password attacks. **Note**: Data must be backed up when switching between `6x` and `7x`. * **2TB Limit**: When using virtual drive functions (ISO/VHD), a **maximum 2TB partition** size is supported on 2531/2541/MINI models. --- ### 17.3 Advanced VHD Naming Conventions (IODD 2531 / 2541 Only) {% hint style="warning" %} **Model Limitation**: The following tips for controlling modes via filenames (**`&D`**, **`&DW`**) apply **only to IODD 2531 and 2541 models**. These features are not supported on newer models like ST400, LK100, or MINI PRO. {% endhint %} For legacy models (2531/2541) and specific automated workflows, the filename of a VHD can control the IODD's behavior upon mounting: * **Standard Mounting**: `filename.VHD` or `filename.VMDK` (Mounts as a fixed disk). iODD supports fixed-size VMDK files (can be created by renaming a VHD to VMDK). * **Removable Mounting**: `filename.RMD` (Mounts as removable media/flash drive). * **Dual Mode (Write-Protected)**: Append **`&D`** to the filename (e.g., `Win2Go&D.VHD`). Mounts in Dual Mode with the physical HDD write-protected. * **Dual Mode (Write-Enabled)**: Append **`&DW`** to the filename (e.g., `Win2Go&DW.VHD`). Mounts in Dual Mode with the physical HDD write-enabled. #### **Virtual FDD Support** IODD supports uncompressed floppy disk images in **IMA, IMG, BIF, or VFD** formats. If using `.IMG`, `.BIF`, or `.VFD`, rename the extension to **`.IMA`** for best compatibility. --- ## Part 2. Support And Chatbot Response Additions ## 18. Appendix: HTML-Derived Support Additions This appendix consolidates the most useful support-oriented content distilled from the exported conversation files `Google Gemini_EN.html` and `IODD ์ณ‡๋ด‡ 2_EN.html`. The goal is not to duplicate the full manual, but to preserve practical operator guidance, ready-to-use response rules, and concise troubleshooting flows that are especially useful for chatbot training, support scripts, and first-line customer handling. ### 18.1 Support Response Policy Use the following response principles when answering customer questions based on the IODD documentation: 1. Answer only from the documented content. 2. Do not guess or invent unsupported details. 3. If the documentation does not clearly cover the case, advise the customer to contact technical support. 4. Maintain a friendly, professional tone. 5. Use numbered steps for complex procedures. 6. Clearly distinguish model-specific behavior, especially between modern models and legacy models. 7. For password reset, encryption reset, or 2nd Password related actions, always highlight the risk of data loss before giving steps. ### 18.2 Mandatory Safety Warnings For Support Agents The following warnings should be repeated prominently whenever relevant: - **Password reset or encryption reset may erase data.** - **2nd Password must be configured before Admin Password** on supported modern encrypted models. - **IODD 2541 does not support Admin Manager** for password reset or recovery. - **Legacy models (2531 / 2541 / MINI Legacy) are MBR-only for virtual drive related workflows** and are limited to the first 2TB. - **Hardware encryption must not be combined with OS-level encryption tools** such as BitLocker or VeraCrypt. ### 18.3 Quick Support FAQ: IODD 2541 UEFI Boot Failure #### Symptom The device appears in the boot menu as `UEFI: iODD Virtual CDRom`, but the system does not actually boot, while Legacy/BIOS boot works. #### Recommended First-Line Troubleshooting 1. **Disable Secure Boot** in BIOS/UEFI. Secure Boot may block unsigned or partially compatible boot media even if the device itself appears in the boot menu. 2. **Verify that the ISO really supports UEFI boot.** The ISO should contain an `EFI` boot structure such as `\EFI\BOOT\bootx64.efi`. 3. **Set the 2541 to ODD Mode instead of Dual Mode.** Some systems handle a single exposed ODD more reliably than a multi-LUN USB device. 4. **Confirm that the internal disk is using MBR and a compatible file system.** For legacy 2541 usage, MBR and NTFS are the safest defaults. 5. **Check physical connection quality.** Use a rear motherboard USB port and a cable shorter than 50 cm. 6. **Check media compatibility.** Some ISOs are Legacy-only, and some older or modified images may fail on strict UEFI firmware. #### Quick Checklist | Item | Recommended Setting | | :--- | :--- | | Secure Boot | Disabled | | Boot Media | UEFI-capable ISO | | Device Mode | ODD Mode | | Disk Layout | MBR | | File System | NTFS preferred | | USB Port | Rear motherboard port | | Cable | Under 50 cm | ### 18.4 Quick Support FAQ: SSD Speed Slowdown #### Symptom The SSD inside the IODD becomes noticeably slower, especially during write operations. #### Recommended Troubleshooting Flow 1. **Run the IODD TRIM Tool first.** This is the most effective recovery step for external USB SSD performance degradation. 2. **Check whether the SSD is connected through a proper high-speed port.** Prefer a direct USB 3.x rear motherboard port. 3. **Check power stability.** If voltage is low or unstable, performance may drop or the drive may behave inconsistently. 4. **Leave free space on the SSD.** Keeping around 10-20% free space helps garbage collection and sustained performance. 5. **Check the file system for errors.** Use `chkdsk X: /f` with the correct drive letter. 6. **Review cable and hub conditions.** Avoid poor-quality or overly long cables, and use a powered hub if voltage is insufficient. #### Recommended Support Questions When handling a speed complaint, ask the customer for the following before escalation: - IODD model name - SSD manufacturer and model - File system in use - USB port type being used - Cable length - Whether the IODD TRIM Tool has already been run - Whether low VBUS voltage has been observed on the device ### 18.5 Support-Ready Script Snippets The following short responses are useful for FAQ/chatbot style support: #### Password / Encryption - **2nd Password is mandatory before Admin Password** on ST400 / LK100 / MINI PRO. - **Resetting or clearing encryption may erase data**, so customers must be warned before any reset workflow is explained. - **IODD 2541 password reset is manual only**; Admin Manager is not supported. #### Legacy Model Notes - **2541 uses touch keys**, while **2531 uses a jog dial**. - On some legacy firmware families, **NTFS-only** and **FAT/exFAT-only** variants exist, so the firmware branch must match the partition/file-system expectation. - Advanced virtual drive filename controls such as **`&D`** and **`&DW`** apply only to **2531 / 2541**. #### Virtual Drive / Utility Notes - For **VHD Tool++**, **exFAT** is generally the safer recommendation when timestamp/locale issues are suspected on NTFS. - If a customer cannot create a virtual disk on Apple Silicon, guide them to the documented macOS Terminal-based alternative instead of the Windows-only VHD Tool. ### 18.6 Suggested Use Of This Appendix This appendix is best used as: - a **chatbot/system prompt support addendum** - a **call-center quick reference** - a **FAQ seed list** for future expansion - a **quality-control checklist** for verifying that support answers remain aligned with the official documentation