07-05-2011
Changed to AHCI, can not access disk???
Here is my problem:
I have an 1.5TB disk with OpenSolaris (b134, b151a) using non AHCI. I then changed to AHCI in BIOS, which results in severe problems: I can not boot the system.
I suspect the problem is because I changed to AHCI. Now I have changed back to non AHCI, but still I can not boot the PC. Solaris gives an error message. How can I solve this?
So this is what I have done:
1) 1.5TB disk worked fine with non AHCI
2) Switched to AHCI
3) Computer refuses to boot. There is an error message.
4) Switched back to non AHCI, booted from LiveCD and tried to import rpool. This resulted in an immediate reboot.
5) Computer refuses now to boot even in AHCI mode. Shows the same error message as in 3). However, WinXP boots fine though.
Now I have a new problem on the same theme.
A) Bought a Vertex 3, 240GB and turned on AHCI
B) Installed S11E, everything went fine.
C) Later I tried to repair the problematic 1.5TB disk above, so I switched off AHCI.
D) While using non AHCI, I booted off from liveCD S11E, and by mistake imported the Vertex 3 rpool.
E) Now I can not boot from my Vertex 3, even if I switch on AHCI. It is the same error message as in 3) and 5) above.
To summarize:
So the problems boils down to this:
Z) Solaris installs using AHCI
X) Switch to non AHCI
Y) Boot from LiveCD S11E and import the rpool
W) Turn back AHCI, and now Solaris refuses to boot. Why?
And vice versa:
ZZ) Solaris installs non AHCI
XX) Switch to AHCI
YY) Boot from LiveCD S11E and import the rpool
WW) Turn off AHCI, and now Solaris refuses to boot. Why?
10 More Discussions You Might Find Interesting
1. Programming
Is there any way to write to disk sector by sector, without any files, filesystems etc. I did that in DOS, but that was DOS. (3 Replies)
Discussion started by: Lopatonosec
3 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I've booted a Digital Unix 4.0D system from cd-rom and I need to access the system's disk drives. I need to run the fixfdmn utility on the root domain so I need to create the root domain in /etc/fdmns.
Could someone tell me how to access my system's disk drives after I've booted from... (1 Reply)
Discussion started by: xadamz23
1 Replies
3. HP-UX
Hi,
I have an HP RX4640 running HP-UX 11iv3 with two internal disks and its connected to a HP disk system 2400 with fibre cable.
If the storage system is online before the server is on then the server can't find the disks. And I get the following error messages:
vgchange: Warning: Couldn't... (3 Replies)
Discussion started by: hoff
3 Replies
4. AIX
How to allow Windows platform to access Unix(AIX) based disk volumes? (2 Replies)
Discussion started by: rainbow_bean
2 Replies
5. SCO
Dear all,
I'm newbie in SCO. I already purchase SCO 5.0.7 and SATA Tape Drive (not SCSI) for IBM server. not a cheap investment :(
my problem is:
I can't use my sata tape on sco 5.0.7 for backup my data because sco can't detect any sata tape has been plug into o/s. i already running "mkdev... (7 Replies)
Discussion started by: asumatezuka
7 Replies
6. Filesystems, Disks and Memory
Hello,
I wanted to share an experience I had today which was quite a learning experience and perhaps useful for others who may run into the issue at some point in the future.
Basically, the scenario involves a OS which was installed on a machine which hardware-wise, had a SATA Drive. The... (0 Replies)
Discussion started by: septima.pars
0 Replies
7. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
8. Solaris
I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all.
How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies
9. AIX
Hello,
I try to access to data after connect a new disk (hdisk1) to a AIX 7.1 system
This new disk was assigned to a rootvg from another AIX 6.1 system.
It seem not assigned to any vg
but if I tried to assigned hdisk1 to rootvg i get :
Data seem to be always here ... ouf ;-)... (4 Replies)
Discussion started by: Voran
4 Replies
10. Shell Programming and Scripting
Hi All,
I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :(
which have similar names ( /var in root and var of some other directory ).:confused:
Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies
AHCI(4) BSD Kernel Interfaces Manual AHCI(4)
NAME
ahci -- Serial ATA Advanced Host Controller Interface driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device pci
device scbus
device ahci
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
ahci_load="YES"
The following tunables are settable from the loader(8):
hint.ahci.X.msi
controls Message Signaled Interrupts (MSI) usage by the specified controller
0 MSI disabled;
1 single MSI vector used, if supported (default);
2 multiple MSI vectors used, if supported;
hint.ahci.X.ccc
controls Command Completion Coalescing (CCC) usage by the specified controller. Non-zero value enables CCC and defines maximum time (in ms),
request can wait for interrupt, if there are some more requests present on controller queue. CCC reduces number of context switches on sys-
tems with many parallel requests, but it can decrease disk performance on some workloads due to additional command latency.
hint.ahcich.X.pm_level
controls SATA interface Power Management for the specified channel, allowing some power to be saved at the cost of additional command
latency. Possible values:
0 interface Power Management is disabled (default);
1 device is allowed to initiate PM state change, host is passive;
2 host initiates PARTIAL PM state transition every time port becomes idle;
3 host initiates SLUMBER PM state transition every time port becomes idle.
4 driver initiates PARTIAL PM state transition 1ms after port becomes idle;
5 driver initiates SLUMBER PM state transition 125ms after port becomes idle.
Some controllers, such as ICH8, do not implement modes 2 and 3 with NCQ used. Because of artificial entering latency, performance degrada-
tion in modes 4 and 5 is much smaller then in modes 2 and 3.
Note that interface Power Management is not compatible with device presence detection. A manual bus reset is needed on device hot-plug.
hint.ahcich.X.sata_rev
setting to nonzero value limits maximum SATA revision (speed). Values 1, 2 and 3 are respectively 1.5, 3 and 6Gbps.
DESCRIPTION
This driver provides the CAM(4) subsystem with native access to the SATA ports of AHCI-compatible controllers. Each SATA port found is rep-
resented to CAM as a separate bus with one target, or, if HBA supports Port Multipliers, 16 targets. Most of the bus-management details are
handled by the SATA-specific transport of CAM. Connected ATA disks are handled by the ATA protocol disk peripheral driver ada(4). ATAPI
devices are handled by the SCSI protocol peripheral drivers cd(4), da(4), sa(4), etc.
Driver features include support for Serial ATA and ATAPI devices, Port Multipliers (including FIS-based switching, when supported), hardware
command queues (up to 32 commands per port), Native Command Queuing, SATA interface Power Management, device hot-plug and Message Signaled
Interrupts.
AHCI hardware is also supported by ataahci driver from ata(4) subsystem. If both drivers are loaded at the same time, this one will be given
precedence as the more functional of the two.
HARDWARE
The ahci driver supports AHCI compatible controllers having PCI class 1 (mass storage), subclass 6 (SATA) and programming interface 1 (AHCI).
Also, in cooperation with atamarvell and atajmicron drivers of ata(4), it supports AHCI part of legacy-PATA + AHCI-SATA combined controllers,
such as JMicron JMB36x and Marvell 88SX61xx.
SEE ALSO
ada(4), ata(4), cam(4), cd(4), da(4), sa(4)
HISTORY
The ahci driver first appeared in FreeBSD 8.0.
AUTHORS
Alexander Motin <mav@FreeBSD.org>.
BSD January 28, 2010 BSD