Bug 16068

Summary: FreeBSD 3.3 with IDE > 32GB causes Panic: ufs_dirbad: bad dir during installation
Product: Base System Reporter: jbebeau <jbebeau>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description jbebeau 2000-01-11 18:50:02 UTC 
I'm upgrading to a bigger dist and chose to install 3.3 again from CD.  During the install process, just after the newfs system panics:
Panic: usf_dirbad: bad dir followed by syncing disks...65 65 9 1 1.. done.
I'm replacing a Matox 8GM with a Matrox 36GM model 93652U8.  At boot time, FreeBSD reports wd0 34837MB (71346240 sectors) 70780 cyl, 16 heads, 63 S/T 512 T/S and the doc indicates I should use the BIOS values. I've tried several combinations, all yeild result.

How-To-Repeat: can't get past the problem during the install
Comment 1 Bruce Evans 2000-01-12 10:37:38 UTC 
On Tue, 11 Jan 2000 jbebeau@1nettw.com wrote:

> >Synopsis:       FreeBSD 3.3 with IDE > 32GB causes Panic: ufs_dirbad: bad dir during installation

> I'm upgrading to a bigger dist and chose to install 3.3 again from CD.  During the install process, just after the newfs system panics:
> Panic: usf_dirbad: bad dir followed by syncing disks...65 65 9 1 1.. done.
> I'm replacing a Matox 8GM with a Matrox 36GM model 93652U8.  At boot time, FreeBSD reports wd0 34837MB (71346240 sectors) 70780 cyl, 16 heads, 63 S/T 512 T/S and the doc indicates I should use the BIOS values. I've tried several combinations, all yeild result.

The limit for the wd driver in CHS mode is 65536 cylinders.  Don't use
cylinders above # 65535, or you will get corrupted data on the
corresponding cylinders mod 65536, and errors like the above.

LBA mode has been reported to work, but is doesn't support kernel dumps.
Don't use kernel dumps with LBA mode, or you will get corrupted data.

Bruce
Comment 2 Søren Schmidt freebsd_committer freebsd_triage 2001-05-29 14:44:34 UTC 
State Changed
From-To: open->closed

This is not a problem from 4.x onwards.