On 23/07/17 00:11, gumb wrote:
Well, seems like the "lazy_itable_init" feature of mkfs.ext4 that Jan mentioned on the other thread (https://lists.opensuse.org/opensuse/2017-07/msg00867.html) was all that was causing the issue in the end.
The drive started behaving shortly after I propagated this panic post this morning. It just needed more time. At least I hope that's all it was.
Hrmph. Just out of curiosity I thought I'd verify the second partition using the router's tool. I don't know what purpose that serves exactly, but this time it comes up with an unspecified error. I don't see anywhere to find out further info or view a log. The first partition still verifies okay. Tried unmounting and mounting again but nope, it's not happy. Inclined to leave it alone as it appears to be doing its job in every other respect. Just some obscure, redundant brain cell that has just been reactivated in order to maintain that minor niggle in the back of my mind now. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org