Fix errors when unplugging a drive exactly when the drive scanning script runs
See original GitHub issueSteps to reproduce:
- Unplug a drive exactly when the drive scanning script is running
You might want to add console.log
above https://github.com/resin-io/etcher/blob/master/lib/gui/modules/drive-scanner.js#L41 to know when exactly the script is running, or decrease the drive scanning interval to increase the chances: https://github.com/resin-io/etcher/blob/master/lib/gui/modules/drive-scanner.js#L36
This is the error I get:
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Fix Scanning and Repairing Drive Stuck - Tenorshare 4DDiG
Fix 1: Check the Drive Status · Fix 2: Use Windows Error Checking Tool · Fix 3: Wait for the Completion of Scanning...
Read more >There Is a Problem with This Drive. Scan the Drive Now and ...
There's a Problem with This Drive FAQs · 1. Right-click the USB drive or SD card and select Properties from its context menu....
Read more >Stop scanning and repairing (G:): external drive?
On startup it continued, and after a while I noticed it had started the process of Scanning and repairing drive (G:): 0% complete....
Read more >“There's a Problem with This Drive” Issue and How to Fix It
Method #1: Continue Without Scanning · Method #2: Scan and Fix · Method #3: Enable Quick Removal · Method #4: Disk Error Checking...
Read more >External Disk Drive Suddenly Became RAW - Unknown Kadath
Now you should make backups of all important files on the drive in case it goes bad again and then run chkdsk to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK, so we were not passing the VBScript exit code to the caller from within the
.bat
wrapper. I’ll send a PR todrivelist
in a minute. This is what I get after my changes:Adding a timeout, as @lurch suggested, revealed the following on Linux: