linux-kernel - Re: Testing 1 hard disk in 3 different usb enclosures: kernel reports 3 different "numbers of sectors"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 21 Mar 2014 09:54:52 +0100
From:	Clemens Ladisch <clemens@...isch.de>
To:	Jaime T <enopatch@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Testing 1 hard disk in 3 different usb enclosures: kernel reports
 3 different "numbers of sectors"

Jaime T wrote:
> I'd like to use my 1TB Seagate hard disk on my linux box, and I've
> tested it using 3 different usb-sata enclosures.
>
> kernel: [10612.017588] usb 1-1: New USB device found, idVendor=14cd, idProduct=6116
> kernel: [10612.017602] usb 1-1: Product: USB Mass Storage Device
> kernel: [10612.017607] usb 1-1: Manufacturer: Generic
> kernel: [10730.225053] usb 1-1: New USB device found, idVendor=152d, idProduct=2509
> kernel: [10730.225067] usb 1-1: Product: Usb production
> kernel: [10730.225072] usb 1-1: Manufacturer: JMicron
> kernel: [10837.309203] usb 1-2: New USB device found, idVendor=152d, idProduct=2339
> kernel: [10837.309218] usb 1-2: Product: USB to ATA/ATAPI Bridge
> kernel: [10837.309223] usb 1-2: Manufacturer: JMicron
>
> kernel: [10613.019646] sd 25:0:0:0: [sdb] 1953525166 512-byte logical blocks: (1.00 TB/931 GiB)
> kernel: [10731.227818] sd 26:0:0:0: [sdb] 1953524995 512-byte logical blocks: (1.00 TB/931 GiB)
> kernel: [10838.311867] sd 27:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
>
> So Linux (v3.10.25) is reporting 3 different sizes/numbers of sectors
> for the same single hard disk.

The kernel just reports what the device reports.

> Could this be a problem with regards to possible future data
> corruption, or is it something that I can safely ignore?

It is likely that you will not be able to access the sectors beyond
the reported limit.  It might be possible that the enclosure does not
ignore those sectors but uses them to store its own management data.


Regards,
Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/