Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 12:53 pm

Hi there!

Yesterday I decided to move my "local cloud" (it's just a flashdrive I use to sync files between two computers) from my FritzBox to my Raspberry Pi 4. In order to do this, I installed Nextcloud.

So a couple of minutes ago I was syncing my computer files to the flashdrive for the first time (naturally, I takes a little bit to transfer everything to the flashdrive) without an issue. At the same time, I started a download to my SSD. Yet after a minute or so, my Nextcloud Windows client told me that the sync failed because the Nextcloud server couldn't be reached. Remembering my inital issues with my SSD, I just went ahead and blacklisted UAS for the flashdrive as well, figuring it was the same issue.

Unfortunately, the issue persisted. This is the dmesg output relating to the flashdrive:

Code: Select all

[    1.345781] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[    1.376908] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[    1.376916] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.376921] usb 2-1: Product: Extreme
[    1.376928] usb 2-1: Manufacturer: SanDisk
[    1.376937] usb 2-1: SerialNumber: 4C530000160907108455
[    1.381447] usb-storage 2-1:1.0: USB Mass Storage device detected
[    1.396004] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[    1.397557] scsi host1: usb-storage 2-1:1.0
[    1.647176] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)

...

[    2.406253] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[    2.406635] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    2.406874] sd 1:0:0:0: [sdb] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[    2.409002] sd 1:0:0:0: [sdb] Write Protect is off
[    2.409008] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[    2.409682] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.452298]  sdb: sdb1
And this is where the errors start:

Code: Select all

[  232.464134] usb 2-1: Disable of device-initiated U1 failed.
[  232.464174] usb 2-1: Disable of device-initiated U2 failed.
[  233.275721] usb 2-1: USB disconnect, device number 3
[  233.325494] print_req_error: I/O error, dev sdb, sector 372864
[  233.325511] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 3211264 size 983040 starting block 46848)
[  233.325519] Buffer I/O error on device sdb1, logical block 46352
[  233.325530] Buffer I/O error on device sdb1, logical block 46353
[  233.325552] Buffer I/O error on device sdb1, logical block 46354
[  233.325559] Buffer I/O error on device sdb1, logical block 46355
[  233.325565] Buffer I/O error on device sdb1, logical block 46356
[  233.325572] Buffer I/O error on device sdb1, logical block 46357
[  233.325578] Buffer I/O error on device sdb1, logical block 46358
[  233.325585] Buffer I/O error on device sdb1, logical block 46359
[  233.325591] Buffer I/O error on device sdb1, logical block 46360
[  233.325597] Buffer I/O error on device sdb1, logical block 46361
[  233.326349] print_req_error: I/O error, dev sdb, sector 428032
[  233.326363] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 4194304 size 2101248 starting block 53760)
[  233.328146] print_req_error: I/O error, dev sdb, sector 430080
[  233.328161] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 4194304 size 3149824 starting block 54016)
[  233.329865] print_req_error: I/O error, dev sdb, sector 432128
[  233.329876] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 4194304 size 4194304 starting block 54272)
[  233.330807] print_req_error: I/O error, dev sdb, sector 121899848
[  233.331490] print_req_error: I/O error, dev sdb, sector 434176
[  233.331503] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 4194304 size 4194304 starting block 54528)
[  233.332502] JBD2: Detected IO errors while flushing file data on sdb1-8
[  233.332523] Aborting journal on device sdb1-8.
[  233.332546] EXT4-fs (sdb1): Delayed block allocation failed for inode 787696 at logical offset 2222 with max blocks 2 with error 30
[  233.332567] print_req_error: I/O error, dev sdb, sector 121899008
[  233.332574] Buffer I/O error on dev sdb1, logical block 15237120, lost sync page write
[  233.332585] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[  233.332589] EXT4-fs (sdb1): This should not happen!! Data will be lost

[  233.332608] EXT4-fs error (device sdb1) in ext4_writepages:2897: IO failure
[  233.332661] print_req_error: I/O error, dev sdb, sector 460800
[  233.332671] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 787696 (offset 8388608 size 712704 starting block 57774)
[  233.333380] JBD2: Detected IO errors while flushing file data on sdb1-8
[  233.333409] print_req_error: I/O error, dev sdb, sector 2048
[  233.333415] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[  233.333429] EXT4-fs (sdb1): I/O error while writing superblock
[  233.333553] print_req_error: I/O error, dev sdb, sector 2048
[  233.333558] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[  233.333571] EXT4-fs (sdb1): I/O error while writing superblock
[  233.333576] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
[  233.333594] EXT4-fs (sdb1): Remounting filesystem read-only
[  233.333625] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[  233.333638] EXT4-fs (sdb1): I/O error while writing superblock
[  233.333644] EXT4-fs (sdb1): ext4_writepages: jbd2_start: 2147483647 pages, ino 787697; err -30
[  234.185836] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[  234.216953] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[  234.216961] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  234.216966] usb 2-1: Product: Extreme
[  234.216971] usb 2-1: Manufacturer: SanDisk
[  234.216976] usb 2-1: SerialNumber: 4C530000160907108455
[  234.219816] usb-storage 2-1:1.0: USB Mass Storage device detected
[  234.219969] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[  234.220016] scsi host2: usb-storage 2-1:1.0
[  235.286816] scsi 2:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[  235.288521] sd 2:0:0:0: Attached scsi generic sg1 type 0
[  235.288654] sd 2:0:0:0: [sdc] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[  235.290203] sd 2:0:0:0: [sdc] Write Protect is off
[  235.290210] sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
[  235.293803] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  235.342897]  sdc: sdc1
[  235.346248] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[  236.355235] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.394177] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.446866] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.446910] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.446939] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.446968] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.447002] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.447026] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  236.447050] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.698884] EXT4-fs error: 62 callbacks suppressed
[  239.698895] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.698974] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.699117] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.699716] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.699789] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.699887] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.700000] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.700126] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.701229] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  239.701312] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.874402] EXT4-fs error: 354 callbacks suppressed
[  244.874410] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.901597] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.961851] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.961909] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.961942] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.961973] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.962025] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.962051] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.962076] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  244.962100] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.200588] EXT4-fs error: 416 callbacks suppressed
[  253.200601] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.234773] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278412] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278454] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278484] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278513] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278548] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278572] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278596] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  253.278620] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  256.231731] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:995: inode #262415: lblock 0: comm vsftpd: error -5 reading directory block
[  256.805866] EXT4-fs warning (device sdb1): htree_dirblock_to_tree:995: inode #262415: lblock 0: comm vsftpd: error -5 reading directory block
[  267.536204] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  280.627458] EXT4-fs error: 61 callbacks suppressed
[  280.627469] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.666622] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.716961] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717005] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717035] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717064] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717098] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717122] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717147] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  280.717170] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  300.415500] usb 2-1: USB disconnect, device number 4
[  301.175781] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[  301.206965] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[  301.206982] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  301.206987] usb 2-1: Product: Extreme
[  301.206992] usb 2-1: Manufacturer: SanDisk
[  301.206997] usb 2-1: SerialNumber: 4C530000160907108455
[  301.209246] usb-storage 2-1:1.0: USB Mass Storage device detected
[  301.209506] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[  301.209555] scsi host2: usb-storage 2-1:1.0
[  302.246625] scsi 2:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[  302.247134] sd 2:0:0:0: [sdc] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[  302.247989] sd 2:0:0:0: Attached scsi generic sg1 type 0
[  302.248646] sd 2:0:0:0: [sdc] Write Protect is off
[  302.248653] sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
[  302.249242] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[  302.298607]  sdc: sdc1
[  302.301727] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[  310.620748] EXT4-fs error: 61 callbacks suppressed
[  310.620755] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.643344] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686157] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686200] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686229] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686259] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686292] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686317] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686341] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  310.686365] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  322.521905] EXT4-fs error: 61 callbacks suppressed
[  322.521911] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.680779] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.698692] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.698756] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.699323] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.699358] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.699405] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.699472] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.711150] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  322.711212] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php: reading directory lblock 0
[  330.256208] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  336.286217] EXT4-fs error: 6 callbacks suppressed
[  336.286228] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.322552] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367409] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367456] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367486] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367516] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367550] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367574] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367598] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  336.367622] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  366.416105] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  366.448050] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[  366.448067] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 05 72 47 98 00 01 00 00
[  366.448077] print_req_error: 1 callbacks suppressed
[  366.448082] print_req_error: I/O error, dev sda, sector 91375512
[  370.631338] EXT4-fs error: 132 callbacks suppressed
[  370.631345] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.672189] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727007] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727049] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727078] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727107] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727141] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727165] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727189] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  370.727212] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.829568] EXT4-fs error: 61 callbacks suppressed
[  391.829581] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.865252] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908122] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908165] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908194] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908224] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908259] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908284] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908309] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  391.908333] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.627048] EXT4-fs error: 132 callbacks suppressed
[  400.627054] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.650956] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693153] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693196] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693226] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693255] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693288] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693313] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693337] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  400.693362] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  401.685757] usb 2-2: Disable of device-initiated U1 failed.
[  406.725965] usb 2-2: Disable of device-initiated U2 failed.
[  406.876282] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  406.909708] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=0x00
[  406.909729] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 05 72 48 98 00 01 00 00
[  406.909744] print_req_error: I/O error, dev sda, sector 91375768
[  421.942620] EXT4-fs error: 61 callbacks suppressed
[  421.942627] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  421.973794] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032296] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032352] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032383] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032413] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032451] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032476] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032500] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  422.032524] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.449027] EXT4-fs error: 132 callbacks suppressed
[  427.449034] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.475055] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.521944] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.521988] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522017] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522046] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522080] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522105] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522128] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  427.522152] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.085842] EXT4-fs error: 132 callbacks suppressed
[  452.085848] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.141028] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234559] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234629] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234663] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234694] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234860] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234902] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234926] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  452.234950] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.627056] EXT4-fs error: 132 callbacks suppressed
[  460.627064] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.651888] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696270] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696314] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696344] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696373] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696408] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696432] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696456] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  460.696480] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.282350] EXT4-fs error: 61 callbacks suppressed
[  482.282359] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.313381] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.359897] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360058] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360090] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360125] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360168] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360194] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360218] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  482.360243] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.629829] EXT4-fs error: 132 callbacks suppressed
[  490.629835] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.674429] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724699] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724745] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724774] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724803] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724837] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724882] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724906] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  490.724930] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.405070] EXT4-fs error: 61 callbacks suppressed
[  512.405077] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.430138] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475146] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475190] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475220] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475249] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475283] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475308] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475332] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  512.475356] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  514.726025] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[  514.767812] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[  514.767821] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 1c 0a a8 b8 00 08 00 00
[  514.767828] print_req_error: I/O error, dev sda, sector 470460600
[  520.630391] EXT4-fs error: 132 callbacks suppressed
[  520.630397] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.666592] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725248] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725331] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725362] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725391] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725427] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725518] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725552] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  520.725576] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.522191] EXT4-fs error: 61 callbacks suppressed
[  542.522198] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.557343] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605081] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605125] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605154] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605183] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605218] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605242] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605266] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  542.605290] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.870574] EXT4-fs error: 132 callbacks suppressed
[  549.870581] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.897100] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.943962] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944006] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944035] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944063] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944097] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944121] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944145] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  549.944168] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.645410] EXT4-fs error: 203 callbacks suppressed
[  572.645423] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.681638] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.723947] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.723991] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724022] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724051] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724085] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724109] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724133] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  572.724157] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.759080] EXT4-fs error: 132 callbacks suppressed
[  602.759094] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.780561] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.797900] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840276] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840320] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840349] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840378] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840413] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840438] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  602.840462] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  620.960915] EXT4-fs error: 274 callbacks suppressed
[  620.960928] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  620.998299] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070192] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070246] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070276] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070306] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070341] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070366] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070390] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  621.070414] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.874650] EXT4-fs error: 148 callbacks suppressed
[  632.874657] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.910275] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.949947] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.949991] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950021] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950050] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950084] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950108] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950132] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  632.950156] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  662.990295] EXT4-fs error: 203 callbacks suppressed
[  662.990308] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.031466] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075273] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075317] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075347] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075376] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075410] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.075434] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.076609] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
[  663.076640] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262145: comm php-fpm7.3: reading directory lblock 0
I have done a bit of research on this issue, but haven't really been able to come up with anything concrete. There's nothing wrong with the flashdrive, just like there was nothing wrong with the SSD, yet it kept disapperaing on me until I blacklisted UAS. Is it a hardware issue, ie is my Raspberry Pi 4 malfunctioning? :|

jamesh
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 26839
Joined: Sat Jul 30, 2011 7:41 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 3:27 pm

What power supply are you using?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed.
I've been saying "Mucho" to my Spanish friend a lot more lately. It means a lot to him.

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 4:10 pm

jamesh wrote:
Sun Jul 12, 2020 3:27 pm
What power supply are you using?
I'm using the original Raspberry Pi Power Supply (https://www.raspberrypi.org/products/ty ... er-supply/). As far as the SSD goes, there is no external power supply.

Here someody suggested going with "over_voltage=1" in case the issues are caused by power variances, yet when I tried that yesterday evening I had a filesystem crash after the ensuing reboot and had to repair both drives before being able to mount them again...should I give that another try?

-------------------------------------------

I finished syncing my local folder with the flashdrive via Nextcloud and didn't encounter a single error while uploading the last 2 GB. Afterwards I restarted the downloads to the SSD and encountered issues yet again (usb 2-1/sdb is the flashdrive, usb 2-2/sda is the SSD):

Code: Select all

[ 2049.345587] usb 2-1: USB disconnect, device number 3
[ 2049.526212] Buffer I/O error on dev sdb1, logical block 15237120, lost sync page write
[ 2049.526221] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 2049.526225] Aborting journal on device sdb1-8.
[ 2049.526233] Buffer I/O error on dev sdb1, logical block 15237120, lost sync page write
[ 2049.526237] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 2050.335768] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[ 2050.366912] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[ 2050.366921] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2050.366926] usb 2-1: Product: Extreme
[ 2050.366931] usb 2-1: Manufacturer: SanDisk
[ 2050.366936] usb 2-1: SerialNumber: 4C530000160907108455
[ 2050.369088] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2050.369367] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[ 2050.369989] scsi host1: usb-storage 2-1:1.0
[ 2051.446548] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[ 2051.447430] sd 1:0:0:0: [sdb] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[ 2051.448288] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 2051.449037] sd 1:0:0:0: [sdb] Write Protect is off
[ 2051.449054] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 2051.449741] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 2051.496677]  sdb: sdb1
[ 2051.500073] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 2078.736227] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2595.315486] usb 2-1: USB disconnect, device number 4
[ 2596.055796] usb 2-1: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 2596.086830] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[ 2596.086837] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2596.086842] usb 2-1: Product: Extreme
[ 2596.086847] usb 2-1: Manufacturer: SanDisk
[ 2596.086852] usb 2-1: SerialNumber: 4C530000160907108455
[ 2596.089061] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2596.089293] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[ 2596.089340] scsi host1: usb-storage 2-1:1.0
[ 2597.126276] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[ 2597.126654] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 2597.129777] sd 1:0:0:0: [sdb] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[ 2597.131334] sd 1:0:0:0: [sdb] Write Protect is off
[ 2597.131341] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 2597.137645] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 2597.183320]  sdb: sdb1
[ 2597.186445] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 2624.656211] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2696.726002] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 2696.757745] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 2696.757754] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 05 d9 97 90 00 04 00 00
[ 2696.757760] print_req_error: I/O error, dev sda, sector 98146192
[ 3043.216139] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4062.736203] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4236.176146] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4363.546128] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4491.536200] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4648.336084] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4680.976191] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4684.345489] usb 2-1: USB disconnect, device number 5
[ 4685.075861] usb 2-1: new SuperSpeed Gen 1 USB device number 6 using xhci_hcd
[ 4685.106985] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[ 4685.107001] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4685.107014] usb 2-1: Product: Extreme
[ 4685.107026] usb 2-1: Manufacturer: SanDisk
[ 4685.107039] usb 2-1: SerialNumber: 4C530000160907108455
[ 4685.109850] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 4685.110177] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[ 4685.111248] scsi host1: usb-storage 2-1:1.0
[ 4686.166546] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[ 4686.167411] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 4686.167431] sd 1:0:0:0: [sdb] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[ 4686.169053] sd 1:0:0:0: [sdb] Write Protect is off
[ 4686.169069] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 4686.176187] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4686.223278]  sdb: sdb1
[ 4686.226388] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 4714.256154] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 4827.535994] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 5119.506010] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 5119.537776] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 5119.537785] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0b 3b b5 58 00 04 00 00
[ 5119.537791] print_req_error: I/O error, dev sda, sector 188462424
[ 5257.616061] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 5296.016225] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 6179.535998] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 6179.567725] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 6179.567733] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0b 33 d8 70 00 01 00 00
[ 6179.567739] print_req_error: I/O error, dev sda, sector 187947120
[ 6214.805848] usb 2-2: Disable of device-initiated U1 failed.
[ 6219.845854] usb 2-2: Disable of device-initiated U2 failed.
[ 6219.996270] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[ 6220.028441] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=0x00
[ 6220.028460] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0b 33 d9 70 00 01 00 00
[ 6220.028474] print_req_error: I/O error, dev sda, sector 187947376
So even though the flashdrive was just sitting there without being accessed, it ended up unmounted yet again.

dustnbone
Posts: 319
Joined: Tue Nov 05, 2019 2:49 am

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 7:09 pm

Smells like USB power issues to me. Try running through a powered hub maybe?

pidd
Posts: 904
Joined: Fri May 29, 2020 8:29 pm
Location: Birkenhead, Wirral, UK
Contact: Website

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 7:15 pm

What model is your SSD drive?

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 8:30 pm

dustnbone wrote:
Sun Jul 12, 2020 7:09 pm
Smells like USB power issues to me. Try running through a powered hub maybe?
So basically there's not enough USB power coming through both ports when I'm putting load on both devices?
pidd wrote:
Sun Jul 12, 2020 7:15 pm
What model is your SSD drive?
It's a Samsung PM961 256 GB SSD running in this enclosure:

https://www.raidsonic.de/en/standards/s ... ectID=5666

pidd
Posts: 904
Joined: Fri May 29, 2020 8:29 pm
Location: Birkenhead, Wirral, UK
Contact: Website

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 9:07 pm

If that is the MZVLB256HAHQ-00000/07 then I'm pretty sure it needs more current than than the Pi can provide, it would need external power to be reliable.

That is the problem with many of the high speed SSD's they have DDR cache which take more power, in this case a typical power of 5.9W but allowing for some inefficiency in the buck converter from 5V to 3.3V it will exceed the 6W available from the Pi.

500MB/s SSD have low power, something like 1.5W and you can run two of them comfortably and most probably a third.

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Sun Jul 12, 2020 11:17 pm

pidd wrote:
Sun Jul 12, 2020 9:07 pm
If that is the MZVLB256HAHQ-00000/07 then I'm pretty sure it needs more current than than the Pi can provide, it would need external power to be reliable.

That is the problem with many of the high speed SSD's they have DDR cache which take more power, in this case a typical power of 5.9W but allowing for some inefficiency in the buck converter from 5V to 3.3V it will exceed the 6W available from the Pi.

500MB/s SSD have low power, something like 1.5W and you can run two of them comfortably and most probably a third.
It's the "MZVLW256HEHP-00000". This datasheet says "Active Power" at 6.1 W for Read and 5.1W W for Write.

I wonder about one thing though: If it is indeed a power issue, how come blacklisting USA has made the "disconnects" disappear? Is the blacklisting somehow throttling the drive which also reduces the power draw?

------------------------------------

Just had another crash with "over_voltage=2" activated:

Code: Select all

[24636.186186] usb 2-1: Disable of device-initiated U1 failed.
[24636.186224] usb 2-1: Disable of device-initiated U2 failed.
[24637.003543] usb 2-1: USB disconnect, device number 3
[24637.043361] print_req_error: I/O error, dev sdb, sector 38248448
[24637.043381] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180481 (offset 0 size 2404352 starting block 4781312)
[24637.043387] Buffer I/O error on device sdb1, logical block 4780800
[24637.043398] Buffer I/O error on device sdb1, logical block 4780801
[24637.043404] Buffer I/O error on device sdb1, logical block 4780802
[24637.043410] Buffer I/O error on device sdb1, logical block 4780803
[24637.043415] Buffer I/O error on device sdb1, logical block 4780804
[24637.043421] Buffer I/O error on device sdb1, logical block 4780805
[24637.043427] Buffer I/O error on device sdb1, logical block 4780806
[24637.043432] Buffer I/O error on device sdb1, logical block 4780807
[24637.043438] Buffer I/O error on device sdb1, logical block 4780808
[24637.043444] Buffer I/O error on device sdb1, logical block 4780809
[24637.044158] print_req_error: I/O error, dev sdb, sector 38250496
[24637.044169] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180481 (offset 0 size 2404352 starting block 4781387)
[24637.044416] print_req_error: I/O error, dev sdb, sector 8456728
[24637.044435] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.044508] print_req_error: I/O error, dev sdb, sector 8391112
[24637.044514] Buffer I/O error on dev sdb1, logical block 1048633, lost async page write
[24637.044529] print_req_error: I/O error, dev sdb, sector 37750784
[24637.044534] Buffer I/O error on dev sdb1, logical block 4718592, lost async page write
[24637.044543] print_req_error: I/O error, dev sdb, sector 2048
[24637.044547] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.044559] EXT4-fs (sdb1): I/O error while writing superblock
[24637.044658] print_req_error: I/O error, dev sdb, sector 8456728
[24637.044666] print_req_error: I/O error, dev sdb, sector 37750784
[24637.044682] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.044687] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:519: comm php-fpm7.3: Cannot read block bitmap - block_group = 144, block_bitmap = 4718592
[24637.044710] print_req_error: I/O error, dev sdb, sector 2048
[24637.044716] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.044727] EXT4-fs (sdb1): previous I/O error to superblock detected
[24637.044743] print_req_error: I/O error, dev sdb, sector 2048
[24637.044748] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.044757] EXT4-fs (sdb1): I/O error while writing superblock
[24637.044810] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.044844] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.044854] EXT4-fs (sdb1): I/O error while writing superblock
[24637.044896] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.044927] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.044936] EXT4-fs (sdb1): I/O error while writing superblock
[24637.044977] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.045007] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.045016] EXT4-fs (sdb1): I/O error while writing superblock
[24637.045058] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.045088] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.045098] EXT4-fs (sdb1): I/O error while writing superblock
[24637.045137] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.045167] Buffer I/O error on dev sdb1, logical block 0, lost sync page write
[24637.045177] EXT4-fs (sdb1): I/O error while writing superblock
[24637.045292] EXT4-fs error (device sdb1): ext4_find_entry:1456: inode #262240: comm php-fpm7.3: reading directory lblock 0
[24637.045331] EXT4-fs (sdb1): I/O error while writing superblock
[24637.045488] EXT4-fs error (device sdb1) in ext4_free_blocks:4962: IO failure
[24637.045552] EXT4-fs (sdb1): I/O error while writing superblock
[24637.046331] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180480 (offset 8388608 size 2101248 starting block 4103680)
[24637.047177] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180480 (offset 8388608 size 2158592 starting block 4103936)
[24637.051803] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180480 (offset 8388608 size 2158592 starting block 4103951)
[24637.051886] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180476 (offset 0 size 2101248 starting block 4108800)
[24637.053689] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180476 (offset 0 size 3149824 starting block 4109056)
[24637.055533] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180476 (offset 0 size 4198400 starting block 4109312)
[24637.058564] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180476 (offset 0 size 5246976 starting block 4109568)
[24637.060101] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 1180476 (offset 0 size 6295552 starting block 4109824)
[24637.075926] JBD2: Detected IO errors while flushing file data on sdb1-8
[24637.075976] Aborting journal on device sdb1-8.
[24637.076014] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[24638.313590] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[24638.344682] usb 2-1: New USB device found, idVendor=0781, idProduct=558b, bcdDevice= 1.00
[24638.344688] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[24638.344693] usb 2-1: Product: Extreme
[24638.344697] usb 2-1: Manufacturer: SanDisk
[24638.344701] usb 2-1: SerialNumber: 4C530000160907108455
[24638.346885] usb-storage 2-1:1.0: USB Mass Storage device detected
[24638.347103] usb-storage 2-1:1.0: Quirks match for vid 0781 pid 558b: 800000
[24638.347145] scsi host1: usb-storage 2-1:1.0
[24639.364428] scsi 1:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
[24639.365301] sd 1:0:0:0: Attached scsi generic sg1 type 0
[24639.365811] sd 1:0:0:0: [sdb] 247201792 512-byte logical blocks: (127 GB/118 GiB)
[24639.367320] sd 1:0:0:0: [sdb] Write Protect is off
[24639.367326] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[24639.367908] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[24639.411212]  sdb: sdb1
[24639.415413] sd 1:0:0:0: [sdb] Attached SCSI removable disk

pidd
Posts: 904
Joined: Fri May 29, 2020 8:29 pm
Location: Birkenhead, Wirral, UK
Contact: Website

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 3:14 am

Any changes can make a difference to peak current draw

renice123
Posts: 226
Joined: Tue Oct 15, 2019 3:56 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 6:01 am

This hard drive consumes a lot, and therefore requires an external power supply. Among other things, it is extremely important to choose the "right" controller. Many controllers have extremely bad and gluttonous chips, which adds to the problems. What is your USB - NVMe controller? Image
Update. Looked at the chipset, you are using JMS583. The chips of this company do not always work stably and do not have a good reputation for energy-saving.
https://www.legitreviews.com/jmicron-jm ... ves_219422
Quote from the article
What we have learned is that JMicron is aware of some performance/stability issues on platforms that have been discovered since the JMS583 bridge chip was introduced in 2018. The AMD X570 platform that we use came out in Q2 2019 and JMicron acknowledges that there were some compatibility issues that were encountered. JMicron has released firmware updates to help solve some of them, but to fully resolve the known issues they needed to make internal changes to the JMS583 bridge chip. So, there are different versions of the JMicron JMS583 bridge chip on the market today.

User avatar
HawaiianPi
Posts: 5953
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 6:46 am

Pillendreher wrote:
Sun Jul 12, 2020 8:30 pm
It's a Samsung PM961 256 GB SSD running in this enclosure...
People really need to follow advice here on the forums and stop using NVMe drives. They are not any faster than SATA SSD on the Pi4, but they consume more power and generate more heat, and the enclosures for them are much more expensive.

As I recall, the PM961 is rated at something like 2.9A @ 3.3V, which is closer to 10W, and that's just for the drive, not including the enclosure, or any efficiency losses in the 5V>3.3V conversion. Of course that SSD will only be running at a fraction of its performance on the Pi4, so it will run on less than 10W, but it's still a bad choice for a Pi4 (as you have now discovered).

A less expensive SATA-III SSD and enclosure would have given you the same performance with less power consumption (yes, I have tested it).

USB 3.0 is spec'd at 5Gbps, and the four USB-A ports on the Pi4B all come from a controller chip on the SoC's single 4Gbps PCIe lane. So both USB 3.0 ports and the pair of USB 2.0 ports all share that 4Gbps bandwidth. SATA-III is spec'd at 6Gbps, which is faster than USB 3.0 5Gbps, which is faster than the Pi4B's 4Gbps. So the Pi4B's SSD performance isn't going to set any records, but it's still way faster than an SD card.

NVMe drives are awesome in computers that support them. My budget gaming laptop boots Windows 10 in just under 10 seconds, and that includes a few seconds displaying the brand's animated gamer logo (so actual boot time is closer to 7 seconds). The NVMe drive in my laptop is over 5X faster than a SATA-III SSD (and I know that because I also have a 1TB SATA-III SSD in the system). They are completely wasted on the Pi4, though, since it cannot take advantage of the extra performance.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 8:40 am

renice123 wrote:
Mon Jul 13, 2020 6:01 am
This hard drive consumes a lot, and therefore requires an external power supply. Among other things, it is extremely important to choose the "right" controller. Many controllers have extremely bad and gluttonous chips, which adds to the problems. What is your USB - NVMe controller? Image
Update. Looked at the chipset, you are using JMS583. The chips of this company do not always work stably and do not have a good reputation for energy-saving.
https://www.legitreviews.com/jmicron-jm ... ves_219422
Quote from the article
What we have learned is that JMicron is aware of some performance/stability issues on platforms that have been discovered since the JMS583 bridge chip was introduced in 2018. The AMD X570 platform that we use came out in Q2 2019 and JMicron acknowledges that there were some compatibility issues that were encountered. JMicron has released firmware updates to help solve some of them, but to fully resolve the known issues they needed to make internal changes to the JMS583 bridge chip. So, there are different versions of the JMicron JMS583 bridge chip on the market today.
Thanks for your research! How did you come up with the JMS583? Going by vendor and product id (152d:0580), isn't it reasonable to assume that it's actually the JMS580?
HawaiianPi wrote:
Mon Jul 13, 2020 6:46 am
Pillendreher wrote:
Sun Jul 12, 2020 8:30 pm
It's a Samsung PM961 256 GB SSD running in this enclosure...
People really need to follow advice here on the forums and stop using NVMe drives. They are not any faster than SATA SSD on the Pi4, but they consume more power and generate more heat, and the enclosures for them are much more expensive.
My apologies - this is my first go at the Raspberry Pi and I had the SSD lying around after swapping it for a bigger one in my Laptop. It didn't even cross my mind that there could be power issues - I simply assumed "USB is USB".

HawaiianPi wrote:
Mon Jul 13, 2020 6:46 am
As I recall, the PM961 is rated at something like 2.9A @ 3.3V, which is closer to 10W, and that's just for the drive, not including the enclosure, or any efficiency losses in the 5V>3.3V conversion. Of course that SSD will only be running at a fraction of its performance on the Pi4, so it will run on less than 10W, but it's still a bad choice for a Pi4 (as you have now discovered).

A less expensive SATA-III SSD and enclosure would have given you the same performance with less power consumption (yes, I have tested it).

USB 3.0 is spec'd at 5Gbps, and the four USB-A ports on the Pi4B all come from a controller chip on the SoC's single 4Gbps PCIe lane. So both USB 3.0 ports and the pair of USB 2.0 ports all share that 4Gbps bandwidth. SATA-III is spec'd at 6Gbps, which is faster than USB 3.0 5Gbps, which is faster than the Pi4B's 4Gbps. So the Pi4B's SSD performance isn't going to set any records, but it's still way faster than an SD card.

NVMe drives are awesome in computers that support them. My budget gaming laptop boots Windows 10 in just under 10 seconds, and that includes a few seconds displaying the brand's animated gamer logo (so actual boot time is closer to 7 seconds). The NVMe drive in my laptop is over 5X faster than a SATA-III SSD (and I know that because I also have a 1TB SATA-III SSD in the system). They are completely wasted on the Pi4, though, since it cannot take advantage of the extra performance.
Like I said - it was just lying around, which is I why I thought that I could just use it for the Pi. I know that these high speed SSDs are more or less a waste in common usage scenarios.

User avatar
HawaiianPi
Posts: 5953
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 10:24 am

Pillendreher wrote:
Mon Jul 13, 2020 8:40 am
It didn't even cross my mind that there could be power issues - I simply assumed "USB is USB".
Well, yes and no.

An internal drive in an external enclosure is not the same as an OEM USB drive. USB drives must conform to USB power standards (500mA for USB 2.0 and 900mA for USB 3.0). Internal drives do not have any such restrictions, so they may exceed the power available on USB ports.

On top of that, the Pi supplies a maximum of 1.2A that is shared between all 4 USB ports, so while there are no per-port restrictions (all 1.2A is available from a single port, if it's the only one in use), the total power available is well below what you would find on a Windows or Mac OS PC with 4 USB ports.

The Pi4B should be able to power any single USB drive that conforms to the USB power spec, but when you install a power hungry drive into an enclosure you may need additional power. For the record, I have successfully run my 4B2 from dual SATA-III SSD with USB 3.0 adapter cables (with power efficient drives you can use more than one).

Pillendreher wrote:
Mon Jul 13, 2020 8:40 am
I know that these high speed SSDs are more or less a waste in common usage scenarios.
On a system that supports USB 3.1 Gen2 it would be about twice as fast as USB 3.0, and while it's still only a fraction of what NVMe is capable of, it's faster than native SATA-III, which is not bad. There are faster enclosures (Gen 2x2 and Thundebolt-3), but they are :shock: expensive.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 10:50 am

HawaiianPi wrote:
Mon Jul 13, 2020 10:24 am
Pillendreher wrote:
Mon Jul 13, 2020 8:40 am
It didn't even cross my mind that there could be power issues - I simply assumed "USB is USB".
Well, yes and no.

An internal drive in an external enclosure is not the same as an OEM USB drive. USB drives must conform to USB power standards (500mA for USB 2.0 and 900mA for USB 3.0). Internal drives do not have any such restrictions, so they may exceed the power available on USB ports.

On top of that, the Pi supplies a maximum of 1.2A that is shared between all 4 USB ports, so while there are no per-port restrictions (all 1.2A is available from a single port, if it's the only one in use), the total power available is well below what you would find on a Windows or Mac OS PC with 4 USB ports.

The Pi4B should be able to power any single USB drive that conforms to the USB power spec, but when you install a power hungry drive into an enclosure you may need additional power. For the record, I have successfully run my 4B2 from dual SATA-III SSD with USB 3.0 adapter cables (with power efficient drives you can use more than one).
So it's safe to assume that blacklisting UAS made the SSD run within what the Pi4 can offer power-wise and adding the flash drive pushed the whole thing over the edge, resulting in the disconnects and i/o errors.

HawaiianPi wrote:
Mon Jul 13, 2020 10:24 am
Pillendreher wrote:
Mon Jul 13, 2020 8:40 am
I know that these high speed SSDs are more or less a waste in common usage scenarios.
On a system that supports USB 3.1 Gen2 it would be about twice as fast as USB 3.0, and while it's still only a fraction of what NVMe is capable of, it's faster than native SATA-III, which is not bad. There are faster enclosures (Gen 2x2 and Thundebolt-3), but they are :shock: expensive.
Well yeah, but with GBit-Ethernet, none of that is really going to matter to me transferring files to and from the SSD over ethernet, unfortunately. :(

User avatar
HawaiianPi
Posts: 5953
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Mon Jul 13, 2020 11:13 pm

Pillendreher wrote:
Mon Jul 13, 2020 10:50 am
So it's safe to assume that blacklisting UAS made the SSD run within what the Pi4 can offer power-wise and adding the flash drive pushed the whole thing over the edge, resulting in the disconnects and i/o errors.
Blacklisting UAS forces USB Mass Storage protocol, which is slower and probably requires less power. It does seem like adding the flash drive is what pushed it over the edge, power wise, but that's a pretty narrow margin. What flash drive were you using?

I experienced something similar when trying to use a Pi3 with dual hard drives. Both drives would spin up and mount, and either could be used individually, but trying to use both at once would result in disconnects. Since those are the same symptoms you are experiencing, power is the most likely conclusion.

Were there any power related errors in dmesg? Have you noticed a small lightning bolt symbol appear near the upper-right of the screen, or observed the red power LED flickering, flashing or turning off momentarily when your trouble happens (those are low power warnings)? The command vcgencmd get_throttled may also detect low power conditions (any non-zero result could indicate thermal or power issues).

One thing I forgot to mention is that USB-C can supply up to 3A at 5V for non-PD devices, which is considerably more than the USB 3.0 power spec, so that drive should work fine on a system with USB 3.1/3.2 Gen2 type C ports. To use it on the Pi you'll need extra power, like from a powered USB hub (a USB-C hub that can supply 3A would be ideal, but it might work with a USB 3.0 powered hub).
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Wed Jul 15, 2020 7:20 pm

HawaiianPi wrote:
Mon Jul 13, 2020 11:13 pm
What flash drive were you using?
https://shop.westerndigital.com/product ... 0-128G-A46

HawaiianPi wrote:
Mon Jul 13, 2020 11:13 pm
Were there any power related errors in dmesg?
Not that I can recall. Mostly I/O stuff.
HawaiianPi wrote:
Mon Jul 13, 2020 11:13 pm
Have you noticed a small lightning bolt symbol appear near the upper-right of the screen, or observed the red power LED flickering, flashing or turning off momentarily when your trouble happens (those are low power warnings)?
Since I wasn't paying attention to the Pi's Power LED, I honestly can't say.
HawaiianPi wrote:
Mon Jul 13, 2020 11:13 pm
The command vcgencmd get_throttled may also detect low power conditions (any non-zero result could indicate thermal or power issues).
I just ran it: 0x0.

Pillendreher
Posts: 8
Joined: Sun Jul 12, 2020 12:24 pm

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Tue Aug 25, 2020 6:25 pm

Just to provide an update on the whole situation: I've recently swapped the Samsung SSD with a Kingston A2000 500GB and have no encountered any issues since (granted, I got rid of the flashdrive because the new SSD is bigger). I even removed the UAS flag and have not had any issues.

smartctl provides me with the following powerstates on the A2000:

Code: Select all

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        0       0
 1 +     4.60W       -        -    1  1  1  1        0       0
 2 +     3.80W       -        -    2  2  2  2        0       0
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4    15000   15000
I guess it just never hits that 9.00W power state, probably because I can't even push it to its maximum speed wise.

User avatar
HawaiianPi
Posts: 5953
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Wed Aug 26, 2020 8:42 am

Thanks for the update. Glad the new SSD is working better for you.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

Doplerr
Posts: 1
Joined: Wed Aug 26, 2020 9:09 am

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Wed Aug 26, 2020 9:12 am

I encountered something comparable when attempting to utilize a Pi3 with double hard drives. The two drives would turn up and mount, and either could be utilized exclusively, yet attempting to utilize both on the double would bring about detaches.

LTolledo
Posts: 3778
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: Simultaneous load on both the SSD and the flashdrive causes the latter to unmount

Wed Aug 26, 2020 11:29 am

if each the drive's current requirement is above 0.6A then the problem starts.
using seagate drives... then totally out of the question.

try using 2 x WD 2.5" drives... maybe you'll get lucky....
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

Return to “Troubleshooting”