From owner-freebsd-hardware Thu Jul 25 10:51:25 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA16006 for hardware-outgoing; Thu, 25 Jul 1996 10:51:25 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA16000 for ; Thu, 25 Jul 1996 10:51:23 -0700 (PDT) Received: (from brett@localhost) by lariat.lariat.org (8.8.Alpha.4/8.8.Alpha.4) id FAA12702 for hardware@freebsd.org; Thu, 25 Jul 1996 05:49:47 -0600 (MDT) Date: Thu, 25 Jul 1996 05:49:47 -0600 (MDT) From: Brett Glass Message-Id: <199607251149.FAA12702@lariat.lariat.org> To: hardware@freebsd.org Subject: More info about disk problem Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Have gotten the system to mail me (on a different machine) its bootstrap messages, which show the bad sector. They look like this (skip to the end to see the disk error): > FreeBSD 2.1.5-RELEASE #0: Wed Jul 17 03:09:31 1996 > jkh@whisker.cdrom.com:/usr/src/sys/compile/GENERIC > CPU: Cy486DLC (486-class CPU) > Origin = "Cyrix" > real memory = 4587520 (4480K bytes) > avail memory = 2732032 (2668K bytes) > pcibus_setup(1): mode1res=0xffffffff (0x80000000), mode2res=0xff (0x0e) > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: MDA/hercules <16 virtual consoles, flags=0x0> > ed0 at 0x300-0x31f irq 5 on isa > ed0: address 00:40:c7:10:61:6c, type NE1000 (8 bit) > ed1: disabled, not probed. > sio0 at 0x3f8-0x3ff irq 4 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > sio2: disabled, not probed. > sio3: disabled, not probed. > lpt0 at 0x378-0x37f irq 7 on isa > lpt0: Interrupt-driven port > lp0: TCP/IP capable interface > lpt1: disabled, not probed. > mse0: disabled, not probed. > psm0: disabled, not probed. > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: NEC 765 > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 124MB (255255 sectors), 1001 cyls, 15 heads, 17 S/T, 512 B/S > wdc1: disabled, not probed. > bt0: disabled, not probed. > uha0: disabled, not probed. > aha0: disabled, not probed. > aic0: disabled, not probed. > nca0: disabled, not probed. > nca1: disabled, not probed. > sea0: disabled, not probed. > wt0: disabled, not probed. > mcd0: disabled, not probed. > matcdc0: disabled, not probed. > scd0: disabled, not probed. > ie0: disabled, not probed. > ep0: disabled, not probed. > ix0: disabled, not probed. > le0: disabled, not probed. > lnc0: disabled, not probed. > ze0: disabled, not probed. > zp0: disabled, not probed. > npx0 on motherboard > npx0: 387 emulator > Device configuration finished. > Considering FFS root f/s. > Configuring root and swap devs. > configure() finished. > BIOS Geometries: > 0:03e70e11 0..999=1000 cylinders, 0..14=15 heads, 1..17=17 sectors > 1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors > 0 accounted for > wd0s1: type 0xa5, start 0, end = 255254, size 255255 : OK > wd0: interrupt timeout: > wd0: status 5c error 4 > wd0a: soft ecc reading fsbn 27808 of 27760-27823 (wd0 bn 27808; cn 27808 tn 0 sn 0)wd0: status 5c error 1 > wd0: interrupt timeout: > wd0: status 5c error 1 If I'm reading this correctly, the drive takes a long time to respond because it's correcting an error, but eventually gets the right data. (That *is* what the "no_dam" part means, right?) There seem to be a few utilities included in FreeBSD that might be able to correct the problem, but it's unclear how to use them or whether they will work on an IDE drive. Also, it's not clear how one determines which file(s) might have to be replaced in case they've been corrupted. Since this system is new, I'm willing to reinstall FreeBSD if I can, in the process, scan the disk for bad blocks and map them out. Is this possible? Or can I do this without reinstalling and be sure that I will not be left with anything corrupted?