4ms/metamodule

User data partition generated with make format-sd on linux cannot be mounted by metamodule

Closed this issue · 5 comments

LnnrtS commented

I haven't digged into this but it's similar to this

  • run make format-sd and copy release files to partiton
  • Metamodule in update mode doesn't not detect the partition (as shown in the log)
  • Manually for that partition in gnome-disks with default parameters and copy release files to partition
  • Everything works

I verified the parameters the partition is generated with in both cases are identical (as they can be read with file -s). The hexdump is very similar but I haven't gotten to check all changes yet.

danngreen commented

Strange. Doing make format-sd and then cp build/release/* /Volumes/METAMOD works for me (it finds the release json and updates). This is on macOS, so quite possible some difference exists between sgdisk versions.

Can you load patches with an SD Card formatted by make format-sd? (on main, there is a bug in the manifest-generator branch)

danngreen commented

I am using sgdisk version:
GPT fdisk (sgdisk) version 1.0.9

But to format the partition, the script is using these commands for linux:

sudo umount ${DISKSTEM}5
sudo mkfs.fat -F 32 -n METAMOD ${DISKSTEM}5 || exit

Perhaps the -F parameter is not correct? We are wanting FAT32, though I think ExFAT also will work.

LnnrtS commented

Diff of start of partition
image

Diff of partition table
image

The good versions are made with Gnome drivers, the bad ones are from the script

danngreen commented

Ok, the partition type is wrong. I'm not sure what the other bytes that are different means.
The PR 191 works for me. If it works for you on Linux, then go ahead and close this.

LnnrtS commented