by ewtoombs » Tue Oct 27, 2020 8:15 pm
I saw the same thing. I have a Raspberry Pi 4 Model B. Changing mmcblk1 back to mmcblk0 isn't a real solution. The correct thing to do is give the boot filesystem a label and mount by label instead. That's what I did. Device node names are subject to race conditions and should never be relied upon. For instance, if somebody attaches a USB sdcard reader to the raspi's USB port, what happens on boot? Exactly. You don't know.
This is a very serious bug. The default raspberry pi 4 64-bit image will not work out of the box until it is fixed.