1 |
On Wed, Mar 3, 2010 at 4:24 AM, Stroller <stroller@××××××××××××××××××.uk> wrote: |
2 |
> There seem to have been a few people posting with filesystem corruption in |
3 |
> the last week or two. It seems to be my turn, so I hope it isn't contagious. |
4 |
> The cause here is quite clear - whilst rummaging in the server cupboard |
5 |
> yesterday, power to the machine was accidentally disconnected. |
6 |
> |
7 |
> I have booted with a live CD & run `reiserfsck --fix-fixable` on the |
8 |
> filesystem, but nevertheless when I attempt to boot the system I get a |
9 |
> "failed to open the device... no such file or directory" message, followed |
10 |
> by another error as per subject line. |
11 |
> |
12 |
> However, you will see from this screenshot (taken with an IP KVM) that the |
13 |
> filesystem does indeed seem to have been mounted successfully, if read-only: |
14 |
> |
15 |
> http://linux.stroller.uk.eu.org/fs-corruption.png |
16 |
> |
17 |
> All I did here was log in with the root password. |
18 |
> |
19 |
> |
20 |
> When I boot with a live CD I can mount, read & write the filesystem: |
21 |
> |
22 |
> root@sysresccd /root % mount -v -L root /mnt/gentoo |
23 |
> mount: you didn't specify a filesystem type for /dev/sda3 |
24 |
> I will try type reiserfs |
25 |
> /dev/sda3 on /mnt/gentoo type reiserfs (rw) |
26 |
> root@sysresccd /root % ls /mnt/gentoo |
27 |
> bin boot dev etc home lib mnt opt proc root sbin sys tmp usr |
28 |
> var |
29 |
> root@sysresccd /root % touch /mnt/gentoo/foo |
30 |
> root@sysresccd /root % echo foobar >> /mnt/gentoo/foo |
31 |
> root@sysresccd /root % ls -lh !!:$ |
32 |
> ls -lh /mnt/gentoo/foo |
33 |
> -rw-r--r-- 1 root root 7 2010-03-03 11:18 /mnt/gentoo/foo |
34 |
> root@sysresccd /root % cat !!:$ |
35 |
> cat /mnt/gentoo/foo |
36 |
> foobar |
37 |
> root@sysresccd /root % rm !!:$ |
38 |
> rm /mnt/gentoo/foo |
39 |
> rm: remove regular file `/mnt/gentoo/foo'? y |
40 |
> root@sysresccd /root % |
41 |
> |
42 |
> All the important system stuff on this PC is on a single partition. I have |
43 |
> two other drives attached at /mnt/space & /mnt/morespace - they are XFS and |
44 |
> I have run xfs_repair on both of them, which completes quickly indicating no |
45 |
> problems. |
46 |
> |
47 |
> I'm not really sure how to proceed next. I feel the problem is indeed on |
48 |
> this reiserfs filesystem, the root filesystem with the label "root". I can't |
49 |
> help thinking that the problem is not that the system "failed to open the |
50 |
> device", but instead maybe that there's an important system file missing |
51 |
> that means the init script (or whatever responsible for mounting the |
52 |
> fiesystem) is not properly returning 0. Does this seem possible? Maybe the |
53 |
> reiserfs handler for mount is somehow broken (performing the mount, but not |
54 |
> returning 0, or perhaps broken in such as was it is able to mount read-only |
55 |
> but not read-write). |
56 |
> |
57 |
> I am tempted to chroot into the system and re-emerge system & baselayout. If |
58 |
> I'm correct in this above guess then re-emerging the correct file will fix |
59 |
> the problem. Right? |
60 |
> |
61 |
> `reiserfsck --help` shows some other options besides the simple |
62 |
> --fix-fixable - I assume the "expert option" of --scan-whole-partition is |
63 |
> unsafe, but what about the --rebuild-sb or --rebuild-tree? Can I safely run |
64 |
> these? Am I advised to run these? |
65 |
> |
66 |
> Stroller. |
67 |
|
68 |
Hi Stroller, |
69 |
Sorry for your problems. I've had a rash of machine problems over |
70 |
the last 6 weeks. No fun. I feel for you. |
71 |
|
72 |
In my most recent case what looked like a simple disk corruption |
73 |
problem was really a prelude to the drive just plain going bad. Have |
74 |
you tried smartctl to see what it says about the drive at this point? |
75 |
|
76 |
It would be even more frustrating to chroot in, do all the work, |
77 |
think you had it fixed and then the underlying foundation of your |
78 |
house crumbles beneath you 3 weeks from now. |
79 |
|
80 |
Good luck, |
81 |
Mark |