Jump to content

Roman B

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Roman B

  1. Did any one try this board with SSD instead of HDD which I beleive topic starter used in his tests? SSD has less power consumption so probably it works ok with this board and usual PSU.
  2. I've tried it again with disabled unattended-update and got the same results. So it is definitely not related to the updates. Only one thing which make it works well is to change SSD drive, so my suggestion is only one: some errors appears because of unsupported SSD drive. But hot to solve it?
  3. I see the following lines in the kern.log: Mar 29 18:01:22 localhost kernel: [ 152.729764] EXT4-fs (sda1): Unrecognized mount option "compress-force=zlib" or missing value Mar 29 18:01:22 localhost kernel: [ 152.810043] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Looks like it tried to use 'compress-force=zlib' for EXT4 fs, is it ok?
  4. Hi @tkaiser, I wrote the latest version on the new SD card, then performed apt-update && apt upgrade. Then I ran nand-sata-intall. Set logs verbosity to 7 and collect logs from SSD and SD card. Please take a look at attached logs.. logs fom SSD.7z kern.log nand-sata-install.log armhwinfo.log
  5. Hello @tkaiser, thank you for provided tips. I'm still collecting this data, which you have requested and I will add it later. Also it looks like I managed to find out one of the reason of the issue: It is new version of Silicon Power SSD drive (SP60). The same issue I've got if try to use Banana Pi M1 with that SSDs, so issue appears not only with M1 + and also with usual M1(I have several such SSDs, so it is not a problem of a particular one). If I transfer system to the old version of SSD, everything works. Thanks, Roman.
  6. I've posted photo for it in my first comment on this issue. Let me duplicate it in attachment to this comment: And there are no other lines, just kernel panic after this screen. Thanks, Roman.
  7. Changing power supply didn't help. Any ideas how to figure out the root cause of that issue or how to resolve it?
  8. @tkaiser, thank you for clarification. It is because I provided screen captures for different attempts. I tried to use older version of armbian, but every time I got the same version. Now I've plugged 3A power supply and upgrade OS to the 4.14.18 version of kernel. Take a look at mon logs: http://ix.io/13Ih.
  9. @tkaiser, could you please clarify your note about kernel versions, I didn't quite catch it.
  10. Hello @tkaiser, Please see below the results of specified command: armbianmonitor -u System diagnosis information will now be uploaded to http://ix.io/13H5 Please post the URL in the forum where you've been asked for.
  11. Hi there, I have a Banana Pi M1+ and connected to it Silicon Power SSD 60 Gb. I've faced with the following error: Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00(see screenshots). Startup: https://drive.google.com/open?id=1s_1mkJWXTC02TnSyVlX8oZZQDaJpgXYu Kernel panic message: https://drive.google.com/open?id=1oDgmnrOspkYy5DY5bobFLTJSE3RJOVE6 I downloaded and wrote Armiban to the SD card from this link: https://dl.armbian.com/bananapi/Debian_stretch_next.7z, It started well. Then I performed apt update && apt upgrade -y and reboot the system. After that I've used 'nand-sata-install' to move system to SATA SSD and got that error. Previouslly I did the same steps with usual Banana Pi M1 (not plus version) and it works well, but with the M1 plus version I got that error. Thanks, Roman.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines