disk check loop... and more problem added...

[divago]

hi all
dunno if this is the right place to post, but... i'm really sad and dunno where asking for help ;_;

today i was (like usual in last weeks) working on my eeepc with gentoo.
then i had to reboot (well, technically i was doing some experiments and i had to reboot several times)

and i said me "/dev/sda1 was mounted X times unchecked, checking forced".
ok
fine
normal fsck routine

then i said "disk error corrected, reboot linux" and froze. after a while i rebooted manually (pressed starting button)

and then he said "disk error detected, check forced". and again "disk errors corrected, reboot linux"
and again
and again
and again
and again...

after 9 or 10 times in a row, i rebooted with live gentoo on usbpen ad did fsck.ext2 manually
then rebooted and started normally
well...
it gave me a lot of errors
libs missing
and like

i did revdep-rebuild
and after 30 minutes it said me "cannot emerge yadda yadda bubba bubba"
dunno why
dunno what to do

really i'm very sad ;_;
i'll need to reinstall everything? ;_;

very sad here ;_;

[Jimini]

Please give us some detailed information about these errors.
What libs are missing?
What does revdep-rebuild want to emerge?

Otherwise it's quite hard to yadda yadda your bubba bubba.

Best regards,
Jimini
_________________
"The most merciful thing in the world, I think, is the inability of the human mind to correlate all its contents." (H.P. Lovecraft: The Call of Cthulhu)

[divago]

[Hu]

Please provide the output of sfdisk -d /dev/sda ; file -s /dev/sd[a-z]* ; nl /etc/fstab ; nl /proc/mounts ; smartctl --log=selftest /dev/sda ; smartctl --log=error /dev/sda ; revdep-rebuild -p -i ; lspci -v ; emerge --info ; emerge --pretend --verbose e2fsprogs. Some of that is just blind guesses to try to extract system information, and may turn out to be irrelevant. My first guess would be a bad disk inducing filesystem corruption, but there is so little concrete information that it is hard to be sure.

[divago]

ok
i tried re-emerging portage and was successful
so i tried re-emerging python (seems to me the one caused this error) and this it gone wrong
output of log file could be loooong
i try to post it inside a [ code ] tag

[divago]

[divago]

[Hu]

[DirtyHairy]

Before spending any time on rebuilding the system, I'd first boot from a live CD and check harddrive health with smartctl. Although the massive corruption you've seen might come from an unclean shutdown, I highly doubt it - ext2 filesystems are always checked after an unclean shutdown, so you'd have noticed right after the shutdown , while your check was triggered by exceeding the maximum mount count. My guess is that the drive has silently gone bad and has caused the corruption, in which case I'd try to recover /etc, /home and /var/lib/portage/world from the defective drive and rebuild the system on a new one.

[divago]

[DirtyHairy]

Using an unjournaled filesystem for a SSD makes sense to me. As for backing up the system for a rebuild, I'd go for the selection I detailed in my previous post. Having /etc and the world file will in principle allow you to rebuild your system in exactly the state it was in. However, I am not sure if keeping /usr/portage and /var/tmp on a SSD is a good idea; the wear on the drive during regular tree updates and especially package compilation is enormous; I'd consider moving them to an external drive (at least /var/tmp).

[divago]

[Hu]

[divago]