USB 드라이브가 사용 중일 때 작동이 중지됩니다.

USB 드라이브가 사용 중일 때 작동이 중지됩니다.

우선 내 영어 실력이 유감스럽습니다.

오랫동안 Google에서 검색했지만 유용한 정보를 찾지 못했기 때문에 여기에 게시합니다. 이 포럼에서도 일부 게시물을 보았지만 모두 너무 오래되었거나 아무것도 해결되지 않습니다.

내 문제는 외부 USB 드라이브에 관한 것입니다. 저는 커널 3.2.0-4-686-pae로 완전히 업데이트된 Debian wheezy Server를 가지고 있고 저장 공간을 확장하기 위해 USB 드라이브를 구입했습니다. 문제는 많은 파일을 외부 저장소에 복사하기 시작하면 드라이브가 작동을 멈춘다는 것입니다. 드라이브가 계속 마운트되었지만 응답하지 않고 작동하도록 하는 유일한 방법은 USB 연결을 끊었다가 다시 연결하는 것입니다.

USB 드라이브는 외부 전원 공급 장치가 있는 Seagate Expansion Desktop 2TB 3.5" USB3.0입니다.

syslog에는 다음이 표시됩니다.

Jul 18 10:57:38 SomeServer kernel: [163444.176034] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
Jul 18 10:57:38 SomeServer kernel: [163444.300025] usb 1-2: device descriptor read/64, error -71
Jul 18 10:57:38 SomeServer kernel: [163444.528031] usb 1-2: device descriptor read/64, error -71
Jul 18 10:57:39 SomeServer kernel: [163444.744043] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
Jul 18 10:57:39 SomeServer kernel: [163444.868054] usb 1-2: device descriptor read/64, error -71
Jul 18 10:57:39 SomeServer kernel: [163445.096045] usb 1-2: device descriptor read/64, error -71
Jul 18 10:57:39 SomeServer kernel: [163445.312044] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
Jul 18 10:57:40 SomeServer kernel: [163445.724044] usb 1-2: device not accepting address 12, error -71
Jul 18 10:57:40 SomeServer kernel: [163445.836063] usb 1-2: reset high-speed USB device number 12 using ehci_hcd
Jul 18 10:57:40 SomeServer kernel: [163446.248060] usb 1-2: device not accepting address 12, error -71
Jul 18 10:57:40 SomeServer kernel: [163446.248133] usb 1-2: USB disconnect, device number 12
Jul 18 10:57:40 SomeServer kernel: [163446.248152] sd 6:0:0:0: Device offlined - not ready after error recovery
Jul 18 10:57:40 SomeServer kernel: [163446.248179] sd 6:0:0:0: [sdc] Unhandled error code
Jul 18 10:57:40 SomeServer kernel: [163446.248184] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Jul 18 10:57:40 SomeServer kernel: [163446.248192] sd 6:0:0:0: [sdc] CDB: Write(10): 2a 00 16 c3 7a 2a 00 00 1e 00
Jul 18 10:57:40 SomeServer kernel: [163446.248211] end_request: I/O error, dev sdc, sector 3055276368
Jul 18 10:57:40 SomeServer kernel: [163446.248244] Buffer I/O error on device sdc1, logical block 381909290
Jul 18 10:57:40 SomeServer kernel: [163446.248278] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.248286] Buffer I/O error on device sdc1, logical block 381909291
Jul 18 10:57:40 SomeServer kernel: [163446.248320] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.248328] Buffer I/O error on device sdc1, logical block 381909292
Jul 18 10:57:40 SomeServer kernel: [163446.248359] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.248366] Buffer I/O error on device sdc1, logical block 381909293
Jul 18 10:57:40 SomeServer kernel: [163446.248402] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.248408] Buffer I/O error on device sdc1, logical block 381909294
Jul 18 10:57:40 SomeServer kernel: [163446.248437] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.248443] Buffer I/O error on device sdc1, logical block 381909295
Jul 18 10:57:40 SomeServer kernel: [163446.249782] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.249790] Buffer I/O error on device sdc1, logical block 381909296
Jul 18 10:57:40 SomeServer kernel: [163446.249820] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.249826] Buffer I/O error on device sdc1, logical block 381909297
Jul 18 10:57:40 SomeServer kernel: [163446.249855] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.249861] Buffer I/O error on device sdc1, logical block 381909298
Jul 18 10:57:40 SomeServer kernel: [163446.249889] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.249895] Buffer I/O error on device sdc1, logical block 381909299
Jul 18 10:57:40 SomeServer kernel: [163446.249923] lost page write due to I/O error on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.249997] sd 6:0:0:0: [sdc] Unhandled error code
Jul 18 10:57:40 SomeServer kernel: [163446.250002] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jul 18 10:57:40 SomeServer kernel: [163446.250010] sd 6:0:0:0: [sdc] CDB: Write(10): 2a 00 16 c3 7a 48 00 00 1e 00
Jul 18 10:57:40 SomeServer kernel: [163446.250028] end_request: I/O error, dev sdc, sector 3055276608
Jul 18 10:57:40 SomeServer kernel: [163446.346073] JBD: Detected IO errors while flushing file data on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.346259] journal_bmap: journal block not found at offset 16396 on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.346302] Aborting journal on device sdc1.
Jul 18 10:57:40 SomeServer kernel: [163446.346375] JBD: I/O error detected when updating journal superblock for sdc1.
Jul 18 10:57:40 SomeServer kernel: [163446.346433] __journal_remove_journal_head: freeing b_committed_data
Jul 18 10:57:40 SomeServer kernel: [163446.346579] __journal_remove_journal_head: freeing b_committed_data
Jul 18 10:57:40 SomeServer kernel: [163446.374086] JBD: Detected IO errors while flushing file data on sdc1
Jul 18 10:57:40 SomeServer kernel: [163446.374142] __journal_remove_journal_head: freeing b_frozen_data
Jul 18 10:57:40 SomeServer kernel: [163446.374147] __journal_remove_journal_head: freeing b_frozen_data
Jul 18 10:57:40 SomeServer kernel: [163446.374151] __journal_remove_journal_head: freeing b_frozen_data
Jul 18 10:57:40 SomeServer kernel: [163446.374154] __journal_remove_journal_head: freeing b_committed_data
Jul 18 10:57:40 SomeServer kernel: [163446.374158] __journal_remove_journal_head: freeing b_frozen_data
Jul 18 10:57:40 SomeServer kernel: [163446.374190] journal commit I/O error
Jul 18 10:57:40 SomeServer kernel: [163446.394650] EXT3-fs (sdc1): error: ext3_journal_start_sb: Detected aborted journal
Jul 18 10:57:40 SomeServer kernel: [163446.394724] EXT3-fs (sdc1): error: remounting filesystem read-only
Jul 18 10:57:41 SomeServer kernel: [163446.820598] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.820722] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.820817] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.820910] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821006] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821101] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821194] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821290] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821386] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821480] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821578] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821669] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821765] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821864] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.821962] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822059] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822157] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822254] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822351] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822454] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822556] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822648] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822740] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822847] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.822950] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.823041] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.823144] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #93773868 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.823632] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92577799 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.831563] __journal_remove_journal_head: freeing b_frozen_data
Jul 18 10:57:41 SomeServer kernel: [163446.840980] sd 6:0:0:0: [sdc] Synchronizing SCSI cache
Jul 18 10:57:41 SomeServer kernel: [163446.841033] sd 6:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jul 18 10:57:41 SomeServer kernel: [163446.863650] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.865293] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.865900] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.903243] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.912264] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.927942] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.928606] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.929807] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.933678] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.935572] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.936040] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.936901] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.937351] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.939195] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.939678] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.940349] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.940860] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.941317] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.941758] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.942208] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.942617] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.943089] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.943557] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.944000] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.944757] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.945234] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.945651] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.946142] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #92561409 offset 0
Jul 18 10:57:41 SomeServer kernel: [163446.952110] usb 1-2: new high-speed USB device number 13 using ehci_hcd

USB 포트를 변경하고, 파티션을 삭제하고, fdisk를 다시 사용하여 EXT3 및 EXT4 형식으로 다시 파티션을 나누려고 했습니다. Linux 문제인지 아니면 USB 드라이브에 결함이 있는지는 알 수 없습니다.

어제는 170GB 정도를 문제 없이 복사했는데, 그다음에 68GB 정도의 파일을 복사하려고 했더니 실패하기 시작했습니다.

누군가 무엇이 실패할 수 있는지 알고 있습니까?. 새 제품으로 교체하고 계속해서 문제가 발생하기 전에 알고 싶습니다.

감사해요!!

답변1

" Buffer I/O error" 불행하게도 이러한 일이 발생한 대부분의 경우 하드웨어 오류였습니다. 문제의 범위를 좁히려면 Live CD/USB로 부팅해 보세요.

업데이트:

Gparted이 드라이브를 및/또는 으로 처리해 볼 수 있습니다 fdisk.갈라진또한 자체적으로라이브 CD

관련 정보