On Wed, Apr 1, 2015 at 11:42 AM, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote: > See below. Perhaps the newer kernel (in latest F21) has regressed in > handling some kinds of errors during mount, or the dracut/systemd > mounting process is less resilient than mounting under a fully booted > system? This is getting even more interesting. Under 3.17.4-301.fc21.x86 from LiveUSB, I could mount, even repair the disk. Since the repair, the on-disk latest kernel (3.18.9-200.fc21) tries to boot, but dracut/systemd time out on mounting sysroot after waiting for quite a while. I don't get a dracut shell anymore so the failure mode has changed. I may try to set a breakpoint to force a shell. I do have an earlier F21 kernel on disk-- 3.18.7-200.fc21 -- and this boots the system without a glitch. After a complete boot with 3.18.7.200, clean shutdown and booting into 3.18.9-200 is still broken, same failure mode. Will try to capture some info from a dracut breakpoint (I'll try mount). At this point this really looks like a regression. cheers, martin -- martin.langhoff@xxxxxxxxx - ask interesting questions - don't get distracted with shiny stuff - working code first ~ http://docs.moodle.org/en/User:Martin_Langhoff -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
