"xpt_config still waiting" solved: bad disk

freebsd-stable at ch.pkts.ca freebsd-stable at ch.pkts.ca
Tue Jan 17 00:54:12 UTC 2012


Hi..

I just wanted to report a bug with FreeBSD 8.2-RELEASE-p5, as packaged
with FreeNAS 8.0.3.

A hard drive failed in a strange way, in that it was detected by the
computer's BIOS and firmware, but did not reply to information
requests from the kernel.  The boot process stopped with a series of
timeout messages, ending with the message:

run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config

Removing the affected hard drive fixed the problem; the other 5
identical drives (3TB Hitachi SATA) in the system were unaffected, and
that SATA port was tested with a working drive and was ok.

So, the problem is hard to reproduce without a drive damaged this
particular way, but if you could allow booting to continue after this
error is triggered, that'd be helpful for future users.

Thanks.
--
freebsd-stable at ch.pkts.ca -- just another bug reporter


More information about the freebsd-stable mailing list