Workaround for error 2 and 1117

Bug #1478406 reported by BJ Stigall
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Image Writer
Fix Released
High
Unassigned

Bug Description

I found what could be a workaround for error 1117.

after inserting the SD card into the system, go into DISKPART.

at the diskpart prompt enter:
automount disable

image your SD card. after imaging the sd card, enter:
automount enable

the above will temporarily disable automount so the program can complete the imaging. I don't know if there is a way for you to do this programmatically.

I had to run a "automount scrub" for some reason also, but I don't know why.

I did this on Windows 10 build10240.

Revision history for this message
Tobin Davis (gruemaster) wrote :

Excellent feedback, thank you. This gives us a reference point to start looking for a programmatic solution.

Not sure when we will be able to implement this though, as neither of us have any spare development time at the moment. Marking it high priority though.

Changed in win32-image-writer:
importance: Undecided → High
Tobin Davis (gruemaster)
Changed in win32-image-writer:
status: New → Triaged
Revision history for this message
Adam (snowwbound) wrote :

This workaround did not work for me, it was very promising :(

diskpart -> automount disable

Still getting the dreadful error message:
Getting Error 1117: The request could not be performed because of an I/O device error.

Dell Latitude E7450
RASPBERRY PI OEM SD card.
Running Windows 10 build 10586.218.
Win32DiskImager v0.9.5 running application as Administrator.

If I insert it into my Raspberry it the SD card works and boots into Raspbian no issues.

Revision history for this message
Adam (snowwbound) wrote :

Forgot to note that I get to about 10% and then the error message pops up and the application crashes.

Revision history for this message
BJ Stigall (bj-stigall) wrote : RE: [Bug 1478406] Re: Workaround for error 2 and 1117

Did you try the automount scrub command?

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Adam
Sent: Saturday, May 7, 2016 8:59 AM
To: Stigall, BJ - Junk Mail <email address hidden>
Subject: [Bug 1478406] Re: Workaround for error 2 and 1117

Forgot to note that I get to about 10% and then the error message pops up and the application crashes.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1478406

Title:
  Workaround for error 2 and 1117

Status in Image Writer:
  Triaged

Bug description:
  I found what could be a workaround for error 1117.

  after inserting the SD card into the system, go into DISKPART.

  at the diskpart prompt enter:
  automount disable

  image your SD card. after imaging the sd card, enter:
  automount enable

  the above will temporarily disable automount so the program can
  complete the imaging. I don't know if there is a way for you to do
  this programmatically.

  I had to run a "automount scrub" for some reason also, but I don't
  know why.

  I did this on Windows 10 build10240.

To manage notifications about this bug go to:
https://bugs.launchpad.net/win32-image-writer/+bug/1478406/+subscriptions

Revision history for this message
Adam (snowwbound) wrote :

Yep, tried automount scrub, didn't seem to work.

I also have paragon ExtFS installed, which I also unmounted the drives and then turned off Auto Mount on it's application but still having issues.

I'm perplexed :(

Revision history for this message
Tobin Davis (gruemaster) wrote :

I'll double check the code for 0.9.5, but the current code 'should' unmount the volume before reading/writing to the raw physical device. I need to do more testing on this (volunteers???), but it should work, at least according to the MSDN documentation.

Tobin Davis (gruemaster)
Changed in win32-image-writer:
status: Triaged → Fix Released
Revision history for this message
R. S. (raflmaster) wrote :

My solution for the I/O-Error was to use an other USB-Port. Pretty trivial, nevertheless I hope it helps some folks ;)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.