trurl Posted November 29, 2018 Share Posted November 29, 2018 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... 👍 Quote Link to comment
trurl Posted November 29, 2018 Share Posted November 29, 2018 Thinking about this some more, possibly what got broken was the OS ability to write to its folders anymore since the RAMfs was full. Quote Link to comment
Kir Posted November 29, 2018 Author Share Posted November 29, 2018 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 🙄 Quote Link to comment
trurl Posted November 29, 2018 Share Posted November 29, 2018 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 🙄 👍 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.