From owner-freebsd-hackers Wed Mar 29 10:50:13 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA25637 for hackers-outgoing; Wed, 29 Mar 1995 10:50:13 -0800 Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA25631 for ; Wed, 29 Mar 1995 10:50:09 -0800 Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id UAA00295 for hackers@freebsd.org; Wed, 29 Mar 1995 20:39:59 +0200 From: Luigi Rizzo Message-Id: <199503291839.UAA00295@labinfo.iet.unipi.it> Subject: MBR corruption To: hackers@FreeBSD.org Date: Wed, 29 Mar 1995 20:39:59 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2184 Sender: hackers-owner@FreeBSD.org Precedence: bulk Has anyone seen this ? On one system running snap950210, for the second time in a month or so, I could not reboot after a (voluntary) because the disk (IDE, 540MB, completely allocated to FreeBSD) had lost the MBR and the label. Other than this the system looks very stable (uptimes of 7-10 days usually followed by voluntary reboots). The disk was "fdisk"ed with the 950210 boot floppy, completely allocated to FreeBSD with a 30 MB root, 64 MB swap, and the rest going to /usr. The system is not under heavy use at the moment (except from serving as firewall between one student lab and the world). Related to the disk, I noticed the following in messages : Mar 27 12:27:34 studenti /kernel: wd0b: wdstart: timeout waiting for DRQ writing fsbn 23657 of 23656-23671 (wd0 bn 85097; cn 84 tn 6 sn 47)wd0: status 50 error 1 Mar 27 12:27:35 studenti /kernel: sio0: 390 more interrupt-level buffer overflow s (total 390) Mar 28 14:58:39 studenti /kernel: wd0b: wdstart: timeout waiting for DRQ writing fsbn 8673 of 8672-8679 (wd0 bn 70113; cn 69 tn 8 sn 57)wd0: status 50 error 1 Mar 28 14:58:40 studenti /kernel: sio0: 358 more interrupt-level buffer overflows (total 748) Mar 29 18:48:35 studenti /kernel: wd0: interrupt timeout: Mar 29 18:48:35 studenti /kernel: wd0: status 58 error 0 Mar 20 11:49:09 studenti /kernel: wd0: interrupt timeout: Mar 20 11:49:09 studenti /kernel: wd0: status 58 error 4 Mar 20 11:53:07 studenti /kernel: wd0: interrupt timeout: Mar 20 11:53:08 studenti /kernel: wd0: status 50 error 1 Mar 20 12:08:10 studenti /kernel: mb_map full Could someone explain them (especially the "wdstart: timeout ..." ones). Note that the "wd0: interrupt timeout:" seems to always within a few minutes from a reboot. Thanks Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 ====================================================================