Leap 42.1 doesn't boot; goes into emergency mode

Lenovo Ideapad Y410p running a dual boot (Win 7 + Leap 42.1). Everything had been fine so until last night, when I noticed it took a bit longer than usual to boot into KDE. Turned the laptop on today afternoon, and it went into emergency mode.

Here is what I see during boot

   21.460091] ata6.00: exception Emask 0x0 SAct 0x40000 SErr 0x40000 action 0x0
   21.460611] ata6.00: irq_stat 0x40000
   21.461115] ata6: SError: { CommWake }
   21.461561] ata6.00: failed command: Read FPDMA QUEUED
   21.461993] ata6.00: cmd 60/08:90:08:76:18/00:00:62:00:00/40 tag 18 ncq 4096 in
   21.461993]             RES 41/40:00:00:76:18/00:00:62:00:00/ Emask 0x409 (media error) <F>
   21.462902] ata6.00: status: { DRDY ERR }
   21.463363] ata6.00: error: { UNC }
   21.795993] blk_update_request: I/O error, dev sda, sector 1645770248
   21.796625] XFS (sda7): metadata I/O error: block 0x3707d688 ("xfs_trans_read_buf_map") error 5 numblks 8
             **] A start job is running for /home (30s / 1min 30s)

It stays stuck at this point for quiet a long time, and the time (indicated in the last line) keeps increasing till about 4min 15s

And then it shows this

    2.936134] nouveau E     PBUS][0000:01:00.0] MMIO write of 0x000000002 FAULT
    3.024200] nouveau E     PBUS][0000:01:00.0] MMIO write of 0x000000000 FAULT a
    3.024379] nouveau E     DRM] Pointer to TMDS table invalid
    3.024381] nouveau E     DRM] Pointer to TMDS flat panel table invalid
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):

Pressing Control-D doesn’t do anything at this stage, and entering root password takes me to the command line.

Newbie here but from what I could make out, it seems to be some disk error with the /dev/sda7 XFS partition, and that is my /home partition. Any ideas on how I can fix this?

Thank you in advance.

There’s a good chance that you have a failed disk.

You could try booting live media, and run “smartctl” tests. If the disk has failed, then the “fix” is to replace the disk and restore from backups.

Looks like something went wrong with the file system on home so it won’t mount

If you don’t know first determine which partition contains home

fdisk -l

will give clues

  1. Unmount sdX#. where X# is the partition containing home
  2. Run “xfs_repair sdX#”. where X# is the partition containing home


Note a failing drive could be the problem run smartctl /dev/sdX whee X is the drive letter

Thank you nrickert & gogalthorp.

It’s past midnight here, but will try what you advised first thing in the morning and get back to you.