reset SuperSpeed USB device 발생

Post Reply
revizes
Posts: 15
Joined: Sat Jan 14, 2017 9:42 pm
languages_spoken: english
ODROIDs: c2
Has thanked: 1 time
Been thanked: 2 times
Contact:

reset SuperSpeed USB device 발생

Post by revizes »

next-804u3라는 DAS device를 odroid-c4에 물려서 사용 계획 중입니다.

디스크는 아래와 같이 구성하였습니다.

Code: Select all

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda            8:0    0 931.5G  0 disk 
└─sda1         8:1    0 931.5G  0 part 
sdc            8:32   0   3.7T  0 disk 
└─sdc1         8:33   0   3.7T  0 part 
sde            8:64   0 465.8G  0 disk 
└─sde1         8:65   0 465.8G  0 part 
sdf            8:80   0   7.3T  0 disk 
└─sdf1         8:81   0   7.3T  0 part 
mmcblk0      179:0    0  14.6G  0 disk 
├─mmcblk0p1  179:1    0   128M  0 part /media/boot
└─mmcblk0p2  179:2    0  14.4G  0 part /
mmcblk0boot0 179:32   0     4M  0 disk 
mmcblk0boot1 179:64   0     4M  0 disk 
mmcblk0rpmb  179:96   0     4M  0 disk
처음에는 잘 마운트 되는듯 해서 사용가능 한데, 조금 지나면 usb 가 reset 되버립니다. das device가 문제인가 싶었는데, PC에 물려서 밤새 rsync를
실행시켰는데 잘동작합니다. PC는 ubuntu 22.04가 설치되어있습니다.

odroid-c4에서 에러가 발생했을 때의 로그는 아래와 같습니다. 어떻게 접근해야 하는지 조언부탁드립니다.

Code: Select all

[  695.174048] usb 2-1.3: reset SuperSpeed USB device number 3 using xhci-hcd
[  695.895917] usb 2-1.3: USB disconnect, device number 3
[  695.909922] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  695.909932] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 64 73 78 00 00 00 08 00 00 00
[  695.909936] blk_update_request: I/O error, dev sdd, sector 1685288960
[  695.910915] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 469762048 size 8388608 starting block 210661376)
[  695.910920] Buffer I/O error on device sdd1, logical block 210660864
[  695.917415] Buffer I/O error on device sdd1, logical block 210660865
[  695.923907] Buffer I/O error on device sdd1, logical block 210660866
[  695.930407] Buffer I/O error on device sdd1, logical block 210660867
[  695.936907] Buffer I/O error on device sdd1, logical block 210660868
[  695.943406] Buffer I/O error on device sdd1, logical block 210660869
[  695.949906] Buffer I/O error on device sdd1, logical block 210660870
[  695.956406] Buffer I/O error on device sdd1, logical block 210660871
[  695.962906] Buffer I/O error on device sdd1, logical block 210660872
[  695.969406] Buffer I/O error on device sdd1, logical block 210660873
[  695.976261] sd 0:0:0:1: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  695.976272] sd 0:0:0:1: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 9b 67 c2 00 00 00 01 00 00 00
[  695.976279] blk_update_request: I/O error, dev sdb, sector 2607268352
[  695.982566] blk_update_request: I/O error, dev sda, sector 0
[  695.988389] sd 0:0:0:1: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  695.988399] sd 0:0:0:1: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 9b 67 c3 00 00 00 01 00 00 00
[  695.988403] blk_update_request: I/O error, dev sdb, sector 2607268608
[  695.995769] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  695.996567] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  695.996576] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 64 73 80 00 00 00 08 00 00 00
[  695.996581] blk_update_request: I/O error, dev sdd, sector 1685291008
[  696.001488] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 469762048 size 8388608 starting block 210661632)
[  696.001998] sd 0:0:0:1: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.002007] sd 0:0:0:1: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 9b 67 c2 00 00 00 00 08 00 00
[  696.002012] blk_update_request: I/O error, dev sdb, sector 2607268352
[  696.008635] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.008647] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 64 73 88 00 00 00 08 00 00 00
[  696.008651] blk_update_request: I/O error, dev sdd, sector 1685293056
[  696.014662] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 2101248 starting block 210661888)
[  696.015619] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.015629] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 01 c9 40 49 00 00 00 08 00 00 00
[  696.015633] blk_update_request: I/O error, dev sdd, sector 7671400704
[  696.021406] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.021416] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 01 c9 40 51 00 00 00 08 00 00 00
[  696.021420] blk_update_request: I/O error, dev sdd, sector 7671402752
[  696.028457] sd 0:0:0:3: [sdd] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.028469] sd 0:0:0:3: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 64 73 90 00 00 00 08 00 00 00
[  696.028473] blk_update_request: I/O error, dev sdd, sector 1685295104
[  696.034421] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 3149824 starting block 210662144)
[  696.034819] sd 0:0:0:1: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.034829] sd 0:0:0:1: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 9b 67 c4 00 00 00 00 80 00 00
[  696.035026] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.036167] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 4198400 starting block 210662400)
[  696.039782] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 5246976 starting block 210662656)
[  696.042346] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 6295552 starting block 210662912)
[  696.044825] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 7344128 starting block 210663168)
[  696.045744] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 8388608 starting block 210663424)
[  696.048157] EXT4-fs warning (device sdd1): ext4_end_bio:313: I/O error -5 writing to inode 14680450 (offset 478150656 size 8388608 starting block 210663680)
[  696.062000] Buffer I/O error on dev sdb1, logical block 672137325, lost async page write
[  696.078431] Buffer I/O error on dev sda1, logical block 121667584, lost sync page write
[  696.081085] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  696.093994] Aborting journal on device sda1-8.
[  696.094047] Buffer I/O error on dev sda1, logical block 121667584, lost sync page write
[  696.101489] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  696.586961] JBD2: Error while async write back metadata bh 672137325.
[  696.587764] Aborting journal on device sdb1-8.
[  696.592584] Buffer I/O error on dev sdb1, logical block 488144896, lost sync page write
[  696.600718] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[  696.615102] sd 0:0:0:1: [sdb] Synchronizing SCSI cache
[  696.615149] sd 0:0:0:1: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.645453] Aborting journal on device sdc1-8.
[  696.645516] Buffer I/O error on dev sdc1, logical block 60850176, lost sync page write
[  696.652665] JBD2: Error -5 detected when updating journal superblock for sdc1-8.
[  696.667446] sd 0:0:0:2: [sdc] Synchronizing SCSI cache
[  696.667495] sd 0:0:0:2: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  696.802977] Buffer I/O error on dev sdd1, logical block 210239497, lost async page write
[  696.805672] JBD2: Detected IO errors while flushing file data on sdd1-8
[  696.805722] Aborting journal on device sdd1-8.
[  696.808995] EXT4-fs (sdd1): ext4_writepages: jbd2_start: 9223372036854774783 pages, ino 14680450; err -30
[  696.820058] Buffer I/O error on dev sdd1, logical block 267943936, lost sync page write
[  696.833821] JBD2: Error -5 detected when updating journal superblock for sdd1-8.
[  696.835801] JBD2: Detected IO errors while flushing file data on sdd1-8
[  697.871622] JBD2: Error while async write back metadata bh 210239497.
[  697.883734] sd 0:0:0:3: [sdd] Synchronizing SCSI cache
[  697.883785] sd 0:0:0:3: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  703.161593] usb 2-1.3: new SuperSpeed USB device number 4 using xhci-hcd
[  703.182050] usb 2-1.3: New USB device found, idVendor=152d, idProduct=0567
[  703.182057] usb 2-1.3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
[  703.182059] usb 2-1.3: Product: USB to ATA/ATAPI Bridge
[  703.182062] usb 2-1.3: Manufacturer: JMicron
[  703.182064] usb 2-1.3: SerialNumber: 152D00539000
[  703.186079] usb-storage 2-1.3:1.0: USB Mass Storage device detected
[  703.189832] scsi host1: usb-storage 2-1.3:1.0
[  704.198413] scsi 1:0:0:0: Direct-Access     HGST HTS 721010A9E630     5031 PQ: 0 ANSI: 6
[  704.198956] scsi 1:0:0:1: Direct-Access     WDC WD40 EZRX-22SPEB0     5031 PQ: 0 ANSI: 6
[  704.199442] scsi 1:0:0:2: Direct-Access     ST350032 0AS              5031 PQ: 0 ANSI: 6
[  704.199918] scsi 1:0:0:3: Direct-Access     WDC WD80 EAZZ-00BKLB0     5031 PQ: 0 ANSI: 6
[  704.200882] sd 1:0:0:0: Attached scsi generic sg0 type 0
[  704.205089] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[  704.205242] sd 1:0:0:1: Attached scsi generic sg1 type 0
[  704.207549] sd 1:0:0:0: [sda] Write Protect is off
[  704.207558] sd 1:0:0:0: [sda] Mode Sense: 67 00 10 08
[  704.207903] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  704.208339] sd 1:0:0:2: Attached scsi generic sg2 type 0
[  704.209114] sd 1:0:0:3: Attached scsi generic sg3 type 0
[  704.213685] sd 1:0:0:1: [sdc] Very big device. Trying to use READ CAPACITY(16).
[  704.213864] sd 1:0:0:1: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[  704.213868] sd 1:0:0:1: [sdc] 4096-byte physical blocks
[  704.214247] sd 1:0:0:1: [sdc] Write Protect is off
[  704.214258] sd 1:0:0:1: [sdc] Mode Sense: 67 00 10 08
[  704.214656] sd 1:0:0:3: [sdf] Very big device. Trying to use READ CAPACITY(16).
[  704.249989] sd 1:0:0:1: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  704.250534] sd 1:0:0:2: [sde] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[  704.250953] sd 1:0:0:2: [sde] Write Protect is off
[  704.250962] sd 1:0:0:2: [sde] Mode Sense: 67 00 10 08
[  704.251182] sd 1:0:0:3: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
[  704.251187] sd 1:0:0:3: [sdf] 4096-byte physical blocks
[  704.251909] sd 1:0:0:3: [sdf] Write Protect is off
[  704.251919] sd 1:0:0:3: [sdf] Mode Sense: 67 00 10 08
[  704.252258] sd 1:0:0:3: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  704.252901] sd 1:0:0:1: [sdc] Very big device. Trying to use READ CAPACITY(16).
[  704.285748] sd 1:0:0:2: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
[  704.321970] sd 1:0:0:3: [sdf] Very big device. Trying to use READ CAPACITY(16).
[  704.323693]  sda: sda1
[  704.358720] sd 1:0:0:0: [sda] Attached SCSI disk
[  704.360315]  sdc: sdc1
[  704.366757]  sde: sde1
[  704.367124] sd 1:0:0:1: [sdc] Very big device. Trying to use READ CAPACITY(16).
[  704.392754] sd 1:0:0:1: [sdc] Attached SCSI disk
[  704.417170] sd 1:0:0:2: [sde] Attached SCSI disk
[  704.418394]  sdf: sdf1
[  704.431019] sd 1:0:0:3: [sdf] Very big device. Trying to use READ CAPACITY(16).
[  704.432298] sd 1:0:0:3: [sdf] Attached SCSI disk
[  742.209664] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035540: comm rsync: reading directory lblock 0
[  742.215095] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035540: comm rsync: reading directory lblock 0
[  742.226036] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168034306: comm rsync: reading directory lblock 0
[  742.237494] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #2: comm rsync: reading directory lblock 0
[  742.247211] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #2: comm rsync: reading directory lblock 0
[  742.257521] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035324: comm rsync: reading directory lblock 0
[  742.268401] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035324: comm rsync: reading directory lblock 0
[  742.279413] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035324: comm rsync: reading directory lblock 0
[  742.290233] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035324: comm rsync: reading directory lblock 0
[  742.301305] EXT4-fs error (device sdb1): ext4_find_entry:1455: inode #168035324: comm rsync: reading directory lblock 0

User avatar
tobetter
Posts: 10289
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: Many
Location: Paju, South Korea
Has thanked: 663 times
Been thanked: 1756 times
Contact:

Re: reset SuperSpeed USB device 발생

Post by tobetter »

외부전원이 연결된 상태에서 에러가 발생되는건가요?
아래 링크에서 C4용 이미지를 다운로드 받아서 동일한 문제가 발생하는지 확인해보시겠어요?
http://ppa.linuxfactory.or.kr/images/raw/arm64/jammy/

revizes
Posts: 15
Joined: Sat Jan 14, 2017 9:42 pm
languages_spoken: english
ODROIDs: c2
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: reset SuperSpeed USB device 발생

Post by revizes »

DAS device는 전원이 따로 들어갑니다.

기존에는 아래와 같이 장기간 사용했는데, 문제가 없었고

Code: Select all

                                                               ------ 2.5인치 1TB 외장형 without power
odroid c4 ----   usb 3.0 hub with power-------|
                                                               ------ 2.5인치 2TB 외장형 without power
아래와 같이 구성하면, 10분안에 USB reset 현상이 발생합니다.

Code: Select all

odroid c4 ---- next-804u3 with own power
                     1) 2.5 1T HDD
                     2) 3.5 500GB HDD
                     3) 3.5 4TB HDD
                     4) 3.5 8TB HDD
테스트로 아래와 같이 구성하고 나서는 11시간 정도 후에 reset이 발생하였습니다.

Code: Select all

odroid c4 ---- usb 3.0 hub without power ----- next-804u3 with own power
                                                                               1) 2.5 1T HDD
                                                                               2) 3.5 500GB HDD
                                                                               3) 3.5 4TB HDD
                                                                               4) 3.5 8TB HDD



알려주신 이미지는 제가 출근중이라, 퇴근하면 집에 가서 바로 테스트해보도록 하겠습니다.

감사합니다.

User avatar
odroid
Site Admin
Posts: 39352
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean
ODROIDs: ODROID
Has thanked: 2610 times
Been thanked: 1427 times
Contact:

Re: reset SuperSpeed USB device 발생

Post by odroid »

혹시 DAS와 C4 사이의 연결 케이블을 짧은 것으로 교체가 가능한지요? USB 3.0 케이블이 너무 길때 비슷한 현상을 보았습니다.
또한 우측 하단의 USB 3.0 포트에서 해당 현상이 유독 많이 나타났습니다만, 2022년 생산품은 모두 개선된 것으로 알고 있습니다.
https://wiki.odroid.com/odroid-c4/hardw ... on_history

revizes
Posts: 15
Joined: Sat Jan 14, 2017 9:42 pm
languages_spoken: english
ODROIDs: c2
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: reset SuperSpeed USB device 발생

Post by revizes »

- 메일을 확인해보니 Odroid C4 구입을 2022/04/12에 했습니다.

- 퇴근 후 아래 테스트를 해보고 결과를 공유드리도록 하겠습니다.
1. USB 케이블 교체
- 지금 사용중인 케이블도 짧은 편이긴 합니다. 케이블이 3.0 B type이라 같은 타입이 있다면 테스트 해보도록 하겠습니다.
2. Odroid C4의 포트 위치별 테스트
3. ubuntu 20.04에서 ubuntu 22.04로 이미지 교체

감사합니다.

revizes
Posts: 15
Joined: Sat Jan 14, 2017 9:42 pm
languages_spoken: english
ODROIDs: c2
Has thanked: 1 time
Been thanked: 2 times
Contact:

Re: reset SuperSpeed USB device 발생

Post by revizes »

아 죄송합니다.

DAS 살때 번들로 들어있었던 케이블이 불량인 것 같습니다.

이더넷 포트의 바로 옆의 아래쪽 포트에서 테스트 했습니다.

집에 있는 같은 타입의 조금 더 긴 케이블로 테스트 중인데, 1시간이 지났는데 괜찮습니다.
기존 케이블은 10분 안에 reset이 발생합니다.

결론은 케이블이 문제였던 것 같습니다. 케이블 버려야 겠습니다.
(그 동안의 테스트로 문제의 케이블은 중간에 허브가 있으면 시간의 차이가 있긴 하지만 reset이 발생했습니다.)

내일 아침까지 테스트 해보고, 문제 있으면 다시 글을 올리고 없으면 올리지 않도록 하겠습니다.

도움 주셔서 감사합니다.
These users thanked the author revizes for the post:
odroid (Tue Jul 05, 2022 9:20 am)

Post Reply

Return to “C4/HC4”

Who is online

Users browsing this forum: No registered users and 0 guests