Date: Thu, 29 Jan 2009 23:52:22 -0600 (CST) From: Wes Morgan <morganw@chemikals.org> To: Mike Barnard <mike.barnardq@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Unable to boot after upgrade to 7.0 or 7.1 STABLE Message-ID: <alpine.BSF.2.00.0901292322570.33814@ibyngvyr.purzvxnyf.bet> In-Reply-To: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com> References: <7dc029620901290634q7ca5361ct496fc2c4a6bfe53f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jan 2009, Mike Barnard wrote: > Hi All, > > I have run into a problem that seem rather puzzling. I have upgraded an > installation of FreeBSD from 7.0-RELEASE to 7.0-STABLE and 7.1-STABLE, but i > fail to boot with either one of the STABLE upgrades. I end up at this point: > > > Trying to mount root from ufs:/dev/ad0s1a > Manual root filesystem specification: > <fstype>:<device> Mount <device> using filesystem <fstype> > eg. ufs:da0s1a > ? List valid disk boot devices > <empty line> Abort manual input > > When i type ?, i get nothing. When i try to load all possible drives, from > ad0s1a to ad9s1a, i get nothing. When i boot kernel.old, i see this: > > atapci0: <Intel ICH7 SATA300 controller> port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfa00-0xfa0f mem 0xfdffe000-0xfdffe3ff > at device 31.2 on pci0 > ... > ad0: 152627MB <WDC WD1600AAJS-60PSA0 21.12M21> at ata0-master SATA150 > > It seems that FreeBSD recognises this drive as a SATA300 but later on refers > to it as SATA150. Could this be the problem. Have you checked the jumper settings on the drive? There may be a jumper forcing SATA150 mode on the drive. I'd reset everything to factory defaults if possible. You might be able to use the ata driver from 7.0-R in -stable to boot your system. If that works, try searching for the commit that breaks your controller.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0901292322570.33814>