(05-25-2019, 05:00 PM)Luke Wrote:(05-25-2019, 04:24 PM)va88 Wrote: Auyfan's stable bionic minimal image gives me this when I try to write on the drive. I'll try DietPi next.
Code:[ 1290.527712] Buffer I/O error on device sdb1, logical block 34816
[ 1290.528427] Buffer I/O error on device sdb1, logical block 34817
[ 1290.529101] Buffer I/O error on device sdb1, logical block 34818
[ 1290.529779] Buffer I/O error on device sdb1, logical block 34819
[ 1290.530455] Buffer I/O error on device sdb1, logical block 34820
[ 1290.531116] Buffer I/O error on device sdb1, logical block 34821
[ 1290.535704] Buffer I/O error on device sdb1, logical block 34822
[ 1290.540151] Buffer I/O error on device sdb1, logical block 34823
[ 1290.544512] Buffer I/O error on device sdb1, logical block 34824
[ 1290.548791] Buffer I/O error on device sdb1, logical block 34825
[ 1290.554958] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 4198400 starting block 35584)
[ 1290.555516] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 4198400 starting block 35840)
[ 1290.557340] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 6295552 starting block 36096)
[ 1290.557892] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 6295552 starting block 36352)
[ 1290.559766] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 8388608 starting block 36608)
[ 1290.560308] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 8388608 starting block 36864)
[ 1290.563064] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 0 size 8388608 starting block 37120)
[ 1290.564834] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 8388608 size 3149824 starting block 37376)
[ 1290.565376] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 12 (offset 8388608 size 3149824 starting block 37632)
[ 1290.586305] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 1290.586334] Aborting journal on device sdb1-8.
[ 1290.590635] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 1290.590884] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
[ 1290.591125] JBD2: Detected IO errors while flushing file data on sdb1-8
[ 1290.599521] EXT4-fs error (device sdb1): ext4_journal_check_start:56: Detected aborted journal
[ 1290.604178] EXT4-fs (sdb1): Remounting filesystem read-only
[ 1290.608543] EXT4-fs (sdb1): previous I/O error to superblock detected
[ 1290.625292] xhci-hcd xhci-hcd.9.auto: USB bus 5 deregistered
[ 1290.625676] xhci-hcd xhci-hcd.9.auto: remove, state 4
[ 1290.625715] usb usb4: USB disconnect, device number 1
[ 1290.626780] xhci-hcd xhci-hcd.9.auto: USB bus 4 deregistered
[ 1290.627094] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[ 1290.627355] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 4
[ 1290.627557] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x00210010
[ 1290.627600] xhci-hcd xhci-hcd.9.auto: irq 179, io mem 0xff600000
[ 1290.627813] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 1290.627824] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1290.627831] usb usb4: Product: xHCI Host Controller
[ 1290.627838] usb usb4: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[ 1290.627844] usb usb4: SerialNumber: xhci-hcd.9.auto
[ 1290.628618] hub 4-0:1.0: USB hub found
[ 1290.628699] hub 4-0:1.0: 1 port detected
[ 1290.629214] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[ 1290.629505] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5
[ 1290.629630] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1290.629758] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003
[ 1290.629767] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1290.629774] usb usb5: Product: xHCI Host Controller
[ 1290.629781] usb usb5: Manufacturer: Linux 4.4.132-1075-rockchip-ayufan-ga83beded8524 xhci-hcd
[ 1290.629787] usb usb5: SerialNumber: xhci-hcd.9.auto
[ 1290.630683] hub 5-0:1.0: USB hub found
[ 1290.630738] hub 5-0:1.0: 1 port detected
[ 1290.948125] usb 5-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 1290.960242] usb 5-1: New USB device found, idVendor=1058, idProduct=0748
[ 1290.960275] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 1290.960298] usb 5-1: Product: My Passport 0748
[ 1290.960319] usb 5-1: Manufacturer: Western Digital
[ 1290.960340] usb 5-1: SerialNumber: 575844314539314E53564632
[ 1290.962826] usb-storage 5-1:1.0: USB Mass Storage device detected
[ 1290.966470] scsi host10: usb-storage 5-1:1.0
[ 1291.969311] scsi 10:0:0:0: Direct-Access WD My Passport 0748 1010 PQ: 0 ANSI: 6
[ 1291.970180] scsi 10:0:0:1: Enclosure WD SES Device 1010 PQ: 0 ANSI: 6
[ 1291.977437] sd 10:0:0:0: [sdc] Spinning up disk...
As you can see, it throws a bunch of I/O errors and the system assigns a new letter for the drive next.
Those have the same kernel. Try this build and let me know if you're still getting errors. You can also try switching over to mainline (currently in ayufan's repo thts 5.1)
I tried the image from 19 Oct 2018, since the last one doesn't seem to get a valid IP from the DHCP, so I couldn't SSH into it.
Unfortunately I had no luck. The HD keeps working for a while longer, but in a few minutes a bunch of I/O and buffer errors appear and the drive disconnects and then reconnects.
DietPi didn't work too, it won't even allow me to mount the drive.
I'm back on the latest Armbian and decided to try the USB2 1TB drive on the USB3 port of the Rock64. Looks like it's working properly.
Maybe the USB3 500Gb drive requires more than 900mA? There's no official info actually, so maybe that's the case.
This is the drive: https://www.amazon.com/Passport-Portable...5UV4U?th=1
Is there any method to restrict the power this drive asks from the usb port, even if this could lower performance? Or maybe increasing the possible output of the USB3 port?
I've seem a topic around talking about a Raspberry Pi running a similar external HDD by setting a max usb output of 1A on its boot file.