kirill9617 Posted August 9, 2018 Share Posted August 9, 2018 Hello everybody! I want setup my nonopi k2 as small home server, but I ran intoproblem with microSD that ruined all my plans. The trouble is that under load such as downloading or unpacking files (about 100M) or even doing 'apt update' can couse I/O errors. In dmesg I see lines like this: [ 309.344144] mmc0: tried to reset card, got error -110 [ 309.344157] print_req_error: I/O error, dev mmcblk0, sector 13022080 [ 309.344169] print_req_error: I/O error, dev mmcblk0, sector 13022088 [ 309.344176] print_req_error: I/O error, dev mmcblk0, sector 13022096 [ 309.344183] print_req_error: I/O error, dev mmcblk0, sector 13022104 [ 309.344190] print_req_error: I/O error, dev mmcblk0, sector 13022112 [ 309.344197] print_req_error: I/O error, dev mmcblk0, sector 13022120 [ 309.344204] print_req_error: I/O error, dev mmcblk0, sector 13022128 [ 309.344211] print_req_error: I/O error, dev mmcblk0, sector 13022136 [ 309.344218] print_req_error: I/O error, dev mmcblk0, sector 13022144 [ 309.344225] print_req_error: I/O error, dev mmcblk0, sector 13022152 [ 309.346208] mmcblk0: error -110 sending status command, retrying [ 309.347117] mmcblk0: error -110 sending status command, retrying [ 309.348024] mmcblk0: error -110 sending status command, aborting [ 309.351791] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384761 (offset 0 size 4341760 starting block 1628016) [ 309.351802] Buffer I/O error on device mmcblk0p1, logical block 1626736 [ 309.351814] Buffer I/O error on device mmcblk0p1, logical block 1626737 [ 309.351820] Buffer I/O error on device mmcblk0p1, logical block 1626738 [ 309.351825] Buffer I/O error on device mmcblk0p1, logical block 1626739 [ 309.351830] Buffer I/O error on device mmcblk0p1, logical block 1626740 [ 309.351835] Buffer I/O error on device mmcblk0p1, logical block 1626741 [ 309.351840] Buffer I/O error on device mmcblk0p1, logical block 1626742 [ 309.351845] Buffer I/O error on device mmcblk0p1, logical block 1626743 [ 309.351851] Buffer I/O error on device mmcblk0p1, logical block 1626744 [ 309.351856] Buffer I/O error on device mmcblk0p1, logical block 1626745 [ 309.352386] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384761 (offset[ 309.576236] EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:61: Detected aborted journal [ 309.584404] EXT4-fs (mmcblk0p1): Remounting filesystem read-only 0 size 4341760 starting block 1628272) [ 309.352925] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384761 (offset 0 size 4341760 starting block 1628528) [ 309.353459] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384761 (offset 0 size 4341760 starting block 1628784) [ 309.353970] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384761 (offset 0 size 4341760 starting block 1628820) [ 309.354081] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384762 (offset 0 size 4358144 starting block 1629076) [ 309.354619] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384762 (offset 0 size 4358144 starting block 1629332) [ 309.355155] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384762 (offset 0 size 4358144 starting block 1629588) [ 309.355694] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384762 (offset 0 size 4358144 starting block 1629844) [ 309.356206] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:323: I/O error 10 writing to inode 384762 (offset 0 size 4358144 starting block 1629884) [ 309.367665] mmc0: card 0001 removed [ 309.570456] Buffer I/O error on dev mmcblk0p1, logical block 135371, lost sync page write [ 309.574990] Aborting journal on device mmcblk0p1-8. [ 309.575014] Buffer I/O error on dev mmcblk0p1, logical block 131072, lost sync page write [ 309.575021] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8. [ 309.576224] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write [ 309.576236] EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:61: Detected aborted journal [ 309.584404] EXT4-fs (mmcblk0p1): Remounting filesystem read-only [ 309.590414] EXT4-fs (mmcblk0p1): previous I/O error to superblock detected [ 309.590435] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write I`ve already tried default, next, dev and self-built images, but every-time get the same problem. On default img i also have such messages. But they don`t cause a chash. [ 309.301045] mmcblk0: response CRC error sending r/w cmd command, card status 0xd00 I have no problems with this SD card if I use it with my phone or laptop. Thank you in advance! Link to comment Share on other sites More sharing options...
TonyMac32 Posted August 9, 2018 Share Posted August 9, 2018 Almost certainly a power supply or SD card issue. Lots of cards will work in laptops/phones that are still no good, and power supply issues are a constant. Are you using the microUSB or barrel jack? Link to comment Share on other sites More sharing options...
kirill9617 Posted August 11, 2018 Author Share Posted August 11, 2018 Thanks you for reply. Using barrel jack didn`t help. But I found solution by disabling UHS in dtb. board-nanopi_k2_disable_uhs.patch Link to comment Share on other sites More sharing options...
TonyMac32 Posted August 12, 2018 Share Posted August 12, 2018 Is it UHS in general or only the highest speed modes? for example, disabling SDR104 may be enough? Link to comment Share on other sites More sharing options...
kirill9617 Posted August 12, 2018 Author Share Posted August 12, 2018 It seems disabling SDR104 is enough 1 Link to comment Share on other sites More sharing options...
TonyMac32 Posted August 12, 2018 Share Posted August 12, 2018 One last question, can you give the kernel versions so I can see if this is an issue that has been addressed upstream or if it's still an active concern? With any support request it's helpful to provide the output of "armbianmonitor -u" Link to comment Share on other sites More sharing options...
kirill9617 Posted August 12, 2018 Author Share Posted August 12, 2018 Now I use self-built 4.18.0-rc8-meson64 , but I also tried default and next images with the same result. Do you need monitor output when it crashes or from working system? Link to comment Share on other sites More sharing options...
TonyMac32 Posted August 13, 2018 Share Posted August 13, 2018 hmmm ok. So the -rc8 show the issue before you disabled SDR104? Just trying to narrow down the issue. What I understand is that, at least for eMMC (and so I would assume SD, but it may not be), before recent clock fixes the old data clock rates were, in reality, only half the desired setting, so now limitations of some boards like the C2 are showing up that weren't known before. Link to comment Share on other sites More sharing options...
kirill9617 Posted August 13, 2018 Author Share Posted August 13, 2018 I don`t remember exactly, but i think -rc8 was the first thing i tried and it shown the issue Link to comment Share on other sites More sharing options...
Igor Posted September 10, 2018 Share Posted September 10, 2018 I can easily reproduce this problem with: so patches were added https://github.com/armbian/build/commit/428c72a6f1ea24dad2de9767ed269c3e5ca0f5d9 Link to comment Share on other sites More sharing options...
TonyMac32 Posted September 10, 2018 Share Posted September 10, 2018 I'll have to snag one of those cards. Link to comment Share on other sites More sharing options...
Recommended Posts