Date: Mon, 9 Mar 2015 10:31:57 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Brett Wynkoop <freebsd-arm@wynn.com> Cc: freebsd-arm@freebsd.org Subject: Re: Oddness with GPT labels on boot Message-ID: <70014E4C-FB67-427C-876E-B646EA0B1AA7@gromit.dlib.vt.edu> In-Reply-To: <20150308221139.687c8f3a@ivory.wynn.com> References: <20150308221139.687c8f3a@ivory.wynn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 8, 2015, at 10:11 PM, Brett Wynkoop <freebsd-arm@wynn.com> wrote: > Greeting- >=20 > So just updated my kernel sources and now I have this oddness = happening: >=20 > No suitable dump device was found. > Starting file system checks: > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% > fragmentation) ugen1.2: <vendor 0x0781> at usbus1 > umass0: <vendor 0x0781 Staples, class 0/0, rev 2.00/1.22, addr 2> on > usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0xc100 > umass0:0:0: Attached to scbus0 > da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 > da0: <Staples 1.22> Removable Direct Access SCSI-5 device=20 > da0: Serial Number 4C532000071129119192 > da0: 40.000MB/s transfers > da0: 15267MB (31266816 512 byte sectors: 255H 63S/T 1946C) > da0: quirks=3D0x2<NO_6_BYTE> > Can't stat /dev/gpt/bbexport: No such file or directory > Can't stat /dev/gpt/bbexport: No such file or directory > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: > ufs: /dev/gpt/bbexport (/export) > Unknown error; help! > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Mar 8 22:04:47 init: /bin/sh on /etc/rc terminated abnormally, going > to single user mode Enter full pathname of shell or RETURN for = /bin/sh:=20 > # fsck -p > /dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/mmcsd0s2a: clean, 560326 free (12950 frags, 68422 blocks, 0.7% > fragmentation) /dev/gpt/bbexport: FILE SYSTEM CLEAN; SKIPPING CHECKS > /dev/gpt/bbexport: clean, 3375570 free (114 frags, 421932 blocks, 0.0% > fragmentation)=20 > #=20 >=20 > Note I did nothing more than run fsck -p as soon as I was at > the /bin/sh prompt.=20 >=20 > # uname -a > FreeBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r279797: Sun Mar 8 > 21:22:04 EDT 2015 > wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm=20 > #=20 >=20 > Before this kernel I had no problem with the filesystem being checked > and mounting at boot. >=20 > I have not rebuilt world, but I am at a loss as to how that could be > the problem. Note above that it said it could not > find /dev/gpt/bbexport.=20 >=20 > I have even put the late param in /etc/fstab for /dev/gpt/bbexport to > see if that would help. One thing that caught me very recently is that when the DTrace code went = in, the BEAGLEBONE kernel config file also grew this line: makeoptions MODULES_OVERRIDE=3D"opensolaris dtrace dtrace/lockstat = dtrace/profile dtrace/fbt" That has the effect of only building those modules. If, like me, you = were using GEOM labels (which, from the above, it looks like you are = using GPT labels), via the geom_label module, then you'd get some = breakage with any new kernel, as the /dev/gpt devices would not appear = and your file systems would not be mountable. :-( If you rely on the vanilla BEAGLEBONE kernel then this might be your = problem. So, I suggest you either comment that out (and revert to building all = modules) or add a nomakeoptions somewhere. (I use another kernel config = file that includes BEAGLEBONE and then disables some things via = nooptions and nomakeoptions.) Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?70014E4C-FB67-427C-876E-B646EA0B1AA7>