> > When you copied the rootfs, the root device is listed in /etc/fstab, > along with the fsck call. Just minimze it: > > voodoo@hades:$ cat /opt/wheezy/etc/fstab > debugfs /sys/kernel/debug debugfs defaults 0 0 >
Yes, on the failing rootfs I see the / mount (/dev/mmcblk0p2 / ext4 noatime,errors=remount-ro 0 1) I'll eliminate that and give it another try. > > Btw, here's how i setup the nfs rootfs.. I first boot the bbb, with > the microSD, then run this: > > > https://github.com/RobertCNelson/boot-scripts/blob/master/tools/developers/nfs-rsync.sh > > > Just change all occurances of: > > 192.168.0.10 & /opt/wheezy/ > > and it should work for you. > Thanks! I'll have a look. Maybe the auto generation isn't working when I boot from a virgin rootfs created from the tarball? Is your expectation that one should be able to use the rootfs tarball as the basis for a root file system mounted on NFS, mounted on flash? Is it possible that the initial bootup is assuming something that it shouldn't be? Thanks again! Cheers, ba -- 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/d/optout.
