Degraded RAID Issue

johnyb · 13. Oktober 2017

Would appreciate advice on next steps, do I need to replace the faulty drive?

First I knew about this was an email notification initially saying this:-
Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sdb[4] sda[3] sdc[2]
8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]

Took drive out and connected to another PC, run Western Digital Lifeguard Diagnostics results below suggested no errors however just noticed the capacity is not showing correctly.

Code

Western Digital Logo
Test Option: QUICK TEST 
Model Number: WDC WD30 EFRX-68AX9N0 
Unit Serial Number:  
Firmware Number: 0A80 
Capacity: 801.57 GB 
SMART Status: Not Available 
Test Result: PASS 
Test Time: 11:53:41, October 13, 2017 


Test Option: EXTENDED TEST 
Model Number: WDC WD30 EFRX-68AX9N0 
Unit Serial Number:  
Firmware Number: 0A80 
Capacity: 801.57 GB 
SMART Status: Not Available 
Test Result: PASS 
Test Time: 19:27:02, October 13, 2017

Alles anzeigen

Drives: 4 x WD RED 3TB (Raid5)
Cause: Unknown - NAS is on UPS so should be no issues with power failure

Code

Personalities : [raid6] [raid5] [raid4]
md126 : inactive sda[0](S)
      2930265560 blocks super 1.2


md127 : active raid5 sdc[4] sdb[3] sdd[2]
      8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]

Code

/dev/sdb: UUID="37ddf068-5701-aac7-8e69-d50a59a2ba35" UUID_SUB="22ec5662-9bbd-bd7e-733e-9ffcaeca4ad5" LABEL="OMV:OMVR5" TYPE="linux_raid_member"
/dev/sdc: UUID="37ddf068-5701-aac7-8e69-d50a59a2ba35" UUID_SUB="d8c3fac7-e183-ecab-ffa6-6613e885912e" LABEL="OMV:OMVR5" TYPE="linux_raid_member"
/dev/md127: LABEL="OMVR5" UUID="26ca4497-4a5c-47d3-80cc-1ff71b99321c" TYPE="ext4"
/dev/sda: UUID="37ddf068-5701-aac7-8e69-d50a59a2ba35" UUID_SUB="d5f708d5-2318-bcac-3653-183ca5730c0a" LABEL="OMV:OMVR5" TYPE="linux_raid_member"
/dev/sde1: UUID="9102f759-ef30-44d6-8b91-442a39047000" TYPE="ext4"
/dev/sdd: UUID="37ddf068-5701-aac7-8e69-d50a59a2ba35" UUID_SUB="8e3d0e42-3d70-dcc7-dfe7-518c8badf634" LABEL="OMV:OMVR5" TYPE="linux_raid_member"
/dev/sde5: UUID="aa110035-b752-46f4-a3a5-da45f44ea624" TYPE="swap"
/dev/sdf1: LABEL="New Volume" UUID="D2862F82862F65E7" TYPE="ntfs"

Code

Disk /dev/sda doesn't contain a valid partition table
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc doesn't contain a valid partition table
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/md127 doesn't contain a valid partition table
Disk /dev/sda: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
Disk identifier: 0x00000000
Disk /dev/sde: 250.1 GB, 250059350016 bytes
Disk identifier: 0x000ec591
Disk /dev/md127: 9001.8 GB, 9001774350336 bytes
Disk identifier: 0x00000000
Disk /dev/sdf: 40.0 GB, 40007761920 bytes
Disk identifier: 0xf9d1d4e8

Alles anzeigen

Code

# 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>


# definitions of existing MD arrays
ARRAY /dev/md/OMVR5 metadata=1.2 name=OMV:OMVR5 UUID=37ddf068:5701aac7:8e69d50a:59a2ba35


# instruct the monitoring daemon where to send mail alerts
MAILADDR xxxxxx@gmail.com
MAILFROM root

Alles anzeigen

Code

ARRAY /dev/md/OMVR5 level=raid5 num-devices=4 metadata=1.2 name=OMV:OMVR5 UUID=37ddf068:5701aac7:8e69d50a:59a2ba35
   devices=/dev/sdc,/dev/sdd,/dev/sdb
ARRAY /dev/md/OMVR5 level=raid5 num-devices=4 metadata=1.2 name=OMV:OMVR5 UUID=37ddf068:5701aac7:8e69d50a:59a2ba35
   devices=/dev/sdc,/dev/sdd,/dev/sdb

Sc0rp · 19. Oktober 2017

Hi,

bevor pulling out any drive, you should just check the SMART values of the faulty drive AND the logs (/var/log/syslog and/or /var/log/messages) ... next time.

But now, you can put it back, then reactivate it in your array (simply add it to the array - and the rebuild will begin) and wait for the next error ... you can scan the logs for errors, if it is not too long ago.

Sc0rp

johnyb · 20. Oktober 2017

Thanks for the suggestion. After testing the drive externally, in order to add it back into the raid I had to wipe it first (Physical Disks > WIpe) then it would show up as a device I could use to recover the Raid5. Not sure how the drive got in this state but obviously have some concern the drive could be on its way out. Didnt have SMART configured by default on raid drives, what would you recommend as the best setting here?

Also I now get the following notificaiton daily, any idea on how to prevent it? Thanks

Code

A SparesMissing event had been detected on md device /dev/md/OMVR5.


Faithfully yours, etc.


P.S. The /proc/mdstat file currently contains the following:


Personalities : [raid6] [raid5] [raid4]
md127 : active raid5 sda[5] sdb[3] sdd[2] sdc[4]
      8790795264 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

Alles anzeigen

tkaiser · 20. Oktober 2017

Zitat von johnyb

After testing the drive externally

You did NOT test your drive at all. When only 800 MB were shown for a 3TB drive on your Windows bix most probably you shoved the drive in an old USB disk enclosure with a crappy USB-to-SATA bridge suffering from both an 32-bit integer overflow and not being SAT capable and therefore no SMART data available and the WD 'test' software stupidly reporting 'Test Result: PASS' when it should have told you 'no SMART available, NO TESTING happened')

Now that the disk is back please provide output from 'smartctl -a /dev/sda' and check the logs as @Sc0rp already suggested. BTW: I won't comment on RAID issues and can only recommend to do a backup/clone of the whole array immediately in case you have none.

johnyb · 21. Oktober 2017

Thanks, makes sense. my bad. included output as requested (too big to post here ) http://txt.do/d4nc4

tkaiser · 21. Oktober 2017

Zitat von johnyb

included output as requested (too big to post here ) txt.do/d4nc4

That's only SMART output (which looks ok except this thing running since 4.3 years now). What about the logs?

johnyb · 21. Oktober 2017

Sorry ,uploaded messages files here

https://www.filestofriends.com…36a3b4d299de3d3c140008cac

Sc0rp · 26. Oktober 2017

Re,

Zitat von johnyb

Sorry ,uploaded messages files here

Uhm "Link expires: October 23 at 1:11 PM ET" ... didn't got it in time, sry.

Sc0rp

johnyb · 27. Oktober 2017

This one expires on October 29 at 11:59 AM ET. Do you know any file storage that last longer? Thanks.

https://www.filestofriends.com…efd644850ae715ce8b261ffea

cabrio_leo · 27. Oktober 2017

Zitat von johnyb

Do you know any file storage that last longer? Thanks.

Why didn´t you attach it directly to your post? The max. file size which you can attach is 1 MB per file, 10 files max. Also possible: attach zip-file if plain file size exceeds 1 MB.
The file size at your download link is 247 kB. This should work. Maybe you have to rename it to "messages.txt".

johnyb · 27. Oktober 2017

Cheers cabrio_leo, didnt know this forum allowed attachments. Added now.

johnyb · 31. Oktober 2017

File was added a couple of post back, would appreciate some guidance on next steps. Thanks

Jetzt mitmachen!