[clug-talk] can't mount software raid array
Mark Carlson
carlsonmark at gmail.com
Sat Jul 25 10:02:55 PDT 2009
On Sat, Jul 25, 2009 at 11:01 AM, Mark Carlson<carlsonmark at gmail.com> wrote:
> On Sat, Jul 25, 2009 at 12:59 AM, Chris q<quilley at gmail.com> wrote:
>> So, I had a power supply and motherboard fail and now I can't get my raid
>> array to mount. Array is up, jfs_fsck says filesystem is clean and yet the
>> darn thing still won't mount. Any help would be greatly appreciated
>>
>>
>> Here is some data:
>>
>> root at serverv2:/home/chris# cat /proc/mdstat
>> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
>> [raid10]
>> md0 : active raid5 sdb1[2] sdd1[0] sdf1[5] sdc1[3] sda1[1] sde1[4]
>> 7325679680 blocks level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
>>
>> unused devices: <none>
>>
>>
>> Fstab entry:
>> /dev/md0 /mnt/md0 jfs relatime 0 2
>>
>>
>>
>> What happens when I try to mount:
>> root at serverv2:/home/chris# mount /mnt/md0
>> mount: wrong fs type, bad option, bad superblock on /dev/md0,
>> missing codepage or helper program, or other error
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so
>>
>>
>>
>>
>> root at serverv2:/home/chris# jfs_fsck -n /dev/md0
> ...
>
> Does your mount command automagically determine the FS type? Or do you
> have to pass in a -t parameter for non-ext file systems?
>
> You ran the jfs specific fsck, so why not the jfs specific mount?
>
> Try:
>
> mount -t jfs /mnt/md0
>
> Instead of:
>
> mount /mnt/md0
>
> -Mark C.
>
Aiyiyi, forget what I just wrote... I just realized fstab specified jfs...
I will not post before my morning coffee...
I will not post before my morning coffee...
I will not post before my morning coffee...
I will not post before my morning coffee...
-Mark C.
More information about the clug-talk
mailing list