Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.hardware > #2436 > unrolled thread

usb external drives not reliable for linux?

Back to article view | Back to comp.os.linux.hardware

Contents

  usb external drives not reliable for linux? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2014-06-21 16:34 +0000
    Re: usb external drives not reliable for linux? Stef <not@this.address.com> - 2014-06-22 01:26 +0000
      Re: usb external drives not reliable for linux? "Ralf S. Hellersen" <schneiderxr@arcor.de> - 2014-08-08 19:59 +0000
        Re: usb external drives not reliable for linux? Bobbie Sellers <bliss-sf4ever@dslextreme.com> - 2014-08-08 15:35 -0700
    Re: usb external drives not reliable for linux? Clark Smith <noaddress@nowhere.net> - 2014-06-22 01:28 +0000
      Re: usb external drives not reliable for linux? JEDIDIAH <jedi@nomad.mishnet> - 2014-06-23 09:42 -0500
        Re: usb external drives not reliable for linux? Eric Pozharski <whynot@pozharski.name> - 2014-06-24 10:18 +0300
          Re: usb external drives not reliable for linux? Baho Utot <baho-utot@invalid.com> - 2014-06-24 07:36 -0400
            Re: usb external drives not reliable for linux? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2014-06-24 18:32 +0000
              Re: usb external drives not reliable for linux? Baho Utot <baho-utot@invalid.com> - 2014-06-24 16:47 -0400
    Re: usb external drives not reliable for linux? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2014-06-22 13:41 +0000
      Re: usb external drives not reliable for linux? Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2014-06-23 05:13 +0000
      Re: usb external drives not reliable for linux? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2014-06-24 20:10 +0000
        Re: usb external drives not reliable for linux? Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> - 2014-06-25 06:04 +0000
          Re: usb external drives not reliable for linux? "Charles T. Smith" <cts.private.yahoo@gmail.com> - 2014-06-25 19:04 +0000

#2436 — usb external drives not reliable for linux?

Hi,

I bought an external usb drive for external storage for my linux system.  
I discover that after a while (15 minutes?) of inactivity, I get this 
message:

  ls: reading directory .: Input/output error

If I cd away and back again, my directory is back.  Is that implicit in 
usb or the drive?  Can a disk be made to not do that?  I have it mounted
in sync mode.

cts

[toc] | [next] | [standalone]

#2437

Charles T. Smith wrote:

> I bought an external usb drive for external storage for my linux system.  
> I discover that after a while (15 minutes?) of inactivity, I get this 
> message:
>
>   ls: reading directory .: Input/output error
>
> If I cd away and back again, my directory is back.  Is that implicit in 
> usb or the drive?  Can a disk be made to not do that?  I have it mounted
> in sync mode.

I'm going to take a wild guess, and say check your Power Settings.
 It sounds like your external drive is being powered down due to lack
of activity.

If you gave more information like what distro you're using and what it's
running on, maybe, more than a guess can be offered.

Stef

[toc] | [prev] | [next] | [standalone]

#2518

Am Sun, 22 Jun 2014 01:26:25 +0000 schrieb Stef:

>>   ls: reading directory .: Input/output error

Hi all,

just my comment. We bought a 320 GB Disk and had no problems. So we were 
happy. With a later bought 1000 GB we got the same errors and sent it 
back. (It worked with Win*).

I read about and found that someone suggested this comes from
"the nfs3g driver under Linux, which was not adapted complete".

I ask for pardon, but I am just user and no expert and did not save any 
sources regarding this issue. Perhaps it helps.


-- 
Wegen SPAM: Für e-mail verwenden: "errr" statt "erxr" oder mein Kontakt-
Formular auf www.pis-db.de  !

[toc] | [prev] | [next] | [standalone]

#2519

On 08/08/2014 12:59 PM, Ralf S. Hellersen wrote:
> Am Sun, 22 Jun 2014 01:26:25 +0000 schrieb Stef:
>
>>>    ls: reading directory .: Input/output error
>
> Hi all,
>
> just my comment. We bought a 320 GB Disk and had no problems. So we were
> happy. With a later bought 1000 GB we got the same errors and sent it
> back. (It worked with Win*).
>
> I read about and found that someone suggested this comes from
> "the nfs3g driver under Linux, which was not adapted complete".
>
> I ask for pardon, but I am just user and no expert and did not save any
> sources regarding this issue. Perhaps it helps.
>
>
	Well I have a 1000 GiB external hard drive in a after market
cheap case and have no problems with it aside of having to chown it
usually after a fresh install.
	So seldom that I forget the procedure in the intervals.

	But USB itself has problems.
<http://www.bbc.com/news/technology-28701124>

	Now I dunno how you have the disk formatted but it sounds since
it works with Windows that it must be NTFS?

	Now that works with my Mageia 4.1 in that I can read and write usually 
to NTFS directories.  But it is not a Linux native system so
I suggest you re-partition that drive so that part according to your
work loads in the various OS you employ but so that you have not only
an NTFS partition but a Linux partition file system depending on use
but ext4 is great except for very large files.

	Now despite USB's critical flaws I am going back to watching my
show on my external hard drive played by my computer thru ,hdmi to the
32 inch full HD screen.

	bliss
	

[toc] | [prev] | [next] | [standalone]

#2438

On Sat, 21 Jun 2014 16:34:34 +0000, Charles T. Smith wrote:

> Hi,
> 
> I bought an external usb drive for external storage for my linux system.
> I discover that after a while (15 minutes?) of inactivity, I get this
> message:
> 
>   ls: reading directory .: Input/output error
> 
> If I cd away and back again, my directory is back.  Is that implicit in
> usb or the drive?  Can a disk be made to not do that?  I have it mounted
> in sync mode.

	You may have been unlucky enough to have bought a defective disk. 
I have had several external USB disks attached to my Linux system for 
years, and have yet to have any problems with them.

[toc] | [prev] | [next] | [standalone]

#2445

On 2014-06-22, Clark Smith <noaddress@nowhere.net> wrote:
> On Sat, 21 Jun 2014 16:34:34 +0000, Charles T. Smith wrote:
>
>> Hi,
>> 
>> I bought an external usb drive for external storage for my linux system.
>> I discover that after a while (15 minutes?) of inactivity, I get this
>> message:
>> 
>>   ls: reading directory .: Input/output error
>> 
>> If I cd away and back again, my directory is back.  Is that implicit in
>> usb or the drive?  Can a disk be made to not do that?  I have it mounted
>> in sync mode.
>
> 	You may have been unlucky enough to have bought a defective disk. 
> I have had several external USB disks attached to my Linux system for 
> years, and have yet to have any problems with them.
>

     I have a "file server" setup to use an external USB drive. It chugs
along pretty much trouble free. It serves a number of Windows desktops and
is the only machine in that office that no one ever has to worry about.

     I also have used various external devices on my own desktop including
thumbdrives, USB hard drives, various mobile devices, an eSATA array, and
a USB SATA socket. These have never given me any trouble.

-- 
	Apple: because TRANS.TBL is an mp3 file. It really is!      |||
								   / | \

[toc] | [prev] | [next] | [standalone]

#2446

with <slrnlqgf6i.c3d.jedi@nomad.mishnet> JEDIDIAH wrote:

*SKIP*
>      I also have used various external devices on my own desktop
>      including thumbdrives, USB hard drives, various mobile devices,
>      an eSATA array, and a USB SATA socket. These have never given me
>      any trouble.

Fast 2.0 USB thumb;  it has been in use (as a big diskette) for a year
(literally), then died.  Resetting controller didn't help.  It really
was fast -- provided ~20MB/s write speed.

SD card has been left without usage for a year then taken for a job (as
a big diskette).  After half year it started requiring massage for being
detected (plug-unplug cycles).  Then came the last time -- now it's 1GB
instead of 16GB.

(not mine) I took a challenge to heavy lift whatever possible from an
USB thumb.  When certain blocks had been accessed the thumb reset itself
-- I've made a script that used 'udevadm monitor' for wakeup detection
and lifted "whatever possible".  According to owner's report the thumb
was in use for a month (literally).

Two IRDA dongles -- never worked;  what's probably OK, they needed weird
setup.  When, after a pause (about a year) I'd made a second attempt
each just ceased to wakeup.

CDMA modem worked for a year (I wouldn't say flawlessly) developed a
requirement -- pppd had to be in within 10min, otherwise negotitions
would take forever.

UMTS modem worked for 4year (literally, it died 4y+2d after first
plug-in) (I wouldn't say flawlessly), then ZeroCD ceased to work with
block device errors present instead.

And not to mention USB closure!  When I'd tried it first time I'd pluged
in by-instructions and unplugged by-logic (reverse-in).  Then The Second
Move has(sic!) come -- I've unplugged by-instructions.  Putting a long
story short -- I've burned down one USB-host.  That was spectacular, no
flames though.

It has been put aside, then squeeze had come.  All DVD-images came out
with errors.  I've collected some stats -- no clear pattern.  So I've
made a script that lifted those 16 DVD-images.  It took some time
though.

I don't mention two UMTS modems with 'normal-termination-by-ncp' disease
-- that's on ISP side and I have no options.

I ain't no heavy user -- I have a couple of thumbs, developing a
collection of SD-cards, some USB-devices and such.  I've never faced
problems with cameras and recorders (whenever I've faced those).

-- 
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom

[toc] | [prev] | [next] | [standalone]

#2447

Eric Pozharski wrote:

> with <slrnlqgf6i.c3d.jedi@nomad.mishnet> JEDIDIAH wrote:
> 
> *SKIP*
>>      I also have used various external devices on my own desktop
>>      including thumbdrives, USB hard drives, various mobile devices,
>>      an eSATA array, and a USB SATA socket. These have never given me
>>      any trouble.
> 
> Fast 2.0 USB thumb;  it has been in use (as a big diskette) for a year
> (literally), then died.  Resetting controller didn't help.  It really
> was fast -- provided ~20MB/s write speed.
> 
> SD card has been left without usage for a year then taken for a job
> (as
> a big diskette).  After half year it started requiring massage for
> being
> detected (plug-unplug cycles).  Then came the last time -- now it's
> 1GB instead of 16GB.
> 
> (not mine) I took a challenge to heavy lift whatever possible from an
> USB thumb.  When certain blocks had been accessed the thumb reset
> itself -- I've made a script that used 'udevadm monitor' for wakeup
> detection
> and lifted "whatever possible".  According to owner's report the thumb
> was in use for a month (literally).
> 
> Two IRDA dongles -- never worked;  what's probably OK, they needed
> weird
> setup.  When, after a pause (about a year) I'd made a second attempt
> each just ceased to wakeup.
> 
> CDMA modem worked for a year (I wouldn't say flawlessly) developed a
> requirement -- pppd had to be in within 10min, otherwise negotitions
> would take forever.
> 
> UMTS modem worked for 4year (literally, it died 4y+2d after first
> plug-in) (I wouldn't say flawlessly), then ZeroCD ceased to work with
> block device errors present instead.
> 
> And not to mention USB closure!  When I'd tried it first time I'd
> pluged
> in by-instructions and unplugged by-logic (reverse-in).  Then The
> Second
> Move has(sic!) come -- I've unplugged by-instructions.  Putting a long
> story short -- I've burned down one USB-host.  That was spectacular,
> no flames though.
> 
> It has been put aside, then squeeze had come.  All DVD-images came out
> with errors.  I've collected some stats -- no clear pattern.  So I've
> made a script that lifted those 16 DVD-images.  It took some time
> though.
> 
> I don't mention two UMTS modems with 'normal-termination-by-ncp'
> disease -- that's on ISP side and I have no options.
> 
> I ain't no heavy user -- I have a couple of thumbs, developing a
> collection of SD-cards, some USB-devices and such.  I've never faced
> problems with cameras and recorders (whenever I've faced those).
> 

[admin@raspberrypi ~]$ uptime
 07:31:48 up 398 days, 20:50,  1 user,  load average: 0.05, 0.12, 0.09

Raspberry PI model B

Has SD card and USB 32GB thumb drive

Runs DNS, News groups, Email and file serving services for LAN.

Cost efficient and very quiet.

[toc] | [prev] | [next] | [standalone]

#2448

On Tue, 24 Jun 2014 07:36:28 -0400, Baho Utot wrote:

> Eric Pozharski wrote:
> 
>> with <slrnlqgf6i.c3d.jedi@nomad.mishnet> JEDIDIAH wrote:
>> 
>> *SKIP*
>>>      I also have used various external devices on my own desktop
>>>      including thumbdrives, USB hard drives, various mobile devices,
>>>      an eSATA array, and a USB SATA socket. These have never given me
>>>      any trouble.
>> 
>> Fast 2.0 USB thumb;  it has been in use (as a big diskette) for a year
>> (literally), then died.  Resetting controller didn't help.  It really
>> was fast -- provided ~20MB/s write speed.
>> 
>> SD card has been left without usage for a year then taken for a job (as
>> a big diskette).  After half year it started requiring massage for
>> being
>> detected (plug-unplug cycles).  Then came the last time -- now it's 1GB
>> instead of 16GB.
>> 
>> (not mine) I took a challenge to heavy lift whatever possible from an
>> USB thumb.  When certain blocks had been accessed the thumb reset
>> itself -- I've made a script that used 'udevadm monitor' for wakeup
>> detection
>> and lifted "whatever possible".  According to owner's report the thumb
>> was in use for a month (literally).
>> 
>> Two IRDA dongles -- never worked;  what's probably OK, they needed
>> weird
>> setup.  When, after a pause (about a year) I'd made a second attempt
>> each just ceased to wakeup.
>> 
>> CDMA modem worked for a year (I wouldn't say flawlessly) developed a
>> requirement -- pppd had to be in within 10min, otherwise negotitions
>> would take forever.
>> 
>> UMTS modem worked for 4year (literally, it died 4y+2d after first
>> plug-in) (I wouldn't say flawlessly), then ZeroCD ceased to work with
>> block device errors present instead.
>> 
>> And not to mention USB closure!  When I'd tried it first time I'd
>> pluged
>> in by-instructions and unplugged by-logic (reverse-in).  Then The
>> Second
>> Move has(sic!) come -- I've unplugged by-instructions.  Putting a long
>> story short -- I've burned down one USB-host.  That was spectacular, no
>> flames though.
>> 
>> It has been put aside, then squeeze had come.  All DVD-images came out
>> with errors.  I've collected some stats -- no clear pattern.  So I've
>> made a script that lifted those 16 DVD-images.  It took some time
>> though.
>> 
>> I don't mention two UMTS modems with 'normal-termination-by-ncp'
>> disease -- that's on ISP side and I have no options.
>> 
>> I ain't no heavy user -- I have a couple of thumbs, developing a
>> collection of SD-cards, some USB-devices and such.  I've never faced
>> problems with cameras and recorders (whenever I've faced those).
>> 
>> 
> [admin@raspberrypi ~]$ uptime
>  07:31:48 up 398 days, 20:50,  1 user,  load average: 0.05, 0.12, 0.09
> 
> Raspberry PI model B
> 
> Has SD card and USB 32GB thumb drive
> 
> Runs DNS, News groups, Email and file serving services for LAN.
> 
> Cost efficient and very quiet.


Hey, that's cool.  I'd like to try that.  What brand flash drive did you 
use?

[toc] | [prev] | [next] | [standalone]

#2450

Charles T. Smith wrote:

> On Tue, 24 Jun 2014 07:36:28 -0400, Baho Utot wrote:
> 
>> Eric Pozharski wrote:
>> 
>>> with <slrnlqgf6i.c3d.jedi@nomad.mishnet> JEDIDIAH wrote:
>>> 
>>> *SKIP*
>>>>      I also have used various external devices on my own desktop
>>>>      including thumbdrives, USB hard drives, various mobile
>>>>      devices, an eSATA array, and a USB SATA socket. These have
>>>>      never given me any trouble.
>>> 
>>> Fast 2.0 USB thumb;  it has been in use (as a big diskette) for a
>>> year
>>> (literally), then died.  Resetting controller didn't help.  It
>>> really was fast -- provided ~20MB/s write speed.
>>> 
>>> SD card has been left without usage for a year then taken for a job
>>> (as
>>> a big diskette).  After half year it started requiring massage for
>>> being
>>> detected (plug-unplug cycles).  Then came the last time -- now it's
>>> 1GB instead of 16GB.
>>> 
>>> (not mine) I took a challenge to heavy lift whatever possible from
>>> an
>>> USB thumb.  When certain blocks had been accessed the thumb reset
>>> itself -- I've made a script that used 'udevadm monitor' for wakeup
>>> detection
>>> and lifted "whatever possible".  According to owner's report the
>>> thumb was in use for a month (literally).
>>> 
>>> Two IRDA dongles -- never worked;  what's probably OK, they needed
>>> weird
>>> setup.  When, after a pause (about a year) I'd made a second attempt
>>> each just ceased to wakeup.
>>> 
>>> CDMA modem worked for a year (I wouldn't say flawlessly) developed a
>>> requirement -- pppd had to be in within 10min, otherwise negotitions
>>> would take forever.
>>> 
>>> UMTS modem worked for 4year (literally, it died 4y+2d after first
>>> plug-in) (I wouldn't say flawlessly), then ZeroCD ceased to work
>>> with block device errors present instead.
>>> 
>>> And not to mention USB closure!  When I'd tried it first time I'd
>>> pluged
>>> in by-instructions and unplugged by-logic (reverse-in).  Then The
>>> Second
>>> Move has(sic!) come -- I've unplugged by-instructions.  Putting a
>>> long
>>> story short -- I've burned down one USB-host.  That was spectacular,
>>> no flames though.
>>> 
>>> It has been put aside, then squeeze had come.  All DVD-images came
>>> out
>>> with errors.  I've collected some stats -- no clear pattern.  So
>>> I've
>>> made a script that lifted those 16 DVD-images.  It took some time
>>> though.
>>> 
>>> I don't mention two UMTS modems with 'normal-termination-by-ncp'
>>> disease -- that's on ISP side and I have no options.
>>> 
>>> I ain't no heavy user -- I have a couple of thumbs, developing a
>>> collection of SD-cards, some USB-devices and such.  I've never faced
>>> problems with cameras and recorders (whenever I've faced those).
>>> 
>>> 
>> [admin@raspberrypi ~]$ uptime
>>  07:31:48 up 398 days, 20:50,  1 user,  load average: 0.05, 0.12,
>>  0.09
>> 
>> Raspberry PI model B
>> 
>> Has SD card and USB 32GB thumb drive
>> 
>> Runs DNS, News groups, Email and file serving services for LAN.
>> 
>> Cost efficient and very quiet.
> 
> 
> Hey, that's cool.  I'd like to try that.  What brand flash drive did
> you use?

generic usb thumb drive

[toc] | [prev] | [next] | [standalone]

#2439

On Sat, 21 Jun 2014 16:34:34 +0000, Charles T. Smith wrote:

> Hi,
> 
> I bought an external usb drive for external storage for my linux system.
> I discover that after a while (15 minutes?) of inactivity, I get this
> message:
> 
>   ls: reading directory .: Input/output error
> 
> If I cd away and back again, my directory is back.  Is that implicit in
> usb or the drive?  Can a disk be made to not do that?  I have it mounted
> in sync mode.
> 
> cts

>> Okay, I may have found it: http://lwn.net/Articles/253587/
>> 
>> But I haven't had a chance to test it yet.


Well, I wasn't able to make progress with that.  But I noticed something
interesting...

My drive is mounted from /dev/disk/by-id.  Every time this event happens,
the device, /dev/sd?3, changes - first, it's at /dev/sdb3, then after
remount it's at /dev/sdc3, and then, the next time it happens, it goes
back to /dev/sdb3 again.

[toc] | [prev] | [next] | [standalone]

#2441

On Sun, 22 Jun 2014 13:41:14 +0000, Charles T. Smith wrote:
> Every time this event happens, the device, /dev/sd?3, changes - first,
> it's at /dev/sdb3, then after remount it's at /dev/sdc3, and then, the
> next time it happens, it goes back to /dev/sdb3 again.

The 'dmesg' command might be able to tell you something about what is 
going on. Maybe as Stef says the disk is powered down. Maybe you have a 
bad USB cable or a bad USB connector causing the disk to get unplugged 
and replugged.

regards Henrik
-- 
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

[toc] | [prev] | [next] | [standalone]

#2449

On Sun, 22 Jun 2014 13:41:14 +0000, Charles T. Smith wrote:

> On Sat, 21 Jun 2014 16:34:34 +0000, Charles T. Smith wrote:
> 
>> Hi,
>> 
>> I bought an external usb drive for external storage for my linux
>> system. I discover that after a while (15 minutes?) of inactivity, I
>> get this message:
>> 
>>   ls: reading directory .: Input/output error
>> 
>> If I cd away and back again, my directory is back.  Is that implicit in
>> usb or the drive?  Can a disk be made to not do that?  I have it
>> mounted in sync mode.
>> 
>> cts
> 
>>> Okay, I may have found it: http://lwn.net/Articles/253587/
>>> 
>>> But I haven't had a chance to test it yet.
> 
> 
> Well, I wasn't able to make progress with that.  But I noticed something
> interesting...
> 
> My drive is mounted from /dev/disk/by-id.  Every time this event
> happens, the device, /dev/sd?3, changes - first, it's at /dev/sdb3, then
> after remount it's at /dev/sdc3, and then, the next time it happens, it
> goes back to /dev/sdb3 again.

(that's determined from dmesg & /var/log/messages)

I'm still casting around in the dark...  I'm reasonably sure that it 
happens primarily when I running on batteries.  But I can't find any
element that takes responsibility for shutting things down.

[ 6540.940526] sd 9:0:0:0: [sdb] CDB: Write(10): 2a 00 4d e0 11 c0 00 00 
08 00
[ 6540.940550] end_request: I/O error, dev sdb, sector 1306530240
[ 6540.940557] Buffer I/O error on device sdb3, logical block 41222280
[ 6540.940563] lost page write due to I/O error on sdb3
[ 6541.076290] usb 2-4: new high speed USB device number 6 using ehci_hcd
[ 6541.210515] scsi10 : usb-storage 2-4:1.0
[ 6542.209486] scsi 10:0:0:0: Direct-Access     WD       Elements 1048    
1025 PQ: 0 ANSI: 6
[ 6542.233160] sd 10:0:0:0: Attached scsi generic sg2 type 0
[ 6542.233386] sd 10:0:0:0: [sdc] 1953519616 512-byte logical blocks: 
(1.00 TB/931 GiB)
[ 6542.235266] sd 10:0:0:0: [sdc] Write Protect is off
[ 6542.235276] sd 10:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 6542.237116] sd 10:0:0:0: [sdc] No Caching mode page present
[ 6542.237126] sd 10:0:0:0: [sdc] Assuming drive cache: write through
[ 6542.239882] sd 10:0:0:0: [sdc] No Caching mode page present
[ 6542.239890] sd 10:0:0:0: [sdc] Assuming drive cache: write through
[ 6542.792326] usb 2-4: reset high speed USB device number 6 using 
ehci_hcd
[ 6542.916226] usb 2-4: device descriptor read/64, error -71
[ 6543.144049] usb 2-4: device descriptor read/64, error -71
[ 6543.360052] usb 2-4: reset high speed USB device number 6 using 
ehci_hcd
[ 6543.484059] usb 2-4: device descriptor read/64, error -71
[ 6543.712077] usb 2-4: device descriptor read/64, error -71
[ 6543.928221] usb 2-4: reset high speed USB device number 6 using 
ehci_hcd
[ 6544.344307] usb 2-4: device not accepting address 6, error -71
[ 6544.456234] usb 2-4: reset high speed USB device number 6 using 
ehci_hcd
[ 6544.872227] usb 2-4: device not accepting address 6, error -71
[ 6544.872285] usb 2-4: USB disconnect, device number 6
[ 6544.872782] sd 10:0:0:0: [sdc] Unhandled error code
[ 6544.872790] sd 10:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[ 6544.872800] sd 10:0:0:0: [sdc] CDB: Read(10): 28 00 00 00 00 00 00 00 
08 00
[ 6544.872826] end_request: I/O error, dev sdc, sector 0
[ 6544.872835] Buffer I/O error on device sdc, logical block 0
[ 6544.873884] ldm_validate_partition_table(): Disk read failed.
[ 6544.874083] Dev sdc: unable to read RDB block 0
[ 6544.874463]  sdc: unable to read partition table
[ 6544.874787] sd 10:0:0:0: [sdc] READ CAPACITY failed
[ 6544.874794] sd 10:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[ 6544.874804] sd 10:0:0:0: [sdc] Sense not available.
[ 6544.874861] sd 10:0:0:0: [sdc] Asking for cache data failed
[ 6544.874868] sd 10:0:0:0: [sdc] Assuming drive cache: write through
[ 6544.874876] sd 10:0:0:0: [sdc] Attached SCSI disk

umounting and remounting clears it up.

I would have expected to find a msg in dmesg or /var/log/messages that 
said something like "power control suspending usb power"  but I can't 
find anything like that.  Am I looking in the wrong place?

[toc] | [prev] | [next] | [standalone]

#2451

On Tue, 24 Jun 2014 20:10:27 +0000, Charles T. Smith wrote:
> [ 6540.940550] end_request: I/O error, dev sdb, sector 1306530240
> [ 6540.940557] Buffer I/O error on device sdb3, logical block 41222280
> [ 6540.940563] lost page write due to I/O error on sdb3
> [ 6541.076290] usb 2-4: new high speed USB device...

> I would have expected to find a msg in dmesg or /var/log/messages that
> said something like "power control suspending usb power"  but I can't
> find anything like that.  Am I looking in the wrong place?

Looking at the time stamps above the new USB device is found 0.13 seconds 
after the old USB device was lost. My guess is that you don't have some 
kind of power control suspending the USB stick for 0.13 seconds. My guess 
is that you instead have a flaky USB connector. This looks like a 
hardware problem to me. Are you able to use other USB devices connected 
to that USB port? Are you able to use that USB stick connected to other 
computers?

regards Henrik
-- 
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

[toc] | [prev] | [next] | [standalone]

#2452

On Wed, 25 Jun 2014 06:04:11 +0000, Henrik Carlqvist wrote:

> On Tue, 24 Jun 2014 20:10:27 +0000, Charles T. Smith wrote:
>> [ 6540.940550] end_request: I/O error, dev sdb, sector 1306530240 [
>> 6540.940557] Buffer I/O error on device sdb3, logical block 41222280 [
>> 6540.940563] lost page write due to I/O error on sdb3 [ 6541.076290]
>> usb 2-4: new high speed USB device...
> 
>> I would have expected to find a msg in dmesg or /var/log/messages that
>> said something like "power control suspending usb power"  but I can't
>> find anything like that.  Am I looking in the wrong place?
> 
> Looking at the time stamps above the new USB device is found 0.13
> seconds after the old USB device was lost. My guess is that you don't
> have some kind of power control suspending the USB stick for 0.13
> seconds. My guess is that you instead have a flaky USB connector. This
> looks like a hardware problem to me. Are you able to use other USB
> devices connected to that USB port? Are you able to use that USB stick
> connected to other computers?
> 
> regards Henrik


Well, it's a drive - the port is surely good, never had a problem.  The 
drive is new ... it's not out of the realm of possibility that the cable 
is poor (it's a WD drive, though).

In fact, though, I've been thinking along the lines of what somebody said 
here somewhere: experimenting with the -S and -B options of the hdparm 
utility.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.hardware

csiph-web