NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/38376: Hitachi HDD need LBA48-QUIRK
>Number: 38376
>Category: kern
>Synopsis: Hitachi HDD need LBA48-QUIRK
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Apr 06 13:55:00 +0000 2008
>Originator: Martin Seibold
>Release: 4.0
>Organization:
none
>Environment:
NetBSD 4.0/i386 - i think all architectures are affected
>Description:
I use Raidframe mode 5 on Hitachi "Deskstar" 500GB disks via the satalink
driver. While writing initial paririty on the disks i discovered that these
discs have also problems with LBA48-addressing like the Seagates. I got "error
reading fsbn 268435424 of 268435424 - 268435455". So i
changed my LBA48_TRESHHOLD to 0xfffffe0 instead the default 268435455 in my
dev/ata/wd.c and built a new kernel. After that, everything seemed fine.
Then - for testing purposes - i manually faild one of my disks and
started reconstruction. After some time the reconstruction progress stopped
with the same error message "error reading fsbn 268435424".
Finally i set my LBA48_TRESHHOLD to 0xfffffd0 and reconstruction finished.
>How-To-Repeat:
Try to access the last sectors in front of the LBA48-area.
>Fix:
Someone should add HD* disks like my HDP725050 to the wd_quirk_table in
ata/wd.clike the following:
This should work for E7K/P7K/T7K [2] "Deskstars":
{ "HD[P-T][0-9][0-9][0-9][0-9][2-9][0-9]*",
WD_QUIRK_FORCE_LBA48 }
It would be nice to see an option for specifying LBA48_TRESHHOLD in kernel
konfiguration file too.
Cave: Maybe there is another Problem in raidframe involved too, since changing
the treshhold to 0xfffffe0 didn't work. _It had to be 0xfffffd0 when using
raidframe_.
Home |
Main Index |
Thread Index |
Old Index