Re: Marvel controller gives errors Squeeze
On Sun, 01 Jul 2012 23:06:40 +0200, Mark Panen wrote:
> On 01/07/2012 18:11, Camaleón wrote:
>> Is ata2 your hdd? Run "dmesg | grep -i ata2" to find out.
> yes looks like it:
>
> [ 0.900101] ata2: SATA max UDMA/133 abar m2048@0xf3ff7000 port 0xf3ff7180 irq 35
> [ 1.722809] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Are you sure? I see no hard disk attached there :-?
This is my output ("ata1" is where my first sata disk is connected):
sm01@stt008:~$ dmesg | grep -i ata1
[ 1.845459] ata1: SATA max UDMA/133 abar m2048@0xdc627000 port 0xdc627100 irq 1277
[ 2.388162] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.428872] ata1.00: ATA-8: ST3250310NS, SN06, max UDMA/133
^^^^^^^^^^^
[ 2.434697] ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 2.475931] ata1.00: configured for UDMA/133
Despite the ata2 port is "up", I wonder why there's no device listed.
> Am i right it's only working at 1.5 Gbps when it should be 6 Gbps?
So it seems :-?
> hdparm -tT /dev/sda
>
> /dev/sda:
> Timing cached reads: 20022 MB in 2.00 seconds = 10021.38 MB/sec
> Timing buffered disk reads: 368 MB in 3.10 seconds = 118.71 MB/sec
>
> Would this be right or must i run hdparm on the / directory?
You should clear the buffer cache first but still, those values seem a
bit conservative for sata 6 hard disk (caviar black) with sata 6
controller.
Greetings,
--
Camaleón
Reply to: