missing or failed raid 5 newbie help!!!!

Mr Norman Slack · 10. Januar 2016

Hi

I hope someone will be able to help,I have been using OMV for some time and the version I am running is 0.4.27. I like the software but I am not really that good with Linux. I created the raid 5 from the web interface but the other day I reboot the server and now I cannot get my raid 5 volume mounted.

it has many family photos on it. as you can imagine my girlfriend is not going to be best pleased.

on boot I get the following errors.

Code

Sun Jan 10 21:49:47 2016: Checking file systems...fsck from util-linux-ng 2.17.2
Sun Jan 10 21:49:47 2016: fsck.ext4: Unable to resolve 'UUID=f59bf2a0-fb7a-4608-b85a-04839301f5df'
Sun Jan 10 21:49:47 2016: fsck.ext4: Unable to resolve 'UUID=f2981c4d-112c-4a7e-abbf-599d07c67ff0'
Sun Jan 10 21:49:47 2016: fsck died with exit status 8
Sun Jan 10 21:49:47 2016: ^[[31mfailed (code 8).^[[39;49m
Sun Jan 10 21:49:47 2016: File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... ^[[$
Sun Jan 10 21:49:47 2016: A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... ^[[33m(warning).^[[39;49m

looking in the checkfs file I see the following message

Code

Log of fsck -C -R -A -a
Sun Jan 10 21:49:47 2016


fsck from util-linux-ng 2.17.2
fsck.ext4: Unable to resolve 'UUID=f59bf2a0-fb7a-4608-b85a-04839301f5df'
fsck.ext4: Unable to resolve 'UUID=f2981c4d-112c-4a7e-abbf-599d07c67ff0'
fsck died with exit status 8


Sun Jan 10 21:49:47 2016

Alles anzeigen

as requested in the forum sticky here is the additional information:

Code

root@NAS:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : inactive sdb[0](S) sdd[2](S) sdc[1](S)
      8790796680 blocks super 1.2

Code

root@NAS:~# blkid
/dev/sda1: UUID="71fe6ae0-148c-4c54-aae2-9ab402ffa090" TYPE="ext4"
/dev/sda5: UUID="2c75db50-d35d-4492-b481-3de7192787a2" TYPE="swap"
/dev/sdb: UUID="4bcc9c01-7a61-1370-5c86-bb24be3d53da" LABEL="NAS:Vol0" TYPE="linux_raid_member"
/dev/sdc: UUID="4bcc9c01-7a61-1370-5c86-bb24be3d53da" LABEL="NAS:Vol0" TYPE="linux_raid_member"
/dev/sdd: UUID="4bcc9c01-7a61-1370-5c86-bb24be3d53da" LABEL="NAS:Vol0" TYPE="linux_raid_member"

Code

fdisk -l 


WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1      266306  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002037f


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       29166   234275863+  83  Linux
/dev/sda2           29167       30401     9920137+   5  Extended
/dev/sda5           29167       30401     9920106   82  Linux swap / Solaris


Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdc doesn't contain a valid partition table


Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000


Disk /dev/sdd doesn't contain a valid partition table

Alles anzeigen

I have done some looking on-line but don't really know what to look.

I have even run testdisk created a image.dd of one disk and then run photorec but most of the data was incomplete.

if someone could point me in the direction on how to resolve this that would be great

Thanks

Norman Slack (so slack I didn't backup the data)

mofarocker33 · 11. Januar 2016

Did you create the /etc/mdadm/mdadm.conf?

Manually with working raid you can run this "mdadm --detail --scan >> /mnt/root/etc/mdadm/mdadm.conf" or in omv "omv-mkconf mdadm"

Mr Norman Slack · 12. Januar 2016

the file is their and it does have information in it

Code

root@NAS:~# cat /etc/mdadm/mdadm.conf
# 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>


# definitions of existing MD arrays
ARRAY /dev/md/Vol0 metadata=1.2 UUID=4bcc9c01:7a611370:5c86bb24:be3d53da name=NAS:Vol0

Alles anzeigen

the problem I have is that the raid has failed and I cannot now mount my volume it could be that the disks have failed

thanks

missing or failed raid 5 newbie help!!!!

Jetzt mitmachen!

Tags