dmraid fails to handle status set by ICH10R Bios

[Raptor 2101]

Binary package hint: dmraid

While exchanging a "damaged" Disk (some SMART-values recommended it) i suffer a strange "bug". Cause of a needed reboot i used the BIOS built-in functionality to add the new disk to my RAID0. After booting all works fine (hidden IO from the leading disk to the new disk), except one thing. "dmraid -s" show me a status named "nosync":

*** Group superset isw_bjcjahbjci
--> Active Subset
name : isw_bjcjahbjci_system
size : 488390912
stride : 128
type : mirror
status : nosync
subsets: 0
devs : 2
spares : 0

After a half hour, the IO disappear and the RAID is in sync (checked it, with booting from the new disk only attached to the PC) but the status from the RAID still remains on "nosync". After forcing the raid to rebuild via dmraid (dmraid -R isw_bjcjahbjci_system) the status jumps immediately to ok, but the background IO appears again an syncing the raid again.

Both behaviors are strange. dmraid should report the correct status. If a raid is rebuilding, it shouldn't reported as "ok" and if the rebuilding is done it should report as "ok".

No messages regarding dmraid appear in syslog neither in dmesg.

Ubuntu -Version: Lycid Lync 10.04 LTS, package-version:1.0.0.rc16-3ubuntu2

[Phillip Susi (psusi)]

Please install the dmeventd package and see if it resolves the issue.

[Launchpad Janitor (janitor)]

[Expired for dmraid (Ubuntu) because there has been no activity for 60 days.]

[Jason McMullan (jason-mcmullan)]

I found that simply doing:

# dmraid -R isw_ccfdgbaahj_Volume0

after the sync was complete was sufficient to move the raid to the 'status: ok' state.

Installing dmeventd did not seem to make a difference.

[Henk-Jan (henk-jan)]

After swapping faulty disk and booting Ubuntu, I could check syncing progress with "dmsetup status".
After this was done, status with "dmraid -s" still was 'nosync'.

[Phillip Susi (psusi)]

It seems that dmraid does not really support properly updating the metadata to handle events like this. It seems that Intel has been focusing their effort on adding support for their metadata format to mdadm and that going forward, hopefully it will take over handling intel fakeraid arrays properly.