File system based on RAID missed after update

Hi there!

I have OMV7 based NAS that I use on my fishing vessel for office documents storage and media server.

System Information
Hostname
media-server

Version
7.7.0-1 (Sandworm)

Processor
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz

Kernel
Linux 6.12.9+bpo-amd64

System time
Fri 21 Feb 2025 06:59:23 PM CAT

Uptime
42 minutes

Inside there are:

- 120Gb Kingston SSD as system drive

- 500GB WD for office purposes

- 2 x 6Tb Seagate drives in RAID 0 for media purposes.

Today I got updated and after rebot got the message on terminal:

dev/disk/by-uuid/6093c634-.....263: Can't lookup blockdev

in storage/disks have:

Device Model Serial Number Vendor Capacity

/dev/sda ST6000VN006-2ZM186 WPV04T78 ATA 5.46 TiB

/dev/sdb KINGSTON SA400S37120G 50026B7678009966 ATA 111.79 GiB

/dev/sdc WDC WD5000AAKX-08ERMA0 WD-WCC2EAA47498 ATA 465.76 GiB

/dev/sdd ST6000VN006-2ZM186 WPV02PC0 ATA 5.46 TiB

but earlier sda and sdd vere indicated as md array

in storage/ file systems have:

Device Type Available Used Mounted Referenced Status

EXT4 - - + Missing

/dev/sdb2 EXT4 99.29 GiB 3.21 GiB + + Online

/dev/sdc1 EXT4 448.91 GiB 8.45 GiB + + Online

Please advice what can I do for RAID restore and save information.

root@Media-Server:~# cat /proc/mdstat

Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]

md0 : inactive sda[0] sdd[1]

11720780976 blocks super 1.2

unused devices: <none>

So, md0 is visible but inactive. How to make it active?

root@Media-Server:~# mdadm --misc --detail /dev/md0

/dev/md0:

Version : 1.2

Creation Time : Sat May 13 09:00:48 2023

Raid Level : linear

Raid Devices : 2

Total Devices : 2

Persistence : Superblock is persistent

Update Time : Sat May 13 09:00:48 2023

State : active, FAILED, Not Started

Active Devices : 2

Working Devices : 2

Failed Devices : 0

Spare Devices : 0

Rounding : 0K

Consistency Policy : unknown

Name : FileBin:0

UUID : df4696b6:3fc58dda:1a01b95d:1313be52

Events : 0

Number Major Minor RaidDevice State

- 0 0 0 removed

- 0 0 1 removed

- 8 0 0 sync /dev/sda

- 8 48 1 sync /dev/sdd

Quote from Krisbee

I hope you have back ups as RAID0 has no redundancy.

If you array is still inactive, you may get it active with: mdadm --run  /dev/md0

Check If that works with:  cat /proc/mdstat

If array is now active but read only, use: mdadm --readwrite /dev/md0 

Thank you for advice.

root@Media-Server:~# mdadm --run /dev/md0

mdadm: failed to start array /dev/md/0: Invalid argument

and in

mdadm --misc --detail /dev/md0

shows

State : active, FAILED, Not Started

And more I just can find out. Before update my raid devices were sda and sdd. Now I can see they are sdb and sdd

mdadm --stop /dev/md0

mdadm -- assemble /dev/md0 /dev/sdb /dev/sdd

finises with error:

mdadm: failed to RUN_ARRAY /dev/md0: Invalid argument

Quote from Krisbee

There is a problem with the backport kernel Linux 6.12.9+bpo-amd64 that was part of the update.

Your RAID array should then be recognised again.

Thank you my friend!!! Problem is sorted. My RAID is back.