OM7 - Lost my RAID 5 (4 disks)

AxelC · Apr 8th 2025

Hi everyone and, please, excuse me for my poor english, I will try to do my best.

I loose my RAID5 (4 x 6 To) in OMV7. I don't know how and when, sorry.

I don't know what is wrong but I can't find the RAID5 in the GUI. Actually, before this problem, I need first to go to storage/encryption in the GUI to decrypt it (LUKS extension) and it works.

Now in Storage/encryption : nothing

The 4 disks are not old and SMART seems fine (It's a bit long but if you need I can give it).

What could be the problem and what can I do to restore it (without lost the data...if possible) ?

I did some tests if that can help you.

With mdadm --examine /dev/sd. , I see that sdc, sdd, sde have an Update Time : Wed Jan 1 09:49:18 2025 thereas sdb has an Update Time : Tue Nov 26 21:44:39 2024 ...maybe the origine of the problem...that I can't solve.

Code

root@nasbam-omv7:~# cat /proc/mdstat

Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdb[4](S) sdd[3](S) sdc[0](S) sde[2](S)      23441561952 blocks super 1.2

unused devices: <none>


root@nasbam-omv7:~# fdisk -l

Disk /dev/sdc: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWN160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sde: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWN160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdb: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWN160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sda: 111,79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SV300S3
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: 0xa6e5b40d

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1  *         2048 232441855 232439808 110,8G 83 Linux
/dev/sda2       232443902 234440703   1996802   975M  5 Extended
/dev/sda5       232443904 234440703   1996800   975M 82 Linux swap / Solaris

Disk /dev/sdd: 5,46 TiB, 6001175126016 bytes, 11721045168 sectors
Disk model: TOSHIBA HDWN160
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


root@nasbam-omv7:~# mdadm --detail /dev/md127

/dev/md127:           
Version : 1.2        
Raid Level : raid5     
Total Devices : 4       
Persistence : Superblock is persistent
State : inactive   
Working Devices : 4
Name : NAS-BAM-2021:NASBAM202106
UUID : 4d09c283:091556a4:8b8d138c:8d8a7e26
Events : 249103
Number    Major    Minor    Raid      Device
  -         8       64        -      /dev/sde
  -         8       32        -      /dev/sdc
  -         8       48        -      /dev/sdd
  -         8       16        -      /dev/sdb


root@nasbam-omv7:~# blkid

/dev/sdd: UUID="4d09c283-0915-56a4-8b8d-138c8d8a7e26" UUID_SUB="9b679a71-c0e4-4787-1d3e-83bcb4de1e6d" LABEL="NAS-BAM-2021:NASBAM202106" TYPE="linux_raid_member"
/dev/sdb: UUID="4d09c283-0915-56a4-8b8d-138c8d8a7e26" UUID_SUB="dcd35e6f-3acb-2f47-6403-26dd7142be81" LABEL="NAS-BAM-2021:NASBAM202106" TYPE="linux_raid_member"
/dev/sde: UUID="4d09c283-0915-56a4-8b8d-138c8d8a7e26" UUID_SUB="83805d56-d29e-9f5d-1c88-85620d48384a" LABEL="NAS-BAM-2021:NASBAM202106" TYPE="linux_raid_member"
/dev/sdc: UUID="4d09c283-0915-56a4-8b8d-138c8d8a7e26" UUID_SUB="b48d15b9-4cd2-f19f-8378-cca2c6880444" LABEL="NAS-BAM-2021:NASBAM202106" TYPE="linux_raid_member"
/dev/sda5: UUID="66ababab-961d-4491-9c6d-24a57e077bde" TYPE="swap" PARTUUID="a6e5b40d-05"
/dev/sda1: UUID="dddf060c-eaee-4138-822c-57c41b933ef0" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a6e5b40d-01"

root@nasbam-omv7:~# cat /etc/mdadm/mdadm.conf

# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays

# This configuration was auto-generated on Sat, 17 Feb 2024 11:39:02 +0000 by mkconf


root@nasbam-omv7:~# mdadm --detail --scan --verbose

INACTIVE-ARRAY /dev/md127 num-devices=4 metadata=1.2 name=NAS-BAM-2021:NASBAM202106 UUID=4d09c283:091556a4:8b8d138c:8d8a7e26   devices=/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde


root@nasbam-omv7:~# mdadm --examine /dev/sdb

/dev/sdb:          
Magic : a92b4efc        
Version : 1.2    
Feature Map : 0x9     
Array UUID : 4d09c283:091556a4:8b8d138c:8d8a7e26           
Name : NAS-BAM-2021:NASBAM202106  
Creation Time : Tue Jun 15 22:52:13 2021     
Raid Level : raid5   
Raid Devices : 4

Avail Dev Size : 11720780976 sectors (5.46 TiB 6.00 TB)    
Array Size : 17581171200 KiB (16.37 TiB 18.00 TB)  
Used Dev Size : 11720780800 sectors (5.46 TiB 6.00 TB)    
Data Offset : 264192 sectors   
Super Offset : 8 sectors   
Unused Space : before=264112 sectors, after=176 sectors          
State : active    
Device UUID : dcd35e6f:3acb2f47:640326dd:7142be81

Internal Bitmap : 8 sectors from superblock    
Update Time : Tue Nov 26 21:44:39 2024  
Bad Block Log : 512 entries available at offset 32 sectors - bad blocks present.       
Checksum : 18328402 - correct         
Events : 95379

Layout : left-symmetric     
Chunk Size : 512K
Device Role : Active device 1   
Array State : AAAA ('A' == active, '.' == missing, 'R' == replacing)


root@nasbam-omv7:~# mdadm --examine /dev/sdc

/dev/sdc:          
Magic : a92b4efc        
Version : 1.2    
Feature Map : 0x1     
Array UUID : 4d09c283:091556a4:8b8d138c:8d8a7e26           
Name : NAS-BAM-2021:NASBAM202106  
Creation Time : Tue Jun 15 22:52:13 2021     
Raid Level : raid5   
Raid Devices : 4

Avail Dev Size : 11720780976 sectors (5.46 TiB 6.00 TB)     
Array Size : 17581171200 KiB (16.37 TiB 18.00 TB)  
Used Dev Size : 11720780800 sectors (5.46 TiB 6.00 TB)    
Data Offset : 264192 sectors   
Super Offset : 8 sectors   
Unused Space : before=264112 sectors, after=176 sectors          
State : clean    
Device UUID : b48d15b9:4cd2f19f:8378cca2:c6880444

Internal Bitmap : 8 sectors from superblock    
Update Time : Wed Jan  1 09:49:18 2025  
Bad Block Log : 512 entries available at offset 32 sectors       
Checksum : 42cb226d - correct         
Events : 249107
         
Layout : left-symmetric     
Chunk Size : 512K
   
Device Role : Active device 0   
Array State : A..A ('A' == active, '.' == missing, 'R' == replacing)


root@nasbam-omv7:~# mdadm --examine /dev/sdd

/dev/sdd:          
Magic : a92b4efc        
Version : 1.2    
Feature Map : 0x1     
Array UUID : 4d09c283:091556a4:8b8d138c:8d8a7e26           
Name : NAS-BAM-2021:NASBAM202106  
Creation Time : Tue Jun 15 22:52:13 2021     
Raid Level : raid5   
Raid Devices : 4
 
Avail Dev Size : 11720780976 sectors (5.46 TiB 6.00 TB)     
Array Size : 17581171200 KiB (16.37 TiB 18.00 TB)  
Used Dev Size : 11720780800 sectors (5.46 TiB 6.00 TB)    
Data Offset : 264192 sectors   
Super Offset : 8 sectors   
Unused Space : before=264112 sectors, after=176 sectors          
State : clean    
Device UUID : 9b679a71:c0e44787:1d3e83bc:b4de1e6d

Internal Bitmap : 8 sectors from superblock    
Update Time : Wed Jan  1 09:49:18 2025  
Bad Block Log : 512 entries available at offset 32 sectors       
Checksum : 25772a53 - correct         
Events : 249107
         
Layout : left-symmetric     
Chunk Size : 512K
   
Device Role : Active device 3   
Array State : A..A ('A' == active, '.' == missing, 'R' == replacing)


root@nasbam-omv7:~# mdadm --examine /dev/sde

/dev/sde:          
Magic : a92b4efc        
Version : 1.2    
Feature Map : 0x1     
Array UUID : 4d09c283:091556a4:8b8d138c:8d8a7e26           
Name : NAS-BAM-2021:NASBAM202106  
Creation Time : Tue Jun 15 22:52:13 2021     
Raid Level : raid5   
Raid Devices : 4
 
Avail Dev Size : 11720780976 sectors (5.46 TiB 6.00 TB)     
Array Size : 17581171200 KiB (16.37 TiB 18.00 TB)  
Used Dev Size : 11720780800 sectors (5.46 TiB 6.00 TB)    
Data Offset : 264192 sectors   
Super Offset : 8 sectors   
Unused Space : before=264112 sectors, after=176 sectors          
State : clean    
Device UUID : 83805d56:d29e9f5d:1c888562:0d48384a

Internal Bitmap : 8 sectors from superblock    
Update Time : Wed Jan  1 09:48:47 2025  
Bad Block Log : 512 entries available at offset 32 sectors       
Checksum : 63acb084 - correct         
Events : 249103
         
Layout : left-symmetric     
Chunk Size : 512K
   
Device Role : Active device 2   
Array State : A.AA ('A' == active, '.' == missing, 'R' == replacing)


root@nasbam-omv7:~#

Display More

Thank you very much for your help and advices

Waiting for read you

votdev · Apr 9th 2025

You need to activate the RAID again. Please search the forum or the internet how to do that via CLI.

AxelC · Apr 9th 2025

HI

Thanks for your answer

Do you think something like that ?

Stop the RAID

Code

mdadm --stop /dev/md127

Rename conf file

Code

mv /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf.20250409

Rescan the disks to fine a RAID config

Code

mdadm --assemble --scan --verbose

I am very sorry but I would be sur that I don't make a mistake which could lost the data

Thank you

Participate now!