Date: Fri, 11 Nov 2016 11:35:45 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: unknown error during root mount on boot (fstab) in 11.0-RELEASE (after updating) Message-ID: <bb8d2164-7f46-7c08-2934-14ca5c1c343d@infracaninophile.co.uk> In-Reply-To: <82d02692-f98e-4605-a002-a7ffcdfdf233@kukulies.org> References: <7f9d7051-be30-54dd-55be-0fa236c28d84@kukulies.org> <e8ed05d3-1242-6bda-6269-20c653118d58@FreeBSD.org> <fae87b2a-07f8-83ff-9b70-9df4ca8686b5@kukulies.org> <eb270d9e-3681-1a26-3347-53f6571ac8d4@freebsd.org> <82d02692-f98e-4605-a002-a7ffcdfdf233@kukulies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --iusjUVLOdrSsj07HDgBq2wr0i5EQN8MJi Content-Type: multipart/mixed; boundary="G0ORgria7L8IuJgrSFDscEFWlWWhmET1D"; protected-headers="v1" From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Message-ID: <bb8d2164-7f46-7c08-2934-14ca5c1c343d@infracaninophile.co.uk> Subject: Re: unknown error during root mount on boot (fstab) in 11.0-RELEASE (after updating) References: <7f9d7051-be30-54dd-55be-0fa236c28d84@kukulies.org> <e8ed05d3-1242-6bda-6269-20c653118d58@FreeBSD.org> <fae87b2a-07f8-83ff-9b70-9df4ca8686b5@kukulies.org> <eb270d9e-3681-1a26-3347-53f6571ac8d4@freebsd.org> <82d02692-f98e-4605-a002-a7ffcdfdf233@kukulies.org> In-Reply-To: <82d02692-f98e-4605-a002-a7ffcdfdf233@kukulies.org> --G0ORgria7L8IuJgrSFDscEFWlWWhmET1D Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 11/11/16 11:19, Christoph P.U. Kukulies wrote: > It doesn't work. I enable console.info and *.* to go to > /var/log/console.log resp. all.log > bute the fiels weren't there. Also touching them in the first place > didn't help. > Maybe because the root FS isn't writeable at this point in time. >=20 > Here is a screenshot: >=20 > http://imgur.com/fEGCWhh So, what disk devices show up in /dev after reboot? Note that /dev/ad? style is old and /dev/ada? is the new standard. In fact the /dev/adXpY device entries should be symlinks to the appropriate /dev/adaNpY devices. Also note that device numbering is not particularly constant over reboots -- if you boot with or without eg. a USB memstick plugged in, it can cause everything to get renumbered. This is why the advice nowadays is to use gpart(8) to set a label on your filesystems and use /dev/gpt/labelname in /etc/fstab Cheers, Matthew --G0ORgria7L8IuJgrSFDscEFWlWWhmET1D-- --iusjUVLOdrSsj07HDgBq2wr0i5EQN8MJi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJYJa0RAAoJEABRPxDgqeTnf1QP/25rHUyXREf2Rj3HooAkiSkv a7RAAWUyZfsjCg3smsQSKE5vqEWPpJyOAU1oocI+x0Vp0SSQCf+92xQCjkXsdGRy kHr8R2C7d5BJsZZmMRPM7K5nXyKo9zbe5B2aBhF8QzbnHoxhfcb82LbZDE4Z/CK0 SQ5HHyygCuHRRXkM8BW7eok6f4S8CI6PGti+icR8e0DzrZhrW/aFFCTQFh7T3U0E eTIv/rWqcZ8yPDj2DhfB4yLuxaFIXRu5zZf1LKHWbN0nQMQBnJ089vspoOZw8wLG sVAP+JqrnDQHKeE56ZdQlCk/A/vtLVM1a4SMxpmBDgDmAyWvZbCDi9LXVuM6EFJH 5DviB4RLd7EETshZcgVvS7Ur6hfiihkgwPO2vHeBSsoUzHEEM1STGd7ILPnJKVeY mySEELdcA8AllqTRhblCgJ/7b4KoOFRN6yFp/X1qGQQnV9/eWv/G7NFrwkBPDQOc eqXRZtQLM7Z+3e1u3YeQWjbb27ZExeIDpU0PCvyv/wC8RGGFU/dSB48EcQLNLufC Eue3+9JlFqcaE72vmYFwD3FqMKDOidNiqc5WykNhh7srgVwI0z3egLAWLvCCAqtx wV5p9fFJhf3ATG50q5rYcf+4TGdmU7TdPX2/EgeMRTiW3oAFrwbrPVDtq4DaqLL/ 3sUgSz/AlHLHUmROGYuE =Ykaf -----END PGP SIGNATURE----- --iusjUVLOdrSsj07HDgBq2wr0i5EQN8MJi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb8d2164-7f46-7c08-2934-14ca5c1c343d>