oops!
here are the error messages before it crashed:
kernel hda: drive-cmd: status=0x51 {Drive Ready
SeekComplete Error}
kernel: drive-cmd: error=0x04 {DriveStatus Error}
It is also possible the draknet or netdrake or
whatever it is called that I ran from mcc may have
caused a problem. When I was setting up journeling
with tune2fs I tried unmounting the drives through
this program. It unmounted /dev/hda6 (Home) but would
not unmount any others (like /dev/hda3 (Boot) or
/dev/hda8 (/usr/local). It gave an error on any
attempt after the 1st success on /dev/hda6.
When I went to reboot it could not properly unmount
during shutdown and it began the long train of endless
crashes. As I mentioned before that even reverting
back to ext2 did not stop this. I also have heard no
other complaints like this on the list about the new
initscripts. Could the mount program in mcc have
severly corrupted something? I know I hear attempted
disk writes on my computer right before it crashes.
--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> It is possible it is initscripts-6.27-2 since I
> updated that file at the same time.
> Another possible clue is that when reading the logs
> this message appeared right before one of the crashs
> (how far before I am uncertain, also I could not go
> through the logs for very long before it crashed
> again
> :-{ )
>
> I am going to see if I can find a previous version
> of
> initscripts and see if I can uninstall...reinstall
> before it crashes on me again.
>
> --- Eugenio Diaz <[EMAIL PROTECTED]> wrote:
> > --- SI Reasoning <[EMAIL PROTECTED]> wrote:
> > > I have had all kinds of problems since I tried
> > ext3.
> > > Linux completely locks up within a few minutes
> of
> > > running. I have even changed fstab back to ext2
> > but I
> > > still have the problem. I have no clue as to
> what
> > > causes it and it crashes too fast for me to
> > research
> > > it. grrrrrrrr
> >
> > May be the problem is not related to ext3. Did you
> > did other changes since the
> > last reboot before the ext3 change. I often find
> > that I attribute a problem to
> > a change, when in fact the real culprit is
> previous
> > change of something else
> > where there was no reboot. If you changed the
> fstab
> > for real, and it is mounted
> > as ext2 then there is no reason why ext3 be
> > involved; in fact, unless you have
> > ext3 listed in /etc/modules, or as part of initrd,
> > the ext3 module shouldn't
> > even be running. Alternatively, you can boot why
> > another kernel (rescue disk,
> > etc.) and see what happens.
> >
> > =====
> > ________________________
> > Eugenio Diaz, BSEE/BSCE
> > Linux Engineer
> > [EMAIL PROTECTED]
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Get email alerts & NEW webcam video instant
> > messaging with Yahoo! Messenger
> > http://im.yahoo.com
> >
>
>
> =====
> SI Reasoning
> [EMAIL PROTECTED]
> gnupg/pgp key id 035213BC
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
=====
SI Reasoning
[EMAIL PROTECTED]
gnupg/pgp key id 035213BC
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
