Lost files on 2.0RC5 upgrade
-
I updated from 1.21 to 2.0RC5, and when the device rebooted it looks like I'm missing a bunch of files from /sys. According to my backup, I had 72 files beforehand, and there are 48 now.
Is there any information I can provide now after the fact to investigate?
<edit>
I think my issue is at least partially (if not fully) explained by this comment:
https://forum.duet3d.com/topic/5394/new-firmware-2-0rc5-available/30
There's one remaining concern though. (See below.)
</edit> -
Pulled the SD card and put it in a reader. Confirmed that the files don't appear under Windows either.
I ran Windows chkdsk on the volume. Afterwards I did a comparison between my backup and the recovered volume, and it looks like chkdsk was able to recover everything. So it seems like filesystem corruption for sure, and of a recoverable variety. Hopefully that will give you an idea of what's going on.
Let me know if you want this disk image and I'll PM you a link.
PS C:\Users\David> chkdsk d:
The type of the file system is FAT32.
Volume Serial Number is 13A9-FA3E
Windows is verifying files and folders...
File and folder verification is complete.
Windows found errors on the disk, but will not fix them
because disk checking was run without the /F (fix) parameter.
Convert lost chains to files (Y/N)? -
This post is deleted! -
This post is deleted! -
This post is deleted! -
I did a full, fresh format, copied all the files back, and booted up. DWC still shows some files as missing. (Alphabetically the last ones, now, more or less.)
However I was able to do an "M98" to run one of the macros that does not appear in DWC, and that macro executed successfully. So it would seem that the part of the system does in fact know about and can read those "missing" files just fine!
I suspect dc42's comment here explains some of the symptoms I was seeing:
https://forum.duet3d.com/topic/5394/new-firmware-2-0rc5-available/30My remaining concern is that the files were initially missing in Windows too, before running chkdsk. Is it possible that the reduced buffer sizes might cause directories to get truncated when they're written out?
I will pull up my pre-repaired image to make sure I'm not misremembering.
-
The reduced buffer sizes apply only to output sent to DWC, USB and PanelDue - not to the file write buffers.
