On Mon, Jan 9, 2017 at 11:54 AM, François Patte <francois.patte@xxxxxxxxxxxxxxxxxxxx> wrote: > janv. 09 19:26:12 bhaskara systemd[1]: Stopped /dev/dm-5. > janv. 09 19:26:12 bhaskara systemd[1]: Stopped > /sys/devices/virtual/block/dm-5. > janv. 09 19:26:12 bhaskara blkdeactivate[10933]: [DM]: deactivating > crypt device luks-63be2188-bd3d-4552-9a8b-9481d942fb46 (dm-5)... done > janv. 09 19:26:12 bhaskara kernel: md122: detected capacity change from > 42951770112 to 0 > janv. 09 19:26:12 bhaskara kernel: md: md122 stopped. > janv. 09 19:26:12 bhaskara kernel: md: unbind<sdb2> > janv. 09 19:26:12 bhaskara kernel: md: export_rdev(sdb2) > janv. 09 19:26:12 bhaskara kernel: md: unbind<sda2> > janv. 09 19:26:12 bhaskara kernel: md: export_rdev(sda2) > janv. 09 19:26:12 bhaskara kernel: BUG: unable to handle kernel paging > request at ffff8f3f29ea8000 OK well it's a kernel bug, seems like to me. The simplest thing to do is try a different kernel. But which one? I'm not seeing immediately relevant patches for md in either 4.8.16 or 4.8.17. What kernel version are you using now? If it's 4.18.15, sure you can try either 4.18.16 (which is in updates-testing) or you can get 4.8.17 from koji. Looks like 4.9.2 is building now in koji and should be done shortly so you could also try that one. If it reproduces with 4.9.2, for sure you should try to get more information. If you can ssh into the system remotely so you can get a complete dmesg that'd be useful. If ssh gets killed off before the bug, then you might see if any of these ideas will get you more information on the nature of the failure. https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 Even if it's not shutting down, maybe the special logging instructions for the "eventually shuts down" case will still log something useful that you can check out at the next reboot. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
