Lilo.conf edit caused inability to mount hard disk
Attempting to get an old box working with Slack. Always hangs on the /udev events part of the boot and after eventual boot things are slow for a while, I think I need to append something to lilo.conf & have attempted acpi=off noapic, also uncommented vga=normal. Looking at http://www.linuxquestions.org/questi...lation-645586/ I also tried appending hda=noprobe but did not precede it with hugesmp.s, as I have changed to generic kernel- perhaps that was wrong?
I ran lilo then rebooted, and the result was Code:
mounting /dev/hda1 on /mnt failed: No such device or address I have taken the hda=noprobe off the append line but cannot get into Slack (either on the generic or the huge kernel, which is still in place) to run lilo. Is there a way to overcome this mounting problem (assuming that's what it is) or boot back in some other way to run lilo? At the moment I have to get in and tweak, or copy/add files onto usbstick, using systemrescuecd. That's OK but takes a while, maybe I'll install another Slack OS on a spare partition. Meanwhile, I have a bit of a history of trouble with this computer, but I'm staying with it as it's great hacking practice. The last time I had Slack up & running yesterday was the fastest this machine has ever been- but am I on the right track with the "append" line and if so are there other codes I should try? Thanks guys latest reading on this issue: http://www.linuxquestions.org/questi...-quirk-635066/ some recent info on this computer:( http://www.linuxquestions.org/questi...events-649392/ my present lilo.conf Code:
# LILO configuration file Code:
# LILO configuration file |
Quote:
samac |
Does your huge kernel still work for you?
|
Samac, I'll do that later & report back. Shadowsnipes, yes the huge kernel is still up & running to the same extent as the generic, ie I booted back into it after adding generic to lilo, in order to check it. However I get the same error whether I boot with huge or generic, after adding the "noprobe".
|
According to Alien Bob's post in the thread you mentioned, using the "noprobe" option makes your hdd /dev/sda instead of /dev/hda.
This is probably why / is not being mounted with the "noprobe" option. |
:( Thanks! But AFAIK I need to get back into slack to run lilo. I tried the obvious ie
Code:
mount -t ext3 /dev/hda1 /mnt Code:
device or mount point not found If I mount sda1 instead, will that work? Or could I get my hdd back as hda instead of sda? In the worst case I'll reinstall, don't mind that. I assume that loading the generic kernel was the right thing to do... unless huge.s (for a really old machine, which mine is) is worth a try? Or a different code on the append line? I'm starting to see that the hang on /udev is probably the result of a module that won't work with my mainboard and unlikely to be hardware. |
Quote:
Once it is mounted properly cd into it and chroot. Then edit your lilo.conf and run lilo. You shouldn't need to reinstall Slackware. |
Thank you! Fixed lilo(& much better than systemrescuecd for these smaller tasks). Although hda was present & not sda I followed your advice exactly & it worked immediately.
However still very slow to boot (udev hang again) & running badly, although I think I've pestered fellow linux users more than enough on this subject...? |
Quote:
I'm sure you already have a thread for that topic so perhaps you could quote part of this post there and point me there. That way we don't get too off-topic on this thread. Don't worry about "pestering" fellow linux users when you have genuine problems that need solving. We're here to help and we want to see you through this. |
Again thank you. Result of
Code:
hdparm -d /dev/hda Code:
hugesmp.s hda=noprobe I have also tried appending hda-noprobe in lilo and making the suggested changes in lilo.conf & fstab. Not accepted in lilo as sda doesn't exist. No harm done. As you suggest, there is a separate thread, http://www.linuxquestions.org/questi...events-649392/ but no replies, I'll continue this post in there. |
All times are GMT -5. The time now is 12:33 AM. |