I'll save everyone time as I just accidentally ran a script that deleted the superblocks, so it is just lost now.
All right. It happens. Life goes on. š
Yesterday I updated to 7.7.2-1 (Sandworm) and the update went like a breeze. At the end, it asked me to reboot and that's when the nightmare started.
Machine would not boot.
I usually give it a couple of minutes, but since no SSH, no UI, I plugged in a monitor and noticed it was haging trying to mount my RAID (/dev/md0) , which I (used to) mount via /etc/fstab with:
I logged in security mode, commented out that one line, system booted, UI showed, but when I tried to manually mount with
I got an error:
mount: /mnt/data: wrong fs type, bad option, bad superblock on /dev/md8, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
Started investigating and tried pretty much everything, but no luck.
Here's the outputs I get:
cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md8 : active raid0 sdc1[2] sdf1[4] sde1[5] sda1[0] sdj1[9] sdh1[6] sdi1[8] sdd1[3] sdg1[7] sdb1[1]
58603888640 blocks super 1.2 4096k chunks
unused devices: <none>
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 Wed, 19 Jun 2024 16:39:11 -0300 by mkconf
Display More
mdadm --detail --scan --verbose
ARRAY /dev/md/8 level=raid0 num-devices=10 metadata=1.2 name=raspberrypi:8 UUID=d6627611:b98a99d1:6f63daac:c9edecde
devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1,/dev/sde1,/dev/sdf1,/dev/sdg1,/dev/sdh1,/dev/sdi1,/dev/sdj1
mdadm --assemble --scan -v
mdadm: looking for devices for further assembly
mdadm: No super block found on /dev/sdj (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdj
mdadm: No super block found on /dev/sdi (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdi
mdadm: No super block found on /dev/sdh (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdh
mdadm: No super block found on /dev/sdg (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdg
mdadm: No super block found on /dev/sde (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sde
mdadm: No super block found on /dev/sdf (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdf
mdadm: No super block found on /dev/sdd (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdd
mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdc
mdadm: No super block found on /dev/sdb (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sdb
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/sdj1 is identified as a member of /dev/md/8, slot 9.
mdadm: /dev/sdi1 is identified as a member of /dev/md/8, slot 8.
mdadm: /dev/sdh1 is identified as a member of /dev/md/8, slot 7.
mdadm: /dev/sdg1 is identified as a member of /dev/md/8, slot 6.
mdadm: /dev/sde1 is identified as a member of /dev/md/8, slot 4.
mdadm: /dev/sdf1 is identified as a member of /dev/md/8, slot 5.
mdadm: /dev/sdd1 is identified as a member of /dev/md/8, slot 3.
mdadm: /dev/sdc1 is identified as a member of /dev/md/8, slot 2.
mdadm: /dev/sdb1 is identified as a member of /dev/md/8, slot 1.
mdadm: /dev/sda1 is identified as a member of /dev/md/8, slot 0.
mdadm: added /dev/sdb1 to /dev/md/8 as 1
mdadm: added /dev/sdc1 to /dev/md/8 as 2
mdadm: added /dev/sdd1 to /dev/md/8 as 3
mdadm: added /dev/sde1 to /dev/md/8 as 4
mdadm: added /dev/sdf1 to /dev/md/8 as 5
mdadm: added /dev/sdg1 to /dev/md/8 as 6
mdadm: added /dev/sdh1 to /dev/md/8 as 7
mdadm: added /dev/sdi1 to /dev/md/8 as 8
mdadm: added /dev/sdj1 to /dev/md/8 as 9
mdadm: added /dev/sda1 to /dev/md/8 as 0
mdadm: /dev/md/8 has been started with 10 drives.
mdadm: looking for devices for further assembly
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/md/8
mdadm: /dev/sdj1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdj
mdadm: /dev/sdi1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdi
mdadm: /dev/sdh1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdh
mdadm: /dev/sdg1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdg
mdadm: /dev/sde1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sde
mdadm: /dev/sdf1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdf
mdadm: /dev/sdd1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdd
mdadm: /dev/sdc1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdc
mdadm: /dev/sdb1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: /dev/sda1 is busy - skipping
mdadm: Cannot assemble mbr metadata on /dev/sda
Display More
And if I try to force rebuild the RAID:
mdadm -C /dev/md0 -l raid0 -n 10 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1
mdadm: cannot open /dev/sda1: Device or resource busy
Can someone please PLEASE help?
I do have most files in a backup disk, but there are things that were still not syncd that are quite important ![]()