I upgraded after a server failure I do not know which drive is the bad one yet.   I went from version 5 to the current version

I have old vers 5 syslog files.  What do I need to look for in the syslog file to determine which drive was my parity drive so I can

see if the raid will almost fully recover and not loose my data.

look for what wording in syslog ...sda????? with what following data to determine parity drive from data drives

 

thanks

 

Look for this section:
 

Quote

Mar 18 17:35:47 Tower kernel: mdcmd (1): import 0 8,48 2930266532 WDC_WD30EZRX-00D8PB0_WD-WMC4N2757642
Mar 18 17:35:47 Tower kernel: md: import disk0: [8,48] (sdd) WDC_WD30EZRX-00D8PB0_WD-WMC4N2757642 size: 2930266532
Mar 18 17:35:47 Tower kernel: mdcmd (2): import 1 8,16 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAH445462
Mar 18 17:35:47 Tower kernel: md: import disk1: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WCAZAH445462 size: 1953514552
Mar 18 17:35:47 Tower kernel: mdcmd (3): import 2 8,32 1953514552 WDC_WD20EZRX-00DC0B0_WD-WMC1T1738087
Mar 18 17:35:47 Tower kernel: md: import disk2: [8,32] (sdc) WDC_WD20EZRX-00DC0B0_WD-WMC1T1738087 size: 1953514552
Mar 18 17:35:47 Tower kernel: mdcmd (4): import 3 8,64 1953514552 WDC_WD20EZRX-00DC0B0_WD-WMC1T1995190
Mar 18 17:35:47 Tower kernel: md: import disk3: [8,64] (sde) WDC_WD20EZRX-00DC0B0_WD-WMC1T1995190 size: 1953514552
Mar 18 17:35:47 Tower kernel: mdcmd (5): import 4 8,96 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAH441575
Mar 18 17:35:47 Tower kernel: md: import disk4: [8,96] (sdg) WDC_WD20EARX-00PASB0_WD-WCAZAH441575 size: 1953514552

 

 

Parity is disk0

I haven't seen a V5 syslog in a very long time, but I don't think this part will have changed. Look for the line that says "import disk 0". That line will have the serial number of your parity disk.

 

Just now, trurl said:

I haven't seen a V5 syslog in a very long time, but I don't think this part will have changed

It's the same, and in fact I used a v5 syslog to make sure

Thanks

 

found it thanks to your replies

 

Lance