On 3 Mar 2010, at 17:14, Willie Wong wrote:
On Wed, Mar 03, 2010 at 04:16:50PM +0000, Stroller wrote:
Many thanks for your help, Willie!
About 13 items. Is this unlucky?
http://linux.stroller.uk.eu.org/fs-corruption-dev.png
Okay, something is screwed up with udev. Is udev started?
Ah!
Ok... this is shown as an error when before the "failed to open the
device" message.
http://linux.stroller.uk.eu.org/fs-corruption.png
Startin udevd... error getting signalfd
Is it upgraded recently?
chroot # genlop udev | tail -n 4
Tue May 26 17:26:46 2009 >>> sys-fs/udev-124-r2
Thu Jun 25 06:05:37 2009 >>> sys-fs/udev-141
Mon Dec 21 04:57:20 2009 >>> sys-fs/udev-146-r1
chroot #
The system last booted ok in October and, until yesterday, has been up
since then. So this December update may well be to blame.
Any config files in /etc that needs updating?
Nope.
chroot # etc-update
Scanning Configuration files...
Exiting: Nothing left to do; exiting. :)
chroot #
Is udev directory in /etc okay?
All looks ok to me:
chroot # ls -l /etc/udev/*
-rw-r--r-- 1 root root 277 2009-12-21 04:56 /etc/udev/udev.conf
/etc/udev/rules.d:
total 24
-rw-r--r-- 1 root root 55 2009-10-11 09:38 30-svgalib.rules
-rw-r--r-- 1 root root 4311 2009-09-11 23:02 70-nut-usbups.rules
-rw-r--r-- 1 root root 1606 2008-12-22 12:33 70-persistent-cd.rules
-rw-r--r-- 1 root root 440 2009-12-21 04:57 70-persistent-net.rules
-rw-r--r-- 1 root root 28 2009-07-22 03:04 99-fuse.rules
chroot #
At this point I don't think your problem is necessarily with the
harddrive itself: I think we now know why fsck cannot open file or
device.
Check /var/log/emerge.log or the portage elogs. Did you upgrade
baselayout recently?
Yes, upgraded to baselayout-1.12.13 at the same time I udev was
upgraded:
chroot # genlop baselayout | tail -n 3
Thu Feb 12 09:36:25 2009 >>> sys-apps/baselayout-1.12.11.1
Mon Dec 21 01:25:32 2009 >>> sys-apps/baselayout-1.12.13
chroot #
What I'm inclined to do now, having taken an image of the drive (I
used ddrescue, which showed no errors) is try `reiserfsck --rebuild-
tree` on the partition, "just to be sure". I get the impression this
is probably quite safe, but I have a backup anyway.
I, too, suspect that won't fix the problem, so after that I guess I'll
try remerging udev & baselayout. I suspect remerging --empty may be
necessary, but any other suggestions welcome.
Stroller.
