is there a fix? I found out this is caused by uboot passing the boot arguments to kernel with rootfs=/dev/mmcblk0, while sd is inserted, the emmc actually became /dev/mmcblk1, therefore kernel unable to find rootfs.
On Tue, May 7, 2013 at 1:10 AM, Venkat Bommakanti <[email protected]>wrote: > Hi, > > In this scenario, where you boot from mSD but have a "cleared up" eMMC, > can the eMMC still be used ? > Read somewhere that SD's in general are error-prone over a period, after > numerous writes. If that is the case, can run-time generated data (like in > a MySQL database) be written to the eMMC and shipped off from there on a > periodic basis... > > thanks, > /venkat > > On Monday, May 6, 2013 9:57:42 AM UTC-7, [email protected] wrote: >> >> ... To do that I boot from the SD card and once into the OS I mount the >> 1st partition of the eMMC and delete the files it contains. From then on >> it will always boot to my SD card which is 8G or 32G. Plenty of space.... >> > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
