DegradedArray event RAID5 issue, help please

danieliod · 10. Januar 2016

Hello,

I have recently joined the OMV community after using for several years QNAP Devices.

I have build my NAS with 1 SSD 120 GB SanDisk
and RAID 5 with 3 HDDs 3TB each:
1. Seagate ST3000VN00 x2
2. Seagate ST3000DM001 x1

I have enabled the Notification Center yesterday and recieved the following email below.

What should I do with this notification? Does it means my RAID 5 is not functioning properly?

"A DegradedArray event had been detected on md device /dev/md0.
Faithfully yours, etc.P.S.

The /proc/mdstat file currently contains the following:

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sdc[1] sdd[2]
5855716352 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [_UU]

unused devices: <none>"

danieliod · 10. Januar 2016

This is the details from my RAID:

danieliod · 11. Januar 2016

Help please

CptHowdy · 7. März 2016

to provide everyone with enough information to help you, please post the results of the following commands...

blkid
fdisk -l
cat /proc/mdstat

danieliod · 7. März 2016

Thank you for the support:
blkid

Code

/dev/md127: LABEL="RAID" UUID="7fbde406-4c77-4bed-94c8-b6b045f9e757" TYPE="ext4"                                
/dev/sde: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="d17728a0-84fe-c5                                04-ffb0-e13849c2282d" LABEL="openmediavault:NAS" TYPE="linux_raid_member"
/dev/sdb1: UUID="c4773f30-7a51-4b82-89b2-dc1e8b25f1ff" TYPE="ext4"
/dev/sdb3: LABEL="DATA" UUID="395fdb16-d339-4c6d-bbf6-6419f1aaa444" TYPE="ext4"
/dev/sdb5: UUID="8cf58870-b3d3-4402-9e95-cbf71c041584" TYPE="swap"
/dev/sdd: UUID="332d8084-c2b3-a139-44a4-f8e16865cc49" UUID_SUB="34c4db9b-ec1b-b6                                1b-2a46-cb372f84d784" LABEL="openmediavault:NAS" TYPE="linux_raid_member"

fdisk -l

Code

Disk /dev/sdb: 126.0 GB, 126035288064 bytes
255 heads, 63 sectors/track, 15322 cylinders, total 246162672 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: 0x0006ad32


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    29493247    14745600   83  Linux
/dev/sdb2        29495294    32567295     1536001    5  Extended
/dev/sdb3        32567296   246161407   106797056   83  Linux
/dev/sdb5        29495296    32567295     1536000   82  Linux swap / Solaris


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: 0x1e011e00


   Device Boot      Start         End      Blocks   Id  System


WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 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: 0x1e011e02


   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1  4294967295  2147483647+  ee  GPT
Partition 1 does not start on physical sector boundary.


Disk /dev/md127: 5996.3 GB, 5996253544448 bytes
2 heads, 4 sectors/track, 1463929088 cylinders, total 11711432704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000


Disk /dev/md127 doesn't contain a valid partition table

Alles anzeigen

CptHowdy · 7. März 2016

it looks like /dev/sdc has dropped from your RAID array. . . you should identify the problem with this. . . could be one of the cables or a faulty drive. . . after you replace the drive the RAID should automatically start rebuilding itself ... hope this was helpful.

also from personal experience, I typically stay away from Seagate drives, and drives designed for desktop use don't always hold up in a RAID setup. I would consider replacing the drives with good NAS rated drives like WD "red" or "red pro" or the "se" datacenter series. several other choices, but those would be my first choice in a NAS environment.

danieliod · 7. März 2016

Thank you, I will have look.
This drives are NAS rated: ST3000VN00.
SDC drive is new and installed last week. I will check that there are no cable issues.
Thank you

danieliod · 7. März 2016

Thank you for the detailed info, it's very appreciated.
I have replaced the SATA cable and the drive boot up correctly.
Then I wiped it via the OMV GUI, restarted and started RAID recovery.
It's running now, let's hope it will last long enough...
I will update once finished.

thank you

CptHowdy · 9. März 2016

glad I could be of some assistance

danieliod · 13. März 2016

Everything works well since the Array finished rebuilding.
Thank you again

CptHowdy · 13. März 2016

You're welcome....only reason I could help is I have had so many issues myself with raid.....wish you the best

DegradedArray event RAID5 issue, help please

Jetzt mitmachen!

Tags