Date: Tue, 30 Jun 2009 11:35:44 +0200 From: Gary Jennejohn <gary.jennejohn@freenet.de> To: Chris Hedley <freebsd-current@chrishedley.com> Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: New builds won't boot (fwd) Message-ID: <20090630113544.3e2bef31@ernst.jennejohn.org> In-Reply-To: <alpine.BSF.2.00.0906300326290.1621@teapot.cbhnet> References: <alpine.BSF.2.00.0906071604540.1724@teapot.cbhnet> <4A2C124A.1050707@freebsd.org> <alpine.BSF.2.00.0906261725570.1809@teapot.cbhnet> <alpine.BSF.2.00.0906261926080.1809@teapot.cbhnet> <alpine.BSF.2.00.0906300051400.33237@teapot.cbhnet> <3c1674c90906291830g1c79c80bq42ce99f44588e968@mail.gmail.com> <alpine.BSF.2.00.0906300326290.1621@teapot.cbhnet>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 30 Jun 2009 03:36:02 +0100 (BST) Chris Hedley <freebsd-current@chrishedley.com> wrote: > But it did give me an opportunity to spot something weird which I hadn't > noticed before, which is the device numbering: instead of getting the > usual ad0-ad9 for my discs, the numbering was a bit peculiar, ad4, ad6 and > so on, as if it were enumerating them according to each logical slot > rather than doing them by discs as they're found. > It does seem to number based on slot, whereby the driver for some reason acts as though SATA has master/slave disks, which of course it doesn't. You can get back to the old behavior by putting "options ATA_STATIC_ID" into your kernel config file. --- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090630113544.3e2bef31>