Date: Sat, 10 May 2003 00:37:30 +0200 From: Farid Hajji <me@farid-hajji.de> To: kientzle@acm.org Cc: freebsd-current@freebsd.org Subject: Re: Lockups with dump(8) Message-ID: <200305100037.30834.me@farid-hajji.de> In-Reply-To: <3EBC010C.8070409@acm.org> References: <200305092054.32885.me@farid-hajji.de> <3EBC010C.8070409@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > ad0: READ command timeout tag=0 serv=0 - resetting > > ata0: resetting devices .. > I had a similar problem with a -STABLE system > that I tracked down to two problems: > * Long 40-wire disk drive cable. > Shorter or 80-wire cable is more reliable Using only short 80-wire cables in all configs so far. > * Mis-jumpered hard disk. I had the > drive jumpered as "master _with_ slave", > even though there was no slave on that > cable. Different hard disks handle this > in different ways. Nope, the drives are jumpered master (without slave). I'm puzzled, because everything else works without any problems. dump(8) with snapshots seems to be an excellent torture test. > Once I fixed the jumpering and swapped in > a better hard disk cable, the problems went > away. I suspect a hardware error too. The kernel doesn't hang since ping works; switching consoles is not possible, perhaps because that may require a disk access, therefore blocking. Hmmm... I'll try again with other cables. > Tim Kientzle Many thanks, -Farid. -- Farid Hajji -- Unix Systems and Network Management. http://www.farid-hajji.net/address.html Quoth the Raven, "Nevermore." --Edgar Allan Poe.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305100037.30834.me>