Startup issue
 

I have a small problem...

I am having an error on loading part of the "wpa_supplicant" in my startup. I don't have the error handy as I am at work right now.

But my issue is that I can't get to a login prompt to resolve the problem because it is hanging well doing the startup. I tried booting off the install dvd and using my root for reference but it still hangs when it gets to that spot.

I know what I need to disable to get rid of it but my problem is not being able to access the system to do that.

How do I go about getting logged in at this point? I tried using the startup disk and mounting my root partition but I could only mount it as read-only.

Any ideas?

Try a live CD (like Knoppix or so).

In the past I have booted using the original Slackware DVD and mounted my root directory to a mount point then made changes to the /etc/rc.d/ directory to fix things. Just as a test I have tried this again just now and all is well.

Out of interest, why can you only mount your root directory read only ? Is the FS corrupt or something ?

Does Ctrl+C pressed during the hangup skip the network setup and let you boot? Otherwise you *should* be able to mount the partition as rw using a LiveCD (or else you are probably doing something incorrectly, or your filesystem may be corrupt).

Hi,

The easiest way would be to use the install cd1 to boot the system as if you were going to install.

After you get to the login then from the cli (command line);

You should now be able to do edits or whatever to your system.

Thanks for the responses...

I tried the ctrl+c initially with no success unfortunately..

And I also tried mounting the partition manually after running the install cd/dvd but failed. I thought it was my most likely me getting my mount command incorrect for the setup, so I did some research and I had it right. Also something to note it's difficult to find many live cd's that recognize the "JFS" filesystem on a sidenote.

Turns out the drive itself was on it's last legs and crashing out it finally just spun down and called it quits.

So turned out to be a hardware issue as to why it wouldn't behave correctly, thanks for the assistance anyway!