On 2017-07-12 12:23, Istvan Gabor wrote:
On Wed, 12 Jul 2017 07:21:29 +0200, Per Jessen wrote:
Istvan Gabor wrote:
In openSUSE Leap 42.2 I can't mount the same raid device:
cat /proc/mdstat
md9 : active raid1 sdc9[1] sdb9[0] 31455164 blocks super 1.0 [2/2] [UU]
# mount /dev/md9 /mnt -o ro mount: wrong fs type, bad option, bad superblock on /dev/md9, missing codepage or helper program, or other error
It probably doesn't really matter, but I've never seen the options added at the end, this is what I would do:
mount -o ro /dev/md9 /mnt
Otherwise, I would have said 'fsck'.
fsck in Leap 42.2:
# fsck -C -t ext3 /dev/md9 fsck from util-linux 2.28 e2fsck 1.42.11 (09-Jul-2014) The filesystem size (according to the superblock) is 7863809 blocks The physical size of the device is 7863791 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? no
You do that without looking first at the log to find out what the problem is? :-o A forced fsck can destroy things. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)