Cannot reliably mount emulated storage under Linux about pxt-ev3 HOT 6 OPEN

I am also having this issue. Possibly the documentation should be updated to state that drag and drop isn't supported on Linux? I'm assuming that this will affect chromebooks as well, which kind of seems like the primary use case.

As this is likely to be a bug with the EV3 firmware, rather than a problem with makecode itself, should it be raised with Lego to be resolved?

from pxt-ev3.

Same problem here on a Raspberry Pi 400 with Raspbian GNU/Linux 10.Would be great for teaching if this problem could be fixed soon!

Doing a fsck file system-check after rebooting the EV3 shows the following:

root@raspberrypi:/# fsck.fat  /dev/sda
fsck.fat 4.1 (2017-01-24)
0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
/EV3
  Contains a free cluster (782). Assuming EOF.
/dmesg.txt
  File size is 131072 bytes, cluster chain length is > 131072 bytes.
  Truncating file to 131072 bytes.
/Projects
  "." is missing. Can't fix this yet.
/Projects
  ".." is missing. Can't fix this yet.

from pxt-ev3.

Snapshot of the raw contents of the emulated USB drive: ev3fs.zip

from pxt-ev3.

This seems to be a problem with the Projects folder only. If I remove all files from the BrkProg_SAVE directory, the folder disappears and there are no more errors while mounting.

from pxt-ev3.

The issue can be reproduced with https://github.com/microsoft/uf2-linux/, so it is not specific to EV3.
With the following directory map, the same errors occur via NBD.

struct DirMap dirMaps[] = { //
    {"Uf2Dir", "/home/kuba/uf2", F_UF2},
    {NULL, NULL, 0}};

from pxt-ev3.

same here :(

lots of kernel: FAT-fs errors, first this:

    error, corrupted directory (invalid entries)  
    Filesystem has been set read-only

and then lots of these at each access:

    error, fat_get_cluster: invalid cluster chain (i_pos 0)

but it seems I cannot see the drive in windows as well and do not see the ev3 in the firmware upgrade tool anymore (otherwise I'd try to downgrade it for instance)..

I also found this alternative explanation/root cause so far: https://serverfault.com/questions/331779/how-do-i-debug-this-fs-error-on-a-flash-device

anyone has some progress on this?

from pxt-ev3.