![]() ![]() They have never booted up without these I/O and journal errors, which will continue at random intervals after boot. These errors will either cause the system boot up process to dump into emergency / maintenance mode, or other times it seems to boot correctly but then the root filesystem gets marked readonly. JBD2: Error -5 detected when updating journal superblock for mmcblk0ps-8 Sometimes there is an accompanying filesystem error: The sector number will vary, the logical block number will vary, the device might be mmcblk0p3, and sometimes it says "lost async page write" instead of "lost sync page write". ![]() Print_req_error: I/O error, dev mmcblk0 sector 1228801īuffer I/O error on dev mmcblk0p2, logical block 131072, lost sync page write But every time I boot from them on the Layerscape box, there are the following I/O errors: I've had no problems reading and writing from them from my Ubuntu host PC. Both came with the Layerscape units that I bought, and both are Kingston brand Canvas Select 16 GB cards (SDS/16GB). I've built two such bootable removable SD cards. There are what appear to be some errors in this section, which I've detailed in another post. 0.3, 04/2019, section 3.1.4.2 Option 1 - Deploy LS1028A BSP images using removable storage device. I'm working through the Layerscape LS1028A BSP User Guide, Rev. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |