From: "Korosi Akos" <korosiakos@mailbox.hu>
To: Newbie <linux-newbie@vger.kernel.org>
Subject: Re[2]: Strange problem
Date: Wed, 22 Jan 2003 16:31:27 +0100 [thread overview]
Message-ID: <20030122153131.21100.qmail@web2.mailbox.hu> (raw)
In-Reply-To: <5.1.0.14.1.20030117102213.021b4900@celine>
Hi!
I have reinstalled RH8.0, because I had to make the
machine work.
But as I am curious about the problem, I will answer
the questions.
Ray Olszewski <ray@comarre.com> wrote
>You really haven't told us enough for good diagnosis. From what you did
> write, I'd guess there is a problem with mounting partitions other
than
> the
> root (/) one (maybe including /, depending on the details of the /etc
I had everything on 1 partition and used the other partitions
(mounted into /mnt) for data storage.
So the / was on the same partition as /etc /boot and also
everything else.
And the programs were able to open some files, but other
not.
> problems you allude to). User root's home directory is normally on the
> root
...
> almost
> never is (I've never seen a case where it was, and doing it that way
> would
> cause real problems during init).
Every directory was on the same partition.
(except explicitli mounted directories)
> Check the status of mounted partitions in /etc/mtab to verify that
they
> are
> mounted RW (and that they are actually mounted as ext3, not ext2). Try
> (as
> root) umount'ing them, then fsck'ing them, in case they failed an
> automated
> fsck during init (this seems farfetched since you use ext3
filesystems,
> but
> it's all I can think of).
I checked the partitions during boot, and nothing was found.
I can not check mtab now :-(
> Since this happened after a reboot (at least I think that's what you
> wrote), you might want to verify that you are running the same kernel
as
> you were before the reboot.
There was only one kernel...
> I'd classify the chance that this is a virus as quite small. The
> hard-reset
> question does make me think of fsck problems with the filesystems.
Actually when I turned off the machine, there were [FAILED]
programs (eg xfs, etc) and they weren't always the same.
This was the reason that I thought about viruses.
> If that doesn't turn up anything, post again, this time quoting the
> actual
> error messages instead of paraphrasing them.
I can not do this anymore, but the error messages that I
wrote were nearly the actual, this means I didn't wore the
meaning of them, but what I saw, only when I wanted to
log in as a user, I can't see the message for a long time,
so I wasn't sure.
As I can not give you more actual information about the
system (because it has been reinstalled), I don't know if
you could guess the source of the problem.
But I would than you Ray for the guesses!
Best regards,
Akos
________________________________________________
http://mailbox.hu - Már SMS értesítéssel is!
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-01-22 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 16:55 GNOME help Anant Aneja
2003-01-16 19:40 ` pa3gcu
2003-01-17 16:06 ` Strange problem Korosi Akos
2003-01-17 18:36 ` Ray Olszewski
2003-01-22 15:31 ` Korosi Akos [this message]
2003-01-22 15:31 ` Re[2]: " Korosi Akos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030122153131.21100.qmail@web2.mailbox.hu \
--to=korosiakos@mailbox.hu \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.