LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   Disk Drive Errors (https://www.linuxquestions.org/questions/slackware-installation-40/disk-drive-errors-645012/)

pxumsgdxpcvjm 05-27-2008 02:17 AM

Disk Drive Errors
 
Tonight I was trying to install Slackware 12.1 on an old computer I have. It was running Slackware 12.0 previously. The specs are; 533Mhz Celeron, 256MB RAM and two HDDs with the capacities of 80GB and 9GB.

Slackware 12.0 had previously ran fine with no problems. My main reason for upgrading was to simply start fresh.

I expected it to go smoothly, but the computer really started to show its age. While installing the packages, about five or six of them failed (some where also required packages) with a 'fatal error' message.

I had previous checked the MD5 of the ISO and just to be sure I verified the disk twice on my primary computer. No problems there.

So now that my drive is starting to die (I guess that it is about time too) and pretty much useless, how can I install Slackware? Unfortunately, my BIOS doesn't support USB booting.

pxumsgdxpcvjm 05-27-2008 05:40 AM

Okay, by using a loop back device I managed to get Slackware installed without a flaw. The trouble I'm having now is that I get a kernel panic on boot. I'm unable to copy it all out, but it happens quite late in the boot process (after DHCP is polled).

The last two lines are as follows...
Code:

EIP: [<d0af452e>] de_set_media+0x15e/0x170 [de2104x] SS:ESP 0068:c08e5e54
Kernel panic - not syncing: Fatal exception in interrupt

Seems to have something to do with a drive, but nothing had been changed since the previous installation of Slackware 12.0.

Big thanks to any replies.

pxumsgdxpcvjm 05-27-2008 06:05 AM

This is a strange problem. After a few reboots (with nothing changed), it came right and I managed to login. I'm sure it won't last long, but I'll try removing another dead CD-ROM drive from the system (as I suspect that may be the cause of the kernel panic). Anyway, before I do that tomorrow, has anyway had this sort of issue before and do know what caused this? I would like to fix it as I'm sure I'll end up seeing again.

Thanks.

onebuck 05-27-2008 01:42 PM

Hi,

Pass the 'noapic' to the kernel at the 'boot:'.

pxumsgdxpcvjm 05-28-2008 03:11 AM

Just tried it. Didn't help. Also tried adding 'nolapic'.

H_TeXMeX_H 05-28-2008 09:16 AM

I would say use memtest86 to check your RAM.

Woodsman 05-28-2008 07:34 PM

Quote:

While installing the packages, about five or six of them failed (some where also required packages) with a 'fatal error' message.
This happened to me many moons ago. The cause was a flaky CD drive.

onebuck 05-28-2008 09:12 PM

Hi,

I agree that the OP may need to run some diagnostics. memtest86 is a good start. Then check the cdrom. You could use 'UBCD'.

pxumsgdxpcvjm 05-29-2008 05:02 PM

I know that the CD drive is on its last legs. Not too much of an issue since I have a USB drive (although I cannot boot from it). I ended up installing Slackware thanks to the loopback device node with the ISO added on the USB drive.

Other then that random kernel panic on startup, the system seems fine.

I did a little looking around and it seems to be a kernel bug. This one here. It's fixed in the latest kernel release, so it looks like I'll have to upgrade my kernel.

onebuck 05-29-2008 10:09 PM

Hi,

You did run memtest86! Let it pass overnight. Make certain to close the case or place the system in the same condition as to when you experienced a failure.

pxumsgdxpcvjm 06-01-2008 10:17 PM

Yea. I just tried running Memtest68+. Not problems found on the first pass and I expect the same once the second is complete. I'm pretty sure that my issue is due to that kernel bug, but I'll have to compile it in order to be sure.

H_TeXMeX_H 06-02-2008 12:57 PM

That's good. I recommended it because an 'EIP' is usually associated with bad RAM or data corruption. Wanted to rule it out. It could also be a kernel bug.

pxumsgdxpcvjm 06-03-2008 12:13 AM

Yea. Just complied a new kernel for the machine. Seems to be working flawlessly now.

onebuck 06-03-2008 12:48 PM

Hi,
Quote:

Originally Posted by pxumsgdxpcvjm (Post 3172830)
Yea. Just complied a new kernel for the machine. Seems to be working flawlessly now.

So compiling a new kernel solved the problem. What were your omissions? What was changed? You should post the results so as to provide others with information in case someone searches and finds the posts. With a complete solution to the problem being posted then everyone benefits.


All times are GMT -5. The time now is 03:04 AM.