Raid5 will no longer mount - can't read super block

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Raid5 will no longer mount - can't read super block

      I am on OMV 3.0.99

      I tried getting into it today, and all my file shares were broke, and the file systems page says that my /dev/sda1 is online, but not mounted. I try to mount it, but it gives me the error:
      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount -v --source '/dev/sda1' 2>&1' with exit code '32': mount: /dev/sda1: can't read superblock

      I don't see any angry LEDs on my server for failed/degraded drives...
      Its on a Dell R710 Perc6i
      I actually not remember the model of the drives in the raid.. I want to say the are all WD Blues. There are 5 of them Raid5 with 7.28TB so its 4x2TB drives if I remember correctly.

      I don't think I have had a power loss on them recently other than me actually shutting it down a few weeks ago for some wire management... otherwise I havent touched the config or hardware in weeks (maybe months).


      I tried:


      mdadm --assemble /dev/sda
      mdadm: device /dev/sda exists but is not an md array.


      mount /dev/sda1
      mount: /dev/sda1: can't read superblock

      sudo mdadm --verbose --assemble --force /dev/sda1
      mdadm: device /dev/sda1 exists but is not an md array.

      root@homelands:~# mdadm --examine --verbose --scan

      root@homelands:~# cat /proc/mdstat
      Personalities :
      unused devices: <none>

      -----------------------------------

      fdisk -l

      Disk /dev/sdb: 232.4 GiB, 249510756352 bytes, 487325696 sectors
      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: 0xafecab9c

      Device Boot Start End Sectors Size Id Type
      /dev/sdb1 * 2048 467525631 467523584 223G 83 Linux
      /dev/sdb2 467527678 487323647 19795970 9.5G 5 Extended
      /dev/sdb5 467527680 487323647 19795968 9.5G 82 Linux swap / Solaris

      Disk /dev/sda: 7.3 TiB, 7999376588800 bytes, 15623782400 sectors
      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: gpt
      Disk identifier: 1198D59B-CE4D-43AC-B6A1-D23042D61B1E

      Device Start End Sectors Size Type
      /dev/sda1 2048 15623782366 15623780319 7.3T Linux filesystem

      -----------------------------------------

      mdadm --examine /dev/sda
      /dev/sda:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)
      root@homelands:~# mdadm --examine /dev/sdb
      /dev/sdb:
      MBR Magic : aa55
      Partition[0] : 467523584 sectors at 2048 (type 83)
      Partition[1] : 19795970 sectors at 467527678 (type 05)
      root@homelands:~# mdadm --examine /dev/sda
      /dev/sda:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)
      root@homelands:~# mdadm --assemble /dev/sda
      mdadm: device /dev/sda exists but is not an md array.
      root@homelands:~# mdadm --examine /dev/sda1 >> raid.status
      mdadm: No md superblock detected on /dev/sda1.
      root@homelands:~# mdadm --examine /dev/sda >> raid.status
      root@homelands:~# mdadm --examine /dev/sda1
      mdadm: No md superblock detected on /dev/sda1.
      root@homelands:~# mdadm --examine /dev/sda
      /dev/sda:
      MBR Magic : aa55
      Partition[0] : 4294967295 sectors at 1 (type ee)

      root@homelands:~# [b]mdadm --assemble /dev/sda1[/b]
      mdadm: device /dev/sda1 exists but is not an md array.


      blkid

      /dev/sdb1: UUID="829457d0-4dfb-4308-9758-64d17daea98d" TYPE="ext4" PARTUUID="afecab9c-01"

      /dev/sdb5: UUID="723ccf96-13fa-4f54-ae54-9ae0031d013a" TYPE="swap" PARTUUID="afecab9c-05"

      /dev/sda1: LABEL="Media" UUID="28bef13c-c94e-4687-a00c-483733bddf62" TYPE="ext4" PARTUUID="ef031a0d-1fdf-4cdd-82bf-e5626920926d"

      cat /etc/mdadm/mdadm.conf
      # mdadm.conf
      #
      # 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

      # 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 root

      # definitions of existing MD arrays

      # This configuration was auto-generated on Mon, 31 Jul 2017 19:38:49 +0000 by mkconf


      I would like to keep my data... it's not world ending since most of my personal junk is backup to my google drive, and some to my old NAS, but I do have a lot of media on here that would be annoying to re-download.

      Not really sure where to go from here... Any help would be appreciated!



      Edit: Added missing info

      The post was edited 2 times, last by krimson: added missing info and formatting ().

    • FIXED!

      Through googling, and some help on here and other places... I wound up fixing it using fsck. It originally would not let me use fsck since it complained that e2fsck was out of date and wouldnt support the drive, and apt-get kept saying it was current...

      I manually downloaded the e2fsprogs and e2fslibs from packages.debian.org/stretch/e2fsprogs with wget and used dpkg -i fille.deb to install the update, and it let me run a full fsck -p on the device in question, found that it was not cleanly unmounted, complained about Inode extent trees and other random crap, repaired those issues, and then it let me mount it...

      Figured I would at least share my resolution in case others find this post.