F19 raid 1 stuck read only after reboot

[lee]

Alan Gagne <alanjgagne at gmail.com> writes:

>> >>/  "SMART is not a reliable warning system for impending failure
>> />/  Maybe not, but when I had one of these drives going bad about a year ago.
>> />/  It did a great job of warning that I had an impending drive failure.
>> />/  The relocated sector count would jump in small blocks over time.
>> /
>> Interesting, did you get a warning message?
>
> Yes, Root got an email on the first occurrence and then after each re-boot.
> Also there was something in logwatch email.

Cool, good to know :)

>> />/  Jul 19 07:35:26 knucklehead.xxxx.com kernel: device-mapper: table:
>> />/  253:4: linear: dm-linear: Device lookup failed
>> />/  Jul 19 07:35:26 knucklehead.xxxx.com kernel: device-mapper: ioctl:
>> />/  error adding target to table
>> /
>> It seems likely that this is what causes your problem.  When you google
>> for the error message, there are a lot of reports about it.  You could
>> look into them and try to figure out how to solve the issue --- someone
>> said old meta information caused it, someone else said removing a
>> package that provides dmraid fixed it for them ...
> Yea, I have been looking at those. I was hoping that between here and
> filing a bug
> I would get the best answer.

The dmraid package seems to be installed by default.  I'd try to remove
it.


-- 
Fedora release 19 (Schrödinger’s Cat)