Raid 5 ist nicht mehr da

Jensbob76 · Dec 19th 2024

Hallo zusammen,

bin Anfänger und benötige Hilfe bei meinem Nas-System mit Raid 5 und OMV. Schiebe das Thema schon lange vor mir her.

Mein NAS funktioniert seit 3 Jahren nicht.... Hat aber davor 2 Jahre super funktioniert. Ich habe damals einen neuen Router bekommen,

danach war mein NAS über Windows per SMB nicht mehr erreichbar. Musste mich dann per Monitor und Tastatur mit den NAS-Rechner verbinden.

Kam dann in ein Menü glaube ich mit "First-Aid" oder so. Ob ich darüber eine neue IP für das NAS vergeben habe, weiß ich nicht mehr.

Seitdem ist das Raid 5 nicht mehr da. Das System erkennt zwar die realen Festplatten, aber das Raid ist weg. Updates und Upgrades gehen seitdem

auch nicht mehr. Aber als erstes steht die Wiederherstellung vom Raid 5 im Vordergrund. Schon mal Danke für eure Hilfe

Habe die 4 eingebauten Festplatten geklont auf 4 Backup-Festplatten. Hoffe meine Bilder werden richtig dargestellt.

Nun zu den Informationen, die ihr wahrscheinlich braucht:

macom · Dec 20th 2024

Suggest to follow this post and provide the output of the mentioned commands in a code box </> each. You can use a ssh session (e.g. with Putty or cmd from Windows) and copy + paste output.

Thread

Degraded or missing raid array questions

If you have a degraded or missing raid array, please post the following info (in code boxes) with your question.

Login as root locally or via ssh - Windows users can use putty:

cat /proc/mdstat
blkid
fdisk -l | grep "Disk "
cat /etc/mdadm/mdadm.conf
mdadm --detail --scan --verbose
Post type of drives and quantity being used as well.
Post what happened for the array to stop working? Reboot? Power loss?

ryecoaaron

May 15th 2015

Feel free to post in German, but the probability of an answer will be bigger if you write in English.

Krisbee · Dec 20th 2024

Jensbob76 You've already posted most of the details that macom has referred to. But can you please post the output of this commandmdadm -E /dev/sd[a-d] and re-post the full output of cat /etc/mdadm/mdadm.conf

Jensbob76 · Dec 20th 2024

Krisbee habe gesehen, das mein Übersetzter die Ausgabe in deutsch übersetzt hat. Soll ich das nochmal in englisch posten?

Jensbob76 · Dec 20th 2024

Mache ich einfach mal:

Code

root@jensnas:~# mdadm -E /dev/sd[a-d]
/dev/sda:
MBR Magic : aa55
Partition[0] :   4294967295 sectors at            1 (type ee)
/dev/sdb:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 0b7af678:7799bab1:7fe48631:9512529c
Name : openmediavault:0
Creation Time : Thu Mar  2 18:32:18 2017
Raid Level : raid5
Raid Devices : 4


Avail Dev Size : 7813775024 (3725.90 GiB 4000.65 GB)
Array Size : 11720661504 (11177.69 GiB 12001.96 GB)
Used Dev Size : 7813774336 (3725.90 GiB 4000.65 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=688 sectors
State : active
Device UUID : 739a8ee7:87cbfcb0:b8243716:469ae59c


Internal Bitmap : 8 sectors from superblock
Update Time : Thu Oct 15 13:21:33 2020
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : c6974dbc - correct
Events : 4654920


Layout : left-symmetric
Chunk Size : 512K


Device Role : Active device 1
Array State : .AAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 0b7af678:7799bab1:7fe48631:9512529c
Name : openmediavault:0
Creation Time : Thu Mar  2 18:32:18 2017
Raid Level : raid5
Raid Devices : 4


Avail Dev Size : 7813775024 (3725.90 GiB 4000.65 GB)
Array Size : 11720661504 (11177.69 GiB 12001.96 GB)
Used Dev Size : 7813774336 (3725.90 GiB 4000.65 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=688 sectors
State : active
Device UUID : ede8905f:e9124995:aa40dedb:2bf05fc6


Internal Bitmap : 8 sectors from superblock
Update Time : Thu Oct 15 13:21:33 2020
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 12075571 - correct
Events : 4654920


Layout : left-symmetric
Chunk Size : 512K


Device Role : Active device 2
Array State : .AAA ('A' == active, '.' == missing, 'R' == replacing)
/dev/sdd:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x9
Array UUID : 0b7af678:7799bab1:7fe48631:9512529c
Name : openmediavault:0
Creation Time : Thu Mar  2 18:32:18 2017
Raid Level : raid5
Raid Devices : 4


Avail Dev Size : 7813775024 (3725.90 GiB 4000.65 GB)
Array Size : 11720661504 (11177.69 GiB 12001.96 GB)
Used Dev Size : 7813774336 (3725.90 GiB 4000.65 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=688 sectors
State : active
Device UUID : 43486b9e:7edef339:d70d8cbf:8f092d2d


Internal Bitmap : 8 sectors from superblock
Update Time : Thu Oct 15 13:21:33 2020
Bad Block Log : 512 entries available at offset 72 sectors - bad blocks present.
Checksum : 400766f5 - correct
Events : 4654920


Layout : left-symmetric
Chunk Size : 512K


Device Role : Active device 3
Array State : .AAA ('A' == active, '.' == missing, 'R' == replacing)

Display More

Krisbee · Dec 20th 2024

Quote from Jensbob76

Krisbee habe gesehen, das mein Übersetzter die Ausgabe in deutsch übersetzt hat. Soll ich das nochmal in englisch posten?

Yes please. Could you also post this in a "code box" using the "</>" symbol in the forum editor.

Jensbob76 · Dec 20th 2024

Code

root@jensnas:~# 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>

Display More

Jensbob76 · Dec 20th 2024

Code

root@jensnas:~# blkid
/dev/sdb: UUID="0b7af678-7799-bab1-7fe4-86319512529c" UUID_SUB="739a8ee7-87cb-fcb0-b824-3716469ae59c" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="06955306-6539-4bbe-8e15-7bad6400156a"
/dev/sdd: UUID="0b7af678-7799-bab1-7fe4-86319512529c" UUID_SUB="43486b9e-7ede-f339-d70d-8cbf8f092d2d" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sdc: UUID="0b7af678-7799-bab1-7fe4-86319512529c" UUID_SUB="ede8905f-e912-4995-aa40-dedb2bf05fc6" LABEL="openmediavault:0" TYPE="linux_raid_member"
/dev/sde1: UUID="9001edb6-e469-4655-8f85-5609ae6e4425" TYPE="ext4" PARTUUID="c8b7d06d-01"
/dev/sde5: UUID="189bc8d7-1c4d-4c51-8efb-3207dac45513" TYPE="swap" PARTUUID="c8b7d06d-05"
/dev/sda2: PARTUUID="7bdba353-6714-4f74-9af2-6e5d8b157203"

Krisbee · Dec 20th 2024

We've lost the important part, never mind I've worked out what I need to know from #5 above.

Your post #5 shows one disk (/dev/sda??) was lost from your array. The good news is that /dev/sdb, /dev/sdc and /dev/sdd have the same "Update Time" (Aktualisierungszeit) and "Events" (Veranstaltungen) count when the array was last working. So, there's a good chance you can re-assmeble the array in a "clean, degraded" state without /dev/sda, but there is no guarantee that the filesystem on the RAID is still intact.

Please do not reboot your system as the /dev/sdX names might change, and we need them to stay the same as in your last output.

Also please understand that your proceed entirely at your own risk. I take no responsibility for any data, or other loss, that may occur by following any instructions and/or guidance I post.

At the CLI:

1. Attempt to re-assemble the array in a degraded state using this exact command: mdadm --assemble --force /dev/md0 /dev/sdb /dev/sdc /dev/sdd

2. Assuming no error messages from 1, check the status of array using cat /proc/mdstat as it re-builds.

3. The re-build could take several hours.

4. When complete, use this command to see if the filesystem on the MD RAID will mount: mount -a

5. If the filesystem mounts you can copy data off the NAS now.

Jensbob76 · Dec 20th 2024

Quote from Krisbee

We've lost the important part, never mind I've worked out what I need to know from #5 above.

Your post #5 shows one disk (/dev/sda??) was lost from your array. The good news is that /dev/sdb, /dev/sdc and /dev/sdd have the same "Update Time" (Aktualisierungszeit) and "Events" (Veranstaltungen) count when the array was last working. So, there's a good chance you can re-assmeble the array in a "clean, degraded" state without /dev/sda, but there is no guarantee that the filesystem on the RAID is still intact.

Please do not reboot your system as the /dev/sdX names might change, and we need them to stay the same as in your last output.

Also please understand that your proceed entirely at your own risk. I take no responsibility for any data, or other loss, that may occur by following any instructions and/or guidance I post.

At the CLI:

1. Attempt to re-assemble the array in a degraded state using this exact command: mdadm --assemble --force /dev/md0 /dev/sdb /dev/sdc /dev/sdd

2. Assuming no error messages from 1, check the status of array using cat /proc/mdstat as it re-builds.

3. The re-build could take several hours.

4. When complete, use this command to see if the filesystem on the MD RAID will mount: mount -a

5. If the filesystem mounts you can copy data off the NAS now.

Display More

Krisbee, erstmal Danke für deine Hilfe. Habe den Befehl ausgeführt. Dann warte ich mal bis morgen.

In der Ausgabe steht jetzt folgendes:

Code

root@jensnas:~# mdadm --assemble --force /dev/md0 /dev/sdb /dev/sdc /dev/sdd
mdadm: Marking array /dev/md0 as 'clean'
mdadm: /dev/md0 has been started with 3 drives (out of 4)

Krisbee · Dec 20th 2024

Jensbob76 So far so good. Fingers crossed the filesystem mounts and you can access your data.

Jensbob76 · Dec 21st 2024

Krisbee vielen herzlichen Dank. Es hat funktioniert und ich kann auf mein NAS per SMB wieder zugreifen.

Krisbee · Dec 21st 2024

Everyone likes a happy ending.

macom · Dec 21st 2024

Quote from Jensbob76

Krisbee vielen herzlichen Dank. Es hat funktioniert und ich kann auf mein NAS per SMB wieder zugreifen.

Denk daran, die Daten sofort zu sichern.

Jensbob76 · Dec 21st 2024

Quote from macom

Denk daran, die Daten sofort zu sichern.

macom , da bin ich gerade bei Ich hatte im Vorfeld von den eingebauten Festplatten eine 1:1 Kopie gemacht.

Raid 5 ist nicht mehr da

ryecoaaron Dec 19th 2024

votdev Dec 21st 2024

Participate now!

Similar Threads

Multiple Device Problem

Synology DSM vs. OMV

Kein Raid5 mehr im WebGui sichtbar nach neuinstallation

Datenverlust keine wiederherstellung möglich? Data loss and no recovery possible?

Tags