Jump to content

[Solved] After reboot, installations is gone


DoXer

Recommended Posts

Hi,

I'm new with Armbian, have some experience with Raspberry.

 

I have succesfully installed it on a bananaPi.

uname -a
Linux bananapipro 4.4.3-sunxi #19 SMP Tue Mar 1 21:34:52 CET 2016 armv7l GNU/Linux

Then I have installed Logitechmediaserver with

dpkg -i logitech....deb

It runs well, but after a reboot the installation is not there anymore.

/var/lib is default, the init.d-script is also not there.

 

Any hints?

 

Edit:

I have the message for 19 updates, so I made

apt-get update

After reboot, all updates are gone and I get the message for the 19 updates again.

 

Regards

DoXer

Link to comment
Share on other sites

That indicates some troubles with the SD media. Can you try to use another card? Can you provide a full boot log?

 

BTW: What about including the f3 package to the list of default packages and introducing 'armbianmonitor -c' (check card)? Would be a bit tricky since we can not allow f3write filling the whole card [1] (might require patching f3write/f3read to be able to specify the size of the test files and adjust this to 100MB instead) and we're not able to test the whole card in this mode but it will rule out 99% of the 'Armbian is unreliable' complaints that are in fact related to faulty SD cards.

 

Seeing the reported sequential write speeds from f3write can also be interesting/frustrating/enlightening (since there exist many cards that show good performance on 75% of the capacity and transfer speeds drop down to a few KB/s on the rest of the capacity) and if we add/install also the iozone3 package and fire up the random I/O tests mentioned here we could provide a simple tool to nail many of the problems related to 'bad storage' down.

 

BTW: 'please provide full boot log' can be translated to recommend 'sudo armbianmonitor -b', reboot,  'sudo armbianmonitor -u' now ;)

 

[1] f3 manual page:

 

 

F3(1)                   test real flash memory capacity                  F3(1)

 

NAME

       f3write, f3read - test real flash memory capacity

 

SYNOPSIS

       f3write [--start-at=NUM] [--end-at=NUM] <PATH>

       f3read  [--start-at=NUM] [--end-at=NUM] <PATH>

 

DESCRIPTION

       F3 (Fight Flash Fraud or Fight Fake Flash) tests the full capacity of a

       flash card (flash drive, flash disk, pendrive). It writes to  the  card

       and  then checks if can read it. It will assure you haven't been sold a

       card with a smaller capacity than stated.

 

       When writing to flash drive, f3write  fills  the  filesystem  with  1GB

       files named N.h2w, where N is a number (i.e. /[0-9]+/).

 

       WARNING: all data on the tested disk might be lost!

 

OPTIONS

       --start-at=NUM

              Initial number of file names. Default value is 1.

 

       --end-at=NUM

              Final number of file names. Default value is "infinity".

 

EXAMPLE

       To write over a flash drive mounted at /media/TEST:

 

             $ f3write /media/TEST

 

       To read this flash drive:

 

             $ f3read /media/TEST

 

AUTHOR

       F3 was written by Michel Machado <michel@digirati.com.br>.  This manual

       page was first written by  Joao  Eriberto  Mota  Filho  <eriberto@erib-

       erto.pro.br>.

 

F3 5.0                           December 2014                           F3(1)

 

 

Link to comment
Share on other sites

Checking SD cards with f3 and if we get close top 99% + statement: "Low quality SD card can lead to system failures", than this is done  :P

sudo armbianmonitor -b', reboot,  'sudo armbianmonitor -u

Working nice but it's n/a on older boards ... yet. Need to pack things together and push to repository.

 

And yes, much better to get wanted info this way. Can't be more simple.

Link to comment
Share on other sites

Checking SD cards with f3 and if we get close top 99% + statement: "Low quality SD card can lead to system failures", than this is done  :P

 

I've just checked that if we implement 'armbianmonitor -c' in a way we ensure it's not called as root or via sudo we can simply use f3write since we use the default 5% reserved space (see here for example -- and this is something we should consider when doing the fs resize: Using 'tune2fs -m 2' if the card is larger than 15GiB and reducing that to maybe even 1% when larger than 30GiB?)

 

I'll test that over the weekend and might push the '-c' functionality as PR

Link to comment
Share on other sites

Here we go. I chose to be able to specify a path so disk checking can also be used with external thumb drives or SD cards in card readers and so on. Looks then like this (this is the SD card where the system is residing on):

 

 

 

tk@orangepipc:~$ armbianmonitor -c /home/tk

Now starting to write to the card, please be patient, this might take a very long time

Free space: 5.21 GB

Creating file 1.h2w ... OK!

Creating file 2.h2w ... OK!

Creating file 3.h2w ... OK!

Creating file 4.h2w ... OK!

Creating file 5.h2w ... OK!

Free space: 325.22 MB

Average writing speed: 14.82 MB/s

 

Now verifying the written data:

                  SECTORS      ok/corrupted/changed/overwritten

Validating file 1.h2w ... 2097152/        0/      0/      0

Validating file 2.h2w ... 2097152/        0/      0/      0

Validating file 3.h2w ... 2097152/        0/      0/      0

Validating file 4.h2w ... 2097152/        0/      0/      0

Validating file 5.h2w ... 1880680/        0/      0/      0

 

  Data OK: 4.90 GB (10269288 sectors)

Data LOST: 0.00 Byte (0 sectors)

      Corrupted: 0.00 Byte (0 sectors)

Slightly changed: 0.00 Byte (0 sectors)

    Overwritten: 0.00 Byte (0 sectors)

Average reading speed: 21.31 MB/s

 

Starting iozone tests:

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: Fri Mar 18 17:01:12 2016

 

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 /home/tk/cardtest.J0kMqR

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     2867     3022     8163     8171     8145     1243                                                          

          102400     512    19708    18935    21583    21593    21528     3033                                                          

          102400   16384    19008    20369    22915    22915    22910    20343                                                          

 

iozone test complete.

 

The results from testing /dev/mmcblk0p1 (ext4):

  Data OK: 4.90 GB (10269288 sectors)

Data LOST: 0.00 Byte (0 sectors)

Average writing speed: 14.82 MB/s

Average reading speed: 21.31 MB/s

                                            random    random

reclen    write  rewrite    read    reread    read     write

     4     2867     3022     8163     8171     8145     1243                                                          

   512    19708    18935    21583    21593    21528     3033                                                          

 16384    19008    20369    22915    22915    22910    20343                                                          

 

Health summary: OK

 

Performance summary:

Sequential reading speed: 21.31 MB/s 

 4K random reading speed:  8145 KB/s 

Sequential writing speed: 14.82 MB/s 

 4K random writing speed:  1243 KB/s 

 

To interpret the results above correctly or search for alternatives 

please refer to http://oss.digirati.com.br/f3/and also

http://www.jeffgeerling.com/blogs/jeff-geerling/raspberry-pi-microsd-card

http://thewirecutter.com/reviews/best-microsd-card/

 

 

 

Now the test is running on a card that is known to be faulty and then afterwards I will let it run on an ultra slow card that might have also minor errors.

Link to comment
Share on other sites

Now test with faulty SD card:

 

 

 

tk@orangepipc:~$ armbianmonitor -c /mnt/faulty-card

 

WARNING: It seems you're not testing the SD card but instead /dev/sda1 (ext4)

 

Now starting to write to the card, please be patient, this might take a very long time

Free space: 3.53 GB

Creating file 1.h2w ... OK!

Creating file 2.h2w ... OK!

Creating file 3.h2w ... OK!

Creating file 4.h2w ... OK!

Free space: 188.71 MB

Average writing speed: 2.08 MB/s

 

Now verifying the written data:

                  SECTORS      ok/corrupted/changed/overwritten

Validating file 1.h2w ... 2097152/        0/      0/      0

Validating file 2.h2w ... 2097152/        0/      0/      0

Validating file 3.h2w ... 1337312/        0/      0/      0 - NOT fully read due to "Input/output error"

Validating file 4.h2w ...       0/        0/      0/      0 - NOT fully read due to "Input/output error"

 

  Data OK: 2.64 GB (5531616 sectors)

Data LOST: 0.00 Byte (0 sectors)

      Corrupted: 0.00 Byte (0 sectors)

Slightly changed: 0.00 Byte (0 sectors)

    Overwritten: 0.00 Byte (0 sectors)

WARNING: Not all data was read due to I/O error(s)

Average reading speed: 11.64 MB/s

 

Test stopped, read-only filesystem

[13855.152371] end_request: I/O error, dev sda, sector 6337504

[13855.156244] end_request: I/O error, dev sda, sector 6337744

[13855.159708] end_request: I/O error, dev sda, sector 6337984

[13855.165025] end_request: I/O error, dev sda, sector 6338016

 

[13856.349531] EXT4-fs (sda1): previous I/O error to superblock detected

 

 

 

And now a pretty old 512MB card, slow as hell when it's about random I/O, especially small block sizes and this is what would make you crazy if you put a Linux image on this card :)

 

 

 

tk@orangepipc:~$ armbianmonitor -c /mnt/slow-card/

 

WARNING: It seems you're not testing the SD card but instead /dev/sdb1 (vfat)

 

fallocate: fallocate failed: Operation not supported

Now starting to write to the card, please be patient, this might take a very long time

Free space: 488.10 MB

Creating file 1.h2w ... OK!

Free space: 0.00 Byte

Average writing speed: 3.11 MB/s

 

Now verifying the written data:

                  SECTORS      ok/corrupted/changed/overwritten

Validating file 1.h2w ...  999632/        0/      0/      0

 

  Data OK: 488.10 MB (999632 sectors)

Data LOST: 0.00 Byte (0 sectors)

      Corrupted: 0.00 Byte (0 sectors)

Slightly changed: 0.00 Byte (0 sectors)

    Overwritten: 0.00 Byte (0 sectors)

Average reading speed: 10.03 MB/s

 

Starting iozone tests:

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: Fri Mar 18 18:12:44 2016

 

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 /mnt/slow-card//cardtest.gXxhVa

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     1727     1724     4561     4560     4554       58                                                          

          102400     512     4590     4785    10246    10180    10240     2560                                                          

          102400   16384     4719     4946    10405    10335    10407     4839                                                          

 

iozone test complete.

 

The results from testing /dev/sdb1 (vfat):

  Data OK: 488.10 MB (999632 sectors)

Data LOST: 0.00 Byte (0 sectors)

Average writing speed: 3.11 MB/s

Average reading speed: 10.03 MB/s

                                            random    random

reclen    write  rewrite    read    reread    read     write

     4     1727     1724     4561     4560     4554       58                                                          

   512     4590     4785    10246    10180    10240     2560                                                          

 16384     4719     4946    10405    10335    10407     4839                                                          

 

Health summary: OK

 

Performance summary:

Sequential reading speed: 10.03 MB/s 

 4K random reading speed:  4554 KB/s 

Sequential writing speed: 3.11 MB/s (too low)

 4K random writing speed:    58 KB/s (too low)

 

To interpret the results above correctly or search for alternatives 

please refer to http://oss.digirati.com.br/f3/and also

http://www.jeffgeerling.com/blogs/jeff-geerling/raspberry-pi-microsd-card

http://thewirecutter.com/reviews/best-microsd-card/

 

 

Link to comment
Share on other sites

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

Important Information

Terms of Use - Privacy Policy - Guidelines