New answers tagged fsck
A few things: First, do you really mean /dev/sdc? Normally, it'd be a partition on the disk (e.g.,: /dev/sdc1). What does fdisk -l /dev/sdc say? You can check what's actually mounted by looking in /proc/mounts. It's a plain text file, I suggest grep sdc /proc/mounts to see if its mounted somewhere. Then you can unmount it. Check dmesg to see if the kernel ...
Since I wasn't able to find any other solution, I reformatted the EXT4 partition. This eliminated the bad geometry error. Wish I knew why.
Run e2fsck -y to say yes to all questions automatically instead of having to manually say yes a million times.
Have a look at the ext4 feature uninit_bg (man tune2fs). Using that may reduce e2fsck time: dumpe2fs -h /dev/sdx | grep "^Filesystem features:"
Actually, fsck ended today. Rebooted and everything worked great!
The solution to your problem of a failed or problematic disk is to restore from backups. If it is a hardware problem, replace the disk first. Attempting to rebuild a broken filesystem is an extremely time consumming operation that seldom results in good results.
The filesystem doesn't care about disk geometry; this is a partition table problem. I suggest that you make a dump of the partition table, check the result and overwrite the partition table with this dump. That should correct the CHS entries. sfdisk -d /dev/sdx >sdx.txt cat sdx.txt sfdisk /dev/sdx <sdx.txt
Top 50 recent answers are included