search

pbatard / rufus

The Reliable USB Formatting Utility
https://rufus.ie
GNU General Public License v3.0
28.43k stars 2.54k forks source link

Rufus 3.8.1580 USB killed? #1394

Closed Fsadju closed 4 years ago

Fsadju commented 4 years ago



Checklist

Additionally (if applicable):

Issue description

Last night installed HBCD.iso from "hirensbootcd.org" with Rufus , that writing task was successful (unfortunately i did not expect that error occurs following morning so no logs for that). Over night i did left HBCD run on my laptop to wipe laptop hard disk completely ("0" type wipe). While on desktop i downloaded last windows 10 .iso file from it's provider. Today in the morning task wiping was completed on laptop so i turned off everything from laptop and backed to desktop with usb. So then i connect normal ether high speed usb port device storage won't appear , "My Computer" doesn't show partition (with letter). I ignored that missing partition of usb and run Rufus anyway.

Things i have tried despite checklist: [*] Format device trough various tools. as result , occurs errors such as "writing-protected" or "check windows logs for more information".

To understand more i could attach photos - if needed.

What i could do with this unexpected error ?

I don't understand why it happen.

Tho device storage is accessible trough Free-ware such as

Am writing here as issue happen with Rufus.

Log

Rufus x86 v3.8.1580
Windows version: Windows 10 64-bit (Build 18362)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.04
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 'USB FLASH DRIVE USB Device' (1005:B113)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x84
Disk type: Removable, Disk size: 16 GB, Sector size: 512 bytes
Cylinders: 1893, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {F2542726-0E65-4833-A9D7-9BD93F91BD25}
Max parts: 128, Start Offset: 17408, Usable = 15571319296 bytes
Partition 1:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {774FEB55-9F71-4B76-96F8-98B22A51FBE9}
  Size: 14.5 GB (15570288128 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000
Scanning image...
ISO analysis:
  Image is an UDF image
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'ESD-ISO'
  Size: 3.9 GB (Projected)
  Note: File on disk is larger than reported ISO size by 556 KB...
  Uses: EFI
  Uses: Bootmgr (BIOS and UEFI)
  Uses: Install.esd (version 0.14.0+)
Using image: Windows.iso (3.9 GB)
Search for conflicting processes was interrupted due to timeout

Format operation started
Requesting disk access...
No drive letter was assigned...
Will use 'G:' as volume mountpoint
Deleting partitions...
Deleting ALL partition(s) from disk '\\?\PhysicalDrive4':
● Partition 1 (offset: 1048576, size: 14.5 GB)
Opened \\.\PhysicalDrive4 for exclusive write access
No logical drive found (unpartitioned?)
Drive does not appear to be partitioned
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Deleting partitions...
Partitioning (GPT)...
● Creating Main Data Partition (offset: 1048576, size: 14.5 GB)
Write error [0x000001B1] A device which does not exist was specified.
Retrying in 5 seconds...
Search for conflicting processes was interrupted due to timeout
Write error [0x000001B1] A device which does not exist was specified.
Retrying in 5 seconds...
Search for conflicting processes was interrupted due to timeout
Write error [0x000001B1] A device which does not exist was specified.
Retrying in 5 seconds...
Search for conflicting processes was interrupted due to timeout
Write error [0x000001B1] A device which does not exist was specified.
Could not zero Main Data Partition: [0x000001B1] A device which does not exist was specified.
Waiting for logical drive to reappear...
Timeout while waiting for logical drive
Logical drive was not found - aborting

Found USB 2.0 device 'USB FLASH DRIVE USB Device' (1005:B113)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x84
Disk type: Removable, Disk size: 16 GB, Sector size: 512 bytes
Cylinders: 1893, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {1069D3BB-B96B-4095-B0A9-65914D27647B}
Max parts: 128, Start Offset: 17408, Usable = 15571319296 bytes
Partition 1:
  Type: {EBD0A0A2-B9E5-4433-87C0-68B6B72699C7}
  Name: 'Main Data Partition'
  ID: {E7E6E790-3D98-49CA-ACB9-1A3FF742028F}
  Size: 14.5 GB (15570288128 bytes)
  Start Sector: 2048, Attributes: 0x0000000000000000

__________________________________

Bad Blocks log
*NOTE DEVICE WAS WORKING FOLLOWING NIGHT*

Rufus bad blocks check started on: 2019.10.21 13:32:20Block 0: write error
Block 1: write error
Block 2: write error
Block 3: write error
Block 4: write error
Block 5: write error
Block 6: write error
Block 7: write error
Block 8: write error
Block 9: write error
Block 10: write error
Block 11: write error
Block 12: write error
Block 13: write error
Block 14: write error
Block 15: write error
Block 16: write error
Block 17: write error
Block 18: write error
Block 19: write error
Block 20: write error
Block 21: write error
Block 22: write error
Block 23: write error
Block 24: write error
Block 25: write error
Block 26: write error
Block 27: write error
Block 28: write error
Block 29: write error
Block 30: write error
Block 31: write error
Block 32: write error
Block 33: write error
Block 34: write error
Block 35: write error
Block 36: write error
Block 37: write error
Block 38: write error
Block 39: write error
Block 40: write error
Block 41: write error
Block 42: write error
Block 43: write error
Block 44: write error
Block 45: write error
Block 46: write error
Block 47: write error
Block 48: write error
Block 49: write error
Block 50: write error
Block 51: write error
Block 52: write error
Block 53: write error
Block 54: write error
Block 55: write error
Block 56: write error
Block 57: write error
Block 58: write error
Block 59: write error
Block 60: write error
Block 61: write error
Block 62: write error
Block 63: write error
Block 64: write error
Block 65: write error
Block 66: write error
Block 67: write error
Block 68: write error
Block 69: write error
Block 70: write error
Block 71: write error
Block 72: write error
Block 73: write error
Block 74: write error
Block 75: write error
Block 76: write error
Block 77: write error
Block 78: write error
Block 79: write error
Block 80: write error
Block 81: write error
Block 82: write error
Block 83: write error
Block 84: write error
Block 85: write error
Block 86: write error
Block 87: write error
Block 88: write error
Block 89: write error
Block 90: write error
Block 91: write error
Block 92: write error
Block 93: write error
Block 94: write error
Block 95: write error
Block 96: write error
Block 97: write error
Block 98: write error
Block 99: write error
Block 100: write error
Block 101: write error
Block 102: write error
Block 103: write error
Block 104: write error
Block 105: write error
Block 106: write error
Block 107: write error
Block 108: write error
Block 109: write error
Block 110: write error
Block 111: write error
Block 112: write error
Block 113: write error
Block 114: write error
Block 115: write error
Block 116: write error
Block 117: write error
Block 118: write error
Block 119: write error
Block 120: write error
Block 121: write error
Block 122: write error
Block 123: write error
Block 124: write error
Block 125: write error
Block 126: write error
Block 127: write error
Block 128: write error
Block 129: write error
Block 130: write error
Block 131: write error
Block 132: write error
Block 133: write error
Block 134: write error
Block 135: write error
Block 136: write error
Block 137: write error
Block 138: write error
Block 139: write error
Block 140: write error
Block 141: write error
Block 142: write error
Block 143: write error
Block 144: write error
Block 145: write error
Block 146: write error
Block 147: write error
Block 148: write error
Block 149: write error
Block 150: write error
Block 151: write error
Block 152: write error
Block 153: write error
Block 154: write error
Block 155: write error
Block 156: write error
Block 157: write error
Block 158: write error
Block 159: write error
Block 160: write error
Block 161: write error
Block 162: write error
Block 163: write error
Block 164: write error
Block 165: write error
Block 166: write error
Block 167: write error
Block 168: write error
Block 169: write error
Block 170: write error
Block 171: write error
Block 172: write error
Block 173: write error
Block 174: write error
Block 175: write error
Block 176: write error
Block 177: write error
Block 178: write error
Block 179: write error
Block 180: write error
Block 181: write error
Block 182: write error
Block 183: write error
Block 184: write error
Block 185: write error
Block 186: write error
Block 187: write error
Block 188: write error
Block 189: write error
Block 190: write error
Block 191: write error
Block 192: write error
Block 193: write error
Block 194: write error
Block 195: write error
Block 196: write error
Block 197: write error
Block 198: write error
Block 199: write error
Block 200: write error
Block 201: write error
Block 202: write error
Block 203: write error
Block 204: write error
Block 205: write error
Block 206: write error
Block 207: write error
Block 208: write error
Block 209: write error
Block 210: write error
Block 211: write error
Block 212: write error
Block 213: write error
Block 214: write error
Block 215: write error
Block 216: write error
Block 217: write error
Block 218: write error
Block 219: write error
Block 220: write error
Block 221: write error
Block 222: write error
Block 223: write error
Block 224: write error
Block 225: write error
Block 226: write error
Block 227: write error
Block 228: write error
Block 229: write error
Block 230: write error
Block 231: write error
Block 232: write error
Block 233: write error
Block 234: write error
Block 235: write error
Block 236: write error
Block 237: write error
Block 238: write error
Block 239: write error
Block 240: write error
Block 241: write error
Block 242: write error
Block 243: write error
Block 244: write error
Block 245: write error
Block 246: write error
Block 247: write error
Block 248: write error
Block 249: write error
Block 250: write error
Block 251: write error
Block 252: write error
Block 253: write error
Block 254: write error
Block 255: write error
Too many bad blocks, aborting test
Check completed: 256 bad block(s) found

  0 read error(s)

  256 write error(s)

  0 corruption error(s)Rufus bad blocks check ended on: 2019.10.21 13:32:22
pbatard commented 4 years ago

The bad blocks check indicates that your device is defective. And yes, things that used to be working do happen to fail, especially when it comes to flash memory, which is A LOT less everlasting that people tend to think to is.

If the Rufus bad blocks check report errors, then your USB flash drive is defective, period. It's a pure hardware issue, and no matter of wishful thinking that, maybe, there's something that Rufus could do, will detract from the fact that your hardware is failing and should no longer be used.

Please use a different flash drive, and either recycle this one or send it for RMA, because your flash memory is defective. Flash memory going bad happens, all the time. And it is not something software can fix.

I will now close this issue.

Fsadju commented 4 years ago

Yes, thank you for replay. Indeed. Will keep that in mind. Anyway , checking trough friends laptop that USB working properly. Tried run other USB's on My Desktop still Failing to load ANY USB Device in fact. Both devices laptop and desktop operation system is failing/lagging that's why i must to reinstall 'em all . Awkward situation . hahah .

,- In the end .Thanks for this freeware !

lock[bot] commented 4 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.