Jump to content

Raketenjoint

Members
  • Posts

    2
  • Joined

  • Last visited

  1. Seems that upgrading console-setup-linux is causing a problem when running "sudo apt-get upgrade": Unpacking console-setup-linux (1.108ubuntu15.3) over (1.108ubuntu15.2) ... dpkg: error processing archive /var/cache/apt/archives/console-setup-linux_1.108ubuntu15.3_all.deb (--unpack): unable to sync file '/lib/systemd/system/setvtrgb.service.dpkg-new': Input/output error
  2. I've got the same problem with the Samsung Evo+ SDHC 32Gb on my Banana Pi Pro. According to F3 it's no counterfeit. I verificated the gpg key. I flashed "Armbian_5.25_Bananapipro_Ubuntu_xenial_next_4.9.7" via ether. When I want to update, it first mentions dpgk: root@bananapipro:/etc/network# sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I'm following its suggestion: root@bananapipro:/etc/network# sudo dpkg --configure -a Setting up libnettle6:armhf (3.2-1ubuntu0.16.04.1) ... Setting up libisc160:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up libisc-export160 (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up libnm0:armhf (1.2.2-0ubuntu0.16.04.4) ... Setting up libdns-export162 (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up libhogweed4:armhf (3.2-1ubuntu0.16.04.1) ... Setting up libisccc140:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Processing triggers for libc-bin (2.23-0ubuntu5) ... Setting up liblwres141:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Processing triggers for man-db (2.7.5-1) ... Setting up libdns162:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up libisccfg140:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up libbind9-140:armhf (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up bind9-host (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Setting up dnsutils (1:9.10.3.dfsg.P4-8ubuntu1.5) ... Processing triggers for libc-bin (2.23-0ubuntu5) ... Over HDMI i see exactly the same code as theroot posted above due to the Read-only Filesystem. Looking at dmesg: [ 1100.164087] mmc0: Card stuck in programming state! mmc_do_erase [ 1100.964095] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1101.764100] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1102.534118] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1102.550106] mmc0: tried to reset card, got error -5 [ 1102.550122] blk_update_request: I/O error, dev mmcblk0, sector 2088736 [ 1102.566000] mmcblk0: error -5 sending status command, retrying [ 1102.580920] mmcblk0: error -5 sending status command, retrying [ 1102.595742] mmcblk0: error -5 sending status command, aborting [ 1103.384140] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1104.174150] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1104.934171] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1104.949897] mmc0: tried to reset card, got error -5 [ 1104.949912] blk_update_request: I/O error, dev mmcblk0, sector 2817248 [ 1104.965287] blk_update_request: I/O error, dev mmcblk0, sector 2817256 [ 1104.980437] blk_update_request: I/O error, dev mmcblk0, sector 2817264 [ 1104.995491] blk_update_request: I/O error, dev mmcblk0, sector 2817272 [ 1105.010395] blk_update_request: I/O error, dev mmcblk0, sector 2817280 [ 1105.025265] blk_update_request: I/O error, dev mmcblk0, sector 2817288 [ 1105.040014] blk_update_request: I/O error, dev mmcblk0, sector 2817296 [ 1105.054755] blk_update_request: I/O error, dev mmcblk0, sector 2817304 [ 1105.069349] blk_update_request: I/O error, dev mmcblk0, sector 2817312 [ 1105.084021] mmcblk0: error -5 sending status command, retrying [ 1105.097886] mmcblk0: error -5 sending status command, retrying [ 1105.111614] mmcblk0: error -5 sending status command, aborting [ 1105.904196] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1106.694208] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1107.454226] sunxi-mmc 1c0f000.mmc: fatal err update clk timeout [ 1107.468835] mmc0: tried to reset card, got error -5 [ 1107.468919] EXT4-fs (mmcblk0p1): Delayed block allocation failed for inode 57349 at logical offset 0 with max blocks 8 with error 5 [ 1107.488787] EXT4-fs (mmcblk0p1): This should not happen!! Data will be lost [ 1107.530227] mmcblk0: error -5 sending status command, retrying [ 1107.546817] mmcblk0: error -5 sending status command, retrying [ 1107.563234] mmcblk0: error -5 sending status command, aborting [ 1107.579520] blk_update_request: 31 callbacks suppressed [ 1107.579530] blk_update_request: I/O error, dev mmcblk0, sector 2973024 [ 1107.596615] blk_update_request: I/O error, dev mmcblk0, sector 2973032 [ 1107.613710] blk_update_request: I/O error, dev mmcblk0, sector 2973040 [ 1107.630835] blk_update_request: I/O error, dev mmcblk0, sector 2973048 [ 1107.647854] blk_update_request: I/O error, dev mmcblk0, sector 2973056 [ 1107.664677] blk_update_request: I/O error, dev mmcblk0, sector 2973064 [ 1107.681485] blk_update_request: I/O error, dev mmcblk0, sector 2973072 [ 1107.698232] blk_update_request: I/O error, dev mmcblk0, sector 2973080 [ 1107.714855] blk_update_request: I/O error, dev mmcblk0, sector 2973088 [ 1107.731267] blk_update_request: I/O error, dev mmcblk0, sector 2973096 [ 1107.747595] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:314: I/O error -5 writing to inode 57350 (offset 0 size 155648 starting block 371666) [ 1107.747613] Buffer I/O error on device mmcblk0p1, logical block 371372 [ 1107.763737] Buffer I/O error on device mmcblk0p1, logical block 371373 [ 1107.779459] Buffer I/O error on device mmcblk0p1, logical block 371374 [ 1107.794574] Buffer I/O error on device mmcblk0p1, logical block 371375 [ 1107.809618] Buffer I/O error on device mmcblk0p1, logical block 371376 [ 1107.824522] Buffer I/O error on device mmcblk0p1, logical block 371377 [ 1107.839237] Buffer I/O error on device mmcblk0p1, logical block 371378 [ 1107.853658] Buffer I/O error on device mmcblk0p1, logical block 371379 [ 1107.868000] Buffer I/O error on device mmcblk0p1, logical block 371380 [ 1107.882142] Buffer I/O error on device mmcblk0p1, logical block 371381 [ 1107.896348] mmcblk0: error -5 sending status command, retrying [ 1107.908082] mmcblk0: error -5 sending status command, retrying [ 1107.919633] mmcblk0: error -5 sending status command, aborting [ 1107.931153] EXT4-fs error (device mmcblk0p1): ext4_find_entry:1463: inode #1878: comm dpkg: reading directory lblock 0 [ 1107.947724] mmcblk0: error -5 sending status command, retrying [ 1107.959213] mmcblk0: error -5 sending status command, retrying [ 1107.970646] mmcblk0: error -5 sending status command, aborting [ 1107.981886] Buffer I/O error on dev mmcblk0p1, logical block 0, lost sync page write [ 1107.995211] Aborting journal on device mmcblk0p1-8. [ 1108.005935] mmcblk0: error -5 sending status command, retrying [ 1108.017226] mmcblk0: error -5 sending status command, retrying [ 1108.028205] mmcblk0: error -5 sending status command, aborting [ 1108.039054] Buffer I/O error on dev mmcblk0p1, logical block 131072, lost sync page write [ 1108.052323] JBD2: Error -5 detected when updating journal superblock for mmcblk0p1-8. [ 1108.065228] EXT4-fs (mmcblk0p1): Remounting filesystem read-only According to this post my file system ext4 is broken. ------------- Solved? ------------- Using my user account instead of root solved my problem.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines