Subject: kern/10430: Wd driver cannot handle bad144 table properly?
To: None <gnats-bugs@gnats.netbsd.org>
From: Takahiro Kambe <taca@sky.yamashina.kyoto.jp>
List: netbsd-bugs
Date: 06/23/2000 09:26:14
>Number: 10430
>Category: kern
>Synopsis: Wd driver cannot handle bad144 table properly?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jun 23 09:27:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Takahiro Kambe
>Release: NetBSD-current 2000/6/14
>Organization:
>Environment:
System: NetBSD edge.sky.yamashina.kyoto.jp 1.4ZD NetBSD 1.4ZD (CF-M33) #32: Thu Jun 15 08:58:49 JST 2000 taca@edge.sky.yamashina.kyoto.jp:/usr/src/sys/arch/i386/compile/CF-M33 i386
>Description:
Wd driver cannot handle bad144 talbe properly?
In my experience, kernel compalins bad sector table is correupted
when hadrdisk has more than 1024 cylinders.
wd0: bad sector table corrupted
wd0: bad sector table corrupted
boot device: wd0
root on wd0a dumps on wd0b
wd0: bad sector table corrupted
wd0: bad sector table corrupted
wd0: bad sector table corrupted
wd0: bad sector table corrupted
Maybe, first two of "corrupted" messages are looking for root
and dump device. Rests are four partiton in wd0.
>How-To-Repeat:
1. IDE hard disk (wd1) which has more than 1024 cylinders.
2. Add "badsect" flag to the disklabel.
3. Initialize bad144 table with bad144(8).
# bad144 wd1 1234
4. Reboot the system and see the boot message.
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted: