Hi Carlo (70 Amiga User) I am also the developer of AROS One x86, some years I had ask

Please go to <a class="issue-link js-issue-link" data-error-text="Failed to load title

Read error: [0x0000001B] The drive cannot find the sector requested when writing VHD image,about pbatard/rufus

Comments (24)

AMIGASYSTEM commented on June 2, 2024 1

Ok thanks I will no longer ZIP compress the VHD images, I was doing it to speed up the Download

I attach Log Error AROS One Image-USB-2.4.zipper with Rufus 4

Rufus x64 v4.4.2103
Windows version: Windows 10 Pro x64 (Build 19045.4046)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.06
System locale ID: 0x0410 (it-IT)
Will use default UI locale 0x0410
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'it-IT'
Found 517 officially revoked UEFI bootloaders from embedded list
Found 2351 additional revoked UEFI bootloaders from this system's SKUSiPolicy.p7b
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
1 device found
No volume information for drive 0x81
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No
Scanning image...
ISO analysis:
  'C:\Users\Win10\Desktop\AROS One Image-USB-2.3.vhd' doesn't look like an ISO image
Disk image analysis:
  Image is a bootable VHD image
Using image: AROS One Image-USB-2.3.vhd (3.7 GB)
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
1 device found
No volume information for drive 0x81
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No

Format operation started
Requesting disk access...
Will use 'E:' as volume mountpoint
Opened \\.\PhysicalDrive1 for exclusive write access
Requesting logical volume handle...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Read error: [0x0000001B] (NB: This system was unable to provide an English error message)
Opened \\.\PhysicalDrive1 for shared write access
Re-mounted volume as E: after error

Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
1 device found
No volume information for drive 0x81
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No
Found USB 2.0 device 'SanDisk Cruzer Blade USB Device' (0781:5567)
1 device found
No volume information for drive 0x81
Disk type: Removable, Disk size: 8 GB, Sector size: 512 bytes
Cylinders: 973, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No
Closed Windows format prompt

from rufus.

pbatard commented on June 2, 2024 1

Thanks. It looks like I am finally able to replicate the error (not sure why I didn't get it earlier on).

Let me investigate this so I can figure out where it comes from.

from rufus.

pbatard commented on June 2, 2024 1

This will be fixed in the next version. This is actually a benign error and the resulting drive contains all the data.

Ironically, I'm pretty sure you only got this error because you worked with the uncompressed VHD and not the zipped version, and I sure wish I had had your log right from the start so that I could see that you were opening the .vhd and not the .zip.

At any rate, thanks for the report, but next time, please do follow the check list, as it's only there to help you get your problem sorted in the most timely manner, by avoiding a lot of unnecessary back and forth.

from rufus.

pbatard commented on June 2, 2024 1

if you need it I'll take a screenshot.

Can you please send me your log instead? Again, I very much need to see your full log whenever you think you encounter an issue, as a screenshot is next to useless, as it tells me practically nothing outside of "Yup, you are seeing an error", which I don't doubt, but which I will have a very hard time to try to replicate and fix unless you provide a full log...

from rufus.

pbatard commented on June 2, 2024

Hi Carlo,

Can you elaborate on your "are no longer compatible with Rufus 4.x" statement? What error do you see, and where does it happen?

I am not seeing any issue writing the AROS One Image-USB-2.4.zip with Rufus 4.4, and since it's a VHD image, whatever happens after Rufus wrote the image should have to do with the content of the image itself and not with Rufus.

In short, as much as I'd like to help, I'm afraid you're not providing enough details with regards to the exact nature of the issue you see, so more details would be welcome...

from rufus.

AMIGASYSTEM commented on June 2, 2024

Hi Pete, with Rufus 4.4 the error appears at the end of writing, see screenshot "Read Error" The problem appears on 2 PCs with Win10 64Bit, also tried 3 different Pendivers of 4GB and 8 GB On the same PCs if I use Rufus 3.2 instead, nope problem the write happens correctly. To the vice versa: If I use Rufus 4.4 to clone the Pendrive, the USB image created, I can write it with Rufus 3.x perfectly, no error Good Night CarloMessage ID: ***@***.***>

from rufus.

pbatard commented on June 2, 2024

Please go to #2468 and attach the screenshot there, as screenshots sent through e-mail replies are not attached, and nobody but you can see them.

Also, as requested in the checklist you were asked to follow when opening the issue, it is MUCH BETTER, if you want your issue to be properly investigated, to attach the log from Rufus (the checklist tells you explicitly how to access it), as screenshots are next to worthless when I cannot replicate an issue, as is the case here.

For instance, here's my log writing AROS One Image-USB-2.4.zip with Rufus 4.4 on Windows 11:

Rufus x64 v4.4.2103
Windows version: Windows 11 Pro for Workstations x64 (Build 22631.3527)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.06
System locale ID: 0x0809 (en-GB)
Will use default UI locale 0x0809
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'en-US'
Found 517 officially revoked UEFI bootloaders from embedded list
Found 2351 additional revoked UEFI bootloaders from this system's SKUSiPolicy.p7b
Found USB device 'Mushkin Ventura Ultra USB Device' (174C:55AA) [ID]
1 device found
Disk type: FIXED, Disk size: 120 GB, Sector size: 512 bytes
Cylinders: 14593, Tracks per cylinder: 255, Sectors per track: 63
Partition type: GPT, NB Partitions: 1
Disk GUID: {5E972E5D-6AA2-4108-88C5-4DDAF3F3313A}
Max parts: 128, Start Offset: 17408, Usable = 120034089472 bytes
Partition 1:
  Type: EFI System Partition
  Name: 'Blah'
  Detected File System: FAT32
  ID: {CDFBD781-63DF-4C5C-9496-6325E9A364FA}
  Size: 8.0 GB (8587951616 bytes)
  Start Sector: 2048, Attributes: 0xD000000000000005
Scanning image...
ISO analysis:
  'D:\Imgs\AROS One Image-USB-2.4.zip' doesn't look like an ISO image
Disk image analysis:
  Image is a compressed bootable disk image
Using image: AROS One Image-USB-2.4.zip (1.9 GB)
Timeout while retrieving conflicting process list

Format operation started
Requesting disk access...
No drive letter was assigned...
Will use 'F:' as volume mountpoint
Opened \\.\PhysicalDrive9 for exclusive write access
Requesting logical volume handle...
No logical drive found (unpartitioned?)
Writing compressed image:
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Opened \\.\PhysicalDrive9 for shared write access
Timeout while waiting for logical drive

Found USB device 'Mushkin Ventura Ultra USB Device' (174C:55AA) [ID]
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x89
Disk type: FIXED, Disk size: 120 GB, Sector size: 512 bytes
Cylinders: 14593, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No

For the record, Timeout while waiting for logical drive is expected for file systems that are unrecognized, and it is not an error. And as you can see, I do not get any read-error.

Now, my guess is that the issue you may be facing probably has to do with the fact that you are using a VHD image, which is NOT a flat disk image, as it contains an additional 512 bytes of data, which you are trying to restore to a drive of the exact same size as the one you used to create the VHD. If you do that, then, these extra 512 bytes should produce an error because you are effectively using a VHD in lieu of a compressed flat disk image, and this is not something Rufus can support (the fact that it might have somehow worked before is no guarantee that it should ever have been supported), and you need to decide as to whether you want to use a proper compressed flat disk image, in which case it should just be that (i.e. not a VHD with the extract 512 bytes, but the part before that) in a zip file, or a proper compressed Microsoft VHD image, a.k.a. a VHDX. You simply cannot have it both way, because Rufus was only ever designed to support flat disk images inside of compressed archive, and any support of VHD inside of an archive would have been an accident that has been rectified, and that I have no plan to "revert".

In short: Do not zip uncompressed VHD images and expect software to be able to handle those. Either compress a pure .img or use a .vhdx.

from rufus.

AMIGASYSTEM commented on June 2, 2024

Thanks for the advice Pete, unfortunately I cannot use the VHDX format, if I try to create a Pendrive Image I get the same error you see in the screenshot attached below "Read Error" attach log

Rufus x64 v4.4.2103
Windows version: Windows 10 Pro x64 (Build 19045.4046)
Syslinux versions: 4.07/2013-07-25, 6.04/pre1
Grub versions: 0.4.6a, 2.06
System locale ID: 0x0410 (it-IT)
Will use default UI locale 0x0410
SetLGP: Successfully set NoDriveTypeAutorun policy to 0x0000009E
Localization set to 'it-IT'
Found 517 officially revoked UEFI bootloaders from embedded list
Found 2351 additional revoked UEFI bootloaders from this system's SKUSiPolicy.p7b
Found USB 2.0 device 'General USB Flash Disk USB Device' (8633:800A)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 4GB, Sector size: 512 bytes
Cylinders: 487, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No
Scanning image...
ISO analysis:
  'C:\Users\Win10\Desktop\AROS-One.vhdx' doesn't look like an ISO image
Disk image analysis:
  Image is a bootable VHD image
Using image: AROS-One.vhdx (3.8 GB)
Found USB 2.0 device 'General USB Flash Disk USB Device' (8633:800A)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 4GB, Sector size: 512 bytes
Cylinders: 487, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No

Format operation started
Requesting disk access...
No drive letter was assigned...
Will use 'E:' as volume mountpoint
Opened \\.\PhysicalDrive1 for exclusive write access
Requesting logical volume handle...
No logical drive found (unpartitioned?)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Read error: [0x0000001B] (NB: This system was unable to provide an English error message)
Opened \\.\PhysicalDrive1 for shared write access

Found USB 2.0 device 'General USB Flash Disk USB Device' (8633:800A)
No logical drive found (unpartitioned?)
1 device found
No volume information for drive 0x81
Disk type: FIXED, Disk size: 4GB, Sector size: 512 bytes
Cylinders: 487, Tracks per cylinder: 255, Sectors per track: 63
Partition type: MBR, NB Partitions: 2
Disk ID: 0x000A86CB
Drive has an unknown Master Boot Record
Partition 1:
  Type: Extended (0x05)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011393024 bytes)
  Start Sector: 192, Boot: Yes
Partition 5:
  Type: Unknown (0x30)
  Detected File System: (Unrecognized)
  Size: 3.7 GB (4011196416 bytes)
  Start Sector: 576, Boot: No

Strange though that with Rufus 3.2 I never had any problem with all the USB VHD images created so far, I have created many AROS One Images (Many versions) and all compacted in ZIP and never had any problem.

Regarding the strange screenshot that on your E-Mail does not show the screenshots, I on my E-mails never had any problem to display the screenshots attached to my E-mail !

Anyway I attach link with the screenshot showing the error

https://i.ibb.co/rm8L4c9/Rufus-Error.jpg

from rufus.

pbatard commented on June 2, 2024

VHDX is a different issue that will be fixed in the next release. Please show me the log from when you use the official AROS One Image-USB-2.4.zip you told me had a problem. VHDX could not be created with Rufus 3.x (this is a very new feature which is why I am still fixing bugs with it), and your original issue was, I quote:

USB Images (Pendrive) created with Rufus 3.x are no longer compatible with Rufus 4.x

(which by the way is inaccurate since Rufus does not create zipped VHD, so if you do zip a .vhd created by Rufus, you are not dealing with an image that was created by Rufus).

So can I please have the log of what Rufus reports when you write AROS One Image-USB-2.4.zip?

As to e-mail attachments, please bear in mind that I do not receive your e-mail replies directly. Instead, GitHub receives them, processes the content (and strips any attachment), generates a GitHub issue update, and once that issue update has been added, it generates an e-mail notification from the update, and not from your original e-mail.

At any rate, screenshots when reporting issue are next to worthless. Please consider them the same as a picture of a body taken by the police at a crime scene. It'll just confirm that somebody is dead, and maybe give some hints, but it's pretty much never enough to tell you exactly what happened. On the other hand, the log is like CCTV footage of the crime scene when the murder happened, and it is invaluable of telling you the sequence of event of how the crime happened, as well as who committed it.

Which is why, when an application does include logging, and the developer asks you for a log, you shouldn't ignore their request and think a mere screenshot will be good enough...

from rufus.

AMIGASYSTEM commented on June 2, 2024

Hi Pete I tested the new version 4.5 beta, the request error is now gone, the "Burning" of the Pendrive image is now done correctly. But be careful, with Rufus 4.5 beta the images created in the "VHDX" format, if you then try to burn, a request warns that the image is not supported by Rufus, if you need it I'll take a screenshot. If instead with Rufus 4.5 I create a VHD Image, the "Live Pendrive" boots, shows the Grub, but then the partition is not detected (it stops at the AROS "Cat Eyes" logo) If I use Rufus 3.2 the VHD Image created by Rufus 4.5 also works fine, the Live Pendrive boots correctly and shows the Operating System. Greetings Carlo Message ID: ***@***.***>

from rufus.

AMIGASYSTEM commented on June 2, 2024

I am sending you 4 logs Rufus 4.5 Burn Image VHD created with Rufus 4.5 Rufus 4.5 Burn Image VHDX created with Rufus 4.5 Rufus 4.5 Burn Image VHD create con Rufus 3.2 Rufus 3.20p Burn Image VHD create con Rufus 3.20p (Ok This Live Pendrive works fine) Allega il file di registro dell'archivio ID messaggio: <pbatard/rufus/issues/2468/2105869548 @ github . com>

from rufus.

pbatard commented on June 2, 2024

As I explained earlier, sending log as attachments will not work, because you are sending them to a GitHub bot which will discard them.

You need to log on to GitHub and attach them to the issue using the web interface if you want them to be shared.

At any rate, I think I have found the issue, and I will fix it, but I wouldn't mind to see the logs to make sure that I am addressing the same thing, rather than have you come back after the Rufus 4.5 release to tell me you're still seeing a problem.

from rufus.

AMIGASYSTEM commented on June 2, 2024

I attach the Logs here, fifth Log added

Rufus 3.20p Burn Image VHD create con Rufus 4.5 (Ok This Live Pendrive works fine)

Logs.zip

from rufus.

pbatard commented on June 2, 2024

Thanks. I believe the fix I am going to push, and which will be part of the 4.5 release, should address the issue.

from rufus.

Read error: [0x0000001B] The drive cannot find the sector requested when writing VHD image about rufus HOT 24 CLOSED

Comments (24)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent