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.

Sign up for GitHub

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

Jump to bottom

Error : device not ready #386

Closed
jimini24 opened this issue Oct 19, 2014 · 8 comments
Closed

Error : device not ready #386

jimini24 opened this issue Oct 19, 2014 · 8 comments
Assignees
@pbatard
Milestone
2.0

Comments

@jimini24
Copy link

Hi, Sorry for my english
When I try to format USB, Ive got this error : the device is not ready
I've read your faq and you talking about bad usb connexion, it's not the case, at least for me
I solved the problem, with diskpart and automount
In a prompt, type:

diskpart
automount enable
exit

When automount is disabled, I have the error
When automount is enabled , everything is fine

So if you experience the same issue, can you please write it in your FAQ.
thanks
@pbatard
Copy link
Owner

pbatard commented Oct 20, 2014

Thanks for the tip! I'll try to add it to the FAQ, but before that, I'd like to try to reproduce the problem when automount is off, which I haven't managed to do in Windows 8.1 x64.

Would it be possible for you to send me a complete log from Rufus for when the issue occurs on your computer? Having a full log will tell me which OS as well as the name of the ISO you tried to use (or the formatting options if you didn't use an ISO).

If I could replicate the issue, I might be able to add a fix for it in a future version of Rufus, which is why the more information I can get about your system, the easier it will be for me to replicate the error and try to add a fix.

@pbatard pbatard self-assigned this Oct 20, 2014
@jimini24
Copy link
Author

of course!

First I use diskpart and type "automount disable"
I obtain this log

Rufus version: 1.4.10.514
Syslinux versions: 4.07/2013-07-25, 5.10/2013-06-04
Windows version: Windows 7 64-bit
Locale ID: 0x040C
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Using autorun.inf label for drive I: 'NEW'
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x000C33DB
Drive has a Rufus Master Boot Record
Partition 1:
  Type: NTFS (0x07)
  Size: 14.9 GB (16007561216 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes
Scanning image...
Disc image is an ISO9660 image
Will use /isolinux/isolinux.cfg for Syslinux
Detected Isolinux version: 4.05/20120131 (from '/isolinux/isolinux.bin')
ISO label: 'Redo Backup'
  Size: 261062656 bytes
  Has a >64 chars filename: No
  Has Symlinks: No
  Has a >4GB file: No
  Uses ReactOS: No
  Uses KolibriOS: No
  Uses EFI: No
  Uses Bootmgr: No
  Uses WinPE: No
  Uses isolinux: Yes (4.05)
    With an old menu.c32: No
    With an old vesamenu.c32: No
Using ISO: redobackup-livecd-1.0.4.iso

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE2 for write access
Will use 'I:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Rufus Master Boot Record
Volume has an unknown Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 8192 bytes
Quick format was selected
The device is not ready
Format error: The device is not ready.
Re-mounted volume as 'I:' after error

Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Using autorun.inf label for drive I: 'NEW'
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0003F9C8
Drive has a Zeroed Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16007561216 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Using autorun.inf label for drive I: 'NEW'
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0003F9C8
Drive has a Zeroed Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16007561216 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

after that I just change diskpart to "automount enable" and
I obtain this one

Rufus version: 1.4.10.514
Syslinux versions: 4.07/2013-07-25, 5.10/2013-06-04
Windows version: Windows 7 64-bit
Locale ID: 0x040C
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Using autorun.inf label for drive I: 'NEW'
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0003F9C8
Drive has a Zeroed Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16007561216 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes
Scanning image...
Disc image is an ISO9660 image
Will use /isolinux/isolinux.cfg for Syslinux
Detected Isolinux version: 4.05/20120131 (from '/isolinux/isolinux.bin')
ISO label: 'Redo Backup'
  Size: 261062656 bytes
  Has a >64 chars filename: No
  Has Symlinks: No
  Has a >4GB file: No
  Uses ReactOS: No
  Uses KolibriOS: No
  Uses EFI: No
  Uses Bootmgr: No
  Uses WinPE: No
  Uses isolinux: Yes (4.05)
    With an old menu.c32: No
    With an old vesamenu.c32: No
Using ISO: redobackup-livecd-1.0.4.iso

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE2 for write access
Will use 'I:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Volume has an unknown Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 8192 bytes
Quick format was selected
Creating file system: Task 1/5 completed
Creating file system: Task 2/5 completed
Creating file system: Task 3/5 completed
Creating file system: Task 4/5 completed
Creating file system: Task 5/5 completed
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Partition is already FAT32 LBA...
Set bootable USB partition as 0x80
Using Syslinux MBR
Found volume GUID \\?\Volume{2d3b8c28-585f-11e4-9528-e0cb4e00bd06}\
\\?\Volume{2d3b8c28-585f-11e4-9528-e0cb4e00bd06}\ was already mounted as I:\
Installing Syslinux 4.05...
Successfully wrote 'ldlinux.sys'
Opened drive \\?\Volume{2d3b8c28-585f-11e4-9528-e0cb4e00bd06} for write access
Successfully wrote Syslinux boot record
Successfully remounted Volume{2d3b8c28-585f-11e4-9528-e0cb4e00bd06}\ on I:\
Copying ISO files...
Extracting files...
libcdio: Found Extension: Joliet Level 3
Disc image is an ISO9660 image
This image will be extracted using Joliet extensions (if present)
Extracting: I:\.disk\base_installable (0 bytes)
Extracting: I:\.disk\cd_type (15 bytes)
Extracting: I:\.disk\info (13 bytes)
Extracting: I:\.disk\release_notes_url (22 bytes)
Extracting: I:\README.diskdefines (183 bytes)
Extracting: I:\autorun.exe (81.8 KB)
Extracting: I:\autorun.inf (81 bytes)
Extracting: I:\casper\filesystem.manifest (16.4 KB)
Extracting: I:\casper\filesystem.manifest-desktop (16.3 KB)
Extracting: I:\casper\filesystem.size (9 bytes)
Extracting: I:\casper\filesystem.squashfs (224.1 MB)
Extracting: I:\casper\initrd.lz (19.7 MB)
Extracting: I:\casper\vmlinuz (4.6 MB)
Extracting: I:\install\memtest (172.6 KB)
Extracting: I:\isolinux\bg_redo.png (115.8 KB)
Extracting: I:\isolinux\boot.cat (2 KB)
Extracting: I:\isolinux\help.txt (1.4 KB)
Extracting: I:\isolinux\isolinux.bin (24 KB)
Extracting: I:\isolinux\isolinux.cfg (2.0 KB)
Extracting: I:\isolinux\vesamenu.c32 (152.1 KB)
Extracting: I:\md5sum.txt (1.1 KB)
Extracting: I:\ubuntu (0 bytes)
Created: I:\syslinux.cfg
Finalizing, please wait...
I:autorun.inf already exists - keeping it

Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
Using autorun.inf label for drive I: 'Redo Backup and Recovery'
1 device found
Disk type: Fixed, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0006EED0
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16007561216 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

When I had this issue, I didn't know my system was switch (alone?) to automount disable
so I'd try a few iso with the same issue, and didn't found the solution on google.

a few hours later I'd realize that automount was off, and so, I decide to try again rufus,

this software has almost goes to the trash for me (lol), cause it was the first time I used it

Anyway if it can help, I'm glad, and thanks for this useful software

@pbatard
Copy link
Owner

pbatard commented Oct 21, 2014

Thanks for the logs. Still haven't had any luck replicating the issue using redobackup-livecd-1.0.4.iso on Windows 8.1 x64 and with automount disable. I'll try to run some tests on Windows 7 to see if it's something specific to that OS, and if I still can't get the issue to manifest itself, I'll add a note in the FAQ.

@jimini24
Copy link
Author

jimini24 commented Nov 9, 2014

Hi, I found another reason for the issue appears.
As you can see in my previous log, the usb disk type is "fixed".That's why.

I try with a kingston "removable" disk type, it's work even with automount disable
but with "fixed" disk type and automount disable it definitly don't work.

You Can recognize an usb "removable" or "fixed" with diskpart and command "list volume".
the type (5th column) is seen as "partition", for fixed usb stick, it's like a harddrive.
for removable device dispart see type as "removable".

a good thing to know is sometimes (or always?) you can't install windows7 from a removable usb stick, but you can with one fixed, there is lot of thread about this, but few answer
http://www.sevenforums.com/installation-setup/333243-setup-unable-create-new-system-partition-new-ssd.html

Here is my working log with removable device and automount disable

Rufus version: 1.4.10.514
Syslinux versions: 4.07/2013-07-25, 5.10/2013-06-04
Windows version: Windows 7 64-bit
Locale ID: 0x040C
Found USB 2.0 device 'Kingston DataTraveler 3.0 USB Device' (0951:1666)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 1913, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x001D3C93
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.7 GB (15735980032 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes
Scanning image...
Disc image is an ISO9660 image
Will use /isolinux/isolinux.cfg for Syslinux
Detected Isolinux version: 4.05/20120131 (from '/isolinux/isolinux.bin')
ISO label: 'Redo Backup'
  Size: 261062656 bytes
  Has a >64 chars filename: No
  Has Symlinks: No
  Has a >4GB file: No
  Uses ReactOS: No
  Uses KolibriOS: No
  Uses EFI: No
  Uses Bootmgr: No
  Uses WinPE: No
  Uses isolinux: Yes (4.05)
    With an old menu.c32: No
    With an old vesamenu.c32: No
Using ISO: redobackup-livecd-1.0.4.iso

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE3 for write access
Will use 'K:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Syslinux Master Boot Record
Volume has an unknown Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 8192 bytes
Quick format was selected
Creating file system: Task 1/5 completed
Creating file system: Task 2/5 completed
Creating file system: Task 3/5 completed
Creating file system: Task 4/5 completed
Creating file system: Task 5/5 completed
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Partition is already FAT32 LBA...
Set bootable USB partition as 0x80
Using Syslinux MBR
Found volume GUID \\?\Volume{a7e4393d-644e-11e4-990b-e0cb4e00bd06}\
Installing Syslinux 4.05...
Successfully wrote 'ldlinux.sys'
Opened drive \\?\Volume{a7e4393d-644e-11e4-990b-e0cb4e00bd06} for write access
Successfully wrote Syslinux boot record
Successfully remounted Volume{a7e4393d-644e-11e4-990b-e0cb4e00bd06}\ on K:\
Copying ISO files...
Extracting files...
libcdio: Found Extension: Joliet Level 3
Disc image is an ISO9660 image
This image will be extracted using Joliet extensions (if present)
Extracting: K:\.disk\base_installable (0 bytes)
Extracting: K:\.disk\cd_type (15 bytes)
Extracting: K:\.disk\info (13 bytes)
Extracting: K:\.disk\release_notes_url (22 bytes)
Extracting: K:\README.diskdefines (183 bytes)
Extracting: K:\autorun.exe (81.8 KB)
Extracting: K:\autorun.inf (81 bytes)
Extracting: K:\casper\filesystem.manifest (16.4 KB)
Extracting: K:\casper\filesystem.manifest-desktop (16.3 KB)
Extracting: K:\casper\filesystem.size (9 bytes)
Extracting: K:\casper\filesystem.squashfs (224.1 MB)
Extracting: K:\casper\initrd.lz (19.7 MB)
Extracting: K:\casper\vmlinuz (4.6 MB)
Extracting: K:\install\memtest (172.6 KB)
Extracting: K:\isolinux\bg_redo.png (115.8 KB)
Extracting: K:\isolinux\boot.cat (2 KB)
Extracting: K:\isolinux\help.txt (1.4 KB)
Extracting: K:\isolinux\isolinux.bin (24 KB)
Extracting: K:\isolinux\isolinux.cfg (2.0 KB)
Extracting: K:\isolinux\vesamenu.c32 (152.1 KB)
Extracting: K:\md5sum.txt (1.1 KB)
Extracting: K:\ubuntu (0 bytes)
Created: K:\syslinux.cfg
Finalizing, please wait...
K:autorun.inf already exists - keeping it

Found USB 2.0 device 'Kingston DataTraveler 3.0 USB Device' (0951:1666)
Using autorun.inf label for drive K: 'Redo Backup and Recovery'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 1913, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0026D94E
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.7 GB (15735980032 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

Hope now you can replicate this bug and correct the FAQ

@pbatard
Copy link
Owner

pbatard commented Nov 10, 2014

Aha!
Thank you so much for following up on this and identifying the missing part.
I was also able to replicate the issue when using a fixed disk (PS: The Rufus log also tells you if a disk is seen as fixed or removable).

I'm also gonna make a note of the following issue that occurs with automount enable when trying to format a drive that didn't get formatted because of automount disable:

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE8 for write access
Will use 'E:' as volume mountpoint
Analyzing existing boot records...
Drive has a Zeroed Master Boot Record
Volume does not have an x86 Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 2176 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Timeout while waiting for logical drive
Formatting (Large FAT32)...
No logical drive found (unpartitioned?)
Invalid logical volume handle
Format error: The device handle is invalid.

I'll see what I can do to fix both these issue in a future version.
And I'll add a new entry in the FAQ about this problem when I get a chance.
Many thanks for spending time investigating this issue - it really helps!

@pbatard pbatard added this to the 1.5.0 milestone Nov 10, 2014
@pbatard
Copy link
Owner

pbatard commented Nov 10, 2014

OK, I have now added an entry in the FAQ with details of the workaround:
https://github.com/pbatard/rufus/wiki/FAQ#Error_0x00000015_The_device_is_not_ready

@pbatard
Copy link
Owner

pbatard commented Nov 10, 2014

Just an addon: It looks like mountvol /e will work just as well as automount enable in diskpart. Since this is simpler, and less dangerous that asking users to run diskpart, this is what I will advise in the FAQ.

@lock
Copy link

lock bot commented Apr 7, 2019

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.

@lock lock bot locked and limited conversation to collaborators Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pbatard pbatard

Labels
None yet
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
2 participants
@pbatard @jimini24