[0xC0030002] The system cannot find the file specified. #1778
Comments
|
Can you please run a bad blocks check (which you can do with Rufus) and post the result. The most common suspect for that issue would be bad flash memory, so this needs to be eliminated first. |
Progress had gone to 60% and no errors what so ever, I will obviously run it to the end, but I don't think bad blocks is an issue in this case |
|
Well, the number of |
The log with the Non-Bootable boot option selected and still getting the error, but no bad blocks were found |
|
Okay. The fact that it's always the same block that the error is being produced (4620290 * 4096 = block around the 18 GB mark in the 20 GB persistent partition) would also indicate that it's not a hardware error. The error being returned however appears to indicate that the handle to the drive has been invalidated by the system (i.e. this is an error that you'd expect to see if the drive was somehow unplugged) and I think I have seen it once or twice in the early days of adding the persistent feature, when I was trying to work at the partition level instead of at the whole drive level, with Windows somehow declaring that a partition it cannot read should be removed from the system after some time (hence the reason why I switched to working at the whole drive level, because the drive should never get removed). But then the failure would happen at a random sector, and I have not seen it since these early days. I'm afraid it's going to be difficult to troubleshoot the issue without being able to replicate it. I'll see what I can do to run tests that are as close as possible to the conditions you have (same image, same drive capacity), but I can't guarantee anything. One thing I am noticing however is that you appear to be using a USB 2.0 drive ( Can you please run a test with a 5 GB, 10 GB and 15 GB persistent partition to see what happens? |
|
I did tests on 5Gb, 10Gb, 18Gb persistent storage and everyone of them worked, I have to note that I didn't try to boot from them, but waited for rufus to start writing iso file. |
|
Thanks for the tests. I have been running some tests on my own adding large persistent partitions on slow speed drives (USB 2.0), and I've been running into timeout errors, which makes me think this is the annoying "Windows may drop access to a volume or a whole disk that contains a file system that it cannot mount" issue: As a matter of fact, when I am getting the error, I am seeing the whole drive disappear from Fighting against Windows removing drives for no good reason while they are still being accessed might be a major pain in the ass because, quite frankly, if the system is not even able to detect that the drive is being written to when deciding to remove it from the system, I'm not sure what else I can do to force Windows to keep it online. But I'll see what I can do... |
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Issue description
Could not format usb drive with kubuntu iso and persistent storage, checked existing issues and found one (#814) from 2016 and the "solution" link responded with 404
The issues I am encountering is etheir
[0xC0030002] The system cannot find the file specified.#1360 (that one in the Log sessionor #814
Log
The text was updated successfully, but these errors were encountered: