Bootpartition won't mount, fsck finds no errors

Question

Hi guys,
got a strange situation here. My Bootpartition /dev/sda2 won't mount in Arch anymore.
mount /dev/sda2:
mount: wrong fs type, bad option, bad superblock on /dev/sda2,
missing codepage or helper program, or other error
Manchmal liefert das Syslog wertvolle Informationen – versuchen
Sie dmesg | tail oder so
The same error appers during boot. I don't know how Arch can boot without bootpartition but ist does...
Another strange thing is that it mounts fine in Mandriva running on the same machine. Also testdisk under Windows didn't complain.
dmesg | tail
EXT2-fs (sda2): error: corrupt root inode, run e2fsc
e2fsck /dev/sda2
e2fsck 1.41.14 (22-Dec-2010)
archboot: sauber, 43/36288 Dateien, 33179/144584 Blöcke
grep -i archboot /etc/fstab
LABEL=archboot /boot ext2 defaults 0 1
file -s /dev/sda2
/dev/sda2: Linux rev 1.0 ext2 filesystem data, UUID=c477713e-ff47-40f3-92f0-537291f24937, volume name "archboot
So what now? Any help is appreciated.

Answer 1

no changes to any partitions were made, just did a fatal "pacman -Syu"...
i removed the /boot completely from fstab and tried to mount the partition manually.
i also recreated the whole partition under ubuntu. copied the files out, deleted the entire partition, recreated it and copied the files back.
arch linux still can't mount it.
also when i'm trying to mount my jfs partition, the "mount" command hangs completely. even "kill -SIGKILL $pid" can't get rid of it.
the jfs partition also mounts fine under ubuntu, i ran tests on every partition under ubuntu, they're all clean.
mounting an jfs partition don't give any logfile entry, dmesg is also empty. it's just hanging. the funny thing is, that ext4 and vfat partitions are mounting fine.
could something be wrong with hal or dbus?
here's e2fsck output:
e2fsck -pvf /dev/sda8
      35 inodes used (0.15%)
       4 non-contiguous files (11.4%)
       0 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 10/6/0
   35980 blocks used (37.34%)
       0 bad blocks
       0 large files
      22 regular files
       4 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
       0 symbolic links (0 fast symbolic links)
       0 sockets
      26 files
--------EDIT:
finally found it!
for some reason (i don't know why) the /boot partition was not mounted during update and thus the kernel26 image was written into the /boot directory of the root partition instead of the /boot partition (where it belongs). this means on next bootup the system was booting with the older kernel but the updated system. maybe some things in filesystem handling were changed between the two versions of the kernel.
i mounted the arch partitions within ubuntu and copied the files from the /boot directory to the partition which should be mounted in /boot on startup.
everything's working now.
Last edited by thok (2011-03-22 16:44:32)