Hello everyone,

Something very strange happened to me yesterday.  I simply rebooted my server, then manually started my array (i have auto disabled).  My configuration before the restart was 2 array devices.   parity drive 6TB, and Disk 1 (drive of 6TB).  Cache pool drive slot using my SSD 128GB drive.  

 

Once I rebooted I then started the array and my cache drive was moved into the array and started to pre-clear with no action taken on my part, other than the reboot and manual starting of the array.  I was able to get the system returned to normal status fairly quickly as I had backups in place.

 

But the big question is why on earth did this happen?  It is very discomforting.   Anyone have any ideas?

 

Thanks,

Frank

tower-diagnostics-20221218-2232.zip

Edited December 19, 20223 yr by Built2Succeed
Added diagnostic file and clarified the configuration. I erroneously referred to parity drive as disk 1.

24 minutes ago, Built2Succeed said:

Disk 1 (parity drive 6TB)

Please don't refer to parity as disk1. What will you call the drive assigned to slot 1 if you are calling parity disk1? Disk1 should refer to the disk in slot1 of the array, disk2 should refer to the disk in slot2 of the array, etc. Unraid thinks of parity as slot0 if you look in syslog. Best to just call it parity.

 

Without diagnostics when the problem occurred can't really guess what happened.

Probably something missing in your explanation that might make some sense of this but without diagnostics don't know what it would be.

1 hour ago, trurl said:

Please don't refer to parity as disk1. What will you call the drive assigned to slot 1 if you are calling parity disk1? Disk1 should refer to the disk in slot1 of the array, disk2 should refer to the disk in slot2 of the array, etc. Unraid thinks of parity as slot0 if you look in syslog. Best to just call it parity.

 

Without diagnostics when the problem occurred can't really guess what happened.

Thank you for that clarification.  I edited my post and will add diagnostic info as soon as I figure out how to do that. 

3 minutes ago, Built2Succeed said:

will add diagnostic info as soon as I figure out how to do that.

The word diagnostics in this and every post is a link to an explanation.

 

Diagnostics won't tell us anything that happened before last boot. If you already had syslog server setup to save syslog somewhere then that might tell us something.

Thank you.  I've setup syslog to be saved.  If it happens again I'll revisit. 

It is not recommended to save syslog to flash for extended periods.