November 29, 20187 yr Community Expert 1 minute ago, Kir said: root@Storage:/mnt# ls / bin/ dev/ etc/ init@ lib64/ proc/ run/ sys/ usr/ boot/ disk1/ home/ lib/ mnt/ root/ sbin/ tmp/ var/ Aha... so there is disk1 there. Now to find what actually got moved... 👍
November 29, 20187 yr Community Expert Thinking about this some more, possibly what got broken was the OS ability to write to its folders anymore since the RAMfs was full.
November 29, 20187 yr Author That was it... Used "du -sh" to find one file that got partially moved, deleted it since it was still present in the source, and array is back online! Thank you, that was quite a scare 🙄
November 29, 20187 yr Community Expert 5 minutes ago, Kir said: That was it... Used "du -sh" to find one file that got partially moved, deleted it since it was still present in the source, and array is back online! Thank you, that was quite a scare 🙄 👍
Archived
This topic is now archived and is closed to further replies.