wiped out two memory sticks: I tried using Rufus to create a bootable memory stick and it wiped them out so my computer doesn't even recognize that they are drives.

[Shovelhead80]

Rufus version 1.3.4.270
Windows version: Windows XP 32-bit
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'PNY USB 2.0 FD USB Device'
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
2 devices found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'PNY USB 2.0 FD USB Device'
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
2 devices found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
2 devices found.
Could not get Disk Extents: [0x00000015] The device is not ready.
Sector Size: 512 bytes
Cylinders: 250, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x2896E767
Partition 1:
  Type: FAT16 LBA (0x0e)
  Size: 1.9 GB (2063581184 bytes)
  Start Sector: 32, Boot: No, Recognized: Yes

Format operation started
Requesting disk access...
Caution: Opened drive \\.\PHYSICALDRIVE3 for write access
Will use 'E:' as volume mountpoint
Could not get Disk Extents: [0x00000015] The device is not ready.
Could not get exclusive access to device \\?\Volume{27218766-60ac-11de-8758-0025562156ca}: [0x00000005] Access is denied.
Could not lock volume

Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'PNY USB 2.0 FD USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'PNY USB 2.0 FD USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.
Found device 'Brother MFC-6490CW USB Device'
Ignoring autorun.inf label for drive G: No media
Found device 'PNY USB 2.0 FD USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
Found device 'SanDisk Cruzer USB Device'
A device was eliminated because it didn't report itself as a non fixed USB disk
1 device found.
Could not get Disk Extents: [0x00000015] The device is not ready.
No volume information for disk 0x81
Could not get geometry for drive 0x81: [0x00000015] The device is not ready.

I used Rufus on two memory sticks and when I hit start after about 30 seconds it came up with an error and asked me to reinsert the drive.

Now I can't access those two memory sticks.

Has this happened to anyone else?

Attached is the Rufus log.

Edited by pbatard to embed the actual log rather than images
original images were at https://f.cloud.github.com/assets/5696240/1339313/1ed4ce40-3601-11e3-8513-f3cbe1d7a0ab.jpg and https://f.cloud.github.com/assets/5696240/1339314/1ed6146c-3601-11e3-8a46-d9e3b2b2f55e.jpg

[pbatard]

Copy pasting the answer I sent earlier by e-mail:

Have you tried this?:
https://github.com/pbatard/rufus/wiki/FAQ#wiki-Help_my_USB_drive_is_not_detected

I don't think your sticks are unreadable. Judging from the log, there may be issue with your OS or hardware or some antivirus app (you're getting an awful lot of errors even before Rufus starts to format your drive, which isn't normal), so the formatting operation couldn't complete. It doesn't even look like Rufus was able to write anything to your drive in the first place, because of these errors.

Are you using Panda USB vaccine or ESET Smart Security by any chance? These applications are known to prevent Rufus from performing its job successfully: https://github.com/pbatard/rufus/wiki/FAQ#wiki-List_of_software_and_hardware_Rufus_isnt_compatible_with

Also, is any of your device using USB 3.0 through an extension cable?
https://github.com/pbatard/rufus/wiki/FAQ#wiki-Error_writing_file_0x00000015_The_device_is_not_ready

Considering that the only people who reported similar errors had flaky USB connections, and your log shows that you are getting a lot of 0x00000015 errors even before Rufus does anything, I suspect that this is a hardware issue with your computer, and that the connection between your USB sticks and your computer is not stable.

Have you tried changing the USB port or removing any extension cable you may be using? Also what happens if you try formatting these USB sticks from another computer?

[Shovelhead80]

Hey Pete,

Been super busy so haven’t had a chance to try what you suggest below, but I will. Yes, I have antivirus software “F-Prot” and it may have messed with your program. I will turn it off as well as my malware program “Spy Hunter” and see if that does the trick. I did all this on my Dell laptop running XP. I’ll let you know how it all plays out.

Respectfully,
Bill Ryan, M.S., P.E.

[Shovelhead80]

Pete,

I used the link below and clicked on the Advanced tab. That fixed the problem and make the memory stick bootable with free dos.

When I boot my laptop using it the computer now thinks the memory stick is drive C: How do I get the computer to find my hard drive? Is that a Free Dos command? Need to get to the C: drive on my desktop so I can fix the Windows XP ntldr file so it will boot properly.

William Ryan

[pbatard]

I used the link below and clicked on the Advanced tab. That fixed the problem and make the memory stick bootable with free dos.

Great!

How do I get the computer to find my hard drive?

By default FreeDOS is only able to access a FAT32 filesystem, and if you are using Windows XP, your drive is most likely formatted using NTFS, which FreeDOS cannot access by default.

Usually the way to switch between drives is to type the drive letter like this: D:, E:, F:, etc. This will bring you to the second, third and fourth partition that DOS can access (but, again, DOS can usually not access all partitions if they use a filesystem that isn't FAT32).

To fix your ntldr, I would suggest that you use something like bartPE or Hiren's Boot CD, or one of the many bootable ISOs that can boot a mini Windows OS, that will give you access to NTFS.

I'm afraid that, since this isn't really a Rufus issue at this stage, and I am a bit too busy to guide you through a recovery, when plenty of guides should be available on the internet, I would advise you to use google or ask your question on forums that are dedicated to supporting Windows.

Best of luck!

/Pete

[Shovelhead80]

Thanks Pete! What you said was quite helpful. My brother did suggest BartPE. I will do what you said below and I should be able to fix the issue.

I thought FreeDOS might not be able to deal with NTFS formatting and you have just confirmed that.

Thank you for all your help!

William Ryan

[lock]

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.