Mdadm raid 1 lost

Support
,
#1

NethServer Version: 6.8
Module: mdadm raid

I’ve noticed that the md1 raid did not appear on the nethserver administration page so i’ve checked on terminal and there is no md1 raid in mdadm.
The md1 raid is the raid on ext3 boot partition.
I think this happen after the last reboot… about 10 days ago.

How can i rebuild the md1 raid [boot partition sda1 - sdb1] without erasing any data ?
Now the server boot up using /dev/sda1 as boot.

#2

@support_team Can anyone help here?

#3

Can you post a screenshot of your “Disk status” dashboard and the output of fdisk -l command?

1 Like
#4

i have the mdadm output:

[root@server ~]# mdadm -E /dev/sd[a-b]1
/dev/sda1:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : be5faf0f:c57fb30e:04b11650:f99aaef5
           Name : server.example.org:1
  Creation Time : Sun Nov 23 19:15:20 2014
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1048552 (511.99 MiB 536.86 MB)
     Array Size : 524224 (511.94 MiB 536.81 MB)
  Used Dev Size : 1048448 (511.94 MiB 536.81 MB)
   Super Offset : 1048560 sectors
   Unused Space : before=0 sectors, after=112 sectors
          State : clean
    Device UUID : 421a5796:f7628266:cb7bfad7:66d84d2a

    Update Time : Mon May 13 08:03:37 2019
       Checksum : aa298164 - correct
         Events : 700


   Device Role : Active device 0
   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdb1:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : be5faf0f:c57fb30e:04b11650:f99aaef5
           Name : server.example.org:1
  Creation Time : Sun Nov 23 19:15:20 2014
     Raid Level : raid1
   Raid Devices : 2

 Avail Dev Size : 1048552 (511.99 MiB 536.86 MB)
     Array Size : 524224 (511.94 MiB 536.81 MB)
  Used Dev Size : 1048448 (511.94 MiB 536.81 MB)
   Super Offset : 1048560 sectors
   Unused Space : before=0 sectors, after=112 sectors
          State : clean
    Device UUID : d49e180f:e77de1ab:1007f14c:5ed7b837

    Update Time : Mon May 13 08:03:37 2019
       Checksum : eaabab23 - correct
         Events : 700


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

but /dev/md1 doesn’t exist

I will report fdisk -l, but will take one day because the server isn’t connected to internet and i cannot manage it remotely.

#5

I’ll wait for your output when server will be online.

#6

It’s an offline server. It’s not connected to internet.
I have to make an appointment and go to the factory where the server is located.
Thanks for your patience.

#7

Here the fdisk -l output

# fdisk -l

Disco /dev/sda: 1000.2 GB, 1000204886016 byte

255 testine, 63 settori/tracce, 121601 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x0001a7f3

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          66      524288   fd  Autorilevamento raid di Linux
La partizione 1 non termina al limite del cilindro.
/dev/sda2              66      121602   976236544   fd  Autorilevamento raid di Linux

Disco /dev/sdb: 1000.2 GB, 1000204886016 byte

255 testine, 63 settori/tracce, 121601 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x0004c524

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          66      524288   fd  Autorilevamento raid di Linux
La partizione 1 non termina al limite del cilindro.
/dev/sdb2              66      121602   976236544   fd  Autorilevamento raid di Linux

Disco /dev/sdc: 4000.8 GB, 4000787030016 byte

255 testine, 63 settori/tracce, 486401 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x3862bdde

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      267349  2147480811   fd  Autorilevamento raid di Linux
Partition 1 does not start on physical sector boundary.

Disco /dev/sdd: 4000.8 GB, 4000787030016 byte

255 testine, 63 settori/tracce, 486401 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0xc2a786fa

Dispositivo Boot      Start         End      Blocks   Id  System
/dev/sdd1               1      267349  2147480811   fd  Autorilevamento raid di Linux
Partition 1 does not start on physical sector boundary.

Disco /dev/md2: 999.5 GB, 999531806720 byte

2 testine, 4 settori/tracce, 244026320 cilindri
Unità = cilindri di 8 * 512 = 4096 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x00000000


Disco /dev/mapper/VolGroup-lv_swap: 4026 MB, 4026531840 byte
255 testine, 63 settori/tracce, 489 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x00000000


Disco /dev/mapper/VolGroup-lv_root: 995.5 GB, 995492888576 byte

255 testine, 63 settori/tracce, 121028 cilindri
Unità = cilindri di 16065 * 512 = 8225280 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Identificativo disco: 0x00000000


Disco /dev/md3: 2198.9 GB, 2198886088704 byte

2 testine, 4 settori/tracce, 536837424 cilindri
Unità = cilindri di 8 * 512 = 4096 byte
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Alignment offset: 512 bytes
Identificativo disco: 0x00000000
RAID1 broken following Power Outage
#8

Any idea ?

#9

You can use mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 (you have to modify disk with your correct disk) and use it to create raid device. But I don’t know if it works fine on Nethserver…

#10

Hi

I’ve had to use mdadm to rebuild a raid1 on Nethserver before (a friends home server).
That box has 3 raids. It’s old, replacement is in situ, but not quite ready yet.
About a year ago, had to replace the disk in a raid due to a power outage and disk failure.
All worked!

Random notes:

mdadm --create --verbose /dev/md1 --level=1 --raid-devices=2 /dev/sdd1 /dev/sde1

mdadm --assemble --verbose /dev/md1 /dev/sdd1 /dev/sde1

MANAGE MODE
Usage: mdadm device options… devices…

This usage will allow individual devices in an array to be failed, removed or added. It is possible to perform multiple operations with on command. For example:

     mdadm /dev/md0 -f /dev/hda1 -r /dev/hda1 -a /dev/hda1

will firstly mark /dev/hda1 as faulty in /dev/md0 and will then remove it from the array and finally add it back in as a spare. However only one md array can be affected by a single command.

Use with caution!
Backup or Image the system if possible.

My 2 cents
Andy