public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: External HDD: sector size incorrectly detected on first connect
Date: Tue, 10 Mar 2015 18:12:56 +0100	[thread overview]
Message-ID: <20150310181256.696b1350@marcec.fritz.box> (raw)
In-Reply-To: <mddo18$b8v$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3406 bytes --]

Am Fri, 06 Mar 2015 18:33:13 -0800
schrieb walt <w41ter@gmail.com>:

[...]
> I once hated replies containing the question "Does it work under Windows?" but
> a bit of experience with usb3 external drives has made me rethink the matter.
> 
> Here's my thinking:  if the usb3 drive works correctly with Windows but not
> with linux, the problem is software -- i.e. the device driver.
> 
> The xhci driver is under heavy development because usb3 is still new tech, and
> I've found and reported a few bugs in the last year or so and they got fixed.
[...]

OK, so I tried this out, and it apparently worked fine under Windows 8 (I
created a third FAT32 partition for this).  Once Windows installed the drivers
(or whatever) the drive was recognised and the partition mounted without
trouble.

Immediately after that, I unplugged it and moved it back to my computer, where I
plugged it in as usual and then turned the computer on.  The problem occurred
again, of course:

    # journalctl -k -b | grep sdg
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] 5860533160 512-byte logical blocks: (3.00 TB/2.72 TiB)
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Write Protect is off
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Mode Sense: 2b 00 00 00
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
    Mär 10 17:58:57 marcec kernel:  sdg: sdg1 sdg2 sdg3
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
    Mär 10 17:58:57 marcec kernel: sd 8:0:0:0: [sdg] Attached SCSI disk
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16).
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] Write Protect is off
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] Mode Sense: 2b 00 00 00
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    Mär 10 18:00:33 marcec kernel:  sdg: sdg1 sdg2 sdg3
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
    Mär 10 18:00:33 marcec kernel: sd 9:0:0:0: [sdg] Attached SCSI disk
    Mär 10 18:00:35 marcec kernel: BTRFS: device label MARCEC_BACKUP devid 1 transid 64666 /dev/sdg2
    Mär 10 18:00:35 marcec kernel: BTRFS info (device sdg2): disk space caching is enabled
    Mär 10 18:00:42 marcec kernel: EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: (null)

So, what do other list members think: is it most likely a driver bug, or
something else (especially considering the reboot behaviour I mentioned in
another email)? Should I ask on the LKML, or is there a specialised ML for the
Linux USB stack?

Greetings
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-03-10 17:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 19:44 [gentoo-user] External HDD: sector size incorrectly detected on first connect Marc Joliet
2015-03-07  2:33 ` [gentoo-user] " walt
2015-03-07 10:24   ` Marc Joliet
2015-03-10  9:45     ` Marc Joliet
2015-03-10 16:58       ` Hans
2015-03-10 17:15         ` Marc Joliet
2015-03-10 17:12   ` Marc Joliet [this message]
2015-03-11  0:38     ` walt
2015-03-11  0:53       ` Dutch Ingraham
2015-03-11  7:04       ` Marc Joliet
2015-03-22 13:28         ` Marc Joliet
2015-04-01 19:04           ` Marc Joliet

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=20150310181256.696b1350@marcec.fritz.box \
    --to=marcec@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox