On Fri, Jul 8, 2016 at 7:06 PM, Terrance Eck
On 7/8/2016 6:35 PM, Chris Murphy wrote:
On Fri, Jul 8, 2016 at 1:45 PM, Terrance Eck
wrote: I get the following display on the monitor when trying to boot Leap 42.1
Welcome to emergency mode! After logging in, type "journalctl -xb to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or press Control-D to continue): [ 21.426046] systemd-journald[523]: File /var/log/a848146 ... e824/system.journal corrupted or uncleanly shutdown, renaming and replacing.
I've issued the suggested commands without much luck in getting my system booted. Can someone help me get the file system corrected (if possible) and booted again.
Insert a USB stick and mount it to /sysroot
mount /dev/sdb1 /sysroot journalctl -b > /sysroot/journal.log umount /sysroot reboot
And now attach journal.log to a reply email or post it somewhere and provide the URL.
See the attached file. It was generated by the failed system using the command journalctl -b > /mnt/journal.log
I could not find where /sysroot is located so I just mounted the USB stick on /mnt.
Hope the information helps someone with my filesystem problem.
Terry
Sorry if this post is too large for some people.
Jul 08 19:11:45 linux-04te kernel: BTRFS info (device sdb3): disk space caching is enabled Jul 08 19:11:45 linux-04te kernel: BTRFS: has skinny extents Jul 08 19:11:46 linux-04te systemd[1]: Mounted /sysroot. The Btrfs rootfs is fine. Jul 08 19:11:52 linux-04te systemd[1]: Starting File System Check on /dev/disk/by-uuid/df4040f2-8331-4e8b-838e-3855ebf13d5b... Jul 08 19:11:52 linux-04te systemd-fsck[830]: /sbin/fsck.xfs: XFS file system. Jul 08 19:11:52 linux-04te systemd[1]: Started File System Check on /dev/disk/by-uuid/df4040f2-8331-4e8b-838e-3855ebf13d5b. Jul 08 19:11:52 linux-04te systemd[1]: Mounting /home... Jul 08 19:11:52 linux-04te kernel: SGI XFS with ACLs, security attributes, realtime, no debug enabled Jul 08 19:11:52 linux-04te kernel: XFS (sdb4): Mounting V5 Filesystem Jul 08 19:11:53 linux-04te kernel: XFS (sdb4): Starting recovery (logdev: internal) Jul 08 19:12:03 linux-04te systemd[1]: home.mount mount process exited, code=killed status=9 Jul 08 19:12:03 linux-04te systemd[1]: Failed to mount /home. Jul 08 19:12:03 linux-04te systemd[1]: Dependency failed for Local File Systems. Jul 08 19:12:03 linux-04te systemd[1]: Dependency failed for Postfix Mail Transport Agent. Jul 08 19:12:03 linux-04te systemd[1]: Triggering OnFailure= dependencies of local-fs.target. Jul 08 19:12:03 linux-04te systemd[1]: Unit home.mount entered failed state. The XFS /home has failed to mount, journal replay failed. There is a chance you can run xfs_repair from the emergency shell if xfsprogs is in the initrd. Otherwise you'll need to boot from alternate media. If you don't have a backup of /home, you should probably do this booted from a livecd so you can use xfs_repair -n so you can see what the complaints are, and the chance of fixing it up. You're almost certainly better off using a newer xfsprogs, e.g. from a Tumbleweed LiveCD for the actual repair, but it really depends on what the problem is. As it's a v5 file system, I personally would use the most recent xfsprogs I could get my hands on. Jul 08 19:12:03 linux-04te kernel: XFS (sdb4): _xfs_buf_find: Block out of range: block 0x7fffffff8, EOFS 0x34f32800 Definitely do not use xfs_repair -l unless an XFS expert (not me) or developer says it's a good idea to do it, it's a big hammer. -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org