problem in remount a mdam raid 6 btrfs

spupuz · Sep 30th 2023

i have a raid 6 raid of 10 disk 2TB each, the raid has sent out 2 disk and i had to reassemble now the status of the raid is fine but the file system is missing the UUID has changed and can't see it on the /dev/disk/by-label nor under /dev/disk/by-UUID

Code

 mdadm --assemble --force --verbose /dev/md127 /dev/sda /dev/sdb /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj /dev/sdk /dev/sd

and

Code

root@omvbe ~ [127]# lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda       8:0    0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdb       8:16   0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdc       8:32   0 149,1G  0 disk
└─sdc1    8:33   0   149G  0 part  /srv/dev-disk-by-uuid-2a45e5d1-f5e4-4387-9061-0a3e108e1cd1
sdd       8:48   0 447,1G  0 disk
├─sdd1    8:49   0 438,8G  0 part  /
├─sdd2    8:50   0     1K  0 part
└─sdd5    8:53   0   8,3G  0 part  [SWAP]
sde       8:64   0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdf       8:80   0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdg       8:96   0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdh       8:112  0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdi       8:128  0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdj       8:144  0   2,7T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdk       8:160  0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6
sdl       8:176  0   1,8T  0 disk
└─md127   9:127  0  14,6T  0 raid6

Display More

or

Code

oot@omvbe ~# blkid
/dev/sda: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="3e12255e-44e1-73e4-dc72-6ce42379ac0c" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdb: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="4e50dc69-db48-0a7a-e74b-19c443ac9126" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdc1: UUID="2a45e5d1-f5e4-4387-9061-0a3e108e1cd1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d01faf1e-a0b3-470a-8336-5d95c8dfbecd"
/dev/sdd1: UUID="4e8bcb7c-149c-4512-af77-7598d5453603" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="38cdc5c0-01"
/dev/sdd5: UUID="87e7014b-a734-4563-9b6c-01a9da1f58c3" TYPE="swap" PARTUUID="38cdc5c0-05"
/dev/sde: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="753d0a80-1d9d-9af4-0e1c-8c94813268f7" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdf: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="52fe1f62-d22a-559d-6f1d-5b26d7736c49" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdg: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="5f7e673d-92a0-4b98-0f75-00a2dd703797" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdh: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="67ccb917-46a9-2727-41ed-20b3c5cddee1" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdi: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="0ee3e622-3562-7c18-c516-d580dfea964b" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdj: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="38ca92d9-3a4c-ffc9-c6fb-7d394d840134" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdk: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="79e0d218-08f4-873e-2be1-3df7a3ca2c11" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"
/dev/sdl: UUID="aa45aa96-4310-3022-2129-bbe0f12ef3c0" UUID_SUB="ad919e5d-e7c2-c882-6000-5744b153f129" LABEL="omvbe:RAID6FS" TYPE="linux_raid_member"

Display More

also

Code

root@omvbe ~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.


# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#


# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions


# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR xxxxxxxx@gmail.com
MAILFROM root


# definitions of existing MD arrays
# old ARRAY /dev/md127 metadata=1.2 name=openmediavault:RAID6 UUID=b5a64cdb:8f834b22:84276d5c:81f60dca
ARRAY /dev/md127 metadata=1.2 name=omvbe:RAID6FS UUID=aa45aa96:43103022:2129bbe0:f12ef3c0

Display More

and

Code

root@omvbe ~# mdadm --detail --verbose /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Fri Sep 29 15:26:54 2023
Raid Level : raid6
Array Size : 15627059200 (14903.13 GiB 16002.11 GB)
Used Dev Size : 1953382400 (1862.89 GiB 2000.26 GB)
Raid Devices : 10
Total Devices : 10
Persistence : Superblock is persistent


Intent Bitmap : Internal


Update Time : Sat Sep 30 22:56:27 2023
State : clean
Active Devices : 10
Working Devices : 10
Failed Devices : 0
Spare Devices : 0


Layout : left-symmetric
Chunk Size : 512K


Consistency Policy : bitmap


Name : omvbe:RAID6FS  (local to host omvbe)
UUID : aa45aa96:43103022:2129bbe0:f12ef3c0
Events : 15534


Number   Major   Minor   RaidDevice State
0       8        0        0      active sync   /dev/sda
1       8       16        1      active sync   /dev/sdb
2       8       64        2      active sync   /dev/sde
3       8       80        3      active sync   /dev/sdf
4       8       96        4      active sync   /dev/sdg
5       8      112        5      active sync   /dev/sdh
6       8      128        6      active sync   /dev/sdi
7       8      144        7      active sync   /dev/sdj
8       8      160        8      active sync   /dev/sdk
9       8      176        9      active sync   /dev/sdl

Display More

but no file system:

spupuz · Sep 30th 2023

and again

Code

root@omvbe ~# btrfs filesystem show /dev/md127
ERROR: no btrfs on /dev/md127

spupuz · Sep 30th 2023

i have lost all data?

spupuz · Oct 1st 2023

ryecoaaron any hint?

BlueCoffee · Oct 1st 2023

Quote from spupuz

What happens if you remove the missing drive and re-add it?

spupuz · Oct 1st 2023

Quote from BlueCoffee

What happens if you remove the missing drive and re-add it?

Nothing, I had to recreate the entire raid since I disk was missing and I had to reboot and the raid after reboot was missing too

spupuz · Oct 1st 2023

But data should be still there but os can't see fs seems

BlueCoffee · Oct 1st 2023

Quote from spupuz

Nothing, I had to recreate the entire raid since I disk was missing and I had to reboot and the raid after reboot was missing too

I mean from the GUI so delete all shares etc.. remove the mounted drive than re-add pain but this has worked for me before tho I didn't use btrfs.

spupuz · Oct 1st 2023

I'll try

Meguinness · Nov 16th 2023

did a solution was found?

spupuz · Nov 16th 2023

Quote from Meguinness

did a solution was found?

Yes restorednfrom backup and created a raid with zfs

problem in remount a mdam raid 6 btrfs

Participate now!

Tags