It is possible that mdadm isn't faulty -- I have similar problems with my root partition (JFS) since upgrade to hardy. I didn't originally report it, because I was using fairly broken system and non-standart suspend method (uswsusp), but now happened the same with intrepid.
In my case: 1) computer suspends fine 2) upon resume, comuter hangs with 'waking...' message, and responds to nothing (even to sysrq) 3) after reboot, superblocks do not match - one reports "FM_CLEAN" and lower serial? number (item 18), the other "FM_MOUNT" and higher number 4) fsck.jfs refuses to check such fs, I've got to manually edit superblocks with jfs_debugfs so they match each other and reboot with power cord plugged to perform fsck -- mdadm problems after suspend https://bugs.launchpad.net/bugs/181888 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
