Re: ATA/CHS problem (path + new information)

2004-04-13 Thread Roman Kurakin
Bruce Evans wrote: On Sun, 11 Apr 2004, Roman Kurakin wrote: I remind you that now I have two problems. First one that FreeBSD uses wrong assumption about which device should be CHS and which LBA: if (!ad_version(atadev->param->version_major) || !(atadev->param->atavalid & ATA_FLAG_54_58) || !l

Re: ATA/CHS problem (path + new information)

2004-04-13 Thread Bruce Evans
On Sun, 11 Apr 2004, Roman Kurakin wrote: > I remind you that now I have two problems. First one that FreeBSD uses > wrong assumption about which device should be CHS and which LBA: > > if (!ad_version(atadev->param->version_major) || > !(atadev->param->atavalid & ATA_FLAG_54_58) || !lbasize) > at

ATA/CHS problem (path + new information)

2004-04-11 Thread Roman Kurakin
Hi, You can find history of my previous postings below. I didn't moved far since that time, because lack of time. But any way I have some new information and one patch I want to share. This patch didn't solve any of my problems. Soren, please review it. This time it is comlete. I hope this patch

[Fwd: [Fwd: Re: ATA/CHS problem]]

2004-03-25 Thread Roman Kurakin
S?ren Schmidt wrote: Roman Kurakin wrote: This is not an LBA request. ATA driver thinks that I have 80G CHS device, cause it's ATA_FLAG_54_58 is zero. (This decision is incorrect, we shouldn't relay on this flag). I've checked another seagate 80G drive in CHS mode(by driver hacking), and prob

Re: ATA/CHS problem

2004-03-24 Thread S?ren Schmidt
Roman Kurakin wrote: This is not an LBA request. ATA driver thinks that I have 80G CHS device, cause it's ATA_FLAG_54_58 is zero. (This decision is incorrect, we shouldn't relay on this flag). I've checked another seagate 80G drive in CHS mode(by driver hacking), and problematic one with LBA mod

ATA/CHS problem

2004-03-24 Thread Roman Kurakin
Hi, (Was "HDD question" on hackers@, posted also here cause this is also CURRENT problem) History: >I have some problems with my HDD (ST380021A). The problem was checked on 5.2, 5.2.1, and some > 5.Current (cvsuped about week or two). > >At first I got this problem while system insta