Resilio Sync CHROOT - F2FS-fs kernel errors

Installing and Using OpenWrt
1

Hi,

I please need help finding out why I get kernel errors and how to fix them.
From what I can understand it probably has something to do with the f2fs partition I added to run Resilio Sync in a chroot since they did not occur until yesterday and seem to stop when I stop the Resilio process and unmount said partition.

I use a Raspberry Pi 4B with a 64GB SD card and a TP-Link UE300 I first set up in march this year and upgraded to a stock 21.02.1 squashfs image with a few user-installed packages.
To put the almost 64GB of free space to use I decided to try setting up a chroot for Resilio sync by adding an f2fs partition and then following the wiki and scegg's more up to date and in-depth guide he thankfully wrote and linked in this post.
Everything worked fine for about 10 days until I checked the sytem log yesterday and found the kernel errors in question.

kernel errors (from today, after a reboot) 
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.580730] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.713862] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.718238] blk_update_request: I/O error, dev mmcblk0, sector 33791536 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.729888] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.734246] blk_update_request: I/O error, dev mmcblk0, sector 33842496 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.745808] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.750173] blk_update_request: I/O error, dev mmcblk0, sector 63005104 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.761722] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.766079] blk_update_request: I/O error, dev mmcblk0, sector 33827024 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.777616] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.781972] blk_update_request: I/O error, dev mmcblk0, sector 33851416 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.793515] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.797872] blk_update_request: I/O error, dev mmcblk0, sector 33852584 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.809391] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.813755] blk_update_request: I/O error, dev mmcblk0, sector 33841880 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.825288] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.829649] blk_update_request: I/O error, dev mmcblk0, sector 33869336 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840709] F2FS-fs (mmcblk0p3): Issue discard(4176838, 4176838, 1082) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840713] F2FS-fs (mmcblk0p3): Issue discard(4183208, 4183208, 377) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840716] F2FS-fs (mmcblk0p3): Issue discard(7828534, 7828534, 298) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840719] F2FS-fs (mmcblk0p3): Issue discard(4181274, 4181274, 189) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840722] F2FS-fs (mmcblk0p3): Issue discard(4184323, 4184323, 135) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840724] F2FS-fs (mmcblk0p3): Issue discard(4184469, 4184469, 46) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840727] F2FS-fs (mmcblk0p3): Issue discard(4183131, 4183131, 37) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.info kernel: [   68.840729] F2FS-fs (mmcblk0p3): Issue discard(4186563, 4186563, 36) failed, ret: -5
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.895669] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.900049] blk_update_request: I/O error, dev mmcblk0, sector 33791192 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.911589] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.915946] blk_update_request: I/O error, dev mmcblk0, sector 34146016 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.927484] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.932234] error 0 requesting status 0x80900
Sun Nov 21 12:26:08 2021 kern.err kernel: [   68.936966] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.941669] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.946400] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.951149] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.955851] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.960557] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.965255] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.969969] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.974669] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.979377] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   68.984074] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.info kernel: [   68.988436] F2FS-fs (mmcblk0p3): Issue discard(4176795, 4176795, 34) failed, ret: -5
Sun Nov 21 12:26:09 2021 kern.info kernel: [   68.988439] F2FS-fs (mmcblk0p3): Issue discard(4221148, 4221148, 34) failed, ret: -5
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.043676] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.048476] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.053224] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.058000] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.062706] error 0 requesting status 0x80900
Sun Nov 21 12:26:09 2021 kern.err kernel: [   69.067404] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.756810] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.warn kernel: [   91.761216] print_req_error: 19 callbacks suppressed
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.761224] blk_update_request: I/O error, dev mmcblk0, sector 1213392 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.777859] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.782234] blk_update_request: I/O error, dev mmcblk0, sector 1213024 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.793729] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.798086] blk_update_request: I/O error, dev mmcblk0, sector 34160976 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.809660] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.814021] blk_update_request: I/O error, dev mmcblk0, sector 1131392 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.825468] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.829853] blk_update_request: I/O error, dev mmcblk0, sector 1131600 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.841300] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.845655] blk_update_request: I/O error, dev mmcblk0, sector 1143168 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.857099] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.861460] blk_update_request: I/O error, dev mmcblk0, sector 1161672 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.872905] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.877265] blk_update_request: I/O error, dev mmcblk0, sector 1161688 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.888703] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.893067] blk_update_request: I/O error, dev mmcblk0, sector 1161720 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.904511] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.908876] blk_update_request: I/O error, dev mmcblk0, sector 1161872 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:31 2021 kern.err kernel: [   91.920377] error 0 requesting status 0x80900
Sun Nov 21 12:26:31 2021 kern.warn kernel: [   91.924817] __remove_discard_cmd: 19 callbacks suppressed
Sun Nov 21 12:26:31 2021 kern.info kernel: [   91.924821] F2FS-fs (mmcblk0p3): Issue discard(104570, 104570, 36) failed, ret: -5
Sun Nov 21 12:26:31 2021 kern.info kernel: [   91.924824] F2FS-fs (mmcblk0p3): Issue discard(104524, 104524, 22) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.930278] F2FS-fs (mmcblk0p3): Issue discard(4223018, 4223018, 17) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982756] F2FS-fs (mmcblk0p3): Issue discard(94320, 94320, 3) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982763] F2FS-fs (mmcblk0p3): Issue discard(94346, 94346, 3) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982766] F2FS-fs (mmcblk0p3): Issue discard(95792, 95792, 1) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982769] F2FS-fs (mmcblk0p3): Issue discard(98105, 98105, 1) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982771] F2FS-fs (mmcblk0p3): Issue discard(98107, 98107, 1) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982774] F2FS-fs (mmcblk0p3): Issue discard(98111, 98111, 1) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.info kernel: [   91.982776] F2FS-fs (mmcblk0p3): Issue discard(98130, 98130, 2) failed, ret: -5
Sun Nov 21 12:26:32 2021 kern.err kernel: [   91.983349] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   91.988103] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   91.992809] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   91.997519] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   92.002270] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   92.006973] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   92.011696] error 0 requesting status 0x80900
Sun Nov 21 12:26:32 2021 kern.err kernel: [   92.016398] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.251420] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.warn kernel: [   97.255833] print_req_error: 9 callbacks suppressed
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.255842] blk_update_request: I/O error, dev mmcblk0, sector 1208744 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.272379] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.276743] blk_update_request: I/O error, dev mmcblk0, sector 1208760 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.288255] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.292614] blk_update_request: I/O error, dev mmcblk0, sector 1212856 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.304068] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.308425] blk_update_request: I/O error, dev mmcblk0, sector 1212960 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.319869] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.324225] blk_update_request: I/O error, dev mmcblk0, sector 1213208 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.335682] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.340039] blk_update_request: I/O error, dev mmcblk0, sector 1228800 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.351516] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.355877] blk_update_request: I/O error, dev mmcblk0, sector 1499984 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.367326] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.371688] blk_update_request: I/O error, dev mmcblk0, sector 1500080 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.warn kernel: [   97.438694] __remove_discard_cmd: 9 callbacks suppressed
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.438701] F2FS-fs (mmcblk0p3): Issue discard(103989, 103989, 1) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.438709] F2FS-fs (mmcblk0p3): Issue discard(103991, 103991, 1) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444045] F2FS-fs (mmcblk0p3): Issue discard(104503, 104503, 1) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444052] F2FS-fs (mmcblk0p3): Issue discard(104516, 104516, 6) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444059] F2FS-fs (mmcblk0p3): Issue discard(104547, 104547, 10) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444070] F2FS-fs (mmcblk0p3): Issue discard(106496, 106496, 11) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444080] F2FS-fs (mmcblk0p3): Issue discard(140394, 140394, 1) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.444090] F2FS-fs (mmcblk0p3): Issue discard(140406, 140406, 1) failed, ret: -5
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.444750] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.449158] blk_update_request: I/O error, dev mmcblk0, sector 1500104 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.460634] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.465000] blk_update_request: I/O error, dev mmcblk0, sector 1500120 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.476439] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.481143] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.485838] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.err kernel: [   97.490545] error 0 requesting status 0x80900
Sun Nov 21 12:26:37 2021 kern.info kernel: [   97.550692] F2FS-fs (mmcblk0p3): Issue discard(140409, 140409, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [   97.550699] F2FS-fs (mmcblk0p3): Issue discard(140411, 140411, 3) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.706899] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.warn kernel: [  160.711313] print_req_error: 4 callbacks suppressed
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.711322] blk_update_request: I/O error, dev mmcblk0, sector 1249280 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.728090] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.732509] blk_update_request: I/O error, dev mmcblk0, sector 1131552 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.744120] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.748489] blk_update_request: I/O error, dev mmcblk0, sector 1172960 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.759938] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.764313] blk_update_request: I/O error, dev mmcblk0, sector 1173000 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.775758] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.780125] blk_update_request: I/O error, dev mmcblk0, sector 1173032 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.791569] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.795938] blk_update_request: I/O error, dev mmcblk0, sector 1490080 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.807377] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.811736] blk_update_request: I/O error, dev mmcblk0, sector 1490128 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.823170] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.827532] blk_update_request: I/O error, dev mmcblk0, sector 1500152 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.838975] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.843335] blk_update_request: I/O error, dev mmcblk0, sector 1500184 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.warn kernel: [  160.854300] __remove_discard_cmd: 4 callbacks suppressed
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.854303] F2FS-fs (mmcblk0p3): Issue discard(109056, 109056, 512) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910283] F2FS-fs (mmcblk0p3): Issue discard(94340, 94340, 3) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910286] F2FS-fs (mmcblk0p3): Issue discard(99516, 99516, 2) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910289] F2FS-fs (mmcblk0p3): Issue discard(99521, 99521, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910292] F2FS-fs (mmcblk0p3): Issue discard(99525, 99525, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910295] F2FS-fs (mmcblk0p3): Issue discard(139156, 139156, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910298] F2FS-fs (mmcblk0p3): Issue discard(139162, 139162, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910300] F2FS-fs (mmcblk0p3): Issue discard(140415, 140415, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.info kernel: [  160.910303] F2FS-fs (mmcblk0p3): Issue discard(140419, 140419, 1) failed, ret: -5
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.910859] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.915236] blk_update_request: I/O error, dev mmcblk0, sector 1500200 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.926680] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.931377] error 0 requesting status 0x80900
Sun Nov 21 12:27:40 2021 kern.err kernel: [  160.936072] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  160.940779] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  160.945478] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  160.950188] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  160.954903] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.info kernel: [  161.014281] F2FS-fs (mmcblk0p3): Issue discard(140421, 140421, 1) failed, ret: -5
Sun Nov 21 12:27:41 2021 kern.err kernel: [  161.014934] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  161.019739] error 0 requesting status 0x80900
Sun Nov 21 12:27:41 2021 kern.err kernel: [  161.024531] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.751974] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.756766] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.761540] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.766267] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.771157] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.775857] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.780556] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.785307] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.790019] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.794714] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.799434] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.804233] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.808934] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.813636] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.818338] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.823035] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.827737] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.832436] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.837135] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.841857] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.846557] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.851257] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.855956] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.860656] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.865354] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.870054] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.874753] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.879483] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.884186] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.888885] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.893583] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.898285] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.902983] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.907682] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.912382] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.917083] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.921781] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.926484] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.931182] error 0 requesting status 0x80900
Sun Nov 21 12:27:42 2021 kern.err kernel: [  162.935880] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.940581] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.945297] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.949998] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.954734] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.959433] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.964132] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.968832] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.973531] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.978228] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.982928] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.987626] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.992339] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  162.997043] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  163.001742] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  163.006443] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  163.011144] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  163.015842] error 0 requesting status 0x80900
Sun Nov 21 12:27:43 2021 kern.err kernel: [  163.020541] error 0 requesting status 0x80900

I already tried

fsck.f2fs -a /dev/mmcblk0p3 
root@Router:~# fsck.f2fs -a /dev/mmcblk0p3
Info: Fix the reported corruption.
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124358656 (60722 MB)
Info: MKFS version
  "Linux version 5.4.106 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16341-bbb9c1c2be)) #0 SMP Fri Mar 26 09:12:12 2021"
Info: FSCK version
  from "Linux version 5.4.106 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16341-bbb9c1c2be)) #0 SMP Fri Mar 26 09:12:12 2021"
    to "Linux version 5.4.154 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16325-88151b8303)) #0 SMP Sun Oct 24 09:01:35 2021"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 124358656 (60722 MB)
Info: CKPT version = 48482956
Info: checkpoint state = c6 :  nat_bits crc compacted_summary orphan_inodes sudden-power-off
Info: No error was reported
root@Router:~#

and

fsck.f2fs -f /dev/mmcblk0p3 
root@Router:~# fsck.f2fs -f /dev/mmcblk0p3
Info: Force to fix corruption
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124358656 (60722 MB)
Info: MKFS version
  "Linux version 5.4.106 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16341-bbb9c1c2be)) #0 SMP Fri Mar 26 09:12:12 2021"
Info: FSCK version
  from "Linux version 5.4.106 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16341-bbb9c1c2be)) #0 SMP Fri Mar 26 09:12:12 2021"
    to "Linux version 5.4.154 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16325-88151b8303)) #0 SMP Sun Oct 24 09:01:35 2021"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 124358656 (60722 MB)
Info: CKPT version = 48482956
Info: Corrupted valid nat_bits in checkpoint
Info: Write valid nat_bits in checkpoint
Info: checkpoint state = c6 :  nat_bits crc compacted_summary orphan_inodes sudden-power-off

[FSCK] Unreachable nat entries                        [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking                [Ok..]
[FSCK] Hard link checking for regular file            [Ok..] [0x2]
[FSCK] valid_block_count matching with CP             [Ok..] [0x209dc]
[FSCK] valid_node_count matching with CP (de lookup)  [Ok..] [0x2e3f]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x2e3f]
[FSCK] valid_inode_count matched with CP              [Ok..] [0x2e0c]
[FSCK] free segment_count matched with CP             [Ok..] [0x7482]
[FSCK] next block offset is free                      [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs                           [Ok..]
Info: Duplicate valid checkpoint to mirror position 1024 -> 512
Info: Write valid nat_bits in checkpoint
Info: Write valid nat_bits in checkpoint

Done: 10.136562 secs
root@Router:~#

but the errors seem to return as soon as I mount the partition.

Additional info in case it's needed:

fdisk /dev/mmcblk0 
root@Router:~# fdisk /dev/mmcblk0

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/mmcblk0: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5452574f

Device         Boot  Start       End   Sectors  Size Id Type
/dev/mmcblk0p1 *      8192    139263    131072   64M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      147456    360447    212992  104M 83 Linux
/dev/mmcblk0p3      376832 124735487 124358656 59.3G 83 Linux

Command (m for help):
block info 
root@Router:~# block info
/dev/loop0: UUID="22657911-d70a-4cb5-9526-f1fb21e5478e" LABEL="rootfs_data" VERSION="1.0" MOUNT="/overlay" TYPE="ext4"
/dev/mmcblk0p1: UUID="C941-3CB7" LABEL="boot" VERSION="FAT16" MOUNT="/boot" TYPE="vfat"
/dev/mmcblk0p2: UUID="8097fbe6-6c4809d7-9ef0b1b9-3fc33c47" VERSION="4.0" MOUNT="/rom" TYPE="squashfs"
/dev/mmcblk0p3: UUID="61dcc456-eb95-467e-9471-4ab3abf806af" VERSION="1.14" MOUNT="/mnt/mmcblk0p3" TYPE="f2fs"
root@Router:~#
df -h 
root@Router:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.8M      4.8M         0 100% /rom
tmpfs                     1.9G      1.1M      1.9G   0% /tmp
/dev/loop0               92.2M     28.4M     56.8M  33% /overlay
overlayfs:/overlay       92.2M     28.4M     56.8M  33% /
/dev/mmcblk0p1           63.9M     15.7M     48.2M  25% /boot
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mmcblk0p3           59.3G      1.8G     57.5G   3% /mnt/mmcblk0p3
root@Router:~#
mount 
root@Router:~# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/loop0 on /overlay type ext4 (rw,noatime)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
/dev/mmcblk0p1 on /boot type vfat (rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
/dev/mmcblk0p3 on /mnt/mmcblk0p3 type f2fs (rw,lazytime,relatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,alloc_mode=default,fsync_mode=posix)
root@Router:~#

Please tell me what I missed and how to fix it.
Kind regards

2

Probably sd card failure, sd card will wear rapidly if used with a high demanding i/o notify applications like a resilio sync.

3

That's certainly one possibility and SD card wear is a concern hence the squashfs image and f2fs on the third partition.
But is it likely considering Resilio was only in use for 10 days, only 3% of that partition is used and the files that are synced are about 100 Excel files with collectively less than 2MB of which all but 3 or 4 did not change during that time?

Could it also be that the discard command is the reason for the errors in the log?
In the meantime I found out that f2fs mounts with the discard command enabled by default which is real-time discard and apparently not the prefered method.
Therefore I tried remounting the partition with the "nodiscard" option and the kernel errors didn't show up in the log ever since.
What I don't know is what disabling discard means for the performance of the SC card in the long run.
I could not find out whether discard/trim is needed to retain the SD cards performance or if it's only needed for SSDs.

I also couldn't really figure out if the SD card even supports discard or not.
On the one hand it's an SDXC card which are supposed to support it and

lsblk --discard

shows "the values of DISC-GRAN (discard granularity) and DISC-MAX (discard max bytes) columns" as non-zero but when I tried

fstrim --verbose /mnt/mmcblk0p3

I got

/mnt/mmcblk0p3: 0 B (0 bytes) trimmed

and when I tried formatting the partition with

mkfs.f2fs -o 5 /dev/mmcblk0p3 
root@Router:~# mkfs.f2fs -o 5 /dev/mmcblk0p3

        F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 0
Info: Trim is enabled
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 124358656 (60722 MB)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
  "Linux version 5.4.154 (builder@buildhost) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 r16325-88151b8303)) #0 SMP Sun Oct 24 09:01:35 2021"
Info: [/dev/mmcblk0p3] Discarding device
Info: This device doesn't support BLKSECDISCARD
Info: This device doesn't support BLKDISCARD
Info: Overprovision ratio = 5.000%
Info: Overprovision segments = 1554 (GC reserved = 48)
Info: format successful
root@Router:~#

it said:

Info: This device doesn't support BLKSECDISCARD
Info: This device doesn't support BLKDISCARD

So I'm still very much confused.

4

If you are using an SD that it's poor quality then even with low usage will wear, just because having small constants reads/writes or even stats reading will act as activity making them hotter, etc.

Can you provide a picture or brand/model of your card?

5

It's the 64GB one:

Something was definitely strange:
after posting I noticed that changes in the settings were lost, additionally installed packages got vanished and uninstalled packages reappeared after a reboot. Might have been this but to be save I flashed an ext4 image (instead of squashfs this time) on a spare SD card which I'm using right now.

I don't know how to check the 64GB's health though. From what I could google it seems SD cards don't make bad sectors transparent to OSs...

6

The SanDisk Extreme microSDXC card is a A2 card. I have three of these cards. They don't work flawlessly in every device, only in my SanDisk MobileMate USB3 reader.

Perhaps this link

may explain, why you have these problems.

Specially the following text is interesting:

>Application Performance Class 2 (A2)
>A2 promises even better performance with 4000/2000 read/write IOPS
>minimum but there's a problem since as outlined by the SD Association A2
>cards show "much higher performance than A1 performance by using
>functions of Command Queuing and Cache".
>
>Cache and Command Queuing require host (driver) support since the host
>needs to activate those new features first. The cache feature on A2 rated
>cards makes use of volatile RAM on the card requiring the host to learn
>new commands to issue flushing the cache (involving the risk of data
>losses -- for details see especially chapter 4.17 in Physical Layer
>Simplified Specification 6.0)

For my raspi-like hosts I avoid to buy A2 cards. With my A1 sdxc cards I
have no problems (neither with a built-in card reader nor an USB card
reader).

2 Likes
7

Thank you, that's interesting!
I do have to admit that I did not consider the SD card's rating/class when I got it and only checked a price comparison site for a recent model with a high read rating, where I found the SanDisk Extreme 64GB for ~15€ at a local retail store...

I could not find any info on whether the 5.4.154-1 kernel or RPi 4B supports A2 these days, so it would probably wise to use the SanDisk Extreme in an Android phone and get a different card for the RPi (ironically the spare I'm using right now is a SanDisk Class 4 from an old Android phone).

Would you recommend to get something like a Kingston SDCIT2/8GBSP which is ~10€ for the 8GB model for it's "industrial-grade" or is any consumer grade card fine as long as it is A1?
(My use case is home/home office, so not a mission critical industry application.)

8

Keep in mind, that the maximum read speed of the rpi4b built-in card reader is about 45 to 50 MB/sec. So there is no gain to buy a SD card with 120 MB/sec.

Instead of buying a card with a high read speed I would invest the extra buckets into a high endurance card. Those cards stand more write operations than the standard cards.

I don't know that card.

I'm not the sd card expert, so can't give you any recommodations. But I can tell you, what sd cards I've used during the last years.

My favorite card is Sandisk Ultra (either 32 MB or 64 MB). I'm using it in different devices and never ever had a failure.

Last year I bought some Transcend cards, up to now no failure.

Don't buy any cheap no-name cards, but cards from manufacturers with a good reputation. The few buckets you save is not worth the trouble with corrupted filesystems.

So, make up your own decision.

Perhaps other forum members can jump in and share their experiences with sd cards.

1 Like
9

That was meant to emphasize how little research I did before I got the Sandisk Extreme A2 SD card first time around.

After this experience I got three more SD cards to have some spares at hand and made sure they'er A1 as you recommended.
2 Kingston SDCIT2/8GBSP and 1 Sandisk Extreme 32GB.
I could not find any endurance values of these cards but one benefit to the Kingston cards is that their health and endurance apparently can be checked with hdsentinel without overwriting the data.

When I formatted the 3rd partition with f2fs this time it didn't say

Info: This device doesn't support BLKDISCARD

only

Info: This device doesn't support BLKSECDISCARD

though I'm not sure what it means.
Mounted it with the "nodiscard" option from the start.

However, I still haven't decided whether or not to set up the chroot and Resilio again to test if this cards does any better than the Sandisk Extreme since I don't want to deliberately ruin another card.