Raid Crash Ich habe das selbe Problem mit der NAS540

dsz376

Guten Tag,

bei mir liegt das selbe Problem vor und ich brauche dringend Hilfe.

Gruß

Dennis


Hallo zusammen,

ich brauche dringend Hilfe bei der Wiederherstellung meins Raid5-Volume. Als vorhin der Kopiervorgang auf die NAS abbrach und ich diese nicht mehr ansprechen konnte, vollzog ich einen Neustart. Anschließend erhielt ich folgende Fehlermeldung in der GUI. Die einzelnen HDDs zeigen keine Defekte an, auch die SMART-Werte passen. Es gibt jedoch keine Option diesen Fehler zu "reparieren". Was muss ich tun um die Daten nicht entgültig zu verlieren?

Vielen Dank vorab für eure Hilfe.
Detlef








#NAS_Apr_2019

Rory

If your RAID is  RAID 1 or JBOD, you can try to get data from Linux:

http://kb.zyxel.com/KB/searchArticle!viewDetail.action?articleOid=010795&lang=EN

Anna

What's the results when you use following commands:

fdisk -l

cat /tmp/sto_log

cat /proc/mdstat

mdadm --examine /dev/sda3

mdadm --examine /dev/sdb3

mdadm --examine /dev/sdc3

mdadm --examine /dev/sdd3

dsz376

I have a Raid 5

dsz376

dsz376

Rory

@dsz376

You should use "root" to check commands.

dsz376

~ $ su root

Password: 

BusyBox v1.19.4 (2018-11-08 14:45:40 CST) built-in shell (ash)

Enter 'help' for a list of built-in commands.

~ # fdisk -l

Disk /dev/loop0: 144 MiB, 150994944 bytes, 294912 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 /dev/mtdblock0: 256 KiB, 262144 bytes, 512 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 /dev/mtdblock1: 512 KiB, 524288 bytes, 1024 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 /dev/mtdblock2: 256 KiB, 262144 bytes, 512 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 /dev/mtdblock3: 10 MiB, 10485760 bytes, 20480 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 /dev/mtdblock4: 10 MiB, 10485760 bytes, 20480 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 /dev/mtdblock5: 110 MiB, 115343360 bytes, 225280 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 /dev/mtdblock6: 10 MiB, 10485760 bytes, 20480 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 /dev/mtdblock7: 110 MiB, 115343360 bytes, 225280 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 /dev/mtdblock8: 6 MiB, 6291456 bytes, 12288 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 /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Disklabel type: gpt

Disk identifier: 993D0B21-2A81-4F77-BFEB-F9A0EDCBC47F

Device       Start        End    Sectors  Size Type

/dev/sda1     2048    3999743    3997696  1.9G Linux RAID

/dev/sda2  3999744    7999487    3999744  1.9G Linux RAID

/dev/sda3  7999488 3907028991 3899029504  1.8T Linux RAID

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Disklabel type: gpt

Disk identifier: B62035F7-DE79-4916-B009-601F804CCC7C

Device       Start        End    Sectors  Size Type

/dev/sdb1     2048    3999743    3997696  1.9G Linux RAID

/dev/sdb2  3999744    7999487    3999744  1.9G Linux RAID

/dev/sdb3  7999488 3907028991 3899029504  1.8T Microsoft basic data

Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Disklabel type: gpt

Disk identifier: A9E4D18A-4CF6-426A-AACA-F05012808A3A

Device       Start        End    Sectors  Size Type

/dev/sdc1     2048    3999743    3997696  1.9G Linux RAID

/dev/sdc2  3999744    7999487    3999744  1.9G Linux RAID

/dev/sdc3  7999488 3907028991 3899029504  1.8T Linux RAID

Disk /dev/sdd: 1.8 TiB, 2000398934016 bytes, 3907029168 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

Disklabel type: gpt

Disk identifier: B3BF3CCA-69C6-4B25-BFC2-FAA0FDAC4F3B

Device       Start        End    Sectors  Size Type

/dev/sdd1     2048    3999743    3997696  1.9G Linux RAID

/dev/sdd2  3999744    7999487    3999744  1.9G Linux RAID

/dev/sdd3  7999488 3907028991 3899029504  1.8T Linux RAID

Disk /dev/md0: 1.9 GiB, 2045706240 bytes, 3995520 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 /dev/md1: 1.9 GiB, 2046754816 bytes, 3997568 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 /dev/md2: 5.5 TiB, 5988506664960 bytes, 11696302080 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 65536 bytes / 196608 bytes

dsz376

Mijzelf

According to mdadm and /proc/mdstat the array is degraded. For some reason sdc3 is kicked off the array at 3 April.

According to /tmp/sto_log the volume can't be mounted. So I think the filesystem is damaged. You can try to repair that

<div>su</div><div><br></div><div>fsck /dev/md2<br></div><div></div>