Date: Tue, 20 Apr 1999 16:49:44 +0930 From: Greg Lehey <grog@lemis.com> To: Aaron Gifford <agifford@infowest.com>, FreeBSD Questions <questions@FreeBSD.ORG> Subject: Re: 3.1 stable crash - what hardware should I suspect first/most? Message-ID: <19990420164944.B40482@lemis.com> In-Reply-To: <199904200702.BAA29709@infowest.com>; from Aaron Gifford on Tue, Apr 20, 1999 at 01:02:55AM -0600 References: <199904200702.BAA29709@infowest.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html] On Tuesday, 20 April 1999 at 1:02:55 -0600, Aaron Gifford wrote: > Hello, > > My workstation crashed over the weekend. It's a PII-350 running > FreeBSD 3.1-STABLE as of the 2nd of April. Heres some additional > system info: > > <snip> > ### Input/output errors begin when I attempt several commands: > > # pstat -s > bash: /usr/sbin/pstat: Input/output error > # disklabel da0 > su: /sbin/disklabel: Input/output error > # disklabel da1 > su: /sbin/disklabel: Input/output error This is pretty typical of having lost a system disk. > # tail /var/log/messages > Apr 19 17:09:46 local su: joecool to root on /dev/ttyv0 > Apr 19 17:20:16 local /kernel: (da1:ncr1:0:1:0): Invalidating pack > Apr 19 17:20:16 local /kernel: (da1:ncr1:0:1:0): Invalidating pack > Apr 19 17:20:32 local /kernel: (da0:ncr1:0:0:0): Invalidating pack And this confirms it: you lost /dev/da0. > Should I suspect a hardware failure in my NCR1 controller, or > something else? This system has functioned flawlessly for over 3 > months 24-hours-a-day, then a crash over the weekend followed by this > strangeness. I figure I'll try swapping cables, try the drives out > in another box, etc. to try to narrow the problem down more > precisely. I just thought I should throw this out just in case > someone out there has a big clue they can throw me. Typically this message means that you've had a catastrophic error on the drive. It's difficult to say where the problem lies, but I'd guess it's the disk. It's also possible that CAM is being overly fussy about this sort of thing; I have an intermittent problem on my test box which does the same thing. Unfortunately, once you've lost your swap partition, there's currently nothing you can do except reboot. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990420164944.B40482>