Degraded RAID..¿?¿?

Can anyone tell me if something goes wrong?

:o

md127

Version : 1.2
Creation Time : Wed Jun 12 00:04:48 2013
Raid Level : raid1
Array Size : 976761424 (931.51 GiB 1000.20 GB)
Used Dev Size : 976761424 (931.51 GiB 1000.20 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent

Update Time : Sun Dec 1 01:09:29 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

Name : nas4free:RAID1
UUID : 062ffd49:17b7d27d:df5a179e:72ca6436
Events : 18660

Number Major Minor RaidDevice State
0 8 64 0 active sync /dev/sde
1 0 0 1 removed

md126

Version : 1.2
Creation Time : Wed Jun 12 00:04:48 2013
Raid Level : raid1
Array Size : 976761424 (931.51 GiB 1000.20 GB)
Used Dev Size : 976761424 (931.51 GiB 1000.20 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent

Update Time : Sun Dec 1 01:11:53 2013
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

Name : nas4free:RAID1
UUID : 062ffd49:17b7d27d:df5a179e:72ca6436
Events : 3134

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 48 1 active sync /dev/sdd

Hello again, thanks for your answer, I have not yet tested those commands.

I have to say also that this is happening to me now and the system is frozen.

I will use your script now to see how it. (if I can boot the OS..)

EDIT: Now, at reboot I have this problem.. :cry:

EDIT: OK, rebooting repeatedly skipped that error.

This is the result of your commands:

root@omv:~# umount /dev/md127
umount: /dev/md127: not mounted
root@omv:~# umount /dev/md126
umount: /dev/md126: not mounted
root@omv:~# mdadm .-stop /dev/md126
mdadm: An option must be given to set the mode before a second device
       (/dev/md126) is listed
root@omv:~# mdadm .-stop /dev/md127
mdadm: An option must be given to set the mode before a second device
       (/dev/md127) is listed
root@omv:~# mdadm -A /dev/md0 -f .-update=summaries /dev/sdd /dev/sde
mdadm: cannot open device .-update=summaries: No such file or directory
mdadm: .-update=summaries has no superblock - assembly aborted
root@omv:~# mdadm /dev/md0 -a /dev/sdd
mdadm: error opening /dev/md0: No such file or directory
root@omv:~#

After the commands, I reboot and get this screen:

I leave the server off to know what to do

Zitat von "ryecoaaron"

You have .- where they should be -- in every command.

Sorry, and now..?

root@omv:~# umount /dev/md126
root@omv:~# umount /dev/md127
umount: /dev/md127: not mounted
root@omv:~# mdadm --stop /dev/md126
mdadm: failed to stop array /dev/md126: Device or resource busy
Perhaps a running process, mounted filesystem or active volume group?
root@omv:~# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
root@omv:~# mdadm -A /dev/md0 -f --update=summaries /dev/sdd /dev/sde
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: /dev/sdd has no superblock - assembly aborted
root@omv:~# mdadm /dev/md0 -a /dev/sdd
mdadm: error opening /dev/md0: No such file or directory
root@omv:~#

OK, I'm downloading systemrescuecd-x86-3.8.1.iso

Please, I beg you to continue to help me.

Thanks.

Zitat von "ryecoaaron"

What is the output of the following now:

cat /proc/mdstat
blkid

I have..
1x 3TB HDD ext3
1x 2TB HDD ext3
2x 1TB HDD in RAID1
1x 32GB SSD for OpenMediaVault SO
+ now 1x 4GB pendrive with SystemRescueCD live

Ouch! Sorryyy! !

OK, and now..?

OK, results..

Zitat von "ryecoaaron"

The good news is that you can still recover files. The bad news is that one of your drives seems to be bad.

Well, I will locate what hard drive is wrong and I try to format from my other tower with ubuntu.

I will keep you informed to see how this story ends

Thank you for your support at all times, you are a beautiful person.

Hello again, I disconnected the damaged HDD, but now get this screen again, happens to me sometimes, and I can take hours or even days trying to boot the computer to boot up.

Do you what you should know this error?