OK, another annoyance... I jut reinstalled my SDcard image and the UUID changed.
The last install (that broke after the apt upgrade) was 0159e561-b327-492f-a73a-b188b2217267. After this install its now 60fc6cad-2e3f-408d-a2f8-5f2320240203. Is it possible that something during the apt upgrade is changing the mmcblk1p1 UUID? Aside... I can kind of understand why the system will not boot if the UUID changes but prior to adding the UUID= to uEnv.txt my system was booting from /dev/mmcblk1p1. That _should_ have still worked but it didn't. Getting rather annoyed by this.... Hartley On Friday, October 23, 2020 at 3:58:15 PM UTC-7, Hartley Sweeten wrote: > > I tried adding the UUID (found with blkid) to my uEnv.txt. Same result. > > 1) Install SDcard image > 2) Boot > 3) sudo apt update > 4) sudo apt upgrade > 5) Reboot, system hangs > > It does change the message: > > Begin: Running /scripts/local-block ... done. > done. > Gave up waiting for root file system device. Common problems: > - Boot args (cat /proc/cmdline) > - Check rootdelay= (did the system wait long enough?) > - Missing modules (cat /proc/modules; ls /dev) > ALERT! UUID=0159e561-b327-492f-a73a-b188b2217267 does not exist. > Dropping to a shell! > (initramfs) > > Hartley > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/758c747a-0e74-45b7-bd5a-91a81c464a75o%40googlegroups.com.
