Date: Tue, 21 Feb 2017 15:37:00 -0500 From: Thomas Laus <lausts@laus.org> To: freebsd-arm@freebsd.org Subject: Re: Fatal kernel abort Message-ID: <7d331926-08e2-9699-aaa9-538d40ee29dc@mail.laus.org> In-Reply-To: <1487692868.73144.118.camel@freebsd.org> References: <155401d28ba9$ccdc28c0$66947a40$@tndh.net> <CAFHCsPWm6fOh1phFfYF%2BjJO5mDV0=mNPd1EtHgDnrp=DBwHekw@mail.gmail.com> <157701d28bda$dd004700$9700d500$@tndh.net> <1487638318.73144.116.camel@freebsd.org> <159c01d28c18$bfbb90d0$3f32b270$@tndh.net> <1487692868.73144.118.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/21/17 11:01, Ian Lepore wrote: > I don't use crochet, hardly know anything about it. But I know a lot > of people do use it, so it seems like if it were really creating broken > unusable images, other people would have something to say about that. > I also have not been able to create a Beaglebone Black image using crochet since sometime in January of this year. I just made another attempt with FreeBSD-CURRENT R314047. It stops at the same point as Tony Hain: ================================================================== Growing root partition to fill device GEOM_PART: mmcsd0s2 was automatically resized. Use `gpart commit mmcsd0s2` to save changes or `gpart undo mmcsd0s2` to revert them. gpart: Read-only file system gpart: Read-only file system growfs: wtfs: write error: 15457272: Read-only file system /etc/rc: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one Setting hostuuid: 52bf42a6-f870-11e6-a48c-8030dc5e941b. Setting hostid: 0xcd97479a. No suitable dump device was found. Starting file system checks: /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s2a: clean, 697863 free (263 frags, 87200 blocks, 0.0% fragmentation) g_vfs_done():mmcsd0s2a[WRITE(offset=163840, length=32768)]error = 30 g_vfs_done():mmcsd0s2a[WRITE(offset=20709376, length=4096)]error = 30 mount: /dev/mmcsd0s2a: Read-only file system Mounting root filesystem rw failed, startup aborted ERROR: ABORTING BOOT (sending SIGTERM to parent)! Feb 21 19:59:59 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: g_vfs_done():mmcsd0s2a[WRITE(offset=163840, length=32768)]error = 30 Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d331926-08e2-9699-aaa9-538d40ee29dc>