> No, the problem is that you must use the ada(4) driver instead of ad(4).
> The new physical and logical sector support has only been implemented
> for the newer AHCI-over-CAM stack.
pass0: Raw identify data:
0: 427a 3fff c837 0010 003f
8: 2020 2020 2057 442d 574d
On 2010-04-09 13:00, Alexey Tarasov wrote:
/dev/ad4
512 # sectorsize
1500301910016 # mediasize in bytes (1.4T)
2930277168 # mediasize in sectors
0 # stripesize
0 # stripeoffset
2907021 # Cylinders according to firmware
Alexander Motin wrote:
> Andriy Gapon wrote:
>> on 09/04/2010 14:00 Alexey Tarasov said the following:
>>> I've booted from dvd to fixit mode and got the following:
>>> /dev/ad4
>>>512 # sectorsize
>>>1500301910016 # mediasize in bytes (1.4T)
>>>2930277168 # mediasize
Andriy Gapon wrote:
> on 09/04/2010 14:00 Alexey Tarasov said the following:
>> I've booted from dvd to fixit mode and got the following:
>> /dev/ad4
>>512 # sectorsize
>>1500301910016 # mediasize in bytes (1.4T)
>>2930277168 # mediasize in sectors
>>0
> I saw it, but I want to see what's reported in reality.
Installing Windows 7 now. How can OS installation be so long? :-)
--
Alexey Tarasov
(\__/)
(='.'=)
E[: | | | | :]З
(")_(")
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.
on 09/04/2010 14:31 Dag-Erling Smørgrav said the following:
> Andriy Gapon writes:
>> P.S. DES's name looks strange in headers :-)
>
> Get a better MUA. MIME quoted-printable has been around for what, 15
> years?
The advice is misdirected. Right, Dmitry? :-)
--
Andriy Gapon
_
on 09/04/2010 14:33 Alexey Tarasov said the following:
> On 09.04.2010, at 15:32, Andriy Gapon wrote:
>
>> on 09/04/2010 14:27 Alexey Tarasov said the following:
Or the disk doesn't actually report 4096 anywhere anyhow... Have you
considered that? If yes, can you verify using any tools
On 09.04.2010, at 15:32, Andriy Gapon wrote:
> on 09/04/2010 14:27 Alexey Tarasov said the following:
>>> Or the disk doesn't actually report 4096 anywhere anyhow... Have you
>>> considered that? If yes, can you verify using any tools of any OS that the
>>> disk reports 4K in any way?
>>
>> In
on 09/04/2010 14:27 Alexey Tarasov said the following:
>> Or the disk doesn't actually report 4096 anywhere anyhow... Have you
>> considered that? If yes, can you verify using any tools of any OS that the
>> disk reports 4K in any way?
>
> In the previous discussion we found that the disk report
Andriy Gapon writes:
> P.S. DES's name looks strange in headers :-)
Get a better MUA. MIME quoted-printable has been around for what, 15
years?
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
> Or the disk doesn't actually report 4096 anywhere anyhow... Have you
> considered
> that? If yes, can you verify using any tools of any OS that the disk reports
> 4K
> in any way?
In the previous discussion we found that the disk reports 512 sector size, but
there are additional ATA comman
on 09/04/2010 14:00 Alexey Tarasov said the following:
> I've booted from dvd to fixit mode and got the following:
>
> FreeBSD 8.0-STABLE-201002 FreeBSD 8.0-STABLE-201002 #0: Tue Feb 16 21:05:59
> UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>
> ATA channel 0:
> M
I've booted from dvd to fixit mode and got the following:
FreeBSD 8.0-STABLE-201002 FreeBSD 8.0-STABLE-201002 #0: Tue Feb 16 21:05:59
UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
ATA channel 0:
Master: ad0 ATA/ATAPI revision 0
Slave: no device present
ATA
On 2010-04-08 21:34, Alexey Tarasov wrote:
Thank you for the information.
In 8-STABLE snapshot 201002 diskinfo shows 512k sector size yet.
I will try CURRENT tomorrow.
It looks like the code was MFC'd to stable/8 in r199443. However, even
in -CURRENT, the sector size you see in diskinfo will a
I agree with you completely.
Seems that support of this disks is already commited in CURRENT, will try it
tomorrow.
> A better approach is to have tunables for geom_disk to do this. This should
> absolutely
> not be part of a partitioning tool. It violates everything there is to
> violate AFAIC
Hello.
Thank you for the information.
In 8-STABLE snapshot 201002 diskinfo shows 512k sector size yet.
I will try CURRENT tomorrow.
On 08.04.2010, at 19:35, Dimitry Andric wrote:
> On 2010-04-08 17:24, Gary Jennejohn wrote:
References
The ATA8-ACS and SBC-3 standards have provisions fo
On Apr 8, 2010, at 6:06 AM, Alexey Tarasov wrote:
> Hello.
>
> There is only one possibility to change sector size of physical disk (gnop -S
> 4096 ...).
> May be it is possible to add such possibility to gpart? e.g. gpart create -S
> 4096 -t gpt ad0?
> It will help all unlucky WD Advanced For
On 2010-04-08 17:24, Gary Jennejohn wrote:
References
The ATA8-ACS and SBC-3 standards have provisions for a disk drive to report
Advanced Format sector sizes and other performance optimization information.
These standards are used for SATA, SAS, USB, and IEEE 1394 based interface
technologies
On Thu, 8 Apr 2010 18:40:50 +0400
Alexey Tarasov wrote:
> http://www.wdc.com/wdproducts/library/WhitePapers/ENG/2579-771430.pdf
>
> > References
> > The ATA8-ACS and SBC-3 standards have provisions for a disk drive to report
> > Advanced Format sector sizes and other performance optimization
>
http://www.wdc.com/wdproducts/library/WhitePapers/ENG/2579-771430.pdf
> References
> The ATA8-ACS and SBC-3 standards have provisions for a disk drive to report
> Advanced Format sector sizes and other performance optimization information.
> These standards are used for SATA, SAS, USB, and IEEE
Alexey Tarasov writes:
> Advanced Format disks reports 512, but there is another command in ATA
> standard which can tell us if it uses 4k sector.
Send me one and I'll look into it :)
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebs
> 1) There is already an ATA command to report both physical and logical
> sector sizes, but the disk lies - it always reports 512/512.
Advanced Format disks reports 512, but there is another command in ATA standard
which can tell us if it uses 4k sector.
> 2) The disk may have already been fo
Alexey Tarasov writes:
> Ok, in case of GPT? :-)
I doubt it, but I don't know for sure.
> GPT implementation can be the simplest solution to this problem
> compared to implementing additional ATA commands to determine if disk
> is in Advanced Format.
There are two issues:
1) There is already a
Ok, in case of GPT? :-)
GPT implementation can be the simplest solution to this problem compared to
implementing additional ATA commands to determine if disk is in Advanced Format.
On 08.04.2010, at 18:09, Dag-Erling Smørgrav wrote:
> Alexey Tarasov writes:
>> I mean that gpart should act like
Alexey Tarasov writes:
> I mean that gpart should act like gnop presenting another sector size
> to user. I that possible at all?
That depends on the underlying partition scheme. My guess is "no".
(it all boils down to whether the desired logical sector size can
somehow be recorded on-disk)
D
No, no.
I mean that gpart should act like gnop presenting another sector size to user.
I that possible at all?
On 08.04.2010, at 17:36, Dag-Erling Smørgrav wrote:
> I don't quite see how that would work - do you mean gpart should
> configure a gnop? AFAIK there is no "gnop label", so you can't s
Alexey Tarasov writes:
> There is only one possibility to change sector size of physical disk
> (gnop -S 4096 ...). May be it is possible to add such possibility to
> gpart? e.g. gpart create -S 4096 -t gpt ad0?
I don't quite see how that would work - do you mean gpart should
configure a gnop?
Hello.
There is only one possibility to change sector size of physical disk (gnop -S
4096 ...).
May be it is possible to add such possibility to gpart? e.g. gpart create -S
4096 -t gpt ad0?
It will help all unlucky WD Advanced Format disks users. :-D
--
Alexey Tarasov
(\__/)
(='.'=)
E[: | |
28 matches
Mail list logo
