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

[issue]: Ventoy bricked external hdd, closed during installation #3084

Open
1 task done
SmokedMonkey420 opened this issue Jan 15, 2025 · 5 comments
Open
1 task done

Comments

@SmokedMonkey420
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

No. I didn't try these alternative boot modes.

BIOS Mode

UEFI Mode

Partition Style

GPT

Disk Capacity

932 GB

Disk Manufacturer

Seagate

Image file checksum (if applicable)

None

Image file download link (if applicable)

https://sourceforge.net/projects/ventoy/files/latest/download

What happened?

I'm not really familiar with ventoy but my friend tried installing it on his external hdd but he closed it at 17% via task manager because he needed to go now it became a bad disk and i/o error keeps appearing i was able to allocate only 183 gb of 1 Tb available I don't know how this happened sorry for the noob question im just trying to help my friend

@booplazer111
Copy link

try to reset the partition table to gpt with gparted

@j-cooper
Copy link

j-cooper commented Jan 23, 2025

Good day, you described a problem that I also had. About a year ago I tried to install this software, Ventoy, on a Kingston flash drive, interrupted the image recording and the flash drive was blocked for recording. I can see some files on it, but in read-only mode. I tried various utilities and programs, in different operating systems, but nothing worked, the flash drive is damaged. Ventoy killed my flash drive completely.
The flash drive went into the trash.

@cheack
Copy link

cheack commented Jan 23, 2025

Ventoy killed my flash drive completely.

You intentionally interrupted a low-level disk operation and now you're puzzled about what went wrong? Nice.

@j-cooper
Copy link

The flash drive controller has a function to close the record to the device, to switch it to read-only mode, when detecting strong wear of the flash memory. This is done to protect data, to provide the last chance to copy information from the dying storage device. I will assume that Ventoy gives the device controller the wrong command and the controller thinks that the data storage device is starting to die and switches it to read-only mode.

@j-cooper
Copy link

Ventoy killed my flash drive completely.

You intentionally interrupted a low-level disk operation and now you're puzzled about what went wrong? Nice.

Who told you that low-level recording occurs behind the disk during installation? Did you come up with this yourself or did someone whisper it to you? Where did you find information about possible disk damage during installation? Nice.

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

4 participants