{"id":151,"date":"2018-12-20T04:38:35","date_gmt":"2018-12-20T04:38:35","guid":{"rendered":"https:\/\/nillsf.wordpress.com\/?p=151"},"modified":"2018-12-20T04:38:35","modified_gmt":"2018-12-20T04:38:35","slug":"how-to-fix-e2fsck-get-a-newer-version-of-e2fsck","status":"publish","type":"post","link":"https:\/\/nillsf.com\/index.php\/2018\/12\/20\/how-to-fix-e2fsck-get-a-newer-version-of-e2fsck\/","title":{"rendered":"How to fix: "e2fsck: Get a newer version of e2fsck! ""},"content":{"rendered":"

This is going to be a short one, and I hope this will save you some time if you hit this same issue.
\nI recently had a VM that didn’t boot anymore. Going to the serial console, I could see it was trying to run fsck on an attached data disk (actually an LVM on top of 2 disks)- but that failed apparently.<\/p>\n

Step 1: login through serial console and remove that LVM from the \/etc\/fstab.<\/h1>\n

This step is quiet straightforward: you enter the root password and you edit the fstab. I had 1 issue here that my filesystem was mounted read-only, so I also needed to change that quickly, but basically did this:<\/p>\n

mount -o remount,rw \/\nvi \/etc\/fstab #comment out the line that is causing fsck to fail now<\/pre>\n
Step 2: installing updated fsck tool.<\/h1>\n
Removing it from the fstab made my VM come up again, but when trying to run fsck I got this error:<\/p>\n
Output: e2fsck 1.41.12 (17-May-2010)\n\/dev\/vgname\/lvname has unsupported feature(s): 64bit\n\u00a0e2fsck: Get a newer version of e2fsck!<\/pre>\n
This sent me through some ratholes, but finally I found the solution here: https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=1101558<\/a>
\nWhat this does is download the newer version of e2fsck, compile and install it this now allows you to succesfully run fsck:<\/p>\n
Wget https:\/\/www.kernel.org\/pub\/linux\/kernel\/people\/tytso\/e2fsprogs\/v1.43\/<\/a>e2fsprogs-1.43.tar.xz\ntar -xf e2fsprogs-1.43.tar.xz\ncd e2fsprogs-1.43\n.\/configure\nmake\nmake install<\/pre>\n
Run a check on the version of e2fsck<\/p>\n
\ne2fsck -V\ne2fsck 1.43 (17-May-2016)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Using EXT2FS Library version 1.43, 17-May-2016<\/pre>\n
This now allowed me to succesfully check my file system:<\/p>\n
e2fsck -f \/dev\/vgname\/lvname<\/pre>\n","protected":false},"excerpt":{"rendered":"
This is going to be a short one, and I hope this will save you some time if you hit this same issue. I recently had a VM that didn’t boot anymore. Going to the serial console, I could see it was trying to run fsck on an attached data disk (actually an LVM on […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-151","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/comments?post=151"}],"version-history":[{"count":0,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/151\/revisions"}],"wp:attachment":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/media?parent=151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/categories?post=151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/tags?post=151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}