[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unable to read data from RAID partition



houghi a écrit :
> 
> root@penne : cat /proc/mdstat
> Personalities : [raid1]
> md124 : active raid1 sdc3[0]
>       1455183616 blocks super 1.0 [1/1] [U]
>             
> unused devices: <none>
> 
> 
> The raid1 device is /dev/md124
> 
> root@penne : mdadm --detail /dev/md124
> /dev/md124:
>         Version : 1.0
>   Creation Time : Sat Oct 10 01:30:57 2015
>      Raid Level : raid1
>      Array Size : 1455183616 (1387.77 GiB 1490.11 GB)
>   Used Dev Size : 1455183616 (1387.77 GiB 1490.11 GB)
>    Raid Devices : 1
>   Total Devices : 1
>     Persistence : Superblock is persistent
> 
>     Update Time : Sun Oct 25 13:10:43 2015
>           State : clean
>  Active Devices : 1
> Working Devices : 1
>  Failed Devices : 0
>   Spare Devices : 0
> 
>            Name : 4
>            UUID : d358edc1:b9272da7:e071f2f0:0462cd1f
>          Events : 10
> 
>     Number   Major   Minor   RaidDevice State
>        0       8       35        0      active sync   /dev/sdc3
> 
> 
> When I try to mount :
> root@penne : mount /dev/sdc1 /mnt/1/
> mount: unknown filesystem type 'linux_raid_member'

Never try to mount directly a partition which is a member of a RAID
array unless you know exactly what you are doing.

> root@penne : mount /dev/md124 /mnt/3
> mount: unknown filesystem type 'drbd'

The keyword seems to be "drbd". IIUC the RAID array does not contain a
filesystem but is used by DRBD (distributed replicated block device),
which  I know nothing about. Like layers such as RAID or LVM, I guess
you have to "activate" the block device(s) with whatever admin command
is designed for the task (drbdadm, drbdsetup, drdbmeta ?). Then, if it
contains a filesystem, you can mount it.


Reply to: