root password for maintenance or Control-D to continue

JustaGuy

Renowned Member
Jan 1, 2010
324
2
83
This all started after a reboot hung for over 5 minutes (Reconfigured the network) & I used the power button to reboot.

I was lost for a day or so on what to do- The following is how it was resolved, for the sake of whoever's next.

I entered a shell & looked at the the log:

File: /var/log/fsck/checkfs

Log of fsck -C -R -A -a
<date>

<version>
fsck: cannot check /dev/sdc1: fsck.xfs not found

/dev/pve/data: recovering journal
/dev/pve/data contains a filesystem with errors, check forced.
/dev/pve/data: /lost+found is not a directory (ino=14)


/dev/pve/data: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
/dev/sda1: clean, 28/32768 files, 10511/131072 blocks
fsck died with exit status 4

<date>

Originally I tried to run fsck from a LiveCD & found my CD-ROM was dead.
Then ran fsck & xfs_repair from a LiveCD installed to a USB stick (used a GPL app at http://www.linuxliveusb.com/) and they returned no errors.
I didn't do anything with LVM because I figured I'd make it worse since I don't quite know what I'm doing in LVM. So I gave up on that route.


Now in the shell that I got to during the failed boot I just did:

fsck /dev/pve/data

& got:

/lost+found is not a directory (ino=14)

Unlink<y>? yes

/lost+found not found. Create<y>? yes

Unattached inode 14
Connect to /lost+found<y>? yes



Then did again:

fsck /dev/pve/data

& got:

/dev/pve/data: clean, 18/786864 files, 89877/3146752 blocks



So then I did:

shutdown -r -F now

And the next reboot was without issue.