Date: Fri, 07 Aug 2009 18:21:08 -0400 From: Michael Powell <nightrecon@hotmail.com> To: freebsd-questions@freebsd.org Subject: Re: Fwd: Boot failure Message-ID: <h5i9c3$47m$1@ger.gmane.org> References: <4d4e09680908061012q6ea8aeacm875c556eaea7a54f@mail.gmail.com> <4A7B1B41.7090507@unsane.co.uk> <4d4e09680908061733v21602321x252a7111a7648ad6@mail.gmail.com> <4A7C074C.9060303@unsane.co.uk> <4d4e09680908070708x635dcd80ha96a61e9c71b0b6b@mail.gmail.com> <4d4e09680908070708i286b98a7j6f03725a848ae83c@mail.gmail.com> <20090807153027.GA39621@slackbox.xs4all.nl> <4d4e09680908070847jfed3447v4863b7637585f54@mail.gmail.com> <20090807212050.GB48236@slackbox.xs4all.nl> <ade45ae90908071439p6903aaa0ve9acd4ff3223c827@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Judd wrote: > On 8/7/09, Roland Smith <rsmith@xs4all.nl> wrote: > >> Looks like your hardware is dying/dead. > > > > Sadly, I agree. > > > Reset BIOS CMOS data (hardware jumper on motherboard) > Enter RAID controller BIOS, (re)set your "boot drive" > > But it looks like a fundamental BIOS control issue is malfunctioning. > > Do you have a PCI Diagnostics card? One like the following? > > http://www.uxd.com/phdpci.shtml > > (I'm not saying that exact model, but rather a device that is able to > see BIOS codes through the PCI bus that can tell very technical detail > to tech support at the motherboard's vendor (you said Intel, right?).) > > Hardware rarely up and dies. Have you tried swapping RAM chips out, > or re-ordering them to see if it might be a RAM problem? > > > Maybe we're not passing POST, or that we're passing POST but the > bootable device list is not finding bootable medium. > > > These kind of issues intrigue me, because it is out of the norm, and > why did it happen. Sometimes I've seen when a hard drive gets old and the head movement mechanism is worn the drive can have problems properly locating the head over track 0. I've also noted that sometimes even when it can find track 0 it couldn't read the mbr. If this happens because of a bad spot has developed in the magnetic media there's nothing at this point that can be done. If it's just worn head slop sometimes you can write out a fresh mbr and use it for a while longer, but the problem will return worse later. Using smartmontools and smartctl test/diags to get a test dump from the drive can be useful at times to decide if replacement is warranted. > I'd get to the point of swapping hardware one at a time until it > fixes, or until you exhaust your options. Have any kind of support > contract with the OEM? > > --Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h5i9c3$47m$1>