nareshkamboju

l-a-m-c failed

Jul 28th, 2016
81
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.54 KB | None | 0 0
  1. mkfs.fat 3.0.26 (2014-03-07)
  2. mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
  3. Image Name: boot script
  4. Created: Wed Jul 27 23:51:06 2016
  5. Image Type: ARM Linux Script (uncompressed)
  6. Data Size: 296 Bytes = 0.29 kB = 0.00 MB
  7. Load Address: 00000000
  8. Entry Point: 00000000
  9. Contents:
  10. Image 0: 288 Bytes = 0.28 kB = 0.00 MB
  11. Traceback (most recent call last):
  12. File "/usr/bin/linaro-android-media-create", line 167, in <module>
  13. unpack_android_binary_tarball(args.system, TMP_DIR)
  14. File "/usr/lib/python2.7/dist-packages/linaro_image_tools/media_create/unpack_binary_tarball.py", line 33, in unpack_android_binary_tarball
  15. stderr = proc.communicate()[1]
  16. File "/usr/lib/python2.7/dist-packages/linaro_image_tools/cmd_runner.py", line 94, in communicate
  17. stderr)
  18. linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process "['tar', '--selinux', '--numeric-owner', '-C', '/tmp/tmpa37GAJ', '-jxf', 'system.tar.bz2']" returned a non-zero value: 2
  19. stderr was
  20.  
  21. bzip2: Compressed file ends unexpectedly;
  22. perhaps it is corrupted? *Possible* reason follows.
  23. bzip2: Inappropriate ioctl for device
  24. Input file = (stdin), output file = (stdout)
  25.  
  26. It is possible that the compressed file(s) have become corrupted.
  27. You can use the -tvv option to test integrity of such files.
  28.  
  29. You can use the `bzip2recover' program to attempt to recover
  30. data from undamaged sections of corrupted files.
  31.  
  32. tar: Unexpected EOF in archive
  33. tar: Unexpected EOF in archive
  34. tar: Error is not recoverable: exiting now
Add Comment
Please, Sign In to add comment