SuSE 9.1 mounting problems
 

Hey guys,

I just installed SuSE 9.1 Pro and in the mounting it calls the drives starting from e...

i.e.

hde
hdf
hdg

Why is it doing this? A few posts pointed to the fact that its caused by SATA.

I have onboard SATA however I'm not using it as I don't have the dosh for a SATA drive.

Anybody have a quick fix for this?

Cheers
hamstar

Re: SuSE 9.1 mounting problems
 

If You look in /etc/fstab you can see which drives are mounted and with which names.

Normally it starts with hda...

like this

/dev/hda1
/dev/hda5
/dev/hdb1
/dev/hdc1

and so on

As you point it out it looks you have more drives but not mounted.

CloudBuilder

Well, yeah..

I only have 3 disks... the setup of the first two is like this....

http://sal.neoburn.net/imagef1/files...structure2.jpg

And the third one has 1 primary ntfs then under and extended partition has a mandrake linux partition and a swap partition.

But now when I lock in, I can even get to X...

It stops halfway through saying that fsck failed.

Then it says some other crazy jibberish about USB (which i havent got enabled anyway)

So I do exactly as it says and it does the same thing next reboot.

I also tried changing the disk names in fstab... like put them all to the letters they should be. i.e hdg5 to hdc5 but to no avail. It just did the same thing.

I'm going to go search the forum and suse portal for this problem now, but incase I dont find anything I wrote it here for anyone whos had the same problem or if anyone already knows a link.

Cheers..
hamstar

omg theres heaps of links.... why did i clog up your forum with this...

http://www.linuxdesktop.it/modules.p...ewtopic&t=6977
http://www.groupsrv.com/linux/viewtopic.php?p=656
http://www.linuxquestions.org/questions/history/219489 <<this looks the most promising...

Ahh well looks like I'm doomed....

lol...

Seems that you have a problem with the file system.
You have at least 5 partitions on 2 drives ..... you talk about 3 drives . So you should have hda.. hfb.. and hdc..

Hdc5 does not make sense for the linux ext3 file, but again there seems to be a problem with the file system , because it is not recognized.

What is in your fstab ? Changing it does not make sense because in Suse you mount by clicking on the desktop and then make drive......

This will update fstab. So it should be very conclusive what is in your fstab.

CloudBuilder

I did it via pico /etc/fstab :D

Ummm, I'll just try what I've read, and if that doesn't fix it, I'll post the contents of my fstab...

Cheers
hamstar

I don't think you have a sata issue but a RAID issue. Do you have raid enabled in the bios and I believe raid start with hde for IDE raid not sata raid nor scsi raid??

Ummm... I haven't enabled raid... however I will double check on that...

Cheers...

I didn't read very carefully, so if something has already been mentioned, sorry for that.

I have two suggestions:

1. If you don't use S-ATA, switch it off in the BIOS

2. You may use boot options to match the ports with the drives:

idex=hdx (look up the numbers in boot.msg)

or try ide=reverse

Boot options?

Where do I do that? In grub editor or something? Got a syntax example?

cheers
hamstar

abisko00 is talking 2 things
you into bios by pressing f2 or del key or whatever your mobo says to get in and find sata and disable it.

look around and turn off raid you may need to look at your mobo handbook or cd

2) the second thing is kernel append lines to your grub.conf file
eg
kernel /boot/vmlinuz root=/dev/hde ro ide=reverse

the "reverse" is sometimes you used to help the kernel find sata drives and yes I know you think you have no sata but I still think you have raid.

aus9 thanks for making that clear!

But one more thing: you do not need to edit the grub.conf or menu.lst in order to pass those parameters to the kernel. In suse, you can type them into the boot menu directly (just type as soon as the menu appears).

umm, the whole idea is that you edit the file once, do some typing once and not have to do it on each boot.

or I have misunderstood the SECRETS of suse? heh heh

No, you did not ;-)

I just mentioned this possibility for testing the parameters. It makes the whole thing much easier when you do not know if the parameter will show the desired effect. Changing config each time you want to try something new is a pain in the ass, especially if the system does not boot with the new parameters. Once you know it will work, you make the changes permanent by adding them to the config.