{"id":1657,"date":"2016-03-04T16:43:48","date_gmt":"2016-03-05T00:43:48","guid":{"rendered":"http:\/\/systemsolver.com\/StatlerBlog\/?p=1657"},"modified":"2016-03-04T16:43:48","modified_gmt":"2016-03-05T00:43:48","slug":"linux-repair-partition-fsck-check-disk","status":"publish","type":"post","link":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/2016\/03\/04\/linux-repair-partition-fsck-check-disk\/","title":{"rendered":"linux repair partition fsck check disk before clonezilla image"},"content":{"rendered":"<p><a href=\"http:\/\/clonezilla.org\/\">Clonezilla<\/a> kept making bad images of my main partition, which I only found out about when trying to restore them (in this case to a different computer)<\/p>\n<p>Here&#8217;s how I went about fixing the partitions in question:<\/p>\n<ol>\n<li>Download <a href=\"https:\/\/www.archlinux.org\/download\/\">archlinux iso<\/a> and put on usb drive using <a href=\"http:\/\/www.pendrivelinux.com\/yumi-multiboot-usb-creator\/\">Yumi<\/a><\/li>\n<li>Boot into archlinux<\/li>\n<li>Find the partition number and partition type.<br \/>\n<a href=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/parted.png\" rel=\"attachment wp-att-1658\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-1658\" src=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/parted.png\" alt=\"parted\" width=\"713\" height=\"389\" srcset=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/parted.png 713w, https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/parted-300x164.png 300w\" sizes=\"auto, (max-width: 713px) 100vw, 713px\" \/><\/a><\/p>\n<ol>\n<li>sudo parted<\/li>\n<li>print\n<ul>\n<li>Near top is the drive being looked at, i.e. \/dev\/sda<\/li>\n<li>The first column is the partition number which would translate to, i.e. \/dev\/sda1 or \/dev\/sda7<\/li>\n<li>The File system column gives information needed for the fsck command.<\/li>\n<li>Only fsck on ext&lt;x&gt; file systems (use windows for fat32 or ntfs)<\/li>\n<\/ul>\n<\/li>\n<li>quit<\/li>\n<\/ol>\n<\/li>\n<li>Check for mounted partitions (we don&#8217;t want to fsck on mounted partitions)<br \/>\n<a href=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/mounted-partitions.png\" rel=\"attachment wp-att-1659\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-1659\" src=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/mounted-partitions.png\" alt=\"mounted partitions\" width=\"732\" height=\"427\" srcset=\"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/mounted-partitions.png 732w, https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-content\/uploads\/2016\/03\/mounted-partitions-300x175.png 300w\" sizes=\"auto, (max-width: 732px) 100vw, 732px\" \/><\/a><\/p>\n<ol>\n<li>df -aTh\n<ol>\n<li>In the case of the image above we could not fsck \/dev\/sda6, \/dev\/sda7, or \/dev\/sda1<\/li>\n<li>The image above is from an active linux mint 17 session.<\/li>\n<li>When booting from ArchLinux you should not see any of the \/dev\/sda partitions mounted<\/li>\n<\/ol>\n<\/li>\n<li>no need to exit<\/li>\n<\/ol>\n<\/li>\n<li>Unmount if needed\n<ol>\n<li>umount \/dev\/&lt;partition&gt;<\/li>\n<li>Example: umount \/dev\/sda6<\/li>\n<\/ol>\n<\/li>\n<li>Check the partition integrity<br \/>\nNo screen shot because I couldn&#8217;t do that in Arch Linux<\/p>\n<ol>\n<li>fsck.ext4 \/dev\/sda7<\/li>\n<li>Obviously, change the ext4 to the type matching in the the parted screen.<\/li>\n<li>Obviously, change the sda7 to match the parted screen<\/li>\n<li>There will be a report<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<p>In my case the fsck reported something like the block had a date in the future. While it reported this it also fixed it. Running the fsck command on that partition again did not show the same error message.<\/p>\n<p>I just hope that this fixed my problem creating a good image with clonezilla!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Clonezilla kept making bad images of my main partition, which I only found out about when trying to restore them (in this case to a different computer) Here&#8217;s how I went about fixing the partitions in question: Download archlinux iso and put on usb drive using Yumi Boot into archlinux Find the partition number and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-1657","post","type-post","status-publish","format-standard","hentry","category-general"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts\/1657","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/comments?post=1657"}],"version-history":[{"count":0,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/posts\/1657\/revisions"}],"wp:attachment":[{"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/media?parent=1657"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/categories?post=1657"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/systemsolver.goodhealthyday.com\/StatlerBlog\/wp-json\/wp\/v2\/tags?post=1657"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}