Jump to content
  • 0

CubieTruck hangs on every Sundays..



I'm using CT with Armbian 5.25(mainline) server version.


The system hangs on every Sundays, and this is the 3rd time, since it hanged two weeks ago for the first time.

When I connected a monitor with it, it says..

mmcblk0 : error -5 sending status command, retrying
blk_update_request : I/O error, dev mmcblk0, sector 1503312
.... similar messages are repeated..

I have no idea what causes this.

I do not use CRON.


I installed these packages.

Mpd, nginx, nfs server, samba server, deluge-daemon, pure-ftpd, Resilio Sync.


Can anyone help me?

Link to comment
Share on other sites

11 answers to this question

Recommended Posts

Help us fund some #badass gear for our continuous integration build framework

  • 0

The results of armbianmonitor -c $HOME.


Starting iozone tests. Be patient, this can take a very long time to complete:
Iozone: Performance Test of File I/O
       Version $Revision: 3.429 $
Compiled for 32 bit mode.
Build: linux 

Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins
            Al Slater, Scott Rhine, Mike Wisner, Ken Goss
            Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR,
            Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner,
            Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone,
            Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root,
            Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer,
            Vangel Bojaxhi, Ben England, Vikentsi Lapa.

Run began: Mon Feb 27 14:57:12 2017

Include fsync in write timing
O_DIRECT feature enabled
Auto Mode
File size set to 102400 kB
Record Size 4 kB
Record Size 512 kB
Record Size 16384 kB
Command line used: iozone -e -I -a -s 100M -r 4k -r 512k -r 16M -i 0 -i 1 -i 2
Output is in kBytes/sec
Time Resolution = 0.000001 seconds.
Processor cache size set to 1024 kBytes.
Processor cache line size set to 32 bytes.
File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride                                    
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4     1151     2766     7293     7306     6765     2958                                                          
          102400     512    17175    19856    21668    21732    21719    20625                                                          
          102400   16384    15232    16455    22040    22038    22037    17607                                                          

iozone test complete.
touch: cannot touch './cardtest.m2rKKL/.starttime': No such file or directory

Test stopped, read-only filesystem

Please be careful using this media since it seems it's already broken. Exiting test.

I don't know why it says read only file system, while it is not.

My sd disk is Samsung MICROSDXC 64GB EVO PLUS.

Is there something wrong with my sd disk?

Link to comment
Share on other sites

  • 0

I don't know why it says read only file system, while it is not.


There's something strange going on. Unfortunately you ran the disk test after providing the output from 'armbianmonitor -u' (we've designed it that '-u' is able to pick up detailed results from '-c' and now this piece of information is missing). In case you've not rebooted in between please provide the output from '-u' again.


(-c provides a logfile '/tmp/armbianmonitor_checks_nnn' which contains useful information. But /tmp will be cleared on every reboot)

Link to comment
Share on other sites

  • 0

@tkaiser Thank you for your concern. Here's another one. Which is the log after I tested armbianmonitor -c.



Thank you. There's a bug in armbianmonitor (but vey low priority to fix it since testing through this was very time consuming). The checks were successfully completed (see the end of the log output) but since your 64GB SD card is mostly filled only ~20GB were tested so maybe there's something wrong with other pages/blocks on the card. The error messages in your 1st post suggest that there's a problem with the card (or card slot, maybe check the seating?)

Link to comment
Share on other sites

  • 0

I've been using Armbian 5.2x since last December, but I've got this error 3 weeks ago.

I'll wait and see if there's an error this Sunday. If so, then try to change the card..


BTW, I don't understand what you meant, "check the seating".

Link to comment
Share on other sites

  • 0

For anyone who might be interested in..


Yes, another Sunday has come.

It did not frozen, and I could connect to CubieTruck with ssh.

However most of commands are not woking.


ls works, but ps, lsof, reboot, shutdown... now work.


I powered down and remove the SD card, and check it on my desktop PC.

Here is the result of fsck.


$ sudo fsck.ext4 -v -C 0 /dev/sdc1
e2fsck 1.42.13 (17-May-2015)
ArmBuntu: 저널 복구중 (Journal recovering, maybe.)
Clearing orphaned inode 6490 (uid=0, gid=0, mode=0100644, size=304832)
Clearing orphaned inode 9584 (uid=0, gid=0, mode=0100644, size=345164)
Clearing orphaned inode 1766981 (uid=999, gid=999, mode=0100600, size=11308)
Clearing orphaned inode 1766927 (uid=999, gid=999, mode=0100600, size=2056)
Setting free inodes count to 3691751 (was 3691763)
Setting free blocks count to 8304046 (was 5050204)
ArmBuntu: clean, 70825/3762576 files, 7326034/15630080 blocks


There must be something wrong with my SD card.

I can change this card to a new one, but I have to visit the Customer center, or send it to them by mail.. Anyway it takes time.


I've just reinstall Armbian again, and wait for another Sunday.

Link to comment
Share on other sites

  • 0

For anyone who might concern.


I reinstalled Armbian, and everything works fine so far.

If anything happens, I'll post it here.


I have no idea what causes this, but I resized(extend the partition to maximum size) the SD card, that could be the reason.

This thread might help.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Create New...