From: "Eugen Rogoza" <euro123@gmx.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Alignment issue with 4K disk
Date: Sun, 10 Jan 2016 18:22:29 +0100 [thread overview]
Message-ID: <trinity-7aa252ab-8466-4bac-9dd3-dac041babeae-1452446548941@3capp-gmx-bs52> (raw)
> My personal opinion is: The test is semantically wrong in different
> aspects. May I ask what drive you are using and what interface it uses?
>
> Regards
>
> -Sven
Hi Sven,
drive info below:
root@nuc:~> hdparm -I /dev/sdc
/dev/sdc:
ATA device, with non-removable media
Model Number: WDC WD60EZRX-00MVLB1
Serial Number: WD-WX41D94RNKAX
Firmware Revision: 80.00A80
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0
Standards:
Used: unknown (minor revision code 0x001f)
Supported: 9 8 7 6 5
Likely used: 9
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:11721045168
Logical Sector size: 512 bytes
Physical Sector size: 4096 bytes
device size with M = 1024*1024: 5723166 MBytes
device size with M = 1000*1000: 6001175 MBytes (6001 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: 5700
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
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
* 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
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* NCQ priority information
* unknown 76[15]
DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
* DOWNLOAD MICROCODE DMA command
* WRITE BUFFER DMA command
* READ BUFFER DMA command
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
Logical Unit WWN Device Identifier: 50014ee20b2a3e40
NAA : 5
IEEE OUI : 0014ee
Unique ID : 20b2a3e40
Checksum: correct
It is an internal 3,5" SATA-drive put into a USB3-enclosure and connected via USB3 in UAS mode:
Jan 10 01:13:26 nuc kernel: usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
Jan 10 01:13:26 nuc kernel: usb 2-4: New USB device found, idVendor=174c, idProduct=55aa
Jan 10 01:13:26 nuc kernel: usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jan 10 01:13:26 nuc kernel: usb 2-4: Product: ASM1153E
Jan 10 01:13:26 nuc kernel: usb 2-4: Manufacturer: asmedia
Jan 10 01:13:26 nuc kernel: usb 2-4: SerialNumber: 1234567891C4
Jan 10 01:13:26 nuc kernel: scsi host4: uas
Jan 10 01:13:26 nuc kernel: usbcore: registered new interface driver uas
Jan 10 01:13:26 nuc kernel: scsi 4:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6
Jan 10 01:13:26 nuc kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
Jan 10 01:13:26 nuc kernel: sd 4:0:0:0: [sdc] Spinning up disk...
Jan 10 01:13:27 nuc kernel: ............ready
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] 11721045168 512-byte logical blocks: (6.00 TB/5.45 TiB)
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] 4096-byte physical blocks
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] Write Protect is off
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] Mode Sense: 43 00 00 00
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 10 01:13:38 nuc kernel: sdc: sdc1 sdc2 sdc3 sdc4
Jan 10 01:13:38 nuc kernel: sd 4:0:0:0: [sdc] Attached SCSI disk
As a side note: sdc4 was a dm-crypt/LUKS-encrypted partition before. To my knowledge the device mapper warnings started to appear after migration to VeraCrypt.
Cheers,
Eugen
next reply other threads:[~2016-01-10 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 17:22 Eugen Rogoza [this message]
2016-01-10 19:13 ` [dm-crypt] Alignment issue with 4K disk Sven Eschenberg
2016-01-10 20:20 ` Eugen Rogoza
2016-01-10 21:00 ` Sven Eschenberg
-- strict thread matches above, loose matches on Subject: below --
2016-01-10 15:37 Eugen Rogoza
2016-01-10 15:18 Eugen Rogoza
2016-01-10 0:25 Eugen Rogoza
2016-01-10 1:14 ` Sven Eschenberg
2016-01-10 4:30 ` Sven Eschenberg
2016-01-04 21:31 Yves-Alexis Perez
2016-01-04 21:54 ` Sven Eschenberg
2016-01-04 22:20 ` Yves-Alexis Perez
2016-01-04 22:41 ` Sven Eschenberg
2016-01-04 23:02 ` Sven Eschenberg
2016-01-05 10:14 ` Yves-Alexis Perez
2016-01-07 18:00 ` .. ink ..
2016-01-09 12:30 ` Milan Broz
2016-01-09 14:47 ` Sven Eschenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-7aa252ab-8466-4bac-9dd3-dac041babeae-1452446548941@3capp-gmx-bs52 \
--to=euro123@gmx.net \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.