I had some cabeling issues before, which leads to disks being ejected. Can someone take a look at the log whether this is the again the reason or the disk indeed this time faulty? Thanks in advance!

tower-diagnostics-20170304-1734.zip

Oh no. I pressed the wrong button, so now lost my config when doing a new config. Can you see from the log, what has been parity disk and what were disks 1-15? Thanks for playing this back and also any ideas whether the parity disk is indeed faulty?

If you have lost track of which disk is the Parity disk then if after the New Config you assign ALL disks as Data disks the Parity drive will be flagged as unmountable when you start the array as it does not contain a file system.   You can now make a note of the serial number of the parity disk'; stop the array; do a New Config and assign the drives again with the parity disk in its correct place and you are good to go and rebuild parity.

 

if this procedure results in more than one disk being flagged as unmountable then stop and ask for advice.

Thanks. I was hoping that I can somehow find out from the diagnostic file what disk had been disk 1, disk 2, etc. Not mission critical, but would be great if this info is still existing.

Any chance one of the mods can take a look? I remember someone helped me before to help out the configuration (which disk is disk 1, 2, etc.) from the log file. Thanks!

Mar  4 17:31:09 Tower kernel: md: import disk0: (sdp) WDC_WD60EFRX-68L0BN1_WD-WX11D363T6L2 size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk1: (sdo) WDC_WD60EZRX-00MVLB1_WD-WX11DA40HUVD size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk2: (sdk) WDC_WD60EZRX-00MVLB1_WD-WX11D741AYXK size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk3: (sdf) WDC_WD60EZRX-00MVLB1_WD-WX41D3402835 size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk4: (sdh) WDC_WD60EZRX-00MVLB1_WD-WXK1H641XM4J size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk5: (sdm) WDC_WD60EZRX-00MVLB1_WD-WX31D55A4944 size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk6: (sdn) WDC_WD40EZRX-00SPEB0_WD-WCC4EHJF6HU0 size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk7: (sdg) WDC_WD60EZRX-00MVLB1_WD-WX11DA49HHVY size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk8: (sdq) WDC_WD40EZRX-00SPEB0_WD-WCC4E1961434 size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk9: (sdr) WDC_WD40EZRX-00SPEB0_WD-WCC4E4Z7FKHA size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk10: (sdc) WDC_WD60EZRX-00MVLB1_WD-WX71DA4A03D2 size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk11: (sdd) WDC_WD40EZRX-00SPEB0_WD-WCC4E0076546 size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk12: (sde) WDC_WD60PURX-64T0ZY0_WD-WX41D964E11T size: 5860522532
Mar  4 17:31:09 Tower kernel: md: import disk13: (sdj) ST4000DM000-1F2168_W3008JLM size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk14: (sds) WDC_WD40EZRX-00SPEB0_WD-WCC4EJ4EN10X size: 3907018532
Mar  4 17:31:09 Tower kernel: md: import disk15: (sdl) WDC_WD60EFRX-68L0BN1_WD-WXB1HB4PHE51 size: 5860522532

Disk0 is parity.

 

Thanks a lot. I have not changed any of the cabling, but the HD numbers and the disk numbers above do not match my current assignment (e.g.,

WDC_WD40EZRX-00SPEB0_WD-WCC4E4Z7FKHA

 is not sdr, but sds). Is that normal and shall I just match disk numbers against the HD numbers instead? Any explanation?

Look at the serial numbers only, sdX can change after a reboot.

Cool, thanks, done. The parity disks erroring out and getting disabled upon each new start. I am running an extended smart on it now. I am at a loss whether the disk is faulty or just the cabling is the issue? Any clues from the diagnostic file?

SMART looks fine but try another cable/backplane and if issues persist it's probably a bad disk