I just wanted to save my Samsung Fit 64GB USB-Stick with Openmediavault and get an Error writing on my local drive.
Any hints?
Verify Backup/Restore: Always with Error
-
- Site Admin
- Posts: 284
- Joined: Fri Jul 29, 2011 11:59 pm
Re: Verify Backup/Restore: Always with Error
Can you provide details about the error? Did you get an error message/code? Do you have logs? Has the backup or verification process been interrupted by something?
-
- Posts: 4
- Joined: Tue Feb 25, 2025 6:47 pm
Re: Verify Backup/Restore: Always with Error
Hi Alex and thanks a lot for your fast answer.
What details do you need exactly?
I'll have another try restoring a USB-Stick backup successfully and give you the data needed.
-
- Site Admin
- Posts: 284
- Joined: Fri Jul 29, 2011 11:59 pm
Re: Verify Backup/Restore: Always with Error
If an error occurs, USB Image Tool displays a message. What is this message displaying? Did the verification stop somewhere in the middle or directly at the beginning? USB Image Tool has two logs (Log and Debug tab). Please copy that with the button provided there and either send it by mail (text files if possible). Screenshots can help as well.
Another note: There are several fake USB sticks out there, so be sure your device is a genuine one. Fakes often have wrong size information (bige size for cheap prize), you don't notice until they are filled above the real limit. Verfication may fail on these as well. USB Image Tool has a built in check for fake sizes, but this will erase all data on your flash drive.
Another note: There are several fake USB sticks out there, so be sure your device is a genuine one. Fakes often have wrong size information (bige size for cheap prize), you don't notice until they are filled above the real limit. Verfication may fail on these as well. USB Image Tool has a built in check for fake sizes, but this will erase all data on your flash drive.
-
- Posts: 4
- Joined: Tue Feb 25, 2025 6:47 pm
Re: Verify Backup/Restore: Always with Error
The error is: Device an image are different.
It popped up after verifying 3%.
I used two different USB-Sticks, an SAMSUNG Fit Plus and a PNY Attaché 4, both with 64GB.
LOG:
DEBUG:
It popped up after verifying 3%.
I used two different USB-Sticks, an SAMSUNG Fit Plus and a PNY Attaché 4, both with 64GB.
LOG:
Code: Select all
I 27.02.2025 20:12:24 00000002 USB DISK 3.2 USB Device: Device added to device list!
A 27.02.2025 20:12:48 00000002 USB DISK 3.2 USB Device: Restore started!
I 27.02.2025 20:12:49 00000000 Device change notification received!
I 27.02.2025 20:12:49 00000002 USB DISK 3.2 USB Device: Device added to device list!
A 27.02.2025 20:14:30 00000002 USB DISK 3.2 USB Device: Restore finished successfully!
A 27.02.2025 20:14:30 00000002 USB DISK 3.2 USB Device: Verify started!
I 27.02.2025 20:15:54 00000000 Device change notification received!
E 27.02.2025 20:15:54 00000002 USB DISK 3.2 USB Device: Verify failed! Device and image are different!
I 27.02.2025 20:15:54 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:15:55 00000000 Device change notification received!
I 27.02.2025 20:15:55 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:15:55 00000000 Device change notification received!
I 27.02.2025 20:15:55 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:15:55 00000000 Device change notification received!
I 27.02.2025 20:15:55 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:15:55 00000000 Device change notification received!
I 27.02.2025 20:15:55 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:15:55 00000000 Device change notification received!
I 27.02.2025 20:15:55 00000002 USB DISK 3.2 USB Device: Device added to device list!
I 27.02.2025 20:23:25 00000002 USB DISK 3.2 USB Device: Device added to device list!
Code: Select all
FD01: \\?\scsi#disk&ven_nvme&prod_wdc_pc_sn730_sdb#5&a624e6b&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: WDC PC SN730 SDBQNTY-512G-1001
FD04: Device ID is SCSI\DISK&VEN_NVME&PROD_WDC_PC_SN730_SDB\5&A624E6B&0&000000
FD05: Media Type is 12
FD06: Location PCI-Bus 61, Gerät 0, Funktion 0
FD07: Hardware ID PCI\VEN_15B7&DEV_5006&SUBSYS_500615B7&REV_00
FD08: Device Number is 0
FD01: \\?\usbstor#disk&ven_&prod_usb_disk_3.2&rev_3.00#fc307a890951b&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
FD02: USB DISK 3.2 USB Device
FD04: Device ID is USBSTOR\DISK&VEN_&PROD_USB_DISK_3.2&REV_3.00\FC307A890951B&0
FD05: Media Type is 11
FD06: Location Port_#0004.Hub_#0001
FD07: Hardware ID USB\VID_346D&PID_5678&REV_0200
FD08: Device Number is 1
FD09: FOUND!
FV01: \\?\storage#volume#{1cddf19d-abe1-11ee-8f29-806e6f6e6963}#0000000008100000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0
FV01: \\?\storage#volume#{1cddf19d-abe1-11ee-8f29-806e6f6e6963}#000000000e500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 0
FV01: \\?\storage#volume#_??_usbstor#disk&ven_&prod_usb_disk_3.2&rev_3.00#fc307a890951b&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
FV02: Device number is 1
FV03: Volume match Port_#0004.Hub_#0001
FV04: Partition number is 1
FV08: Volume information for \\?\Volume{53fdb118-f38b-11ef-8f56-ac675df10206}\ unknown! Partition type is 0x04.
FV09: UNKNOWN!
-
- Site Admin
- Posts: 284
- Joined: Fri Jul 29, 2011 11:59 pm
Re: Verify Backup/Restore: Always with Error
Thanks for the logs. Looks like the verification is detecting a difference for some reason. I will try to reproduce the issue.
-
- Posts: 4
- Joined: Tue Feb 25, 2025 6:47 pm
Re: Verify Backup/Restore: Always with Error
Thanks a lot for helping Alex
-
- Site Admin
- Posts: 284
- Joined: Fri Jul 29, 2011 11:59 pm
Re: Verify Backup/Restore: Always with Error
Quick update: I was able to reproduce the bug with the logs. The verification reports a false error when restore target device and image file have a different size. Will fix this in the next days with a new version. Thanks for reporting.
-
- Site Admin
- Posts: 284
- Joined: Fri Jul 29, 2011 11:59 pm
Re: Verify Backup/Restore: Always with Error
The issue was fixed with new version 1.91.