Official moOde 7.3.0 support thread

[TheOldPresbyope]

@Ouchita

I choose not to get into debates about reliability of various memory technologies.

However, I do wonder about your issue A.

ATM I'm testing moOde 7.4.0tr1 on an RPi4B. The case I'm using makes exchanging the uSD card awkward so I'm using a USB thumbdrive (16GB Cruzer Fit) for moOde and another USB thumbdrive (32GB SanDisk Gen1) for my library. I can boot moOde just fine,

Code:

Disk /dev/sda: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Disk model:  SanDisk 3.2Gen1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1          32 60063743 60063712 28.7G  c W95 FAT32 (LBA)


Disk /dev/sdb: 14.3 GiB, 15376318464 bytes, 30031872 sectors
Disk model: Cruzer Fit      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x067e19d7

Device     Boot  Start     End Sectors  Size Id Type
/dev/sdb1         8192  532479  524288  256M  c W95 FAT32 (LBA)
/dev/sdb2       532480 8724479 8192000  3.9G 83 Linux

I'm not sure why this configuration is working for me but not for you. Yes, I'm working with a test release but I was using the same dual-thumbdrive setup with 7.3.0 without issue. 

Another difference is that I'm booting an RPi4B and you're booting an RPi3B+. The RPF has quite a lot of model-specific information starting from https://www.raspberrypi.org/documentatio...t-sequence

Regards,
Kent