File System N/A, status missing

Dear all,

my problem is as follows (see attachment 1-3).
I found this after a large copy task was aborted and I could not get access to my files via AFP.
The report ist also attached.

The following commands did not help to reactivate the RAID, which I thought might bei the (only) problem:

# mdadm -A /dev/md127
# mdadm --examine --scan >> /etc/mdadm/mdadm.conf

Output (see attachment 4).

The interesting point here is, that I use 5 hard drives, but only 4 seem to be online.

The command
# omv-mkconf mdadm
did not help either, more precisely it gave the following output:
"mdadm: cannot open /dev/md/RAID: No such file or directory“

The last information I have, which is from
# cat /proc/mdstat
is as follows (see attachment 5).

Most important thing again:
There should still be data on the RAID, which I would love to get back! It worked fine before and suddenly stopped working.
Could it be that there is just one of the five hard drives broken and just plugging in a new one would solve the problem (thats what a RAID is for, isn’t it?!), more precisely enable the restoring-mode or something else?

I would be very happy for your support!

Many thanks & best regards,
Denis

... forgot to say, I already tried it with a copy of the system, which I took after a fresh install, while it still worked.

@ryecoaaron, I am very sorry about the 19x-posting, but also very desperate. So I wasn't sure which thread might be the closest one to my problem and which contains the right experts. With that multiple posting I only wanted to make sure to reach the right person. My apologies again!

Unfortunately I am using a beamer, because the RAID used to work smoothly in the past, so no monitoring screen has been neceassary; WebGUI was enough. Furthermore the RAID is running on a stand alone device without any other operating system and consequently no web browser running parallel in order to post things directly from the system. This is why C&P won't work I am afraid.
What extracts should I type down?

I am not in front of the system right now, but will post the output asap. Thank you very much so far!

Any recommendations about the copy and paste problem? More precisely, is it somehow possible to access the console via WebGUI in order to post proper outputs?

Hello,

sorry to sound like a dummy again, but I haven't read the threat while I haven't been in front of the machine.
However, I did now and have to tell, that I am neither a windows user (and there I am afraid to test windows-based commands), nor do I have omv-extras installed (and cannot see an option like this under plugins).
Is there any other way to get the needed infos?

Okay, I installed the plugin and it seems to work. Here is the report:

Personalities : [raid6] [raid5] [raid4]
md127 : inactive sde[0] sdb[4] sda[3] sdd[2]
      11721062240 blocks super 1.2


unused devices: <none>
/dev/sda: UUID="bf6b7c6a-ea91-ae40-15bf-36fc6e2a4d6c" UUID_SUB="5e5d512f-28a3-6be1-3539-27dc0a18d9cd" LABEL="RAID:RAID" TYPE="linux_raid_member"
/dev/sdb: UUID="bf6b7c6a-ea91-ae40-15bf-36fc6e2a4d6c" UUID_SUB="89bdde18-86e9-37ab-53e9-0148631da630" LABEL="RAID:RAID" TYPE="linux_raid_member"
/dev/sdc: UUID="bf6b7c6a-ea91-ae40-15bf-36fc6e2a4d6c" UUID_SUB="5e181077-6334-d5e5-ea9f-d9c84a0d26f7" LABEL="RAID:RAID" TYPE="linux_raid_member"
/dev/sdd: UUID="bf6b7c6a-ea91-ae40-15bf-36fc6e2a4d6c" UUID_SUB="b409ffcf-69fd-996a-bb6a-f2d4b597730d" LABEL="RAID:RAID" TYPE="linux_raid_member"
/dev/sde: UUID="bf6b7c6a-ea91-ae40-15bf-36fc6e2a4d6c" UUID_SUB="0ef2cda2-8f33-d13c-023a-68972a2be25f" LABEL="RAID:RAID" TYPE="linux_raid_member"
/dev/sdf1: UUID="6ee3fa3e-757e-4895-8299-1c996740e2f5" TYPE="ext4"
/dev/sdf5: UUID="bf294a79-6dbe-40e8-9e9b-b42b4b71d23e" TYPE="swap"


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


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


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


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


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


Disk /dev/sdf: 7747 MB, 7747397632 bytes
239 heads, 62 sectors/track, 1021 cylinders, total 15131636 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
Disk identifier: 0x0004b9b2


   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1            2048    14409727     7203840   83  Linux
/dev/sdf2        14411774    15130623      359425    5  Extended
/dev/sdf5        14411776    15130623      359424   82  Linux swap / Solaris

Wow, you are a genius!!!

It now says, that the RAID is assembled with 4 out of 5 drives and I can see it. However, as you might already know, I used to use 5 drives; means one (sdc) is broken?
Do I have to do something more now, like mounting it or something else to get all drives back? Sorry I might seem a bit "over-careful".

Alright, but where can I see when it is finished? I did not even see that it is actually doing something.

What could be wrong with the one drive?

What do you mean I might be worried about, my data during zeroing the superblock etc.? Should I?
If I tried to get the data off the raid, I would have to mount it etc., right?

Still somebody there?

Hi ryecoaaron,

in June it deleted the broken HDD and recovered the RAID. I guess this is what you meant by "we can zero the superblock on the missing drive and try to add it again.". It worked quite well until a few days ago, the RAID was degraded again.

So I bought a new HDD, replaced the broken one and restarted the system.
But when I was trying to start the raid again, with the command "mdadm --stop /dev/md127", it said that there is no such directory and under "file systems" in the WebGUI, now the device is called "OMV.data.Store.ImplicitModel-ext-1468-23".
So I tried the commands from Degraded or missing raid array questions which gave me the info, that there are no used devices, but none of the HDDs does contain a valid partition table. Very strange ...

I am pretty sure you a very good idea again to solve my problem. May I ask what it could be, please?

Many thanks & best regards,
Denis

Hi all,

I continued trying a few things and ... found the solution, maybe this helps for anyone how has the same problem:

When I booted the system, I saw that it hast the name (in my case) "RAID:RAID", don't ask me why.
As the system was always replying, that there is now such file or directory (when I worked with MD127), it just tried to use "RAID" instead in every command. That did not really work out either, but no worries - finally I came to ...

madam -A /dev/md/RAID

... and the system said "dev/md/RAID has been started [...]" and in the WebGUI, the raid was marked as degraded again. All I had to do now was to enable the file system and start the recovery by selecting the new HDD.

All I had do do no