Re: Raid recovery

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

 



>From what I assume looking on the disk app sd [bcde]1 is file system,
sd [bcde]2 is swap and  sd [bcde]3 is data

root@Raid-on:~# mdadm --examine /dev/sdc3
/dev/sdc3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : ba35c20f:00e99fb7:438a7341:dd60ea4a
           Name : 7c6ee8d2:data-0
  Creation Time : Sat Mar 12 10:39:04 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5850830321 (2789.89 GiB 2995.63 GB)
     Array Size : 8776244352 (8369.68 GiB 8986.87 GB)
  Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
    Data Offset : 261504 sectors
   Super Offset : 8 sectors
   Unused Space : before=261424 sectors, after=753 sectors
          State : clean
    Device UUID : d33abbf7:3e8bbf40:c6c1f306:32c93b10

    Update Time : Thu Jul 12 12:08:02 2018
       Checksum : da270dcd - correct
         Events : 27162

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 1
   Array State : AA.. ('A' == active, '.' == missing, 'R' == replacing)
root@Raid-on:~# mdadm --examine /dev/sdb3
/dev/sdb3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : ba35c20f:00e99fb7:438a7341:dd60ea4a
           Name : 7c6ee8d2:data-0
  Creation Time : Sat Mar 12 10:39:04 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5850830321 (2789.89 GiB 2995.63 GB)
     Array Size : 8776244352 (8369.68 GiB 8986.87 GB)
  Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
    Data Offset : 261504 sectors
   Super Offset : 8 sectors
   Unused Space : before=261424 sectors, after=753 sectors
          State : clean
    Device UUID : e0bbecd9:223757af:3dfcac89:296ea8a3

    Update Time : Thu Jul 12 12:08:02 2018
       Checksum : 41161a2d - correct
         Events : 27162

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 0
   Array State : AA.. ('A' == active, '.' == missing, 'R' == replacing)
root@Raid-on:~# mdadm --examine /dev/sdd3
/dev/sdd3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : ba35c20f:00e99fb7:438a7341:dd60ea4a
           Name : 7c6ee8d2:data-0
  Creation Time : Sat Mar 12 10:39:04 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5850830321 (2789.89 GiB 2995.63 GB)
     Array Size : 8776244352 (8369.68 GiB 8986.87 GB)
  Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
    Data Offset : 261504 sectors
   Super Offset : 8 sectors
   Unused Space : before=261224 sectors, after=753 sectors
          State : clean
    Device UUID : db67bc23:9c8c1498:44d9e2c8:1a3c0efe

    Update Time : Thu Jul 12 00:29:40 2018
  Bad Block Log : 512 entries available at offset 264 sectors
       Checksum : d4a23f3 - correct
         Events : 27155

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 3
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
root@Raid-on:~# mdadm --examine /dev/sde3
/dev/sde3:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : ba35c20f:00e99fb7:438a7341:dd60ea4a
           Name : 7c6ee8d2:data-0
  Creation Time : Sat Mar 12 10:39:04 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5850830321 (2789.89 GiB 2995.63 GB)
     Array Size : 8776244352 (8369.68 GiB 8986.87 GB)
  Used Dev Size : 5850829568 (2789.89 GiB 2995.62 GB)
    Data Offset : 261504 sectors
   Super Offset : 8 sectors
   Unused Space : before=261224 sectors, after=753 sectors
          State : clean
    Device UUID : e3a165da:9422bcb7:829f1db7:a53be056

    Update Time : Thu Jul 12 00:29:40 2018
  Bad Block Log : 512 entries available at offset 264 sectors
       Checksum : 2aa7b9bb - correct
         Events : 27155

         Layout : left-symmetric
     Chunk Size : 64K

   Device Role : Active device 2
   Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)
On Thu, Sep 20, 2018 at 10:36 PM François Goudal <francois@xxxxxxxxxx> wrote:
>
> Le 20/09/2018 à 22:19, Madalin Grosu a écrit :
> > Thank you François for your answer.
> > now the drives are connected to an hp workstation - Intel® Xeon(R) CPU
> > E5430 @ 2.66GHz × 4
> > I have a dual boot on machine with win 7 ultimate and Ubuntu 18.04.1 LTS
> > I think I put my drives in the correct  order based on the logs from
> > my NAS and this is the point were I am in this moment
> >
> > [...]
>
> The order doesn't really matter. The disks have some metadata that will
> tell linux what their position within the array is. So Linux won't be
> looking at the disk order but will just look at this data in the superblock.
>
> At this point, I would guess that your md0 array is probably the NAS
> operating system. It is quite typical for NAS devices to install their
> OS on a raid1 volume that spreads on all the disks that are installed.
> My Synology NAS does this too. So, there's probably nothing interesting
> there. So the focus would have to be on the other volumes I think.
> More specifically, your data is likely to be in the md127  volume due to
> its much larger size.
>
> Can you please post the output of the following commands:
> mdadm --examine /dev/sdc3
> mdadm --examine /dev/sdb3
> mdadm --examine /dev/sdd3
> mdadm --examine /dev/sde3
>
> Also, at this point, do *not* run any command to re-assemble your raid
> volumes. First we need to properly understand what those arrays are for
> and in which precise state they are. Let's also hope your windows
> software didn't harm your data...
>




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux