On Fri, 9 Jan 2004, Matthew Bardeen wrote:
> Nope. No go.
>
> A little more information might help, so here goes. It's a custom built 2.4.21
> kernel, with ext3 support built in. Nothing has changed OS wise (AFAIK) that
> would cause this problem.
>
> Just before trying to launch into fsck in the
Nope. No go.
A little more information might help, so here goes. It's a custom built 2.4.21
kernel, with ext3 support built in. Nothing has changed OS wise (AFAIK) that
would cause this problem.
Just before trying to launch into fsck in the bootup sequence, it gives:
EXT3-fs: invalid journal i
On Fri, 9 Jan 2004, Matthew Bardeen wrote:
> After travelling with my laptop (safely in suspended mode), I turn it on only
> to find the following error when it tries to fsck the drive..
>
> fsck.ext3: Illegal block number while checking ext3 journal for /dev/hda2
>
> an 'ls -al' of the journal fi
After travelling with my laptop (safely in suspended mode), I turn it on only
to find the following error when it tries to fsck the drive..
fsck.ext3: Illegal block number while checking ext3 journal for /dev/hda2
an 'ls -al' of the journal file reveals the following information:
b--sr-S--x 2697
> > I don't think that's too unreasonable. A while ago, the X server for
> > my video card was quite unstable (ATI Mach64 w/chrontel ramdac), and I
> > ended up needing to kill the xserver remotely about once every 2 or 3
> > days (the xserver would take over the console and refuse to operate
> >
I use KDM, the KDE xdm variant. It does not manage my local display.
X is not the problem. X works fine. I just can't get my text console
back.
On Wed, Sep 16, 1998 at 02:44:22PM +0100, IH McKeag wrote:
> Sorry, I have missed your earlier correspondence but have you tried
>
> /etc/init.d/x
On Wed, Sep 16, 1998 at 09:33:52AM -0600, John Larkin wrote:
> > No... This is not the problem. As I said, X crashed. This makes the X
> > server quit without restoring the display, so you just get your X
> > desktop sitting there. You can restart X remotely, but when you exit,
> > it restores the
Sorry, I have missed your earlier correspondence but have you tried
/etc/init.d/xdm start
as super-user?
Ian.
On Tue, 15 Sep 1998, Ian Eure wrote:
> Don't think a "reset" will do it, as that just manipulates the terminal
> behaviours... I'll give it a shot anyways in a minute though.
> No... This is not the problem. As I said, X crashed. This makes the X
> server quit without restoring the display, so you just get your X
> desktop sitting there. You can restart X remotely, but when you exit,
> it restores the previous mode, eg a graphical mode instead of a text
> console. When
-BEGIN PGP SIGNED MESSAGE-
Hi!
[...]
> I have X running on the console (login to another box, ssh over to the
> borken one, screen, startx, detatch) - I just can't get the text vtys
> back to normal. Tried running a SVGALib program. No dice. The only
> thing that works is X.
I suffered
No... This is not the problem. As I said, X crashed. This makes the X
server quit without restoring the display, so you just get your X
desktop sitting there. You can restart X remotely, but when you exit,
it restores the previous mode, eg a graphical mode instead of a text
console. When I close my
Don't think a "reset" will do it, as that just manipulates the terminal
behaviours... I'll give it a shot anyways in a minute though.
As for the ``shutdown -r now'', I know that I can reboot the system and
be fine, I just want to fix this without doing that, as I stated in the
last sentence of my
Ok. Interesting thing happened. Accidentally killed my X server remotely with
-9. Oops. I come back down to the console and it's all FUBARd. OK. So I try
a couple things ssh'ing from another box, like SVGATextMode & such. No dice.
I can get X running, but my text console is dead. Anyone have any su
13 matches
Mail list logo
