Yunohost ne boote plus / Yunohost doesn't boot anymore

Korbak · September 5, 2020, 9:21am

/ Yunohost doesn’t boot anymore

My YunoHost server

Hardware: Internet Cube (LIME 1) with VPN
YunoHost version: not sure / should be the latest in july 2020
I have access to my server : file system on the SD card / physically to the olimex
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
If yes, please explain: It’s pretty hard to explaint it fully, but I have this server since 2015, so there is a lot of things I did modifiy during theses years in order to make things work (before Yunohost corrected it). Lastly, thanks to the diagnosis tool, I did edit a few to get back in the normal installation. I was as close as possible to its recommendations. I guess it’s good to have all of it in mind.

Description of my issue

On july 16th, my cube got down and nothing happened anymore at boot (it didn’t even appeared on the local network). The LIME 1 card looked like it oddly reacted when plugged in (the orange LED didn’t blink anymore), and the SD card looked fully functionnal, so I decided to get a new LIME 1 in order to make it easier for me and not have to make a new install on a LIME 2.
I now have the new LIME 1. It seems to react a bit differently in terms of LED blinking, but in the end, I have nothing more once the SD is in.
While, again, the SD nothing’s corrupted looking at fsck, and nothing is on readonly mode.
So I am confused : it doesn’t look corrupted.
I have been able to get a HDMI cable that I plugged on my videoprojector (I have nothing better to use next to the internet box and the cube). It writes “no signal”.
The ext4 partition of the Cube ain’t full. There are a bit more of 2.5Gb of free space.

I really don’t know where to check to get deeper, does anyone have any idea?
I can access to every logs, that all stopped the same day : july 16th. In the ones I’ve read (syslog & kern) I haven’t seen any error correlated to the situation, but I don’t know where to look and what for.

Yunohost doesn’t boot

Mon serveur YunoHost

Matériel : Brique Internet avec VPN
Version de YunoHost : pas certain, normalement la dernière quand nous étions en juillet 2020
J’ai accès à mon serveur : système de fichiers sur la carte SD / physiquement à la olimex
tes-vous dans un contexte particulier ou avez-vous effectué des modifications particulières sur votre instance ? : oui
Si oui, expliquer: C’est assez dur d’être exhaustif, mais j’ai ce serveur depuis 2015, donc il y a beaucoup de choses que j’ai modifiées durant ces années pour que tout fonctionne (avant que Yunohost ne le corrige). Dernièrement, avec l’aide de l’outil de diagnostic, j’ai pu revenir un peu vers l’installation normale. J’étais aussi proche que ça m’était possible de ses recommandations. Je pense que ça reste bien d’avoir ça à l’esprit.

Description du problème

Le 16 juillet, ma brique est tombée down et plus rien au boot (même pas d’apparition en réseau local). La carte LIME 1 avait l’air de réagir bizarrement au branchement (la LED orange ne clignotait plus), et la carte SD semblait parfaitement fonctionnelle, donc j’ai décidé d’acheter une nouvelle LIME 1 pour me simplifier les choses et ne pas avoir à refaire une installation sur une LIME 2.
J’ai désormais la nouvelle LIME 1. Elle semble réagir un peu différemment en termes de clignotement des LED, mais au final, je n’ai pas plus de résultat une fois la carte SD dedans.
Or, sur la carte SD, rien de corrompu d’après fsck, et rien n’est en lecture seule.
Donc je suis confus : elle n’a pas l’air corrompue.
J’ai pu mettre la main sur un câble HDMI que j’ai branché à mon vidéoprojecteur (je n’ai rien de plus pratique sous la main près de la box et de la brique). Il indique “aucun signal”.
La partition ext4 de la Brique n’est pas pleine, il reste un peu plus de 2.5Go.

Je ne sais pas bien où regarder pour avance, est-ce que quelqu’un a des idées ?
Je peux accéder à tous les logs, qui se sont arrêtés le même jour : le 16 juillet. Dans ceux que j’ai regardé (syslog & kern) je n’ai vu aucune erreur semblant liée à la situation, mais je ne sais ni ou ni quoi chercher.

Logs

syslog :

Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualize le_traquemort...
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualize fx...
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualize india...
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualize tzitzimitl...
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b69a3340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualize komodo...
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b6981340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b6981340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b6981340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b6981340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:04 cyphergoat FreshRSS[955]: FreshRSS actualization done for 6 users, using 4.00 MiB of memory, in 0 day(s), 0 hour(s), 0 minute(s) and 0 seconds.
Jul 16 09:00:04 cyphergoat mysqld[26317]: 2020-07-16 09:00:04 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:07 cyphergoat mysqld[26317]: 2020-07-16 09:00:07 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:08 cyphergoat mysqld[26317]: 2020-07-16 09:00:08 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:09 cyphergoat mysqld[26317]: 2020-07-16 09:00:09 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
Jul 16 09:00:10 cyphergoat mysqld[26317]: 2020-07-16 09:00:10 b695f340 InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).

kern.log :

ul 16 06:25:36 cyphergoat kernel: [75739.038834] Out of memory: Kill process 7233 (mysqld) score 171 or sacrifice child
Jul 16 06:25:36 cyphergoat kernel: [75739.046640] Killed process 7233 (mysqld) total-vm:584612kB, anon-rss:83688kB, file-rss:2616kB, shmem-rss:0kB
Jul 16 06:30:09 cyphergoat kernel: [76011.693964] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jul 16 06:30:09 cyphergoat kernel: [76011.852984] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

yunohost-api.log :

2020-07-13 15:06:17,675 DEBUG    geventwebsocket.handler run_application - Initializing WebSocket
2020-07-13 15:06:17,681 DEBUG    geventwebsocket.handler upgrade_websocket - Validating WebSocket request
2020-07-13 15:06:17,703 INFO     geventwebsocket.handler log_request - 127.0.0.1 - - [2020-07-13 15:06:17] "GET /installed HTTP/1.1" 200 159 0.021154
2020-07-15 09:23:32,502 DEBUG    moulinette.actionsmap __init__ - loading actions map namespace 'yunohost'
2020-07-15 09:23:33,392 DEBUG    moulinette.actionsmap __init__ - extra parameter classes loaded: ['required', 'pattern']
2020-07-15 09:23:33,414 DEBUG    moulinette.interface __init__ - initializing base actions map parser for api
2020-07-15 09:23:46,205 DEBUG    moulinette.interface.api run - starting the server instance in localhost:6787 with websocket=True
2020-07-15 15:06:52,437 DEBUG    geventwebsocket.handler run_application - Initializing WebSocket
2020-07-15 15:06:52,448 DEBUG    geventwebsocket.handler upgrade_websocket - Validating WebSocket request
2020-07-15 15:06:52,475 INFO     geventwebsocket.handler log_request - 127.0.0.1 - - [2020-07-15 15:06:52] "GET /installed HTTP/1.1" 200 159 0.036306

yunohost-cli.log :

https://paste.yunohost.org/uzakasufaj.sql

Aleks · September 5, 2020, 12:20pm

Wokay I deleted that because it contained a cleartext password and not sure that’s relevant

What’s confusing is :

the system stopped on july 16
you tried booting
but nothing new shows up in kern.log

Which tends to indicate it’s a hardware or boot issue (e.g. in grub or whatever is used before the kernel actually takes over the system) - oooooor maybe check if there’s a file called dmesg ? (But that should be pretty similar to kern.log)

I had a few issue in the past where my ARM board wasn’t booting just because there was some dust or whatever between the SD card and SD connector … but maybe you already checked that ?

ljf · September 6, 2020, 7:45pm

Si tu utilises une batterie vérifie que tu l’as bien branché au bon endroit (et non pas sur le power sata, sur les cartes olimex c’est le même type de connecteur donc facile de se tromper).

Korbak · September 15, 2020, 2:30pm

Sorry for the delay of my answer…

Which tends to indicate it’s a hardware or boot issue (e.g. in grub or whatever is used before the kernel actually takes over the system)

Any way to identify and, if necessary, fix this?

oooooor maybe check if there’s a file called dmesg

Yeah, it’s empty :(.

I had a few issue in the past where my ARM board wasn’t booting just because there was some dust or whatever between the SD card and SD connector … but maybe you already checked that ?

I did not, but now I did (on the SD card at least). It would be surprising to have the same dust problem on two different boards, wouldn’t it?
Do you have any tips to get everything clean btw?

Korbak · September 15, 2020, 2:30pm

Si tu utilises une batterie vérifie que tu l’as bien branché au bon endroit (et non pas sur le power sata, sur les cartes olimex c’est le même type de connecteur donc facile de se tromper).

Je n’utilise pas de batterie, la brique est directement sur secteur :(.

Aleks · September 15, 2020, 3:40pm

Imho le plus simple pour investiguer serait d’avoir un cable USB<->Serial pour voir ce que la carte raconte pendant le boot … (Si tu n’as pas de tel cable mais un arduino, y’a aussi moyen de bricoler pour le transformer en USB<->Serial)

ljf · September 17, 2020, 11:58am

Tu peux aussi essayer de vérifier ta carte: la mienne se montait sur mon laptop et j’avais l’impression de pouvoir écrire dedans (avec dd, ou même en créant un fichier). Mais en la démontant et la remontant je me suis aperçu que ce qui était écrit disparaissait (et que donc c’était juste en cache mais que c’était jamais écris physiquement…).

En regardant avec un arduino, on a pu voir que évidement ça bloquait le démarrage du système. Là aussi rien sur l’écran hdmi.

Aleks · September 17, 2020, 1:11pm

(Beh il disait que fsck ne rapporte pas d’erreur alors la carte a l’air good :s )

Korbak · September 29, 2020, 7:07pm

Bonjour, désolé pour mon silence :/.
J’attendais de mettre la main sur une carte micro-SD neuve, pour tester.

J’ai fait ceci :

sudo dd if=/dev/sdb of=/dev/mmcblk0 bs=4M status=progress
31906070528 bytes (32 GB, 30 GiB) copied, 1598 s, 20,0 MB/s
dd: erreur d'écriture dans '/dev/mmcblk0': Aucun espace disponible sur le périphérique
7610+0 enregistrements lus
7609+0 enregistrements écrits
31914983424 bytes (32 GB, 30 GiB) copied, 1598,83 s, 20,0 MB/s

Et pourtant, les deux cartes font 32Go (et celle d’origine n’est pas pleine)…

En essayant de monter la neuve sur mon PC, j’obtiens une erreur indiquant que le superblock n’existe pas. Je me souviens avoir déjà eu cette erreur sur l’originale, sans bien parvenir à comprendre si c’était de mon fait ou non (genre que j’essayais de fsck la carte au lieu de la partition), aussi dans le doute je me demande si ce n’est pas la clé du problème.

sudo fsck -a /dev/sdb
fsck de util-linux 2.31.1
fsck.ext2: Numéro magique invalide dans le super-bloc lors de la tentative d'ouverture de /dev/sdb
/dev/sdb: 
Le superbloc n'a pu être lu ou ne contient pas un système de fichiers ext2/ext3/ext4 correct. Si le périphérique est valide et qu'il contient réellement
un système de fichiers ext2/ext3/ext4 (et non pas de type swap, ufs ou autre),
alors le superbloc est corrompu, et vous pourriez tenter d'exécuter
e2fsck avec un autre superbloc :
e2fsck -b 8193 <périphérique>
ou
e2fsck -b 32768 <périphérique>
Trouvé une table de partitions dos dans /dev/sdb

Je vous laisse ces logs au cas où, je retente ce soir de faire mon dd en spécifiant les partitions… Je vous informerai du résultat, s’il y a un résultat perceptible.

EDIT : même situation quand je fais un dd de /dev/sdb1 vers /dev/mmcblk0p1… Mon PC me dit :

Error mounting /dev/mmcblk0p1 at /media/korbak/a4aed306-8cea-43af-b9f7-a9eaee0d6bea1: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error.

Et donc sur la carte microSD qui était dans ma brique, j’obtiens ceci :

sudo fsck -a /dev/sdb
fsck de util-linux 2.31.1
fsck.ext2: Aucun support trouvé lors de la tentative d'ouverture de /dev/sdb
/dev/sdb: 
Le superbloc n'a pu être lu ou ne contient pas un système de fichiers
ext2/ext3/ext4 correct. Si le périphérique est valide et qu'il contient réellement
un système de fichiers ext2/ext3/ext4 (et non pas de type swap, ufs ou autre),
alors le superbloc est corrompu, et vous pourriez tenter d'exécuter
e2fsck avec un autre superbloc :
    e2fsck -b 8193 <périphérique>
 ou
    e2fsck -b 32768 <périphérique>

Et :

sudo fsck -a /dev/sdb1
fsck de util-linux 2.31.1
/dev/sdb1 est monté.
e2fsck: Ne peut continuer, arrêt immédiat.

Alors je ne comprends pas bien, car j’avais bien eu à l’origine un résultat différent m’indiquant que fsck ne trouve pas d’erreur.

Aleks · September 29, 2020, 9:21pm

Et si tu refais cette commande avec /dev/sdb1 démonté ?

Sinon ça ressemble furieusement au même soucis qu’a eu @ljf … Le problème semblait avoir “contaminé” la carte SD neuve (Bad superbloc sur la nouvelle carte etc) … Pas sur de comprendre pourquoi ce soucis surviens chez deux personnes soudainement

Mais bref, normalement t’as encore accès en lecture sur la carte existante, et déjà la première étape serait de faire une copie complète du système de fichier (genre un dd if=/dev/sdb of=mon_backup.img … ou un truc dans le style) au cas où. À part ça en reflashant une carte SD à l’aide du backup ça devrait le faire (soit une copie brute avec dd, soit avec un cp des fichiers) … C’est juste pas très clair pourquoi y’a des soucis de bad superblock sur des SD neuves…

system · October 14, 2020, 9:21pm

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.