On Sun, 2003-11-02 at 14:37, Jerry Feldman wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Sat, 01 Nov 2003 14:24:41 -0800 Tom Nielsen <tom@neuro-logic.com> wrote:

...

I just got 9.0 loaded and everything right where I wanted it when I just had to screw around and cause a problem.

I was trying to transfer information from my CF card reader and I couldn't get it to stop so I hit the reset button on my computer. Ya, I know it was stupid, but something was locked up and I didn't know what. Well, upon rebooting, I had a ton of errors, which would be expected, including not being able to get my reiserfs systems mounted. / and /home wouldn't mount and during bootup, I got a message saying it couldn't fsck and that I would have to do it manually. I tried tweaking and playing and finally got to KDE. The problem was that it would reboot itself have way through loading. I managed to get into Gnome just fine.

So, what is the correct way to fsck my / and /home partitions? I read the man page but it made about as much sense to me as reading it in a foreign language. So, any help would be great!! fsck will run automatically when you transition from single to multi-user mode during bootup. Or, you can run it manually. You must be in single user mode to fsck root, AND the root file system must be mounted read-only. SuSE generally does this for you when you either boot up into run level 1 or change to run level 1 from other run levels.

The other file systems must be unmounted. If you try to run fsck on a rw root or mounted file system, you can do bad things.

Here isi what I generally use: fsck -fsy /dev/hda1 /dev/hda2 The options are: f == force s == serial (in other words run one at a time). y == answere yes to all questions (can be dangerous).

Many of the options are file system specific (such as ext2 or reiserfs), but this is reasonably generic.

From what I understand it's supposed to run automatically, but it told me it couldn't do it and I would have to do so manually. Manually??!! I don't do anything manually. So, at this point, how do I unmount, or set it as read only, to check?

Thanks for the commands. As soon as I figure out how to do the read only thing, I'll try it. Tom

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Sat, 01 Nov 2003 14:24:41 -0800 Tom Nielsen <tom@neuro-logic.com> wrote:

...

I just got 9.0 loaded and everything right where I wanted it when I just had to screw around and cause a problem.

I was trying to transfer information from my CF card reader and I couldn't get it to stop so I hit the reset button on my computer. Ya, I know it was stupid, but something was locked up and I didn't know what. Well, upon rebooting, I had a ton of errors, which would be expected, including not being able to get my reiserfs systems mounted. / and /home wouldn't mount and during bootup, I got a message saying it couldn't fsck and that I would have to do it manually. I tried tweaking and playing and finally got to KDE. The problem was that it would reboot itself have way through loading. I managed to get into Gnome just fine.

So, what is the correct way to fsck my / and /home partitions? I read the man page but it made about as much sense to me as reading it in a foreign language. So, any help would be great!! fsck will run automatically when you transition from single to multi-user mode during bootup. Or, you can run it manually. You must be in single user mode to fsck root, AND the root file system must be mounted read-only. SuSE generally does this for you when you either boot up into run level 1 or change to run level 1 from other run levels.

The other file systems must be unmounted. If you try to run fsck on a rw root or mounted file system, you can do bad things.

Here isi what I generally use: fsck -fsy /dev/hda1 /dev/hda2 The options are: f == force s == serial (in other words run one at a time). y == answere yes to all questions (can be dangerous).

Many of the options are file system specific (such as ext2 or reiserfs), but this is reasonably generic.

I ran /dev/hda3, which is my home directory, and got a ton of messages. Most of them have to do with objectids being shared by 2 files. The last note says: 14 found corruptions can be fixed only when running with --rebuild-tree. Can't I delete the files instead? If not, how do I run the option? I tried and can't seem to get it working. Thanks, Tom

* tom@neuro-logic.com <tom@neuro-logic.com> [11-02-03 19:23]:

...

I ran /dev/hda3, which is my home directory, and got a ton of messages. Most of them have to do with objectids being shared by 2 files. The last note says: 14 found corruptions can be fixed only when running with --rebuild-tree. Can't I delete the files instead? If not, how do I run the option? I tried and can't seem to get it working.

Have you looked at: man reiserfsck or googled ???? --

The man page was absolutely no help at all. It never is. Anyway, I had to do an fsck --rebuild-tree /dev/hda3 and everything's fine so far. Tom