K Won't Load With 2nd Drive Connected

StarSage · 05-21-2007, 12:33 AM

I've installed openSuSE 10.2 on one drive but have been having trouble getting yast2 to recognize a secondary drive. This drive was previously in ext3 format and I've since tried fat32 and have even wiped the drive clean. None of SuSE's utilities (KDiskFree..etc) even acknowledge the drive exists.

When this secondary drive is attached I'm unable to get SuSE to load the KDE desktop.

Is there an easier way to go about this?

Sp1t · 05-21-2007, 02:18 AM

Does it get to any form of login? If it gets to a text mode login you could log in, su into yast and add the partition that way.

Have you checked master/slave pins on the back of the drive? Does it appear in BIOS?

I think Suse does disk checks on boot and it is this that causes the problem. If the checking is switched off, you will get into it - problem is I can't remember how to do that! I'll see if I can find out......

StarSage · 05-21-2007, 01:17 PM

Yes, after SuSE spits out a bunch of error on boot up I think I get a Sudo prompt. How do I go about accessing yast from the command line?

The pin is set to slave on the drive. I'll need to recheck bios later (am at work presently)

Quote:

Originally Posted by Sp1t

Does it get to any form of login? If it gets to a text mode login you could log in, su into yast and add the partition that way.

Have you checked master/slave pins on the back of the drive? Does it appear in BIOS?

I think Suse does disk checks on boot and it is this that causes the problem. If the checking is switched off, you will get into it - problem is I can't remember how to do that! I'll see if I can find out......

StarSage · 05-22-2007, 11:51 AM

okay.. so I get a command line, but not one that I recognize. It says something about bash. I'm not able to apply 'mount /dev/hdb1 mnt/storage' even though I've written it into my fstab.

Is it possible linux isn't seeing my drive even though it's properly connected and powered up?

Quote:

Originally Posted by StarSage

Yes, after SuSE spits out a bunch of error on boot up I think I get a Sudo prompt. How do I go about accessing yast from the command line?

The pin is set to slave on the drive. I'll need to recheck bios later (am at work presently)

StarSage · 05-22-2007, 09:45 PM

I was able to reformat this drive and install SuSE. The drive even boots. When I set the pin back to slave I'm unable to load the desktop from the latest kernel on the main drive.

Here's what I get:

waiting for device /dev/hdb1 ... not found (ignoring)
waiting for device /dev/hdb5 to appear... not found
-- exiting to /bin/sh

sh: no job control in this shell

I can load the desktop from the initial kernel but it doesn't seem to matter if I've edited fstab from there.

HELP!

Quote:

Originally Posted by Sp1t

Does it get to any form of login? If it gets to a text mode login you could log in, su into yast and add the partition that way.

Have you checked master/slave pins on the back of the drive? Does it appear in BIOS?

I think Suse does disk checks on boot and it is this that causes the problem. If the checking is switched off, you will get into it - problem is I can't remember how to do that! I'll see if I can find out......