Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #159774 > unrolled thread

Unable to read data from RAID partition

Started byhoughi <houghi@houghi.org>
First post2015-10-25 19:30 +0100
Last post2015-10-25 20:10 +0100
Articles 4 — 3 participants

Back to article view | Back to linux.debian.user

Contents

  Unable to read data from RAID partition houghi <houghi@houghi.org> - 2015-10-25 19:30 +0100
    Re: Unable to read data from RAID partition Reco <recoverym4n@gmail.com> - 2015-10-25 20:00 +0100
      Re: Unable to read data from RAID partition houghi <houghi@houghi.org> - 2015-10-25 22:10 +0100
    Re: Unable to read data from RAID partition Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-10-25 20:10 +0100

#159774 — Unable to read data from RAID partition

Fromhoughi <houghi@houghi.org>
Date2015-10-25 19:30 +0100
SubjectUnable to read data from RAID partition
Message-ID<qnydk-6ms-5@gated-at.bofh.it>
If I have not given enough information or if another place is better to
ask, please let me know.

I have a QNAP NAS and I have replaced one drive because I thought I would
just plug in the HD in my machine, boot it and mount the device.

I have done so in the past, but now it does not seem to work anymore.
This due to the fact that drives are now standard in RAID and not just
ext3 or ext4 anymore. I removed the drive, because the other drive that
contained the same data failed. So I had the data twice on two separate
drives and now I have none. Just adding it to the QNAP does not work
either.

I would like to be able to mount /dev/sdc3 and retrieve the data.
I run Debian GNU/Linux 8 (jessie)

Here is some of the output:
root@penne : fdisk -l /dev/sdc

Disk /dev/sdc: 1.4 TiB, 1500301910016 bytes, 2930277168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7968AD58-41D8-48EA-A55B-AE1EF3689B68

Device          Start        End    Sectors   Size Type
/dev/sdc1          40    1060289    1060250 517.7M Microsoft basic data
/dev/sdc2     1060296    2120579    1060284 517.7M Microsoft basic data
/dev/sdc3     2120584 2912488109 2910367526   1.4T Microsoft basic data
/dev/sdc4  2912488112 2913548399    1060288 517.7M Microsoft basic data
/dev/sdc5  2913548408 2930255999   16707592     8G Microsoft basic data

The data is on /dev/sdc3

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'
root@penne : mount /dev/md124 /mnt/3
mount: unknown filesystem type 'drbd'

I have removed and added it with
root@penne : mdadm --manage /dev/md124 --stop
mdadm: stopped /dev/md124
root@penne : mdadm --assemble /dev/md124 /dev/sdc3
mdadm: /dev/md124 has been started with 1 drive.

All to no avail.

I have searched the past week and am not able to figure out how to mount
the partition. Any help would be appreciated.

houghi

[toc] | [next] | [standalone]

#159775

FromReco <recoverym4n@gmail.com>
Date2015-10-25 20:00 +0100
Message-ID<qnyGm-6x5-5@gated-at.bofh.it>
In reply to#159774
	Hi.

On Sun, 25 Oct 2015 19:16:30 +0100
houghi <houghi@houghi.org> wrote:

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

This seems to be the key to the problem. It seems that they don't use
simple RAID1 based on mdadm in QNAP NAS. They use DRBD (Distributed
Replicated Block Device) atop of it.

To mount this disk you'd need to add DRBD on your Debian host.
Installing drbd-utils (and configuring it properly) should be
sufficient.

Reco

[toc] | [prev] | [next] | [standalone]

#159780

Fromhoughi <houghi@houghi.org>
Date2015-10-25 22:10 +0100
Message-ID<qnAI9-7Yc-3@gated-at.bofh.it>
In reply to#159775
On Sun, Oct 25, 2015 at 09:56:29PM +0300, Reco wrote:
> 	Hi.
> 
> On Sun, 25 Oct 2015 19:16:30 +0100
> houghi <houghi@houghi.org> wrote:
> 
> > root@penne : mount /dev/md124 /mnt/3
> > mount: unknown filesystem type 'drbd'
> 
> This seems to be the key to the problem. It seems that they don't use
> simple RAID1 based on mdadm in QNAP NAS. They use DRBD (Distributed
> Replicated Block Device) atop of it.
> 
> To mount this disk you'd need to add DRBD on your Debian host.
> Installing drbd-utils (and configuring it properly) should be
> sufficient

OK, have those installed. No I need to figure out how that works.

ct 25 21:44:34 penne drbdadm[27832]: no resources defined!
Oct 25 21:44:34 penne systemd[1]: drbd.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Oct 25 21:44:34 penne systemd[1]: Failed to start Distributed Replicated Block Device.
-- Subject: Unit drbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit drbd.service has failed.
-- 
-- The result is failed.
Oct 25 21:44:34 penne systemd[1]: Unit drbd.service entered failed state.

So just running the service was not it. :-/ There will be a LOT to read for me
https://drbd.linbit.com/users-guide/drbd-users-guide.html

Thanks for pointing me in the right direction with drbd-utils

houghi

[toc] | [prev] | [next] | [standalone]

#159777

FromPascal Hambourg <pascal@plouf.fr.eu.org>
Date2015-10-25 20:10 +0100
Message-ID<qnyQ2-6PP-27@gated-at.bofh.it>
In reply to#159774
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.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web