New IT forum
27 June 2022, 05:19:50 am *
Welcome, %1$s. Please login or register.

: MiraBox now in stock.
 
Pages: 1 [2] 3

Author Topic: Guruserver plus esata bottleneck? [SOLVED]  (Read 34004 times)

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Guruserver plus esata bottleneck?
« Reply #15 on: 20 January 2012, 05:36:59 pm »

Quote
What exactly areyou trying to see here?
Fishing, and I caught a whale.

Quote
Logical/Physical Sector size:           512 bytes
This is wrong, we know it is 4k

The drive is either being misinterpreted by Linux, or is reporting the wrong information, I put my money on the latter.
Does the disk come with "special" drivers for use with windows, if so alarm bells should start ringing ?

The only two viable options I can think of are

1) upgrade the drive firmware (if available)
2) return to supplier for a different model

NB: I just googled and ended up at http://community.wdc.com/ seems you are not alone.....
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Guruserver plus esata bottleneck?
« Reply #16 on: 20 January 2012, 05:58:22 pm »

Apparently there are some jumpers on the drive that can change its behaviour, read the 'bit of paper' that came with the drive to see if it sheds any light.
Reading this may help a little ? http://hothardware.com/Reviews/WDs-1TB-Caviar-Green-w-Advanced-Format-Windows-XP-Users-Pay-Attention/
Don't see how the jumper is going to help after reading that....if I interpret it correctly for linux, you want the jumper off and the partition correctly aligned for best performance.
« Last Edit: 20 January 2012, 06:26:23 pm by Confusticated »
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Guruserver plus esata bottleneck?
« Reply #17 on: 20 January 2012, 07:20:01 pm »

Got this from the http://community.wdc.com forum

Code: [Select]
hdparm --yes-i-know-what-i-am-doing -m 16 /dev/sdaTry the 'dd' test after applying this.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #18 on: 20 January 2012, 07:49:56 pm »

grin about the i know what i am doing part (for i don't)

This is the before
Code: [Select]
hdparm -m /dev/sda

/dev/sda:
 multcount     =  0 (off)
aarde:/mnt/esata# dd if=/dev/zero of=/mnt/esata/test bs=1M count=256
256+0 records in
256+0 records out
268435456 bytes (268 MB) copied, 56.1324 s, 4.8 MB/s


and this was the after:

Code: [Select]
hdparm --yes-i-know-what-i-am-doing -m 16 /dev/sda

/dev/sda:
 setting multcount to 16
ata1.00: configured for UDMA/133
ata1: EH complete
 multcount     = 16 (on)
aarde:/mnt/esata# dd if=/dev/zero of=/mnt/esata/test bs=1M count=256
256+0 records in
256+0 records out
268435456 bytes (268 MB) copied, 60.8524 s, 4.4 MB/s

btw I checked sectorsize on an XP system and it is 512 bytes
Logged

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #19 on: 20 January 2012, 07:56:48 pm »

I read something on the label. It says i have to use a jumper when i use XP. For all the other OS'es NO jumper is just fine.

Cant I change sectorsize by formatting to 4k?
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Guruserver plus esata bottleneck?
« Reply #20 on: 20 January 2012, 09:33:04 pm »

I'm beaten, try anything you can think of :)
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #21 on: 21 January 2012, 07:03:33 am »

I am reading this article http://linuxconfig.org/linux-wd-ears-advanced-format

This seams to deal with my problem. *EDIT* Challenge *EDIT*
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Guruserver plus esata bottleneck?
« Reply #22 on: 21 January 2012, 05:08:58 pm »

Here is the 'hdparm -I' from the drive I used earlier in the thread. Apart from the size the output is identical to rjmentjens problem drive.



ATA device, with non-removable media
   Model Number:       WDC WD20EARS-00J2GB0                   
   Serial Number:      WD-WCAYY0148854
   Firmware Revision:  80.00A80
   Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
Standards:
   Supported: 8 7 6 5
   Likely used: 8
Configuration:
   Logical      max   current
   cylinders   16383   16383
   heads      16   16
   sectors/track   63   63
   --
   CHS current addressable sectors:   16514064
   LBA    user addressable sectors:  268435455
   LBA48  user addressable sectors: 3907029168
   Logical/Physical Sector size:           512 bytes
   device size with M = 1024*1024:     1907729 MBytes
   device size with M = 1000*1000:     2000398 MBytes (2000 GB)
   cache/buffer size  = unknown
Capabilities:
   LBA, IORDY(can be disabled)
   Queue depth: 32
   Standby timer values: spec'd by Standard, with device specific minimum
   R/W multiple sector transfer: Max = 16   Current = 0
   Recommended acoustic management value: 128, current value: 254
   DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
        Cycle time: min=120ns recommended=120ns
   PIO: pio0 pio1 pio2 pio3 pio4
        Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
   Enabled   Supported:
      *   SMART feature set
          Security Mode feature set
      *   Power Management feature set
      *   Write cache
      *   Look-ahead
      *   Host Protected Area feature set
      *   WRITE_BUFFER command
      *   READ_BUFFER command
      *   NOP cmd
      *   DOWNLOAD_MICROCODE
          Power-Up In Standby feature set
      *   SET_FEATURES required to spinup after power up
          SET_MAX security extension
          Automatic Acoustic Management feature set
      *   48-bit Address feature set
      *   Device Configuration Overlay feature set
      *   Mandatory FLUSH_CACHE
      *   FLUSH_CACHE_EXT
      *   SMART error logging
      *   SMART self-test
      *   General Purpose Logging feature set
      *   64-bit World wide name
      *   {READ,WRITE}_DMA_EXT_GPL commands
      *   Segmented DOWNLOAD_MICROCODE
      *   Gen1 signaling speed (1.5Gb/s)
      *   Gen2 signaling speed (3.0Gb/s)
      *   Native Command Queueing (NCQ)
      *   Host-initiated interface power management
      *   Phy event counters
      *   NCQ priority information
          DMA Setup Auto-Activate optimization
      *   Software settings preservation
      *   SMART Command Transport (SCT) feature set
      *   SCT Features Control (AC4)
      *   SCT Data Tables (AC5)
          unknown 206[12] (vendor specific)
          unknown 206[13] (vendor specific)
Security:
   Master password revision code = 65534
      supported
   not   enabled
   not   locked
   not   frozen
   not   expired: security count
      supported: enhanced erase
   426min for SECURITY ERASE UNIT. 426min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee25a1ed73a
   NAA      : 5
   IEEE OUI   : 0014ee
   Unique ID   : 25a1ed73a
Checksum: correct
Logged
NewITJames

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Guruserver plus esata bottleneck?
« Reply #23 on: 21 January 2012, 05:13:36 pm »

rmentjens,

What does dmesg report when the drive is mounted.

This is my 2TB  WD being mounted on a Dreamplug.

Quote
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
ata1.15: Port Multiplier 1.1, 0x197b:0x2352 r0, 2 ports, feat 0x0/0x0
ata1.15: Asynchronous notification not supported, hotplug won't
         work on fan-out ports. Use warm-plug instead.
ata1.00: hard resetting link
ata1.01: hard resetting link
ata1.00: ATA-8: WDC WD20EARS-00J2GB0, 80.00A80, max UDMA/133
ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata1: EH complete
scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EARS-00J 80.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 1:0:0:0: Attached scsi generic sg2 type 0
sd 1:0:0:0: [sdc] Write Protect is off
sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdc: sdc1 sdc3
sd 1:0:0:0: [sdc] Attached SCSI disk
Logged
NewITJames

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #24 on: 21 January 2012, 09:02:58 pm »

Well here goes:

Code: [Select]
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
ata1.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133
ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      WDC WD10EARS-00Y 80.0 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
Logged

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #25 on: 22 January 2012, 07:42:15 am »

Hello

I see no diffirence in the hdparm -I between our drives (apart from the obvious size difference).

There is however a difference between dmesg response (which is the same i presume as the bootup message i get with my jtag??)
My SATA link is at 1.5 Gbps, yours is at 3 Gbps.

Question, How is your drive connected to the plug. In an esata enclosure or directly with an esata -> sata cable?



I am making some progress here. I reformatted the drive but now in stead of sector 63 (Default) i started at sector 64.

This was my result:

Code: [Select]
dd if=/dev/zero of=/mnt/esata/test bs=1M count=256
256+0 records in
256+0 records out
268435456 bytes (268 MB) copied, 26.2425 s, 10.2 MB/s

So it went from 4 to 10 MB/s That is still not the 45 MB/s that NewIT_James found on his 20EARS drive.


Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: Guruserver plus esata bottleneck?
« Reply #26 on: 22 January 2012, 09:17:51 am »

Have you tried without Squeezebox and Mysql running?

Quote
1555 squeezeb  20   0 85104  74m 5208 S  2.3 14.8  13:49.53 squeezeboxserve
  870 root      20   0     0    0    0 S  0.7  0.0   0:00.09 jbd2/sda1-8
 1861 root      20   0  2548 1168  932 R  0.7  0.2   0:00.11 top
  141 root      20   0     0    0    0 S  0.3  0.0   0:00.22 ata/0
 1151 mysql     20   0  124m  16m 4736 S  0.3  3.3   0:58.81 mysqld

Which kernel are you running?


Logged
NewITJames

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #27 on: 22 January 2012, 11:02:15 am »

without squeezebox and mysql:

Code: [Select]
dd if=/dev/zero of=/mnt/esata/test bs=1M count=256
256+0 records in
256+0 records out
268435456 bytes (268 MB) copied, 26.0024 s, 10.3 MB/s

so no joy

My kernel:

Code: [Select]
uname  -a
Linux aarde 2.6.33.2-00003-g4b82fc0 #1 PREEMPT Thu Apr 22 03:29:35 PDT 2010 armv5tel GNU/Linux
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Guruserver plus esata bottleneck?
« Reply #28 on: 23 January 2012, 11:23:28 am »

Now the partition is correctly aligned, try taking u-boot out of the equation.
Boot Linux on the plug from either NAND, u-SD, or USB (don't do an 'ide reset' or any other 'ide' command in u-boot), then
Code: [Select]
dmesg -c
Connect the eSATA HDD (with the power already on and the drive spun up).
And post
Code: [Select]
dmesg
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

rmentjens

  • Newbie
  • *
  • Posts: 29
Re: Guruserver plus esata bottleneck?
« Reply #29 on: 23 January 2012, 06:50:34 pm »

Hello

Here the results. Are you suspecting something in the uboot?

dmesg -c after boot without HDD

Code: [Select]
dmesg -c
Linux version 2.6.33.2-00003-g4b82fc0 ([email protected]) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33.fa1)) #1 PREEMPT Thu Apr 22 03:29:35 PDT 2010
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Marvell GuruPlug Reference Board
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 131072
free_area_init_node: node 0, pgdat c052d684, node_mem_map c05dc000
  Normal zone: 1024 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 130048 pages, LIFO batch:31
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS0,115200 ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 513536KB available (4808K code, 862K data, 140K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:114
Console: colour dummy device 80x30
Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Kirkwood: MV88F6281-A1, TCLK=200000000.
Feroceon L2: Cache support initialised.
initial MPP regs: 01111111 11113311 33331111 33333333 00003333 00000222 00000000
  final MPP regs: 01111111 11113311 33331111 33333333 00003333 00000222 00000000
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: 00
    (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
    (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
    (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource orion_clocksource
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
PCI: CLS 0 bytes, default 32
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 4014, nTxLock = 32113
msgmni has been set to 1003
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
console [ttyS0] enabled
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0xec, Chip ID: 0xdc (Samsung NAND 512MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 1150 at 0x000008fc0000
Creating 3 MTD partitions on "orion_nand":
0x000000000000-0x000000100000 : "u-boot"
0x000000100000-0x000000500000 : "uImage"
0x000000500000-0x000020000000 : "root"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd2 to ubi0
UBI: MTD device name:            "root"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4055
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 4055
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 963/209
UBI: image sequence number: -1
UBI: background thread "ubi_bgt0d" started, PID 449
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
net eth0: port 0 with MAC address 00:50:43:01:90:1c
net eth1: port 0 with MAC address 00:50:43:01:90:1d
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
Registered led device: guruplug:red:health
Registered led device: guruplug:green:health
Registered led device: guruplug:red:wmode
Registered led device: guruplug:green:wmode
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mmc0: new high speed SDIO card at address 0001
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
Gating clock of unused units
before: 0x00dfc3fd
 after: 0x00cf41d9
rtc-mv rtc-mv: setting system clock to 2012-01-23 18:26:41 UTC (1327343201)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   516096000 bytes (504000 KiB, 492 MiB, 4000 LEBs)
UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
Freeing init memory: 140K
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 21
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
uap_probe: vendor=0x02DF device=0x9104 class=0 function=1
uap_sdio mmc0:0001:1: firmware: requesting mrvl/helper_sd.bin
ata1: SATA link down (SStatus 0 SControl F300)
uap_sdio mmc0:0001:1: firmware: requesting mrvl/sd8688_ap.bin
UAP FW is active
Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): eth1: link is not ready
warning: `ntpd' uses 32-bit capabilities (legacy support in use)
eth1: link up, 1000 Mb/s, full duplex, flow control disabled
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: no IPv6 routers present



and this is the dmesg after connecting:

Code: [Select]
dmesg
ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
ata1: SError: { PHYRdyChg DevExch }
ata1: hard resetting link
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
ata1.00: ATA-8: WDC WD10EARS-00Y5B1, 80.00A80, max UDMA/133
ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata1: EH complete
scsi 0:0:0:0: Direct-Access     ATA      WDC WD10EARS-00Y 80.0 PQ: 0 ANSI: 5
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
Logged
Pages: 1 [2] 3
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!