Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report]: Windows 11 Compatibility Issue with USSD Disks: error sem timeout (USB 3.0/Higher Issue) #3076

Open
1 task done
SunnyPai0413 opened this issue Jan 12, 2025 · 0 comments

Comments

@SunnyPai0413
Copy link

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.99

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

Both

Partition Style

MBR

Disk Capacity

1TB

Disk Manufacturer

DIY

Image file checksum (if applicable)

None

Image file download link (if applicable)

No response

What happened?

I'm encountering a compatibility issue with USSD disks on Windows 11 (both 23H2 and 24H2). I have three USSD disks with the following hardware specifications:

Bridge: ASM1153e
Controller: SM2258XT
NAND Flash: Intel B17A (29F04T2AOCTH1)
Firmware Version: U1230A0

Problem:
After upgrading to the latest version of Ventoy and trying both MBR and GPT partition tables, the USSD disks consistently display an `error sem timeout' error after about 1 minute of initialization. The disks are recognized and the hardware information is read quickly, but the system hangs for about 1 minute while trying to read the data partition (probably the partition table). In addition, there is a 20-30 percent chance that it will work after the 1 minute hang.

Windows Event Log:

  - System 

  - Provider 

   [ Name]  Microsoft-Windows-Kernel-PnP 
   [ Guid]  {9c205a39-1250-487d-abd7-e831c6290539} 
 
   EventID 442 
 
   Version 0 
 
   Level 3 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x4000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2025-01-12T03:08:56.0569733Z 
 
   EventRecordID 1226 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  4 
   [ ThreadID]  4768 
 
   Channel Microsoft-Windows-Kernel-PnP/Configuration 
 
   Computer Laptop 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  DeviceInstanceId SCSI\Disk&Ven_USSD&Prod_Solid_state_USB\6&2aa1c02c&0&000000 
  LastDeviceInstanceId SCSI\Disk&Ven_&Prod_SDXC_\5&2a967811&0&000000 
  ClassGuid {4d36e967-e325-11ce-bfc1-08002be10318} 
  LocationPath  
  MigrationRank 0xf000fc000000f020 
  Present false 
  Status 0xc0000719 

Additional Information:
Normal Operation: Brand new disks with NTFS or exFAT filesystems work normally on the same devices.
Linux Compatibility: The issue does not occur on my Linux server.
Windows Versions: The issue is observed on Windows 11 23H2 and 24H2. I haven't tested on Windows 10 or older versions due to their limited support for hybrid CPU architectures.
USB Interface: This issue is more likely to occur when the USSD disk is connected to a USB 3.0 or higher port. The disk works normally when connected to a USB 2.0 port.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant