Date: Sat, 18 Jul 2015 00:59:00 +0000 From: Glen Barber <gjb@FreeBSD.org> To: Kevin Oberman <rkoberman@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Head from yesterday's snapshot fails to mount root Message-ID: <20150718005900.GG1438@FreeBSD.org> In-Reply-To: <CAN6yY1txGzm8RywyrqNtdXZuU0iJ=MowTJvP-ivcx1UyqxsOcw@mail.gmail.com> References: <CAN6yY1txGzm8RywyrqNtdXZuU0iJ=MowTJvP-ivcx1UyqxsOcw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--YH9Qf6Fh2G5kB/85 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 17, 2015 at 05:52:58PM -0700, Kevin Oberman wrote: > I just tried to install HEAD from the July 16 snapshot. Installation went > fine using all defaults. (I am trying to test whether a problem with resu= me > is present with HEAD.) >=20 > I booted up the system from a USB drive with no problems until it tried to > mount root. It simply sat "Waiting for /dev/da0p2" forever (or more than > the 3 minutes I waited). System is a Lenovo ThinkPad T520 (amd64) that ru= ns > 10.2-BETA1 (r285359) without any issues other than the inability to resum= e/ >=20 > da0 is an old 120GB USB drive and I can mount and examine it using either > the install system or 10.2-BETA1 system. >=20 > This is my first experience with HEAD since the release of 10.0. The boot > looks quite normal and the UMASS and da0 devices show up and look normal. > ugen1.3: <JMicron> at usbus1 > umass0: <MSC Bulk-Only Transfer> on usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0x4000 > umass0:5:0:-1: Attached to scbus5 > da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > da0: <WDC WD12 00UE-00KVT0 3K01> Fixed Direct Access SCSI-2 device > da0: Serial Number D578C6060290 > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > da0: quirks=3D0x2<NO_6_BYTE> >=20 > Would screen shots of the boot help? (I sure see anything unusual.) Is th= is > a known issue? >=20 Yes, please provide screenshots. I did not observe this, although this does not sound like a problem with the image(s), necessarily. Thanks. Glen --YH9Qf6Fh2G5kB/85 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVqaTUAAoJEAMUWKVHj+KTQH4P/2CLV76qoeREr56PFkRES9td JGzuTwu//gYkbaFoBJe6P4rkeAY13C6MH4VjTjkkGE4bse2tYjbKW8tkq90Ol5eB Prj1dVkz7zW6IgrUGm1VcYNpz6zXh2bGETpNhvIBxr8IGMyvRlksHBBQ3vFeTp7s mb4Axjbt6r0MoCwMg7UVndy2l4SOhexzT6r3Ld0bBZxpUNFL4KIwIlNrrlSezvcA slaZLJG1UIFJT/4V13kAWv7IUhq5QNiTolFhwULsaC6cZkwtezuIo5tFI7Br51d7 HQV63bWyLu3FFFa2gwWRxKP8iesvhJyohNhUcPA6YEnRU+yhfomgtFoPsPVZhDUe PPltACkfxWi1yeCh+mewqlTRKt+8zIkBJr5UtpzgXKTDWXLBdp8MHJPNo2GF8QLI 4B5qrqK6Hi/pEwCF+wOT97igGdV+doEje8V2UdG59avvabpCJhwLuqdG1/HUNAM7 5ljouWMhExNxGBaVCcOEdxH2pOf8iOj+33Ck07O6/3gMs0BCMeaqBpcarKqTac7h LOBZaz+DXFblfnKSpEHd0DsEzuYsbIP/ZTFq6vra3k38bL/FJqtwB1VS+rjHNho7 fSHfBflnZhjYmQ7DSXuPTagi0Q5kOd+rJ8k8HSijPi52MvD4NY76aQKiiuHFORtR mNhMCd6T+3900KCNKmax =UFEL -----END PGP SIGNATURE----- --YH9Qf6Fh2G5kB/85--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150718005900.GG1438>