I have a raid 5 array constructed of three partitions, one of which is another array. This array should be assembled during boot so that it can be mounted and other services can access the mounted data.
Gcool wrote:Try the following:# e2fsck -cc /dev/md127 (this is going to take a long time, so do it when you have the possibility to keep the box running for 2 days straight or so)
# resize2fs /dev/md127
# fsck -f /dev/md127What most likely happened here is something getting messed up during the array creation, which has now led to some data being written to where the RAID superblock is stored.
I've been using two HDDs equally partitioned so that there is a RAID0 Array for the root filesystem and another RAID0 array for the swap. I have future plans to switch over to my SSD I just got, so I popped it in the same box (without physically altering the cabling for the RAID array) and began to install Ubuntu to the SSD.
I just finished setting up a RAID5 array with 3 new 1.5TB hard drives using mdadm. I spent the last 5 days trying to get the RAID array working. Everything is up and running now except I have not been able to share folders on this drive using Samba. I can share files in my home directory and on my NTFS drive, but not the RAID array. I am trying to access the shares from a Windows Vista PC.
A friend's machine running Windows XP refused to boot recently which is running 3 SATA disks on RAID 5 (which was previously upgraded from RAID 1 not by me). I have determined there to be a disk failure. The disks have been replaced many times in the past few years. I wish to backup the RAID5 partition before I try anything to fix it.
Currently I have a raid card running two drives in an RAID 1+0 stripe. I want to know can I remove the raid card and have the computer operate on one drive. Without having to reload Windows. I suspect some boot files are held on the raid card.