tree-t
commented
2 years ago Edit: 1
This is what I get when I use diskpart:
Thank you in advance.
Closed tree-t closed 2 years ago
tree-t
commented
2 years ago Edit: 1
This is what I get when I use diskpart:
Thank you in advance.
ventoy
commented
2 years ago Open Ventoy2Disk.exe and upload the log.txt here.
tree-t
commented
2 years ago Hello, Sorry for a late answer, as I had removed ventoy from windows 7 after deployment, so I have installed a fresh copy of it and tried both install and update options, but none of them appear to work. Here is ventoy-1.0.70/log.txt log.txt And how it looks from inside(maybe you wanted it this way):
[2022/03/04 09:42:49.223]
##################################################################################
######################### Ventoy2DiskX86 1.0.0.3 (1.0.70) #########################
##################################################################################
[2022/03/04 09:42:49.239] Current directory:
tree-t
commented
2 years ago Hello, I just wanted to add that I can although still boot my isos(which were on the usb before it became read-only). With the hope that I will be able to use my usb as what it was( as I believe that I will find the solution here itself ). Thanks again in advance.
ventoy
commented
2 years ago You USB disk name is General USB Flash Disk 4GB , this is not a normal case.
Normally the disk name is like Sandisk xxx Kingson xxx ...
I have recieved many many similar reports since I developed Ventoy.
So your USB disk has big chance to be fake or faulty.
You can find some tool to do a fully test of your USB disk to make sure that it has no hardware problem.
tree-t
commented
2 years ago Hello again, I have tried Rufus, Unetbootin, Ventoy, Yumi, etcher, etchdroid and dd with the usb in the past and they all have worked flawlessly, hence confirming that the usb is not fake. But one thing that I missed out was that when the usb became read-only, at that time a power failure had occurred (my battery had run out of charge and it was at the bios screen). Hope that info helps. But how can I test a hardware problem, like can you list any such thing? Plus the usb doesn't have a hardware switch (to turn it to read-only). Thanks in advance.
ventoy
commented
2 years ago You can use some USB Flash memory test program such as H2TESTW, FakeFlashTest to test it.
tree-t
commented
2 years ago Hello, Thanks, but the above mentioned apps are just to test whether the usb is fake or not, for which a simple formatting will also work, but I already know that it is not a fake usb.( I just found its case and its logo says 'Schneider Electric'. The problem is that the usb has become read-only (the brand isn't, but I don't actually know if it was turned read-only by a ventoy setting or not, as I also performed some tweaks using the .exe file in the .zip of ventoy(the .exe opened a chrome window and I filled whatever I thought as useful) and my isos are in (hd1,0)/ventoy/*.iso . Thank you in advance.
ventoy
commented
2 years ago It may not be fake, but it may have some bad physical sectors, especially at the end of the USB disk.
The biggest difference between Ventoy and other tool is the disk layout. As descripted here: https://www.ventoy.net/en/doc_disk_layout.html Ventoy will use the end of the USB disk as partition 2 when install. Many other tools use USB disk from the beginning to the end step by step.
For many fake or faulty USB disk, it's OK if you don't use more space enough. For example, for a 32GB fake USB disk, if you only use the first 16GB space it may be OK. But it will fail if you use 30GB or more space.
tree-t
commented
2 years ago Hello,
Here is what I got from FakeFlashTest:
FAKEFLASHTEST v1.1.2 [SSi]
DRIVE 1 - 3.7GiB General USB Flash Disk
FFT - Quick Size Test (destructive)
DRIVE 1 - 3.7GiB General USB Flash Disk
Writing marker blocks to drive 1 ERROR writing to drive at Sector 7920044 WRITE ERROR: Sector = 7920044 WRITE ERROR: Sector = 7894444 WRITE ERROR: Sector = 7868844 WRITE ERROR: Sector = 7843244 WRITE ERROR: Sector = 7817644 WRITE ERROR: Sector = 7792044 WRITE ERROR: Sector = 7766444 WRITE ERROR: Sector = 7740844 WRITE ERROR: Sector = 7715244 WRITE ERROR: Sector = 7689644 WRITE ERROR: Sector = 7664044 WRITE ERROR: Sector = 7638444 WRITE ERROR: Sector = 7612844 WRITE ERROR: Sector = 7587244 WRITE ERROR: Sector = 7561644 WRITE ERROR: Sector = 7536044 5% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 7510444 WRITE ERROR: Sector = 7484844 WRITE ERROR: Sector = 7459244 WRITE ERROR: Sector = 7433644 WRITE ERROR: Sector = 7408044 WRITE ERROR: Sector = 7382444 WRITE ERROR: Sector = 7356844 WRITE ERROR: Sector = 7331244 WRITE ERROR: Sector = 7305644 WRITE ERROR: Sector = 7280044 WRITE ERROR: Sector = 7254444 WRITE ERROR: Sector = 7228844 WRITE ERROR: Sector = 7203244 WRITE ERROR: Sector = 7177644 WRITE ERROR: Sector = 7152044 10% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 7126444 WRITE ERROR: Sector = 7100844 WRITE ERROR: Sector = 7075244 WRITE ERROR: Sector = 7049644 WRITE ERROR: Sector = 7024044 WRITE ERROR: Sector = 6998444 WRITE ERROR: Sector = 6972844 WRITE ERROR: Sector = 6947244 WRITE ERROR: Sector = 6921644 WRITE ERROR: Sector = 6896044 WRITE ERROR: Sector = 6870444 WRITE ERROR: Sector = 6844844 WRITE ERROR: Sector = 6819244 WRITE ERROR: Sector = 6793644 WRITE ERROR: Sector = 6768044 WRITE ERROR: Sector = 6742444 15% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 6716844 WRITE ERROR: Sector = 6691244 WRITE ERROR: Sector = 6665644 WRITE ERROR: Sector = 6640044 WRITE ERROR: Sector = 6614444 WRITE ERROR: Sector = 6588844 WRITE ERROR: Sector = 6563244 WRITE ERROR: Sector = 6537644 WRITE ERROR: Sector = 6512044 WRITE ERROR: Sector = 6486444 WRITE ERROR: Sector = 6460844 WRITE ERROR: Sector = 6435244 WRITE ERROR: Sector = 6409644 WRITE ERROR: Sector = 6384044 WRITE ERROR: Sector = 6358444 20% complete - 0 min 4 sec remaining WRITE ERROR: Sector = 6332844 WRITE ERROR: Sector = 6307244 WRITE ERROR: Sector = 6281644 WRITE ERROR: Sector = 6256044 WRITE ERROR: Sector = 6230444 WRITE ERROR: Sector = 6204844 WRITE ERROR: Sector = 6179244 WRITE ERROR: Sector = 6153644 WRITE ERROR: Sector = 6128044 WRITE ERROR: Sector = 6102444 WRITE ERROR: Sector = 6076844 WRITE ERROR: Sector = 6051244 WRITE ERROR: Sector = 6025644 WRITE ERROR: Sector = 6000044 WRITE ERROR: Sector = 5974444 WRITE ERROR: Sector = 5948844 25% complete - 0 min 3 sec remaining WRITE ERROR: Sector = 5923244 WRITE ERROR: Sector = 5897644 WRITE ERROR: Sector = 5872044 WRITE ERROR: Sector = 5846444 WRITE ERROR: Sector = 5820844 WRITE ERROR: Sector = 5795244 WRITE ERROR: Sector = 5769644 WRITE ERROR: Sector = 5744044 WRITE ERROR: Sector = 5718444 WRITE ERROR: Sector = 5692844 WRITE ERROR: Sector = 5667244 WRITE ERROR: Sector = 5641644 WRITE ERROR: Sector = 5616044 WRITE ERROR: Sector = 5590444 WRITE ERROR: Sector = 5564844 30% complete - 0 min 3 sec remaining WRITE ERROR: Sector = 5539244 WRITE ERROR: Sector = 5513644 WRITE ERROR: Sector = 5488044 WRITE ERROR: Sector = 5462444 WRITE ERROR: Sector = 5436844 WRITE ERROR: Sector = 5411244 WRITE ERROR: Sector = 5385644 WRITE ERROR: Sector = 5360044 WRITE ERROR: Sector = 5334444 WRITE ERROR: Sector = 5308844 WRITE ERROR: Sector = 5283244 WRITE ERROR: Sector = 5257644 WRITE ERROR: Sector = 5232044 WRITE ERROR: Sector = 5206444 WRITE ERROR: Sector = 5180844 WRITE ERROR: Sector = 5155244 35% complete - 0 min 2 sec remaining WRITE ERROR: Sector = 5129644 WRITE ERROR: Sector = 5104044 WRITE ERROR: Sector = 5078444 WRITE ERROR: Sector = 5052844 WRITE ERROR: Sector = 5027244 WRITE ERROR: Sector = 5001644 WRITE ERROR: Sector = 4976044 WRITE ERROR: Sector = 4950444 WRITE ERROR: Sector = 4924844 WRITE ERROR: Sector = 4899244 WRITE ERROR: Sector = 4873644 WRITE ERROR: Sector = 4848044 WRITE ERROR: Sector = 4822444 WRITE ERROR: Sector = 4796844 WRITE ERROR: Sector = 4771244 40% complete - 0 min 2 sec remaining WRITE ERROR: Sector = 4745644 WRITE ERROR: Sector = 4720044 WRITE ERROR: Sector = 4694444 WRITE ERROR: Sector = 4668844 WRITE ERROR: Sector = 4643244 WRITE ERROR: Sector = 4617644 WRITE ERROR: Sector = 4592044 WRITE ERROR: Sector = 4566444 WRITE ERROR: Sector = 4540844 WRITE ERROR: Sector = 4515244 WRITE ERROR: Sector = 4489644 WRITE ERROR: Sector = 4464044 WRITE ERROR: Sector = 4438444 WRITE ERROR: Sector = 4412844 WRITE ERROR: Sector = 4387244 WRITE ERROR: Sector = 4361644 45% complete - 0 min 2 sec remaining WRITE ERROR: Sector = 4336044 WRITE ERROR: Sector = 4310444 WRITE ERROR: Sector = 4284844 WRITE ERROR: Sector = 4259244 WRITE ERROR: Sector = 4233644 WRITE ERROR: Sector = 4208044 WRITE ERROR: Sector = 4182444 WRITE ERROR: Sector = 4156844 WRITE ERROR: Sector = 4131244 WRITE ERROR: Sector = 4105644 WRITE ERROR: Sector = 4080044 WRITE ERROR: Sector = 4054444 WRITE ERROR: Sector = 4028844 WRITE ERROR: Sector = 4003244 WRITE ERROR: Sector = 3977644 50% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 3952044 WRITE ERROR: Sector = 3926444 WRITE ERROR: Sector = 3900844 WRITE ERROR: Sector = 3875244 WRITE ERROR: Sector = 3849644 WRITE ERROR: Sector = 3824044 WRITE ERROR: Sector = 3798444 WRITE ERROR: Sector = 3772844 WRITE ERROR: Sector = 3747244 WRITE ERROR: Sector = 3721644 WRITE ERROR: Sector = 3696044 WRITE ERROR: Sector = 3670444 WRITE ERROR: Sector = 3644844 WRITE ERROR: Sector = 3619244 WRITE ERROR: Sector = 3593644 WRITE ERROR: Sector = 3568044 55% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 3542444 WRITE ERROR: Sector = 3516844 WRITE ERROR: Sector = 3491244 WRITE ERROR: Sector = 3465644 WRITE ERROR: Sector = 3440044 WRITE ERROR: Sector = 3414444 WRITE ERROR: Sector = 3388844 WRITE ERROR: Sector = 3363244 WRITE ERROR: Sector = 3337644 WRITE ERROR: Sector = 3312044 WRITE ERROR: Sector = 3286444 WRITE ERROR: Sector = 3260844 WRITE ERROR: Sector = 3235244 WRITE ERROR: Sector = 3209644 WRITE ERROR: Sector = 3184044 60% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 3158444 WRITE ERROR: Sector = 3132844 WRITE ERROR: Sector = 3107244 WRITE ERROR: Sector = 3081644 WRITE ERROR: Sector = 3056044 WRITE ERROR: Sector = 3030444 WRITE ERROR: Sector = 3004844 WRITE ERROR: Sector = 2979244 WRITE ERROR: Sector = 2953644 WRITE ERROR: Sector = 2928044 WRITE ERROR: Sector = 2902444 WRITE ERROR: Sector = 2876844 WRITE ERROR: Sector = 2851244 WRITE ERROR: Sector = 2825644 WRITE ERROR: Sector = 2800044 WRITE ERROR: Sector = 2774444 65% complete - 0 min 2 sec remaining WRITE ERROR: Sector = 2748844 WRITE ERROR: Sector = 2723244 WRITE ERROR: Sector = 2697644 WRITE ERROR: Sector = 2672044 WRITE ERROR: Sector = 2646444 WRITE ERROR: Sector = 2620844 WRITE ERROR: Sector = 2595244 WRITE ERROR: Sector = 2569644 WRITE ERROR: Sector = 2544044 WRITE ERROR: Sector = 2518444 WRITE ERROR: Sector = 2492844 WRITE ERROR: Sector = 2467244 WRITE ERROR: Sector = 2441644 WRITE ERROR: Sector = 2416044 WRITE ERROR: Sector = 2390444 70% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 2364844 WRITE ERROR: Sector = 2339244 WRITE ERROR: Sector = 2313644 WRITE ERROR: Sector = 2288044 WRITE ERROR: Sector = 2262444 WRITE ERROR: Sector = 2236844 WRITE ERROR: Sector = 2211244 WRITE ERROR: Sector = 2185644 WRITE ERROR: Sector = 2160044 WRITE ERROR: Sector = 2134444 WRITE ERROR: Sector = 2108844 WRITE ERROR: Sector = 2083244 WRITE ERROR: Sector = 2057644 WRITE ERROR: Sector = 2032044 WRITE ERROR: Sector = 2006444 WRITE ERROR: Sector = 1980844 75% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 1955244 WRITE ERROR: Sector = 1929644 WRITE ERROR: Sector = 1904044 WRITE ERROR: Sector = 1878444 WRITE ERROR: Sector = 1852844 WRITE ERROR: Sector = 1827244 WRITE ERROR: Sector = 1801644 WRITE ERROR: Sector = 1776044 WRITE ERROR: Sector = 1750444 WRITE ERROR: Sector = 1724844 WRITE ERROR: Sector = 1699244 WRITE ERROR: Sector = 1673644 WRITE ERROR: Sector = 1648044 WRITE ERROR: Sector = 1622444 WRITE ERROR: Sector = 1596844 80% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 1571244 WRITE ERROR: Sector = 1545644 WRITE ERROR: Sector = 1520044 WRITE ERROR: Sector = 1494444 WRITE ERROR: Sector = 1468844 WRITE ERROR: Sector = 1443244 WRITE ERROR: Sector = 1417644 WRITE ERROR: Sector = 1392044 WRITE ERROR: Sector = 1366444 WRITE ERROR: Sector = 1340844 WRITE ERROR: Sector = 1315244 WRITE ERROR: Sector = 1289644 WRITE ERROR: Sector = 1264044 WRITE ERROR: Sector = 1238444 WRITE ERROR: Sector = 1212844 85% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 1187244 WRITE ERROR: Sector = 1161644 WRITE ERROR: Sector = 1136044 WRITE ERROR: Sector = 1110444 WRITE ERROR: Sector = 1084844 WRITE ERROR: Sector = 1059244 WRITE ERROR: Sector = 1033644 WRITE ERROR: Sector = 1008044 WRITE ERROR: Sector = 982444 WRITE ERROR: Sector = 956844 WRITE ERROR: Sector = 931244 WRITE ERROR: Sector = 905644 WRITE ERROR: Sector = 880044 WRITE ERROR: Sector = 854444 WRITE ERROR: Sector = 828844 WRITE ERROR: Sector = 803244 90% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 777644 WRITE ERROR: Sector = 752044 WRITE ERROR: Sector = 726444 WRITE ERROR: Sector = 700844 WRITE ERROR: Sector = 675244 WRITE ERROR: Sector = 649644 WRITE ERROR: Sector = 624044 WRITE ERROR: Sector = 598444 WRITE ERROR: Sector = 572844 WRITE ERROR: Sector = 547244 WRITE ERROR: Sector = 521644 WRITE ERROR: Sector = 496044 WRITE ERROR: Sector = 470444 WRITE ERROR: Sector = 444844 WRITE ERROR: Sector = 419244 95% complete - 0 min 1 sec remaining WRITE ERROR: Sector = 393644 WRITE ERROR: Sector = 368044 WRITE ERROR: Sector = 342444 WRITE ERROR: Sector = 316844 WRITE ERROR: Sector = 291244 WRITE ERROR: Sector = 265644 WRITE ERROR: Sector = 240044 WRITE ERROR: Sector = 214444 WRITE ERROR: Sector = 188844 WRITE ERROR: Sector = 163244 WRITE ERROR: Sector = 137644 WRITE ERROR: Sector = 112044 WRITE ERROR: Sector = 86444 WRITE ERROR: Sector = 60844 WRITE ERROR: Sector = 35244 WRITE ERROR: Sector = 9644 100% complete - 0 min 1 sec remaining ERROR writing to drive at Sector 0 Reading back marker blocks... 5% complete - 0 min 1 sec remaining 10% complete - 0 min 1 sec remaining 15% complete - 0 min 1 sec remaining 20% complete - 0 min 1 sec remaining 25% complete - 0 min 1 sec remaining 30% complete - 0 min 1 sec remaining 35% complete - 0 min 1 sec remaining 40% complete - 0 min 1 sec remaining 45% complete - 0 min 1 sec remaining 50% complete - 0 min 1 sec remaining 55% complete - 0 min 1 sec remaining 60% complete - 0 min 1 sec remaining 65% complete - 0 min 1 sec remaining 70% complete - 0 min 1 sec remaining 75% complete - 0 min 1 sec remaining 80% complete - 0 min 1 sec remaining 85% complete - 0 min 1 sec remaining 90% complete - 0 min 1 sec remaining 95% complete - 0 min 1 sec remaining Memory tested in blocks of 25600 sectors.
BAD MEMORY from sector 35244 (17.2089MiB) to sector 7920044 (3,867.2089Mib)
WARNING: no memory detected at one or more locations. Test took 4 seconds.
*** FAILED ***DEVICE HAS DUPLICATE OR BAD BLOCKS!
Recommended maximum usable partition size: 4.7089Mib (approx. Last good Sector=35244)
Unplug and re-connect the drive, then reformat it using Windows or RMPrepUSB.
And here is what RMPrepUSB shows:
tree-t
commented
2 years ago And here is what rufus says: Rufus x86 v3.17.1846 (Portable) Windows version: Windows 7 SP1 32 bit Syslinux versions: 4.07/2013-07-25, 6.04/pre1 Grub versions: 0.4.6a, 2.06 System locale ID: 0x0409 (en-US) Will use default UI locale 0x0409 SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E Localization set to 'en-US' Found USB 2.0 device 'General USB Flash Disk USB Device' (090C:1000) 1 device found Disk type: Removable, Disk size: 4.1GB, Sector size: 512 bytes Cylinders: 493, Tracks per cylinder: 255, Sectors per track: 63 Partition type: MBR, NB Partitions: 2 Disk ID: 0xB78FE37C Drive has an unknown Master Boot Record Partition 1: Type: exFAT (0x07) Size: 3.7 GB (4023382016 bytes) Start Sector: 2048, Boot: Yes Partition 2: Type: EFI FAT (0xef) Size: 32 MB (33554432 bytes) Start Sector: 7860216, Boot: No
Format operation started Requesting disk access... Will use 'F:' as volume mountpoint Warning: Could not delete partition(s): [0x80070013] The media is write protected. Opened \.\PhysicalDrive1 for shared write access Requesting logical volume handle... I/O boundary checks disabled Analyzing existing boot records... Drive has an unknown Master Boot Record Clearing MBR/PBR/GPT structures... Erasing 128 sectors Write error [0x00000013] The media is write protected. Retrying in 5 seconds... Write error [0x00000013] The media is write protected. Retrying in 5 seconds... Write error [0x00000013] The media is write protected. Retrying in 5 seconds... Write error [0x00000013] The media is write protected. Could not reset partitions Re-mounted volume as F: after error
Found USB 2.0 device 'General USB Flash Disk USB Device' (090C:1000) 1 device found Disk type: Removable, Disk size: 4.1GB, Sector size: 512 bytes Cylinders: 493, Tracks per cylinder: 255, Sectors per track: 63 Partition type: MBR, NB Partitions: 2 Disk ID: 0xB78FE37C Drive has an unknown Master Boot Record Partition 1: Type: exFAT (0x07) Size: 3.7 GB (4023382016 bytes) Start Sector: 2048, Boot: Yes Partition 2: Type: EFI FAT (0xef) Size: 32 MB (33554432 bytes) Start Sector: 7860216, Boot: No Found USB 2.0 device 'General USB Flash Disk USB Device' (090C:1000) 1 device found Disk type: Removable, Disk size: 4.1GB, Sector size: 512 bytes Cylinders: 493, Tracks per cylinder: 255, Sectors per track: 63 Partition type: MBR, NB Partitions: 2 Disk ID: 0xB78FE37C Drive has an unknown Master Boot Record Partition 1: Type: exFAT (0x07) Size: 3.7 GB (4023382016 bytes) Start Sector: 2048, Boot: Yes Partition 2: Type: EFI FAT (0xef) Size: 32 MB (33554432 bytes) Start Sector: 7860216, Boot: No
And what windows' chkdisk says:
Although FakeFlashTest says that the usb has so many bad sectors, my isos(almost 1.68GB seem to work flawlessly. And I have no idea how to fix the bad sectors, as the disk according windows and linux is read-only or write-protected. Thank you in advance.
steve6375
commented
2 years ago USB Flash drives that have a Model name of 'General USB Flash Disk' and a capacity of 3.8GiB tend to indicate that it is a fake flash drive and may only contain 1GB or 2GB of memory and also may contain bad memory as it is not 4GiB. I have bought and tested many fake USB drives (I am the developer of FakeFlashTest) and 99% of them either stop working or return 'Read-only' (WP) status and are then useless. You could try running ChipGenius and see if it reports the memory chips used and their size (or disassemble it). It would not surprise me it it only had 1GiB or 2GiB of memory inside it. In any case, I am afraid the USB stick is no more, it is a dead USB stick, it has shuffled off it's mortal coil, it is no longer with us, it has waived goodbye to life and joined the angels in heaven, it is an ex-USB stick! https://youtu.be/vZw35VUBdzo
P.S. Beware of ChipGenius as many versions contain viruses. Only download from a site which checks for viruses and has a good reputation!
tree-t
commented
2 years ago Hello @steve6375 , Please refer to this.
Hello again, I have tried Rufus, Unetbootin, Ventoy, Yumi, etcher, etchdroid and dd with the usb in the past and they all have worked flawlessly, hence confirming that the usb is not fake. But one thing that I missed out was that when the usb became read-only, at that time a power failure had occurred (my battery had run out of charge and it was at the bios screen). Hope that info helps. But how can I test a hardware problem, like can you list any such thing? Plus the usb doesn't have a hardware switch (to turn it to read-only). Thanks in advance.
This was written by me earlier in this issue
tree-t
commented
2 years ago USB Flash drives that have a Model name of 'General USB Flash Disk' and a capacity of 3.8GiB tend to indicate that it is a fake flash drive and may only contain 1GB or 2GB of memory and also may contain bad memory as it is not 4GiB. I have bought and tested many fake USB drives (I am the developer of FakeFlashTest) and 99% of them either stop working or return 'Read-only' (WP) status and are then useless. You could try running ChipGenius and see if it reports the memory chips used and their size (or disassemble it). It would not surprise me it it only had 1GiB or 2GiB of memory inside it. In any case, I am afraid the USB stick is no more, it is a dead USB stick, it has shuffled off it's mortal coil, it is no longer with us, it has waived goodbye to life and joined the angels in heaven, it is an ex-USB stick! https://youtu.be/vZw35VUBdzo
P.S. Beware of ChipGenius as many versions contain viruses. Only download from a site which checks for viruses and has a good reputation!
Ok, will try chip genius (from file horse) and will send the result here
tree-t
commented
2 years ago @steve6375, using chip genius wasn't a good idea for me, can you suggest a source?
steve6375
commented
2 years ago https://www.softpedia.com/get/System/System-Info/ChipGenius.shtml older version But check it for viruses first using VirusTotal.
tree-t
commented
2 years ago Ok, but as soon as I downloaded it, my anti-virus removed it
steve6375
commented
2 years ago well you can disable it, the decision is yours! but in any case, it wont fix your USB drive. Just buy another - they are very cheap!
tree-t
commented
2 years ago Sorry, can't take that much of risk for just a checking.
tree-t
commented
2 years ago @ventoy its not an usb hardware issue! And it is an issue IDK whether of ventoy or something else, but its not a hardware issue!
leoadn
commented
2 years ago @ventoy its not an usb hardware issue! And it is an issue IDK whether of ventoy or something else, but its not a hardware issue!
have u found the solution?, same issue for me after using ventoy when i want to delete the ventoy my usb become read only....
tree-t
commented
2 years ago Hello @leoadn, Brief ans: No ~Tree-t
reza00farjam
commented
1 year ago Hi everyone. So our USBs are broke after using Ventoy and no fix, right? That's weird, it should be mentioned in official documents as a BIG WARNING before user find it out in the hard way!
Alex7175
commented
4 months ago I managed to fix it!!! The thing is ventoy breaks USB controller/firmware settings. Devs should put a disclaimer instead of saying that USBs are fake. You can fix your USB too if you're willing to go to a scary Russian website with the help of google translate. (there is a risk to brick, but it's better then throwing it away, right?) 1) Download ChipGenius and find your USB Controller Part-Number. Link: https://www.usbdev.ru/files/chipgenius/ 2) Download SMI MPTool for specific version of your controller. Always use the latest one at the bottom. (If doesn't work download older version) 3) Follow the guide to repair your USB. Link: https://www.usbdev.ru/articles/a_smi/smimptool-repair/ I really hope that anyone googling it managed to repair their USBs. Also, shame on you, devs!
steve6375
commented
4 months ago Ventoy just writes data to sectors on the USB drive. It does nothing to the firmware. It just uses perfectly standard sector write API calls to Windows or Linux (depending on what you used). The problem is that fake USB drives use hacked/modified firmware so that it lies about the total memory capacity of the USB drive - but the firmware is often very buggy - e.g. the firmware may be for a different capacity drive. It may contain corrupt tables about bad nvram flash pages and spare pages (used to replace bad sectors) and often the hacker does not even test each USB drive or the memory chips inside to make a valid flash memory page swap map. For instance the memory where page swap tables are held should be hidden and inaccessible to standard sector writes and not included as part of the 'user' area. This is why a good 32B flash drive may actually have only 30GB reported capacity (2GB are used for page sparing, sparing tables, spare pages, housekeeping and even firmware code storage). Typically, fake drives will seem OK as long as you only use the first 1/4 of it. However, the last 1/2 or 1/4 of the memory may be bad or simply not present! Ventoy writes to the last 32MB of memory of the USB drive (capacity is reported by the USB drive firmware) by default, as does any program or standard OS file copy which writes to the very end of the drive, this often causes the whole of a fake drive to become inoperative. It is a classic symptom of many fake flash drives that when you write to the sectors at the end of the (false) reported capacity, the firmware will then crash because it's code or page tables, etc. have been overwritten by user data when it should have been hidden to the user by the firmware.
TempleISO
commented
2 months ago I agree there are valid points here, considering fake USB drives, but what about my Kingston Data Traveler 3.0 Exodia M 128GB? I was on Linux mint, and upon moving slackware iso image into the USB, I renamed it (I just capitalised the S) and all of a sudden, the drive got unmounted. After replugging it, it was in read-only mode ever since. No tool has helped so far, I tried with gdisk, fdisk, gparted, nothing worked.
Heres the output of gdisk when I tried wiping the partition table: (Note, I mounted the partition 1, which holds the ISO files, but both partitions give the same error)
GPT fdisk (gdisk) version 1.0.8 NOTE: Write test failed with error number 30. It will be impossible to save changes to this disk's partition table! Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present
Found invalid GPT and valid MBR; converting MBR to GPT format in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if you don't want to convert your MBR partitions to GPT format!
Command (? for help): x Expert command (? for help): z About to wipe out GPT on /dev/sdb1. Proceed? (Y/N): Y Problem opening '/dev/sdb1' for writing! Program will now terminate. Blank out MBR? (Y/N): Y Warning! MBR not overwritten! Error is 30!
My Kingston was partitioned by using this method: https://www.ventoy.net/static/img/disklayout.png Instead of what you guys recommended here: https://www.ventoy.net/static/img/disklayout_reserve.png
If it's actually true that no matter what USB we use, if we have no reserved space we're basically screwed, and the dev didnt even put a warning.... This reserved space should be mandatory when installing Ventoy. I sincerely ask of you Ventoy developers, if reserved space is what would have prevented this from happening, why not make it mandatory? Or at least put a warning.
As for the other people that came here because of the same issue, you might want to read this: https://unix.stackexchange.com/questions/647445/unable-to-open-device-dev-sdb-for-writing-errno-is-30-aborting-write Seems like there isnt much you can do here.
Conan179
commented
2 months ago @TempleISO The Stick is Death. I know that from Micro SD cards, if it is defective, the internal electronics turns it into a ROM and you can only dispose of it or have it exchanged by the manufacturer.
Official FAQ
Ventoy Version
1.0.70
What about latest release
No. I didn't try the latest release.
BIOS Mode
Legacy BIOS Mode
Partition Style
MBR
Disk Capacity
4.1GB
Disk Manufacturer
Don't know
Image file checksum (if applicable)
No.
Image file download link (if applicable)
No response
What happened?
Hello everyone, When I was using a disk using Ventoy, I suddenly noted(before that, the previous two boots were wierd, in one the display was blank and in the second one, the grub bootloader could be seen without the ventoy beautifications), that the disk had become read-only. Even in linux(Slax 11.2.0 & Fossadog) the disk showed itself as read-only, but in Windows 7 using diskpart I found out that the current read-only state was set to yes, whereas read-only was set to no. I tried using etchdroid in Android [as rufus, ventoy and chk failed in windows and gparted failed in linux(Fossadog)], but it said that the drive was not properly connected (even though some other apps did recognise it properly, but they could only copy data from usb). Can anybody please help me?