automatic RAID 5 recovery after disk failure in old TS 659?

[MichaelS2]

meanwhile I formated the existing partitions 2 and 3 on the disk to EXT3 with DiskGenius. (Earlier Primary 0 was EXT3, Primary 1 was 'Linux Swap', Pimary 2 und Primary 3 were unformatted)

now it looks likes this:

HD6.jpg

should this also work?

[dolbyman]

as said before .. use diskpart to clear ALL partitions from the disk

[P3R]

dolbyman is giving you excellent advice, please listen to and try to follow that instead of trying other things.

[MichaelS2]

OK. done.

thank you.

now - just re insert the cleaned disk in the old TS 659 disk array?

[dolbyman]

yes....see if the rebuild starts now

[MichaelS2]

thank yoiu.

log files indicate that rebuidling started but was abandonded later due to errors:

2020-09-16 07:24:33 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Rebuilding skipped.
2020-09-16 07:24:14 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Start rebuilding.
2020-09-16 07:24:13 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Rebuilding skipped.
2020-09-16 07:22:56 System 127.0.0.1 localhost Default share Multimedia is not found. TwonkyMedia start failed.
2020-09-16 07:22:55 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Mount the file system read-only failure.
2020-09-16 07:17:54 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Error occurred while accessing the devices of the volume in degraded mode.
2020-09-16 07:16:19 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Error occurred while accessing Drive 1.
2020-09-16 00:39:14 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Start rebuilding.
2020-09-16 00:38:27 System 127.0.0.1 localhost [RAID5 Disk Volume: Drive 1 2 3 4 5 6] Drive 3 added into volume 1.
2020-09-16 00:35:30 System 127.0.0.1 localhost Drive 3 plugged in.

RAID management also does not look correct from my point of views?
Current Disk Volume Configuration
Volume Total Size Bitmap Status Description
RAID 5 Disk Volume: Drive 1 2 3 4 5 6-- No Unmounted Unlocked No operation can be executed for this drive configuration.

putty does not deliver back results now:
[~] # cat proc/mdstat
cat: proc/mdstat: No such file or directory

what to do?

[OneCD]

putty does not deliver back results now:
[~] # cat proc/mdstat
cat: proc/mdstat: No such file or directory

Your syntax is not-quite-right. Try this:

Code: Select all

cat /proc/mdstat

[MichaelS2]

I do not see any difference in the syntax? (and I am not at home know and may not yet try differently)

additionally - does the content from the logs and the RAID management not show significant problems/errors?

[P3R]

I do not see any difference in the syntax? (and I am not at home know and may not yet try differently)

You missed the slash "/" before proc.

You did:

Code: Select all

cat proc/mdstat

You need:

Code: Select all

cat /proc/mdstat

additionally - does the content from the logs and the RAID management not show significant problems/errors?

It tell us that disk 1 probably have a problem. As a RAID 5 can only handle one faulty disk at a time it's time to prepare yourself mentally for that a storage reinitialization and restore from backups may be your only option.

[MichaelS2]

As a RAID 5 can only handle one faulty disk at a time it's time to prepare yourself mentally for that a storage reinitialization and restore from backups may be your only option.

thank you.

re mentally prepare: I already evaluate options for purchasing a new NAS instead of the 9-10 year old one.

my current favorite is the TS-H886.

[P3R]

re mentally prepare: I already evaluate options for purchasing a new NAS instead of the 9-10 year old one.

Then I recommend that you go for NAS or Enterprise disks in that one. WD Black are not bad disks but they're intended for desktop usage and not ideal for NAS/RAID applications. Check out the compatibility list and then ask here in the forum before buying new disks.

[MichaelS2]

OK. understood. the WD Black were selected and distributed by the old QNAS NAP distributor.

[MichaelS2]

...QNAS NAS distributor...

[MichaelS2]

current mdstat:

[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active (read-only) raid5 sdc3[6] sda3[0] sdf3[5] sde3[4] sdd3[3] sdb3[1]
9759728000 blocks level 5, 64k chunk, algorithm 2 [6/5] [UU_UUU]

md6 : active raid1 sdc2[2](S) sdf2[3](S) sde2[4](S) sdd2[5](S) sdb2[1] sda2[0]
530048 blocks [2/2] [UU]

md13 : active raid1 sdc4[3](S) sda4[0] sdd4[2] sde4[4](S) sdf4[5](S) sdb4[1]
458880 blocks [3/3] [UUU]
bitmap: 0/57 pages [0KB], 4KB chunk

md9 : active raid1 sdc1[2] sda1[0] sdf1[5] sde1[4] sdd1[3] sdb1[1]
530048 blocks [6/6] [UUUUUU]
bitmap: 2/65 pages [8KB], 4KB chunk

unused devices: <none>
[~] #

hints/opinions?

[dolbyman]

I thought we established that you had two drives fail in a raid5

there is no path to go here