Revive RAID 0 Array From Buffalo Duo NAS

UNIX for Advanced & Expert Users
1

Thank you in advanced,

I had a Buffalo DUO crap out on me that was setup as RAID 0. I dont belive it was the drives but rather the controller in the DUO unit. I bought another external HDD enclosure and was able to fireup the two older DUO drives in it and I think I resembled the RAID successfully:

sudo mdadm --examine /dev/sdd6
/dev/sdd6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 8577ffd0:8892c451:2dd41f56:0e001d01
           Name : UNINSPECT-EME0C:2
  Creation Time : Sat Jan 18 08:17:34 2014
     Raid Level : raid0
   Raid Devices : 2

 Avail Dev Size : 1923497952 (917.20 GiB 984.83 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
   Unused Space : before=1968 sectors, after=0 sectors
          State : clean
    Device UUID : 874c45ae:5b772a48:396f6e41:79f42c62

    Update Time : Sat Jan 18 08:17:34 2014
       Checksum : eeaa9c97 - correct
         Events : 0

     Chunk Size : 512K

   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
daman$ sudo mdadm --examine /dev/sde6
/dev/sde6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 8577ffd0:8892c451:2dd41f56:0e001d01
           Name : UNINSPECT-EME0C:2
  Creation Time : Sat Jan 18 08:17:34 2014
     Raid Level : raid0
   Raid Devices : 2

 Avail Dev Size : 1923497952 (917.20 GiB 984.83 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
   Unused Space : before=1968 sectors, after=0 sectors
          State : clean
    Device UUID : bcde0889:4934f6b6:e1af9882:9b7ad11e

    Update Time : Sat Jan 18 08:17:34 2014
       Checksum : 3608b286 - correct
         Events : 0

     Chunk Size : 512K

   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
daman$ sudo mdadm --create /dev/md123 --assume-clean --level=0 --verbose --chunk=64 --raid-devices=2 --metadata=0.90 /dev/sdd6 /dev/sde6
mdadm: /dev/sdd6 appears to be part of a raid array:
       level=raid0 devices=2 ctime=Sat Jan 18 08:17:34 2014
mdadm: /dev/sde6 appears to be part of a raid array:
       level=raid0 devices=2 ctime=Sat Jan 18 08:17:34 2014
Continue creating array? y
mdadm: array /dev/md123 started.

Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 5BD4E39E-AC17-4070-9569-94B2D6F52367

Device        Start        End    Sectors   Size Type
/dev/sdd1      2048    2002943    2000896   977M Microsoft basic data
/dev/sdd2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sdd3  12003328   12005375       2048     1M Microsoft basic data
/dev/sdd4  12005376   12007423       2048     1M Microsoft basic data
/dev/sdd5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sdd6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/sde: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 82EA65C5-432A-4966-8110-EBF425364748

Device        Start        End    Sectors   Size Type
/dev/sde1      2048    2002943    2000896   977M Microsoft basic data
/dev/sde2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sde3  12003328   12005375       2048     1M Microsoft basic data
/dev/sde4  12005376   12007423       2048     1M Microsoft basic data
/dev/sde5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sde6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/md123: 1.8 TiB, 1969663770624 bytes, 3846999552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes

But when I try and mount the array using:

$ sudo mount /dev/md123 /mnt/caca/
NTFS signature is missing.
Failed to mount '/dev/md123': Invalid argument
The device '/dev/md123' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

sudo mount -t ntfs /dev/md123 /mnt/caca/
NTFS signature is missing.
Failed to mount '/dev/md123': Invalid argument
The device '/dev/md123' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a

cat /proc/mdstat
Personalities : [raid0] 
md123 : active raid0 sde6[1] sdd6[0]
      1923499776 blocks 64k chunks
      
md124 : inactive sdc5[0](S) sdb5[1](S)
      2000872 blocks super 1.2
       
md125 : inactive sdc6[0](S) sdb6[1](S)
      1923497952 blocks super 1.2
       
md126 : inactive sdc2[0](S) sdb2[1](S)
      9998336 blocks super 1.2
       
md127 : inactive sdc1[0](S) sdb1[1](S)
      2000768 blocks
       
unused devices: <none>

It simply wont mount. What am I doing wrong?

------ Post updated at 10:41 PM ------

[27866.641697]  sdd: sdd1 sdd2 sdd3 sdd4 sdd5 sdd6
[27866.641998]  sde: sde1 sde2 sde3 sde4 sde5 sde6
[27866.642985] sd 4:0:0:1: [sde] Attached SCSI disk
[27866.643433] sd 4:0:0:0: [sdd] Attached SCSI disk
[28455.514768] md: array md125 already has disks!
[28479.074982] md: array md125 already has disks!
[30110.845958] md123: detected capacity change from 0 to 1969663770624
[30190.553774] XFS (md123): Invalid superblock magic number
[30430.769434] EXT4-fs (md123): VFS: Can't find ext4 filesystem

------ Post updated at 10:41 PM ------

[27866.641697]  sdd: sdd1 sdd2 sdd3 sdd4 sdd5 sdd6
[27866.641998]  sde: sde1 sde2 sde3 sde4 sde5 sde6
[27866.642985] sd 4:0:0:1: [sde] Attached SCSI disk
[27866.643433] sd 4:0:0:0: [sdd] Attached SCSI disk
[28455.514768] md: array md125 already has disks!
[28479.074982] md: array md125 already has disks!
[30110.845958] md123: detected capacity change from 0 to 1969663770624
[30190.553774] XFS (md123): Invalid superblock magic number
[30430.769434] EXT4-fs (md123): VFS: Can't find ext4 filesystem
2

Can you show output of lsblk -f ?

Regards
Peasant.

3

What operating system are you trying to mount this on? I notice that the system complains that a NTFS signature is missing, but you don't specify that it's a Windows filesystem on your 'mount' command line. Most Linux/Unix OS's don't look for a Windows filesystem unless you tell it to.

4

Gentleman,

thanks for the response: ** Moderator - sorry about the php tags **

lsblk -f

NAME      FSTYPE            LABEL              UUID                                 MOUNTPOINT
sda                                                                                 
sda1    ext4                                 1eb8913a-d1e9-4b33-8780-0652bdbfe1fb /
sda2                                                                              
sda5    swap                                 7460f125-5abb-47f0-947d-d07453d094ca [SWAP]
sda6    ext4                                 02a8d909-6a3d-49e9-9879-37b24c6f10f2 /home
sdd                                                                                 
sdd1    linux_raid_member                    156bff7d-9ec1-1723-eddf-b9e77f24a349 
sdd2    linux_raid_member UNINSPECT-EME0C:1  3d6e5a18-8af9-0d86-cd86-4b8a18142b59 
sdd3                                                                              
sdd4                                                                              
sdd5    linux_raid_member UNINSPECT-EME0C:10 af16b765-c95a-10de-a3f3-c8f0eb93b21a 
sdd6    linux_raid_member                    fa3576f5-0b51-66a9-c247-9c29a02d54af 
  md123                                                                           
sde                                                                                 
sde1    linux_raid_member                    156bff7d-9ec1-1723-eddf-b9e77f24a349 
sde2    linux_raid_member UNINSPECT-EME0C:1  3d6e5a18-8af9-0d86-cd86-4b8a18142b59 
sde3                                                                              
sde4                                                                              
sde5    linux_raid_member UNINSPECT-EME0C:10 af16b765-c95a-10de-a3f3-c8f0eb93b21a 
sde6    linux_raid_member                    fa3576f5-0b51-66a9-c247-9c29a02d54af 
  md123 

sudo fdisk -l
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 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: dos
Disk identifier: 0x87266eff

Device     Boot    Start       End   Sectors  Size Id Type
/dev/sda1  *        2048  58593279  58591232   28G 83 Linux
/dev/sda2       58595326 234440703 175845378 83.9G  5 Extended
/dev/sda5       58595328  66605055   8009728  3.8G 82 Linux swap / Solaris
/dev/sda6       66607104 234440703 167833600   80G 83 Linux


Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 5BD4E39E-AC17-4070-9569-94B2D6F52367

Device        Start        End    Sectors   Size Type
/dev/sdd1      2048    2002943    2000896   977M Microsoft basic data
/dev/sdd2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sdd3  12003328   12005375       2048     1M Microsoft basic data
/dev/sdd4  12005376   12007423       2048     1M Microsoft basic data
/dev/sdd5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sdd6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/sde: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 82EA65C5-432A-4966-8110-EBF425364748

Device        Start        End    Sectors   Size Type
/dev/sde1      2048    2002943    2000896   977M Microsoft basic data
/dev/sde2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sde3  12003328   12005375       2048     1M Microsoft basic data
/dev/sde4  12005376   12007423       2048     1M Microsoft basic data
/dev/sde5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sde6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/md123: 1.8 TiB, 1969663770624 bytes, 3846999552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 131072 bytes

sudo file -s /dev/md123
/dev/md123: data

sudo mdadm --detail /dev/md123
/dev/md123:
           Version : 0.90
     Creation Time : Sat Nov 24 21:28:30 2018
        Raid Level : raid0
        Array Size : 1923499776 (1834.39 GiB 1969.66 GB)
      Raid Devices : 2
     Total Devices : 2
   Preferred Minor : 123
       Persistence : Superblock is persistent

       Update Time : Sat Nov 24 21:28:30 2018
             State : clean 
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

        Chunk Size : 64K

Consistency Policy : none

              UUID : fa3576f5:0b5166a9:c2479c29:a02d54af (local to host Hijo-De-Dios)
            Events : 0.1

    Number   Major   Minor   RaidDevice State
       0       8       54        0      active sync   /dev/sdd6
       1       8       70        1      active sync   /dev/sde6

Additionally, I tried to mount the stuff using:

sudo mount -t ntfs /dev/md123 /mnt/caca/
NTFS signature is missing.
Failed to mount '/dev/md123': Invalid argument
The device '/dev/md123' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

sudo mount -t ntfs-3g /dev/md123 /mnt/caca/
NTFS signature is missing.
Failed to mount '/dev/md123': Invalid argument
The device '/dev/md123' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

The OS that I am using to mount this on is Kali 2018 linux which is essentially Debian,

5

Hmmmm.......if it was Debian then I'd be typing.............

$ sudo mount -t ntfs-3g /dev/md123 /mnt/caca

to mount a NTFS filesystem.

6

Sorry about the typo. I did do that. I changed it to what it was caca. So:

sudo mount -t ntfs-3g /dev/md123 /mnt/caca
7

I'm not familiar with Buffalo NAS specifically but there are two different architectures of RAID controller.

One stores the array configuration information on the disks, including type of array (Raid 0,1,3,5,6 or whatever) and the disk member number of that array. When this type of controller fails you can replace it with a new one which, at boot, will read the disk labels and run with the previous RAID array(s).

The second, and most common type, stores the array configuration in its own NVRAM and if the controller fails you have to find a way of resetting the correct configuration into NVRAM. Often this is by using some new disks to configure the same array and then swapping the disks back to the originals. The manufacturer would usually be referred to for advice.

It seems to me like the NTFS filesystem is not as it was so your recovery technique was flawed. Perhaps the disks are in the wrong order or something like that. Kali doesn't like what it's seeing. It might be quicker to initialise the array and restore from backup.

8

I changed machines to a raspberry pi. Could it be that when I assembled the array, I did it as raid 0 when it needed to be raid 1? The reason I ask this is because I see this from lsblk as in:

sudo lsblk 
NAME        MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda           8:0    0 931.5G  0 disk  
sda1        8:1    0   977M  0 part  
 md126     9:126  0   977M  0 raid1 
sda2        8:2    0   4.8G  0 part  
 md125     9:125  0   4.8G  0 raid1 
sda3        8:3    0     1M  0 part  
sda4        8:4    0     1M  0 part  
sda5        8:5    0   977M  0 part  
 md124     9:124  0   977M  0 raid1 
sda6        8:6    0 917.2G  0 part  
  md127     9:127  0   1.8T  0 raid0 
sdb           8:16   0 931.5G  0 disk  
sdb1        8:17   0   977M  0 part  
 md126     9:126  0   977M  0 raid1 
sdb2        8:18   0   4.8G  0 part  
 md125     9:125  0   4.8G  0 raid1 
sdb3        8:19   0     1M  0 part  
sdb4        8:20   0     1M  0 part  
sdb5        8:21   0   977M  0 part  
 md124     9:124  0   977M  0 raid1 
sdb6        8:22   0 917.2G  0 part  
  md127     9:127  0   1.8T  0 raid0 
mmcblk0     179:0    0   1.9G  0 disk  
mmcblk0p1 179:1    0  43.2M  0 part  /boot
mmcblk0p2 179:2    0   1.8G  0 part  /

? Should i have been:

sudo mdadm --create /dev/md127 --assume-clean --level=1 --verbose --chunk=64 --raid-devices=2 --metadata=0.90 /dev/sda6 /dev/sdb6

If I resamble it as a raid 1, will it destroy the data?

9

Those do rather look like a RAID1 (identical data partitioning).

It depends whether initialising an array also creates an empty array on Buffalo.

As I said, if you have a couple of spare drives exactly the same I'd be inclined to configure the array with them, and then swap to the originals.

Have you got a Buffalo dealer/distributor that you can talk to. This is the kind of question that they get asked all the time, i.e. recovery.

10

Hi,

Hicksd8 is partially right, from what I see there are three raid 1 one partitions (md124, md125 and md126) there is also a raid 0 stripe (md127 comprising sda6 and sdb6) are you sure these disks are being addressed in the right order?

Regards

Gull04

11

@gull04........I've never come across a RAID controller that can RAID0 a couple of partitions on different disks and, at the same time, mirror (RAID1) other partitions on the same disks. I assume that the RAID0 we're seeing here is as a result of the previous attempt at recreating a RAID0 array.

12

Hi,

Yes I have the drift here now, I suspect that you should have specified --level=1 in the mdadm command. I am pretty sure that destroying and recreating the mirror will leave the data intact - but I'd dd the disk to an image "clonezilla" or something similar if you have the tin.

@Hicksd8, at the bottom end yes it's not that common for hardware RAID to support only at device level. When it comes to software, whole different ball game - take a look at LVM, VxFS, SVM or in this case mdadm. You can slice and dice any way that you want.

Regards

Gull04

13 
mdadm --create /dev/md127 --assume-clean --level=1 --verbose --chunk=64 --raid-devices=2 --metadata=1.2 /dev/sda6 /dev/sdb6

NAME          SIZE FSTYPE            TYPE  MOUNTPOINT
sda         931.5G                   disk  
sda1        977M linux_raid_member part  
 md127     977M ext3              raid1 
sda2        4.8G linux_raid_member part  
 md1       4.8G ext3              raid1 
sda3          1M                   part  
sda4          1M                   part  
sda5        977M linux_raid_member part  
 md10      977M swap              raid1 
sda6      917.2G linux_raid_member part  
  md126   917.1G                   raid1 
sdb         931.5G                   disk  
sdb1        977M linux_raid_member part  
 md127     977M ext3              raid1 
sdb2        4.8G linux_raid_member part  
 md1       4.8G ext3              raid1 
sdb3          1M                   part  
sdb4          1M                   part  
sdb5        977M linux_raid_member part  
 md10      977M swap              raid1 
sdb6      917.2G linux_raid_member part  
  md126   917.1G                   raid1 
mmcblk0       1.9G                   disk  
mmcblk0p1  43.2M vfat              part  /boot
mmcblk0p2   1.8G ext4              part  /

sudo cat /proc/mdstat
Personalities : [raid1] 
md126 : active (auto-read-only) raid1 sda6[0] sdb6[1]
      961618880 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk

md1 : active (auto-read-only) raid1 sdb2[1] sda2[0]
      4999156 blocks super 1.2 [2/2] [UU]
      
md10 : active (auto-read-only) raid1 sdb5[1] sda5[0]
      1000436 blocks super 1.2 [2/2] [UU]
      
md127 : active (auto-read-only) raid1 sdb1[1] sda1[0]
      1000384 blocks [2/2] [UU]
      
unused devices: <none>

daman@alpha:~ $ sudo mount /dev/md126 /media/caca/
mount: wrong fs type, bad option, bad superblock on /dev/md126,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
daman@alpha:~ $ sudo mount -t ext4 /dev/md126 /media/caca/
mount: wrong fs type, bad option, bad superblock on /dev/md126,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
daman@alpha:~ $ sudo mount -t ext3 /dev/md126 /media/caca/
mount: wrong fs type, bad option, bad superblock on /dev/md126,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
daman@alpha:~ $ sudo mount -t ntfs /dev/md126 /media/caca/
mount: wrong fs type, bad option, bad superblock on /dev/md126,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

daman@alpha:~ $ sudo gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5BD4E39E-AC17-4070-9569-94B2D6F52367
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 16018829 sectors (7.6 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2002943   977.0 MiB   0700  primary
   2         2002944        12003327   4.8 GiB     0700  primary
   3        12003328        12005375   1024.0 KiB  0700  primary
   4        12005376        12007423   1024.0 KiB  0700  primary
   5        12007424        14008319   977.0 MiB   0700  primary
   6        14008320      1937508319   917.2 GiB   0700  primary
daman@alpha:~ $ sudo gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 82EA65C5-432A-4966-8110-EBF425364748
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 16018829 sectors (7.6 GiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2002943   977.0 MiB   0700  primary
   2         2002944        12003327   4.8 GiB     0700  primary
   3        12003328        12005375   1024.0 KiB  0700  primary
   4        12005376        12007423   1024.0 KiB  0700  primary
   5        12007424        14008319   977.0 MiB   0700  primary
   6        14008320      1937508319   917.2 GiB   0700  primary

udo mdadm --examine /dev/sd[ab]6
/dev/sda6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 482ed47b:00163f12:651d5389:7a570e47
           Name : alpha:127  (local to host alpha)
  Creation Time : Wed Nov 28 12:19:01 2018
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1923237856 (917.07 GiB 984.70 GB)
     Array Size : 961618880 (917.07 GiB 984.70 GB)
  Used Dev Size : 1923237760 (917.07 GiB 984.70 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=96 sectors
          State : clean
    Device UUID : fca88779:0cb1197c:fbc3353a:d1ad1b83

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 28 12:19:01 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : f2831a9d - correct
         Events : 1


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb6:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 482ed47b:00163f12:651d5389:7a570e47
           Name : alpha:127  (local to host alpha)
  Creation Time : Wed Nov 28 12:19:01 2018
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1923237856 (917.07 GiB 984.70 GB)
     Array Size : 961618880 (917.07 GiB 984.70 GB)
  Used Dev Size : 1923237760 (917.07 GiB 984.70 GB)
    Data Offset : 262144 sectors
   Super Offset : 8 sectors
   Unused Space : before=262056 sectors, after=96 sectors
          State : clean
    Device UUID : f2c5ca18:584daa0d:ced70de7:ccd6bcc7

Internal Bitmap : 8 sectors from superblock
    Update Time : Wed Nov 28 12:19:01 2018
  Bad Block Log : 512 entries available at offset 72 sectors
       Checksum : 14d010af - correct
         Events : 1


   Device Role : Active device 1
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 5BD4E39E-AC17-4070-9569-94B2D6F52367

Device        Start        End    Sectors   Size Type
/dev/sda1      2048    2002943    2000896   977M Microsoft basic data
/dev/sda2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sda3  12003328   12005375       2048     1M Microsoft basic data
/dev/sda4  12005376   12007423       2048     1M Microsoft basic data
/dev/sda5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sda6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 82EA65C5-432A-4966-8110-EBF425364748

Device        Start        End    Sectors   Size Type
/dev/sdb1      2048    2002943    2000896   977M Microsoft basic data
/dev/sdb2   2002944   12003327   10000384   4.8G Microsoft basic data
/dev/sdb3  12003328   12005375       2048     1M Microsoft basic data
/dev/sdb4  12005376   12007423       2048     1M Microsoft basic data
/dev/sdb5  12007424   14008319    2000896   977M Microsoft basic data
/dev/sdb6  14008320 1937508319 1923500000 917.2G Microsoft basic data


Disk /dev/md127: 977 MiB, 1024393216 bytes, 2000768 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


Disk /dev/md10: 977 MiB, 1024446464 bytes, 2000872 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


Disk /dev/md1: 4.8 GiB, 5119135744 bytes, 9998312 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


Disk /dev/md126: 917.1 GiB, 984697733120 bytes, 1923237760 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

I can mount md1, md10, md127 fine which tells me the data is in tacked but its something with md126 (/dev/sda6,/dev/sdb6) that has something special with it that I cannot mount.

[code]