Date: Wed, 16 Aug 2017 07:58:02 -0700 From: Kurt Buff <kurt.buff@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: FUBAR on an upgrade - need some help Message-ID: <CADy1Ce41Dfi%2BArt5h1hPharg489SPOKfqF%2B4BJTDHriSMHpAEA@mail.gmail.com> In-Reply-To: <20170816092641.038c1860.freebsd@edvax.de> References: <CADy1Ce4Su5NDequMC3t10Suut6iSsw=zT0RK1h_GpRxnQQsFEQ@mail.gmail.com> <20170816092641.038c1860.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 16, 2017 at 12:26 AM, Polytropon <freebsd@edvax.de> wrote: > On Tue, 15 Aug 2017 19:29:23 -0700, Kurt Buff wrote: >> I have an old Acer AspireOne netbook that's been running 10.1-RELEASE. >> >> Yesterday I upgraded it using freebsd-update to 10.2 and then to 10.3, >> and it went fine. >> >> Then I upgraded it to 11.0-RELEASE, and it failed during boot, saying >> it wanted to boot from ad4s1a, but couldn't find it. >> >> I have managed to get it into single user, and have run "df-h" and >> "gpart show", which don't agree at all. Output: >> >> # df -h >> Filesystem Size Used Avail Capacity Mounted on >> /dev/ad4s1a 140G 36G 93G 28% / >> devfs 1.0k 1.0k 0B 100% /dev >> >> #gpart show >> => 63 312581745 ada0 MBR (149GB) >> 63 312581745 1 freebsd [active] (149GB >> >> => 0 312581745 ada0s1 BSD (149GB) >> 0 8388608 2 freebsd-swap (4.0GB) >> 8388608 304193137 1 freebsd-ufs (145GB) >> >> # cat /etc/fstab >> # Device Mountpoint FStype Options Dump Pass# >> /dev/ad4s1b none swap sw 0 0 >> /dev/ad4s1a / ufs rw >> 1 1 > > The OS now has associated /dev/ada0 to the device formerly known > as /dev/ad4, so the root partition needs to be adjusted in /etc/fstab > from /dev/ad4s1a to /dev/ada0s1a. > > When in single-user mode, do this: > > # mount -w / > > so you can write to /, then use > > # vi /etc/fstab > > or > > # ee /etc/fstab > > to make the required changes (for the swap partition as well). > > Finally reboot. > > > >> I can't seem to use vi to modify fstab. > > This is because the system leaves / mounted read-only when booting > into single-user mode (and it does not mount anything than /, so if > you have /usr on a different file system, you need to mount that > as well). Excellent. I've done this, and now find that wireless isn't working - it seems that it's detecting the NIC (ath0), but something has changed, so now I'll do some research on that. Many thanks. Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADy1Ce41Dfi%2BArt5h1hPharg489SPOKfqF%2B4BJTDHriSMHpAEA>