Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yesterday, I rebooted my CentOS 7 laptop after couple of days and it got updated automatically. I tried to take a backup image of the root (/) partition with clonezilla, but it failed with the error message "extfsclone.c bitmap error at group 1".
I did lots of research and tried the following options.
1. Tried using the option fsck-chk-part as part of clonezilla backup, but got the same error.
2. Tried fsck.ext4 /dev/sda6 in partedmagic and got an error message saying "e2fsck is old. Please update to new version".
3. Tried booting with latest elementary OS live cd and ran the same command, but it did not report any errors.
4. Opened up gparted and it shows an exclamation mark (!) at /dev/sda6 and when I double click it, it shows "/dev/sda6 has a bad superblock". Gparted shows the fstype as ext4.
5. I booted with hiren boot cd and tried partition recovery and it shows /dev/sda6 as "unformatted".
I saw couple of guides related to fixing the superblock and I will try them today.
But, my question is can it be fixed by simply formatting the /dev/sda6 partition?
my question is can it be fixed by simply formatting the /dev/sda6 partition?
If there is nothing wrong with your hardware then you can fix the bad superblock problem by formatting the partition. However if you format the partition then you will lose all of your data on the partition.
Before you do that I suggest that you try running fsck against an alternate superbock. Here is an explanation of how to do that:
Thanks for your reply. I tried this with the backup at 32768. It appeared to have fixed something, but when I run clonezilla, I still got the bitmap error. I ran the same e2fsck and tried the backup super block from 32768. the command runs, I get the final output as "file system was modified" though clonezilla is still reporting the same error.
I mounted /home on /dev/sda7 where most of my data resides. So, if formatting /dev/sda6 will resolve the issue, I will try and reinstall linux.
I tried the imaging with todobackup, and it is reporting that /dev/sda6 is unformatted. I did a surface test and it came out clean.
are there any other HDD diagnostic tool that I can use to confirm that it is not a hardware issue?
Also, should I try the backup super block from different location, other than 32768?
No, Gparted is not showing any errors. Even running sudo fsck.ext4 -f -v -y /dev/sda6 is not throwing any errors. But, clonezilla is continuing to report the bitmap error.
If everything works with the file system except clonezilla then there is likely a bug in clonezilla. If that is the case then I suggest you report the clonezilla bug to the clonezilla developers and try using a different backup program. I recommend that you use rsync or one of the GUI programs which interface with rsync to do your backups.
Yes, the CentOS update added two new boot entries, one with debugging. I tried the new entry without debugging and did not boot. The previous kernel entry boots fine with out any issues.
Ummm.. The documentation for clonezilla has one warning: "The partition to be imaged or cloned has to be unmounted." (reference: http://clonezilla.org/)
It is rather unlikely that the root partition is unmounted (it might accept single user mode with root mounted read-only though).
Any time a filesystem is actually mounted, and active, it will have bitmaps modified in memory, and possibly only partially updated on disk. This always leads to imaging problems as the resulting copy is corrupted due to the active modification of the partition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.