Problems with AHCI after installation

Hi,

I’m having a system with a Gigabyte GA-P55M-UD2 board and activated AHCI for the harddisks, for getting more speed on the harddisks. After the installation of openSUSE 11.3 the AHCI controller will not find the harddisks anymore. It is just hanging on the detecting and don’t start to boot. When I’m setting the BIOS to handle the harddisks in IDE mode, the system is booting, but it is much slower.

I’ve tried a lot of different partitioning layouts, but nothing helped.

With OpenSUSE 11.2 it is working fine, but to install 11.2 is not an option, because i have to install a lot of systems with 11.3 and this middle-step will slow down my works extremely.

Has anybody an idea how I can use AHCI with 11.3 on this board?

Best regards,

Robert

So I have several Gigabyte boards and I have not noticed any problem with the IDE mode being “slow”. How did you determine it was slow? I must ask that you tried the install using the AHCI mode right off the bat, right? That is, you did not install as IDE and then try to switch to AHCI did you? Gigabyte boards I use are GA-G31M-S2L & GA-965P-DS3 for Intel and GA-790XTA-UD4 & GA-M750SLI-DS4 for AMD. These work great for me in IDE mode.

If I really thought this was a problem, I would make sure I was running the latest BIOS update before I did anything else. Otherwise, I am not sure that using IDE is any slower at all. IN fact the only recommendation I have found for the AHCI mode is when using eSATA and the desire to use hot-swapping, something few people really need.

You mention Partition layouts, but really that would not be the issue, the interface type would be the problem, though I can suggest a good layout for openSUSE if you would like. I suggest you proceed with an installation using IDE mode and see what you get. If the two computers and hard drives are not the same for a speed comparison, then the slow speed problem may be something else you have not thought of.

Thank You,

I don’t think I already had that problem with Linux but I had it with OpenBSD. What happens, is that the IDE diver fails to handle the device in Ultra DMA mode and reverts to PIO mode. In that case I/O operations become very very slow (it’s impossible to work).

First I would boot from a liveCD while in AHCI mode and see if the harddisk is found or not. If it is found, you probably have to tweak the system. If it is not, you might have to tweak the BIOS (look if there are specific AHCI options in BIOS setup). You can check on GigaByte site if there is a Bios update for your mainboard and read what it does fix.

It could be a kernel issue too (the latest kernel updates have broken so many different things). In that case, the kernel you first installed was OK, but the kernel installed later was not. You could try to install openSUSE from DVD but without doing any update ( just say ‘no’ when prompted at the end of setup).

On some mainboards (there were GigaByte), I already had the problem - in AHCI mode but not in legacy mode - that Grub could not boot some partitions if there were lying to far on the disk.

We are using enterprise harddisks from WD and made a lot of tests with different systems. In the end with activated AHCI the read/write speed was a lot faster than with IDE mode.

First I would boot from a liveCD while in AHCI mode and see if the harddisk is found or not. If it is found, you probably have to tweak the system. If it is not, you might have to tweak the BIOS (look if there are specific AHCI options in BIOS setup). You can check on GigaByte site if there is a Bios update for your mainboard and read what it does fix.

I think I’ve written my problem a little bit complicated. The problem exists directly after the installation, when the computer is making the first reboot. From this point the computer is hanging during the AHCI Bios. I can not imagine that this is a problem of the AHCI BIOS. My assumption is, that there is a problem during the OpenSUSE 11.3 is writing the partitions or the boot sector, because OpenSUSE 11.2 is working fine.

We have already updated the BIOS to the newest version.

It could be a kernel issue too (the latest kernel updates have broken so many different things). In that case, the kernel you first installed was OK, but the kernel installed later was not. You could try to install openSUSE from DVD but without doing any update ( just say ‘no’ when prompted at the end of setup).

We are installing OpenSUSE 11.3 via PXE with AutoYaST from a local mirror which we have created in front of 2 weeks… There is no automatic update at the end of the installation.

I have no idea, on which point i have to search for the problem. Also to say we are set all the computers with this mainboard back to IDE mode is not an option, because we are talking on a grand number of computers on different locations.

I just can hope that anybody here has an idea, how to solve this problem :slight_smile:

Metrax it has been suggested that perhaps there is an issue for you with the 2.6.34 kernel version that comes with openSUSE 11.3. I have in fact upgraded to kernel 2.6.35.5, and it is working very well. It is easy to upgrade your kernel, but I don’t think you can switch to ACHI mode from IDE and still have a working system. It might be worth a try though, even to retest in the IDE mode. Look at my thread on the kernel compile and install instructions.

S.A.K.C - SuSE Automated Kernel Compiler

You may also want to know how to maintain more than one kernel version, which allows you to drop back from a kernel that is not working for you:


Yes, it is possible to keep both your old and new kernels. You need to change how YaST Software Management works with kernel updates, to allow you to maintain both the old kernel and the newer kernel.

edit the file /etc/zypp/zypp.conf to say:

##
## Packages which can be installed in different versions at the same time.
##
## Packages are selected either by name, or by provides. In the later case
## the string must start with "provides:" immediately followed by the capability.
##
## Example:
##    kernel                - just packages whith name 'kernel'
##    provides:multiversion(kernel)   - all packages providing 'multiversion(kernel)'
##                      (kenel and kmp packages should do this)
## Valid values:
##    Comma separated list of packages.
##
## Default value:
##    empty
##
# multiversion = provides:multiversion(kernel)

**multiversion = kernel-desktop**

If you use KDE, you can use the menu Run Command:

kdesu kwrite /etc/zypp/zypp.conf 

The file zypp.conf has a whole lot more in it than the small portion shown above. You are adding only the line shown in bold (and it will not be in bold in your file after being added. So be careful not to mess anything else up. caf 4926, posted a page from Software Management showing how to then select the added kernel, though this is from the newer openSUSE 11.4, in beta testing right now.

http://dl.dropbox.com/u/10573557/SUS…dio-switch.png

After making the change, restart your computer and then do the following after you are logged back into openSUSE:

menu / System / YaST & Enter Root User Password, then in YaST Select:

Software Management / View (top Left) / Package Groups / Multiversion Packages

There will be a listing for your loaded kernel. Now select the Versions Tab. Notice on the versions tab that instead of having a Bullet to select, where only one bullet can be active, you now have check blocks and more than one check can be selected.

Now when you select more than one kernel to be loaded, each installed kernel will have two (or more) entries made in your grub, menu.lst file. Thus allowing you to select both the old and new kernel loads. If you install a new kernel and normally install a binary video driver, the hard way, you must reinstall the video driver for each new kernel that you install.


I hope that some of this information might prove helpful to you. Consider that you might just need to stick with openSUSE 11.2 until version 11.4 comes out next year.

Thank You,

Yeah, same problems here Robert. I just installed opensuse 11.4 into AHCI hdds -from the installation DVD-,and everything seemed to be fine, i was fully able to access all my hdds but since I rebooted, I am stuck in the BIOS message screen.
I assume that grub messed up with the mbr.
The solution that jdmcdaniel3 suggests can be done from a liveCD?
I am glad to hear if you’ve find any solution to this, it’s really disturbing.

From a openSUSE 12.1 KDE LiveCD (http://download.opensuse.org/pub/opensuse/distribution/12.1/iso/openSUSE-12.1-KDE-LiveCD-x86_64.iso), you can do many things and having one is highly recommended. I would download the application findgrub from here: http://www.unixversal.com/linux/openSUSE/findgrub-3.6.tgz

and run the program and post the results here. I would also open up a terminal session in the LiveCD and run the command:

fdisk -l

And I would post those results as well here for us to look ta and make suggestions for a fix.

Thank You,

3.6.2 is the latest: [noparse] http://www.unixversal.com/linux/openSUSE/findgrub-3.6.2.tgz[/noparse]](http://www.unixversal.com/linux/openSUSE/findgrub-3.6.2.tgz)

But I’m sure you know that, James. :wink:

First of all, I did those 2 steps, but I thought that downloading the liveCD was unnecessary as:
If I turn to AHCI mode I have to unplug one drive ( the one that carries the openSUSE installation and the /boot partition ) so it will findgrub and fdisk would be useless. So I kept the IDE mode and I normally login in to openSUSE and here are the results:

findgrub


Find Grub Version 3.6.2 - Written for openSUSE Forums

 - reading MBR on disk /dev/sda                       ...
 - reading bootsector  /dev/sda1   *  (LINUX)         ... --> Legacy GRUB  found in /dev/sda1   => sda1   0x83 (openSUSE)
 - reading bootsector  /dev/sda2      (LINUX)         ...
 - reading bootsector  /dev/sda3      (LINUX)         ...
 - reading bootsector  /dev/sda4      (Extended)      ...
 - reading bootsector  /dev/sda5      (LINUX)         ...
 - skipping partition  /dev/sda6      (swap)         
 - searching partition /dev/sda7      (NTFS)          ...

 - reading MBR on disk /dev/sdb                       ...
 - searching partition /dev/sdb1   *  (NTFS)          ... --> Windows7/Vista Loader found in /dev/sdb1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can add the following entry to /boot/grub/menu.lst :

###Don't change this comment - YaST2 identifier: Original name: WindowsBootLoader###
title Windows on /dev/sdb1
    rootnoverify (hd1,0)
    map (hd1) (hd0)
    map (hd0) (hd1)
    chainloader +1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 - searching partition /dev/sdb2      (NTFS)          ...

*note I have add a windows entry from yast and I don't have a prob

fdisk


Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x49568221

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1060863      529408   83  Linux
/dev/sda2       327163725   488392064    80614170   83  Linux
/dev/sda3         1060864    69224447    34081792   83  Linux
/dev/sda4        69224448   327161855   128968704    f  W95 Ext'd (LBA)
/dev/sda5        69226496   218097663    74435584   83  Linux
/dev/sda6       218099712   222291967     2096128   82  Linux swap / Solaris
/dev/sda7       222294016   327161855    52433920    7  HPFS/NTFS/exFAT

Partition table entries are not in disk order

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sdb: 74.4 GB, 74355769344 bytes
255 heads, 63 sectors/track, 9039 cylinders, total 145226112 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0f8004b0

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sdb2          206848   145223679    72508416    7  HPFS/NTFS/exFAT


That’s all. Nevertheless I am seriously thinkin of abandon the whole thing and make a clean install of 12.1 version. Will this skip my current error?
One more question I have the ASUS P5K deluxe motherboard and I looked in their site and I saw there’s a raid driver for downloading. Should I have provide them at install time?

DhmhsL, let me say that I would start my own thread over jumping onto an old existing one and there is no reason you can’t make a link to the old message thread if you feel it is useful. So, consider that next time though you can start your own thread anytime you feel you need to.

As for AHCI mode, the basics here is that you must turn AHCI mode on before you do your Operating System installation and you can’t switch modes after an installation is completed. If I had IDE mode working OK I am not sure I would reinstall just for AHCI mode, but I would surely turn on the AHCI mode before I did any installations AND this effects both Windows and Linux. Set what you want before you go any further and don’t change your mind after the installation is completed. As for doing a re-installation of openSUSE, there no reason not to do that unless you spent a long time customizing what you have now and even then, just don’t wipe out the /home partition (only mount it and do not reformat it) and most customizations will be preserved.

Thank You,

yeah, my bad jdmcdaniel3 for not mentioning my started thread, I will be glad to continue our conv there
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/472526-opensuse-11-4-ahci-trouble.html