[Eisfair] Raidpartition wird nicht mehr gemountet und Eisfair config läßt sich nicht mehr editieren

[David Brandes]

Am 25.10.2019 um 12:08 schrieb Marcus Roeckrath:
> tune2fs -l /dev/sda1 | grep "Filesystem state"
> tune2fs -l /dev/sdb1 | grep "Filesystem state"
> tune2fs -l /dev/md1 | grep "Filesystem state"

Da kommmen einige Meldungen zu "Bad magic number in super-block "

Eisfair-server #
Eisfair-server # tune2fs -l /dev/sda1 | grep "Filesystem state"
Filesystem state:         clean
Eisfair-server # tune2fs -l /dev/sdb1 | grep "Filesystem state"
Filesystem state:         clean
Eisfair-server # tune2fs -l /dev/md1 | grep "Filesystem state"
Filesystem state:         clean

Eisfair-server # tune2fs -l /dev/sda2 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sda2
Eisfair-server # tune2fs -l /dev/sdb2 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sdb2
Eisfair-server # tune2fs -l /dev/md2 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/md2


Eisfair-server # tune2fs -l /dev/sda3 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sda3
Eisfair-server # tune2fs -l /dev/sdb3 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sdb3
Eisfair-server # tune2fs -l /dev/md3 | grep "Filesystem state"
Filesystem state:         clean


Eisfair-server # tune2fs -l /dev/sda4 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sda4
Eisfair-server # tune2fs -l /dev/sdb4 | grep "Filesystem state"
tune2fs: Bad magic number in super-block while trying to open /dev/sdb4
Eisfair-server # tune2fs -l /dev/md4 | grep "Filesystem state"
Filesystem state:         clean