Dear people on the mailing list,
Disclaimer: this is my first time reaching out to a mailing list and if
I broke any rules on doing so please let me know. I read the guides as
best as I could but I'm just a human.
I need help with the recovery of a RAID5, that lost the superblock after
a reboot. I have read the articles about "RAID_Recovery" and "Recovering
a failed software RAID" on the kernel wiki and follow the advice given
there, to write you before attempting a recreation of the array.
I have to confess, the second article is multiple km out of my comfort
zone and understanding how this works. As it is labeld with "This page
is obsolete" I did not put multiple hours into the research of
"parallel". Please correct me if this was/is a mistake.
I'm not 100% sure but I did save a copy of the commands from the time I
created the raid. Am I correct, that recreating the array is my last hope?
Kind regards,
Dave
### Logs ###
--- sudo mdadm --examine /dev/sd[a-c] | egrep 'Event|/dev/sd' ---
/dev/sda:
/dev/sdb:
/dev/sdc:
--- sudo dmesg ---
[ 3.540074] scsi 2:0:0:0: Direct-Access ATA WDC WD8003FFBX-6
0A83 PQ: 0 ANSI: 5
[ 3.540427] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 3.540540] sd 2:0:0:0: [sda] 15628053168 512-byte logical blocks:
(8.00 TB/7.28 TiB)
[ 3.540544] sd 2:0:0:0: [sda] 4096-byte physical blocks
[ 3.540563] sd 2:0:0:0: [sda] Write Protect is off
[ 3.540567] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.540602] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 3.540606] scsi 3:0:0:0: Direct-Access ATA WDC WD8003FFBX-6
0A83 PQ: 0 ANSI: 5
[ 3.540640] sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
[ 3.540994] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 3.541038] sd 3:0:0:0: [sdb] 15628053168 512-byte logical blocks:
(8.00 TB/7.28 TiB)
[ 3.541042] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[ 3.541078] sd 3:0:0:0: [sdb] Write Protect is off
[ 3.541084] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 3.541109] sd 3:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 3.541132] sd 3:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[ 3.543813] ata10.00: configured for UDMA/133
[ 3.549042] scsi 5:0:0:0: CD-ROM HL-DT-ST DVD+-RW GH50N
B103 PQ: 0 ANSI: 5
[ 3.581434] sdb:
[ 3.581481] sd 3:0:0:0: [sdb] Attached SCSI removable disk
[ 3.586773] sda:
[ 3.586813] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 3.589970] sr 5:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram
cd/rw xa/form2 cdda tray
[ 3.589973] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 3.608265] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 3.608464] sr 5:0:0:0: Attached scsi generic sg2 type 5
[ 3.608664] scsi 9:0:0:0: Direct-Access ATA WDC WD8003FFBX-6
0A83 PQ: 0 ANSI: 5
[ 3.609032] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 3.609096] sd 9:0:0:0: [sdc] 15628053168 512-byte logical blocks:
(8.00 TB/7.28 TiB)
[ 3.609102] sd 9:0:0:0: [sdc] 4096-byte physical blocks
[ 3.609114] sd 9:0:0:0: [sdc] Write Protect is off
[ 3.609118] sd 9:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 3.609135] sd 9:0:0:0: [sdc] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 3.609158] sd 9:0:0:0: [sdc] Preferred minimum I/O size 4096 bytes
[ 3.656107] sdc:
[ 3.656172] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[...]
[ 319.784903] systemd-fstab-generator[3678]: Failed to create unit file
'/run/systemd/generator/mnt-raid.mount', as it already exists. Duplicate
entry in '/etc/fstab'?
[ 320.493627] sda:
[ 320.523036] sda:
[ 320.553208] sdb:
[ 320.582539] sdb:
[ 320.611367] sdc:
[ 320.645390] sdc:
[ 380.427225] systemd-fstab-generator[4106]: Failed to create unit file
'/run/systemd/generator/mnt-raid.mount', as it already exists. Duplicate
entry in '/etc/fstab'?
[ 397.527095] systemd-fstab-generator[4317]: Failed to create unit file
'/run/systemd/generator/mnt-raid.mount', as it already exists. Duplicate
entry in '/etc/fstab'?
[ 398.090051] sda:
[ 398.125241] sda:
[ 398.154056] sdb:
[ 398.183259] sdb:
[ 398.208969] sdc:
[ 398.242772] sdc:
--- fstab ---
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/12ab46a1-9aa5-4592-950a-3453232d4be8 / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/727D-6DE0 /boot/efi vfat defaults 0 1
/swap.img none swap sw 0 0
/dev/md0 /mnt/raid ext4 defaults 0 0
/dev/md0 /mnt/raid ext4 defaults 0 0
--- sudo mdadm --assemble --force /dev/md0 /dev/sd[a-c] ---
mdadm: looking for devices for /dev/md0
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: /dev/sda has no superblock - assembly aborted
--- sudo mdadm --examine /dev/sd[a-c] ---
/dev/sda:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
/dev/sdb:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
/dev/sdc:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
--- Reports from: smartctl -d ata -a ---
for:
/dev/sda
/dev/sdb
/dev/sdc
show now logged errors.
--- mdadm --version ---
mdadm - v4.3 - 2024-02-15 - Ubuntu 4.3-1ubuntu2
--- sudo journalctl ---
kernel: EXT4-fs error (device md0): ext4_validate_block_bitmap:423: comm
ext4lazyinit: bg 106111: bad block bitmap checksum
--- sudo mdadm --detail /dev/md0 ---
mdadm: Array associated with md device /dev/md0 does not exist.
--- sudo nano /etc/mdadm.conf ---
ARRAY /dev/md0 metadata=1.2 spares=1
UUID=e8926355:c08133be:4a187ab2:9524a7cc
