How to fix errors on ext4 partition (Ubuntu 12.04)?

Question

linux

In general, the situation is like this. Did resize the disk (when trying to install Backtrack)
Resize ended incorrectly, as a result, the system does not boot. After chkdsk /F, the windows partition started to boot, but everything is still bad with ubuntu. When trying to download - black screen.
I booted from the Live CD, the sections are visible, everything is OK, the data is in place.
Output of fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000695ca
Device Boot Start End Blocks Id System
/ dev / sda1 * 2048 558 841 855 279 419 904 83 the Linux
/ dev / sda2 558 841 856 870 467 583 155 812 864 7 the HPFS / the NTFS / the exFAT
/ dev / sda3 870,467,584 972,867,583 51,200,000 7 the HPFS / the NTFS / the exFAT
/ dev / sda4 972,869,630 976,771,071 1,950,721 5 the Extended
/ dev / sda5 972 869 632 976771071 1950720 82 Linux swap / Solaris
Output fsck.ext4 -p /dev/sda1 /dev/sda1 contains a file system with errors, check forced.
/dev/sda1: Duplicate or bad block in use!11
/dev/sda1: Multiply-claimed block(s) in inode 28542: 4291065 4291066 4291067 4291068 4291069 4291070 4291071 4291072
.............. ...................................
............... .................................
/dev/sda1: (There are 5671 inodes containing multiply-claimed blocks.)
/dev/sda1: File /???/alsactl (inode #18927, mod time Wed Apr 4 04:12:07 2012)
has 21 multiply-claimed block(s), shared with 1 file(s):
/dev/ sda1: ... (inode #4718598, mod time Wed Apr 4 04:12:07 2012)
/dev/sda1:
/dev/sda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(ie, without -a or -p options)
Content of /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=2deb8529-27a5-46a5-9b3e-0eafb90f746d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=f7394914-0a5a-4833-9645-4f696023b27c none swap sw 0 0
Sample output of fsck.ext4 /dev/sda1 (without -p option)
..............
File /???/brltty (inode #19653, mod time Tue Apr 10 20:06: 23 2012)
has 107 multiply-claimed block(s), shared with 1 file(s):
... (inode #4718605, mod time Tue Apr 10 20:06:23 2012)
Clone multiply-claimed blocks<y>? yes
clone_file_block: internal error: can't find dup_blk for 5043283
...............
Question: What to do and how to live on? I don't want to reinstall the system from scratch

Answer 1

Some strange errors ... If there are no other solutions, you can take somewhere an external screw of sufficient size, dump the image of the broken partition onto it using dd (preferably to a file), then format the partition, mount this backup image in read-only mode and restore data from it with some kind of rsync or double tar through a pipe (you need to select the parameters so that the copying is preserving all attributes, access rights, timestamps, etc.)

Answer 2

try fsck.ext4 -f /dev/sda1
will manually ask questions about the repair of each glitch in the fs, decide on the spot

Answer 3

For a note who will face:
This error is a bug in e2fsck, link to launchpad'e
For Ubuntu 12.04 and above, it is necessary (and sufficient) to update the utilities manually to:
e2fslibs_1.42.12-1
e2fsprogs_1.42.12-1
For example from here: launchpad.net
Faced a similar problem after a power outage and there is a suspicion that fsck killed the file system, which unfortunately could not be completely restored.