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