Yeah, you can fix ( revert this ) by editing /boot/uEnv.txt and change the line for uname_r to . .
uname_r=4.1.18-ti-r56 That should get your board booting again, but no idea why the initrd is choking on what appears to be an old uuid for the disk ? Perhaps it's an /etc/fstab issue, but that doesnt make sense . . . On Thu, Apr 14, 2016 at 1:14 AM, Steve Osselton < steve.ossel...@prismtech.com> wrote: > Hi, > > Have just updated a a board from 4.1.18-ti-r56 to 4.4.6-ti-r17 using > "update_kernel.sh --lts-4_4". > This now fails to reboot. Looking at console is stuck in initramfs where > it looks there has been a failure > to find the actual file system by uuid: > > ALERT! /dev/disk/by-uuid/09d2505d-bc65-4001-ac78-1d2489083e0c does not > exist. Dropping to a shell! > > Could see the ramfs being rebuilt as part of the install: > > update-initramfs: Generating /boot/initrd.img-4.4.6-ti-r17 > > Note that file system is actually on attached SSD. Updated another board > from 4.4.6-ti-r16 and this worked fine. > Any idea what has happened here/how to fix? > > Cheers Steve. > > -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
