Kernel problems with Seafile server

[ameisentier]

Hello guys,

I have a problem with my seafile server.
I installed and configured my seafile server according following tutorials by @saljut7:

Tutorial for Seafile CE + Nginx + dynamic DNS (on ARM / Cubietruck / RaspberryPi)

This tutorial is licensed under CC-BY-SA - feel free to share and modify it (but keep all information free)! This tutorial is not longer maintained. Anyway it can be helpful to get an idea how to set up a current version of Seafile server CE. The official tutorial steps I used for this tutorial were: https://manual.seafile.com/deploy/using_mysql.html https://manual.seafile.com/deploy/add_memcached.html https://manual.seafile.com/deploy/depl…

Tutorial for a complete certificate chain with your own Certificate Authority (CA)

This tutorial is licensed under CC-BY-SA - feel free to share and modify it (but keep information free)! This tutorial was originally written for the first Seafile forum of Seafile GmbH. Since the announcement to fork Seafile by Seafile GmbH I’ve decided to move my tutorials to the new Seafile forum of the original developers of Seafile (so this one). This tutorial version is the maintained one. Tutorial for a complete certificate chain with your own Certificate Au…

I installed the server on my Raspberry Pi 2 B V1.1 on a Toshiba microSDHC card 32gb, 30MB/s.
Everything worked fine for a few weeks. Then I had no connection to my server anymore.

When I put the server on my TV with HDMI the booting process stopped suddenly.
In the picture I attached you can see the las entry of the booting process.
Here it stopped booting. I do not changed anything on the server or in the network.

Maybe someone is knowing this issue and can help me. Thank you for your help.

Greetings,
Ameisentier

[arjones85]

Unknown block sounds like a hardware issue to me.

Install clean on another SD card and restore your repo and database from the backups you maintain.

[ameisentier]

Thank you for your fast help.
A new installation on a different sd card was on my list too.
If no one had an other idea I will do this next week.

[saljut7]

@ameisentier

Thank you for your fast help.
A new installation on a different sd card was on my list too.
If no one had an other idea I will do this next week.

According to Unable to mount root fs on unknown-block (179,2) · Issue #167 · raspberrypi/noobs · GitHub you could try:

If you’re getting the error using standalone Raspbian, then perhaps your
root partition has become corrupt somehow. You could try inserting your
SD card into a desktop / laptop Linux PC, and running e2fsck against
the faulty root partition?

[shoeper]

By the way entering dmesg via SSH should print the same messages being displayed on the photo. You can then just copy the text.

[ameisentier]

I got following information after e2fsck:

ameisentier@netbook:/dev$ sudo e2fsck /dev/sdb
e2fsck 1.42.12 (29-Aug-2014)
e2fsck: Kein Medium gefunden beim Versuch, /dev/sdb zu öffnen

Der Superblock ist unlesbar bzw. beschreibt kein gültiges ext2/ext3/ext4-
Dateisystem. Wenn das Gerät gültig ist und ein ext2/ext3/ext4-
Dateisystem (kein swap oder ufs usw.) enthält, dann ist der Superblock
beschädigt, und Sie könnten versuchen, e2fsck mit einem anderen Superblock
zu starten:
e2fsck -b 8193 <Gerät>
oder
e2fsck -b 32768 <Gerät>

I also cannot make an image out of the sd card. Linux the process after a few seconds.

ameisentier@netbook:/dev$ sudo pv /dev/sdb | dd of=/home/ameisentier/image
dd: Fehler beim Lesen von „Standardeingabe“: Eingabe-/Ausgabefehler% ETA 1:06:19
138760+0 Datensätze ein
138760+0 Datensätze aus
71045120 Bytes (71 MB) kopiert, 9,98748 s, 7,1 MB/s
pv: /dev/sdb: read-Aufruf fehlgeschlagen: Eingabe-/Ausgabefehler
67,8MiB 0:00:09 [ 6,8MiB/s] [> ] 0%

I thougt I buy a new sd card with more resistance and for server use.

Thank you all for your help. Maybe someone get another idea?

[Smith_John]

See, I also faced that problem in my device. And I had seen upper instructions which are good for all,