I recently corrupted my linux distro. I then reinstalled Ubuntu 16.04.3 and after setting it up, I have been unable to mount my Raid 5 setup after extensive troubleshooting.
Note even after the original system was corrupted I still had access (the windows explorer still worked) and I know I was still able to access the Raid.
When I try to mount the drive I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/isw_cidjefdfai_Volume0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.
I then did what it instructed:
dmesg | tail
... Lots of other output, then:
[63460.380362] EXT4-fs (dm-0): bad geometry: block count 2783759360 exceeds size of device (1173146784 blocks)
After searching solutions to the bad geometry problem I came across articles saying to run fsck. Here is the output from fsck:
$ sudo fsck /dev/mapper/isw_cidjefdfai_Volume0 fsck from util-linux 2.27.1 e2fsck 1.42.13 (17-May-2015) Error reading block 1391493120 (Invalid argument). Ignore error<y>? yes Force rewrite<y>? no Superblock has an invalid journal (inode 8). Clear<y>? no fsck.ext4: Illegal inode number while checking ext3 journal for DriveName DriveName: ********** WARNING: Filesystem still has errors **********
Most articles I come across have similar problems after resizing, however I did not resize the drive.
Additional info that may be helpful, This raid setup was created with Intel PCH RSTe on a SuperMicro board, which I found is typically referred to as fakeRaid. However when I boot the machine, Intel RSTe finds the raid volume (as well as the 4 drives that make it up) and says the status is "Normal" as well as all 4 drives as members of the Raid volume (picture attached). I then found that these are usually managed on linux with
dmraid so I then ran the following:
$ sudo dmraid -s *** Group superset isw_cidjefdfai --> Active Subset name : isw_cidjefdfai_Volume0 size : 9385174272 stride : 128 type : raid5_la status : ok subsets: 0 devs : 4 spares : 0 $ sudo dmraid -r /dev/sdc: isw, "isw_cidjefdfai", GROUP, ok, 7814037166 sectors, data@ 0 /dev/sde: isw, "isw_cidjefdfai", GROUP, ok, 7814037166 sectors, data@ 0 /dev/sdd: isw, "isw_cidjefdfai", GROUP, ok, 7814037166 sectors, data@ 0 /dev/sdf: isw, "isw_cidjefdfai", GROUP, ok, 7814037166 sectors, data@ 0
I am going to try and use dd to copy all the information from the drives before attempting something like a rebuild. But I find it odd that both dmraid and Intel think the drive is perfectly fine, but I cannot mount it.