Back to the errors. Could not acquire the org. There are a few things to consider that might help anyone coming across this. The box is running an asus dsbf-de board, with 2x e cpus and 16g of ram. You can use the –preload option to manually specific modules though, so you could always try turning AHCI off, booting Fedora, making your custom image: Sign up or log in Sign up using Google.
|Date Added:||15 August 2005|
|File Size:||22.58 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Home Questions Tags Users Unanswered. What happens if you switch back to IDE?
linux – Why boot fails with bios SATA Mode as AHCI? – Super User
There is also a supermicro 8 port sata hba in the system, with five g drives on it. I think it does, it would include AHCI in initrd as long as it detects you’re using it There are six drives on the ahci, one 80g “system” drive the boot driveand five g storage drives.
The original bios says American Megatrends at the top. Email Required, but never shown.
We Love Servers.
I’m using the bit 2. Just be sure to power cycle after making change in the BIOS. I’ve captured and re-deployed the server to a physical machine.
My steps for future reference: I want to use the board’s controller’s AHCI mode. I’m not surprised by this fact alone, but I am surprised with the message I’m getting: When I put it in custom bios, not successful.
Could not acquire the org. The box is running an asus dsbf-de board, with 2x e cpus and 16g of ram. So I can take the disk, boot it in the standard bios, and everything is successful.
There are a few things to consider that might help anyone coming across this. I retried the installation after wiping the HDD and this made no difference.
So I’m wondering what config files I need to tweak, to help the already installed system use the “new” ahci controller? Long ago, I posted about only seeing four of the six sata ports on my asus server board.
Linux @ CERN
Full time Geek, part time moderator. Dec 20, at 3: I will configure partitioning: The Crux OS has slightly outdated custom kernel on it and uses initramfs also custom. After studying the man page for mkinitrd, I also used –preload ahci to make sure the ahci driver was the first one to look for drives. This allows the disk to be seen, but boot still fails.
centos – Add AHCI to initrd on CentOS7 after installation – Unix & Linux Stack Exchange
I traced the problem down to AHCI. I went backwards and forwards a few times to make sure. You need to recompile the kernel, if you compile with built-in support then you’re safe, but mkinitrd will only take the modules that are needed to boot the running kernel – cenntos that unless you can boot the machine into Fedora with AHCI on and then run mkinitrd, it won’t take it by default.
I’m not surprised by this fact alone, but I am surprised with the message I’m getting:. Gordon McLellan 2 Joseph L.