8 Replies Latest reply on Oct 17, 2016 11:40 PM by xd11223

    EXT4-fs error (device mmcblk0p8) on Edison after flash

    CristianMori

      Hello everyone

      I am pretty new with the Edison so I have been playing with it and flashed a few times. Loggin in with putty I see several lines like this

       

       

       

      [  589.382151] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm node: deleted inode referenced: 46219

      [  589.387858] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm node: deleted inode referenced: 46219

      [  604.458268] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm configure_ediso: deleted inode referenced: 46218

      [  604.698049] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm configure_ediso: deleted inode referenced: 46218

      [  605.449150] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm node: deleted inode referenced: 46219

      [  605.454843] EXT4-fs error (device mmcblk0p8): ext4_lookup:1437: inode #7020: comm node: deleted inode referenced: 46219

       

      I tryed re flashing but they persist. running fsck gives no result

       

      Any idea????

        • 1. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hello CristianMori,
           
          When did this behavior started? Which flashing method were you using?
           
          In case you haven't tried it, I'd suggest you to try flashing your board using the flashall method. You can find how to use flashall in https://communities.intel.com/docs/DOC-25154.
           
          -Peter.

          • 2. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
            CristianMori

            Hi Peter

            I tried first with the intel application installer, but was not working.

            I tried with the flashall, and still not working. Could not find the dfu device.

            Then I had to login and stop the boot and force the dfu manually, and at that point I could use the flash all

            Even after the flash all, the same problem persisted.

             

            I am going to play with it more tonight. A colleague suggested to remove the edison from the board and plug it back in. I'll keep you posted

            • 3. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              In that case I believe your best option would be to submit an email to this form:

              https://customercare.intel.com/?lang=en-US

              We should be able to help you more accurately there.
              -Peter.

              • 4. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
                CristianMori

                Thanks Peter.

                Curiously enough, against what I was thinking, popping the module out of the baseboard (with no power, of course) and putting it back in solved the issue with no more flashing needed......

                 

                I'll keep monitoring and update...

                • 5. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  That is very strange. Nevertheless, I'm glad to hear that it is now working fine. If you ever notice any other odd behavior, please post it on the community, we'll try to help you in any way we can.

                  -Peter.

                  • 6. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
                    xd11223

                    I got the same error. I use the command 'dd if=/media/sdcard/tmp.img of=/dev/mmcblk0 bs=1M' to backup my system. In source edison, do not show the error, but the backup show as follow.

                     

                    [  709.032200] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  709.271845] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  709.401410] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  709.531772] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  712.261281] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  712.434322] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  712.611272] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    [  712.741457] EXT4-fs error (device mmcblk0p8): htree_dirblock_to_tree:920: inode #34510: block 9226: comm gunicorn: bad entry in directory: directory entry across range - offset=0(0), inode=959658551, rec_len=27680, name_len=111

                    • 7. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
                      Intel Corporation
                      This message was posted on behalf of Intel Corporation

                      Hello xd11223,

                      Have you already tried to reflash and remount the board just like CristianMori? In case you haven't, could you please do and let us know if something changes?

                      In case the issue persist, do you have access to another expansion board? I would like to check if the issue is related to it.

                      Let me know.
                      -Peter.

                      • 8. Re: EXT4-fs error (device mmcblk0p8) on Edison after flash
                        xd11223

                        Hi,

                         

                        I already try to use flashall.sh to re-flash the board. After the first post-install.sh, then restart.

                        After restart, use dd to restore my system. Sometimes there are same error.

                         

                        This system is which using the create_debian_image.sh created, and follow the flash flow: using the flashall.sh.

                         

                        Now I create my system by mounting ext4 and chroot, it seems like okay. Thanks.