Date: Thu, 7 May 2020 12:32:30 -0700 From: David Christensen <dpchrist@holgerdanske.com> To: freebsd-questions@freebsd.org Subject: Re: SSD woes - boot Message-ID: <82936c42-1bfa-02da-7dea-60658df8d9bb@holgerdanske.com> In-Reply-To: <E35B2E1F-8BEB-458C-97BF-3EF030CA0643@kukulies.org> References: <28BC0AA1-FF58-406A-A5EE-FB0641D2C2B5@kukulies.org> <b5a1c463-e522-f9f1-8bd5-d092953d797b@holgerdanske.com> <E35B2E1F-8BEB-458C-97BF-3EF030CA0643@kukulies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-05-07 02:16, Christoph Kukulies wrote: > Today I went into my local computer store and bought me a new SATA cable. Connected the Kingston SSD with the new cable and > it got recognized immediately. I would cut the connectors off the old cable and recycle it. > Anyway, I booted, but still hit the wrong disk (with F5 which was preset). I hit F1. Got into the FreeBSD boot(8) prompt > >>> FreeBSD/i386 BOOT > Default: 0:ad(0,a) > boot: > After some fiddling - ? gave me a directory listing but could not much do with that - I found that everything I typed, like lsdev, > ended up in being appended to the Default line, like: > > Default: 0:ad(0,a)lsdev > > So I type /boot/loader and - voila - I hit it, landed exactly in the desired disk/partition. > > Now I got to figure out the UUID labeling thing - maybe :) Let us know how it works out. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82936c42-1bfa-02da-7dea-60658df8d9bb>