Jan Engelhardt composed on 2015-01-07 09:13 (UTC+0100):
Felix Miata wrote:
http://fm.no-ip.com/Tmp/Linux/big41raidNADA.txt contains output from lsmod, cat /proc/mdstat, and tune2fs -l.
My (years old) marking on it made unclear as to whether I had only prepped its partitions for use as a backup HD, or had actually used it in this system and later replaced one with newer leaving this as an offline spare.
md120 : inactive sdb14[0](S) 156280216 blocks super 1.0
Just a spare. (S)
OK...
The array is also incomplete, i.e. you do not even have enough non-spare data volumes in your system to at least start it in degraded mode.
This I don't understand. Providing mdadm.conf and susequently being able to mount its md devices as /dev/mdX devices (ro, because degraded to one partition per device instead of 2 configured) seems to prove whatever needed to be wherever it needed to be was there, and the only problem had been lack of activation.
tune2fs: Invalid argument while trying to open /dev/md120, and Couldn't find valid filesystem superblock
Naturally, if the array is not even active, it reports zero size and e2fs won't find anything.
It doesn't seem natural to me to see the invalid argument message actually produced instead of something providing some kind of clue to an underlying problem. Apparently "couldn't find" is resulting from some different metadata location on the extX filesystem contained on the md devices, but won't find "anything" is just wrong. Surely there is recognizable stuff there somewhere or it wouldn't work after activation. Doesn't the existant partition type 0xFD provide e2fs a useful clue, or is maybe that what blinds it to what is actually present? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org