Hi Buchan
and thanks for the reply. I think I got one other, but KMAIL
LOST IT before it got read, so if you replied, please resend it.
I haven't changed hostname, or it hasn't changed itself. The last
changes were to fit an agp graphics card in place of a pci one, and to update
modutils in a vain attempt to get harddrake running. This latter one caused
complaints, and I was intending to downgrade again. modules were for
inconsequential things anyhow (soundcard, scanner) in that particular kernel.
Booting to runlevel 3 as you suggested changed nothing. But I
did get an interesting insight from a console attempt to mount /dev/hdd3.
It gave me something like:
DMA Disabled hdd: status=0x58 { DriveReady SeekComplete DataRequest }
DMA Disabled hdc:
ide 1 reset: success
Prompt#
Then I found this in /var/log/messages on the old drive. At THIS stage hdb =
Seagate 4.3 Gig drive with hdd my new 6.5 gig drive.
Nov 5 19:23:26 genius kernel: hdb: irq timeout: status=0x58 { DriveReady SeekComplete
DataRequest }
Nov 5 19:23:26 genius kernel: hda: DMA disabled
Nov 5 19:23:26 genius kernel: hdb: DMA disabled
Nov 5 19:23:26 genius kernel: ide0: reset: success
It would appear DMA is erratic on this drive, hence my problem :-((. It has
failed on both ide 0 and ide 1. I don't think xfs runs on the thing. It hangs
at the bootup stage when it's mounting the disks, which is before most processes
start, in the mandrake_everytime script ... but I'm illiterate in perl :-((.
#On Thu, 09 Nov 2000, you wrote:
> Did your hostname change at some stage ? This would kill xfs (which is
> really a pain in the **). Did you try booting up in level 3 (LILO: linux
> 3) ?
Original message:
> > There I was minding my own business when out of the blue, I could
> > not log in. The exact sysptoms were about 1 second after the login screen
> > appeared, the screen would blank, there would be periodic very brief flashes
> > onscreen, and periodic disk activity. Ctrl/alt/del would bring back the login
> > screen and shutdown activity as normal. No faults shown in /var/log/messages,
> > or on /var/log/boot.log. e2fsck gave a clean bill of health to the linux drives.
> >
> > The system is a K6/2-500, 64MB ram, Appollo MVP3 (?) chipset, Award Bios, 8MB S3
> > Trio agp card, 2.2.14-15 kernel, and disks: hda = 2.5 gig; hdb1 = /boot; hdb2 =
> > swap; hdb3 (4 gig) = /; hdc =cdrom. All are ide, which is built into the
> > kernel. The version is the version 6 gold pack, with the 7.0 update.
> [snip]
> >
> > 1. what caused the first system to die 1 second after login prompt? There's
> > very little running on it.(atd, cron, gpm, network, linuxconf, lpd, kudzu, and
> > local - none of the network protocol stuff which could have delays in there).
> > Last thing showing in /var/log was linuxconf. I killed that (Interactive
> > startup) but it didn't help. I wouldn't claim to be fully competent with linux,
> > but I can access this old install if such is needed.
>
> Buchan
>
> > 2. Are the hdd problems the result of it's unkoshered positioning, or is the
> > disk the problem? Why does e2fsck pass it when the system can't optimize it?
> > The disk in question is a Seagate ST34311A, and about 1 year old.
> >
> > --
> > Regards,
> >
> > Declan Moriarty
> >
> --
> |--------------------------------------------------------------|
> Buchan Milne Mechanical Engineer, Network Manager
> Cellphone +27824722231
> email mailto:[EMAIL PROTECTED]
> Centre for Automotive Engineering http://www.cae.co.za
> South Africas first satellite: http://sunsat.ee.sun.ac.za
> Control Models http://www.control.co.za
> |----------------Registered Linux User #182071-----------------|
>
>
----------------------------------------
Content-Type: text/plain; name="message.footer"
Content-Transfer-Encoding: 8bit
Content-Description:
----------------------------------------
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
