OS2AHCI can not operate on large Disks (2 TB)

[Michaelhz]

When running a 512MB and a 2TB disk on an Intel NM10/ICH7 controller (8086:27C0) in IDE mode, everything works fine. Changing to AHCI-mode, only c-drive with 512 MB is visible.

DFSEE states:
ERROR disk nr 2 : EBR at 0x0000fe01, Cyl:1 cannot be read! RC:087

(Hopefully this is not a known problem, I did not find a similar ticket)

[David Azarewicz]

Please see ​http://svn.ecomstation.nl/ahci/wiki/Troubleshooting and attach a startup debug log to this ticket.

[Michaelhz]

The ahci.log-file is attached. Running now the dfsdisk-command.

[Michaelhz]

And now the output from dsfdisk

[Michaelhz]

Changed priority back since feedback was given.

[David Azarewicz]

The analysis of your log file indicates that you have 2 AHCI adapters enabled. Adapter 0 has 2 ports with 1 device connected to each port. The device connected to port 0 is working correctly. The device connected to port 1 is not working correctly. Adapter 1 has 7 ports with 1 device connected to port 7. This device is not working correctly. The other 6 ports on adapter 1 are empty.

It is well known that not all hardware is compatible with AHCI adapters. In particular, many atapi drives are not AHCI compatible. Drives that are not AHCI compatible cannot be used on an AHCI adapter, and can only be used on an EIDE adapter, or in EIDE mode.

Clearly the device on adapter 1, port 7 is not AHCI compatible. You cannot use this device on an AHCI adapter.

The device on adapter 0 port 1 is questionable. It worked for one transaction, and then failed to respond to the second transaction. This is a device error which may indicate that the device is not AHCI compatible.

Since these devices seem to work when connected to an EIDE adapter, it would indicate that the devices are not AHCI compatible. It could also indicate that port 1 on your AHCI adapter 0 is faulty. There is also a slight possibility something else is wrong. It is impossible to exactly identify the problem without more data, including an analysis of the hardware. I cannot think of anything else that can be done remotely.

You might try plugging the device that is currently plugged into adapter 0 port 1 into a different port. However, since the device on adapter 1 port 7 cannot be used on an AHCI adapter, you will have to switch at least one of the adapters to EIDE mode in order to use that device.

Just to be clear, this issue has absolutely nothing to do with the size of the disk(s).

[Michaelhz]

Following harddisks were tested:

WD500BPVT(17 Mar 2012, 2,5) - works in IDE and AHCI mode
WD30EZRX (08 May 2012, 3,5) - works only in IDE mode
WD20EZRx (28 Mar 2013, 3,5) - works only in IDE mode
WD20EZRX (28 Mar 2013, 3,5) - works only in IDE mode

The HD's are quite modern, so I do not think they are not AHCI-capable.

The WD500 drive is the boot drive, so it has to stay on the intel-adapter. The second adapter cannot boot. So I have only the big HD, which do not work on this adapter.

Unfortunately the second adapter cannot run in IDE-Mode and is not considered by DANIS506.

Any idea to come closer to the problem? Maybe I will install Win7 to the 2 new 2 TB HD's to show their AHCI-capability...

The controller is

Bus 0 (PCI Express), Device Number 31, Device Function 2
Vendor 8086h Intel Corporation
Device 27C0h N10/ICH7 Family SATA IDE Controller
Command 0007h (I/O Access, Memory Access, BusMaster?)
Status 02B0h (Has Capabilities List, Supports 66MHz,

Supports Back-To-Back Trans., Medium Timing)

Revision 02h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
PCI Class Storage, type IDE (ATA)
PCI EIDE Controller Features :

BusMaster? EIDE is supported
Primary Channel is in native mode at Addresses 0 & 1
Secondary Channel is in native mode at Addresses 2 & 3

Subsystem ID 20128086h DeskTop? Board D945GTP (Guess Only!)
Subsystem Vendor 8086h Intel Corporation
Address 0 is an I/O Port : 40B8h..40BFh
Address 1 is an I/O Port : 40CCh..40CFh
Address 2 is an I/O Port : 40B0h..40B7h
Address 3 is an I/O Port : 40C8h..40CBh
Address 4 is an I/O Port : 40A0h..40A7h
Address 5 is a Memory Address (0-4GiB) : D0700000h..D07003FFh
System IRQ 19, INT# B
New Capabilities List Present:

Power Management Capability, Version 1.1

Does not support low power State D1 or D2
Supports PME# signalling from mode(s) D3hot
PME# signalling is currently disabled
3.3v AUX Current required : 0 mA (Self powered)
Current Power State : D0 (Device operational, no power saving)

The second controller is:

Bus 2 (PCI Express), Device Number 0, Device Function 0
Vendor 1B4Bh Marvell Technology Group Ltd.
Device 9123h 88SE9123 PCIe SATA 6.0 Gb/s controller
Command 0007h (I/O Access, Memory Access, BusMaster?)
Status 0010h (Has Capabilities List, Fast Timing)
Revision 11h, Header Type 80h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
Cache line size 64 Bytes (16 DWords)
PCI Class Storage, type Serial ATA (AHCI 1.0)
Subsystem ID 91231B4Bh Unknown (Generic ID)
Subsystem Vendor 1B4Bh Marvell Technology Group Ltd.
Address 0 is an I/O Port : 2038h..203Fh
Address 1 is an I/O Port : 204Ch..204Fh
Address 2 is an I/O Port : 2030h..2037h
Address 3 is an I/O Port : 2048h..204Bh
Address 4 is an I/O Port : 2010h..201Fh
Address 5 is a Memory Address (0-4GiB) : D0500000h..D05007FFh
System IRQ 16, INT# A
Expansion ROM of 64 KiB decoded by this card, currently disabled
New Capabilities List Present:

Power Management Capability, Version 1.2

Does not support low power State D1 or D2
Supports PME# signalling from mode(s) D3hot
PME# signalling is currently disabled
3.3v AUX Current required : 0 mA (Self powered)
Current Power State : D0 (Device operational, no power saving)

Message Signalled Interrupt Capability

MSI is disabled
MSI function can generate 32-bit addresses

PCI Express Capability, Version 2

Device/Port? Type :

Legacy PCI Express Endpoint Device

Device Capabilities :

Unsupported Request Severity is Fatal

Device Status :

Correctable Error Detected
Unsupported Request Detected

Link Capabilities :

Maximum Link speed : Unknown (02h)!!
Maximum Link Width : x1
Link Port Number : 0

Link Control :

Common Clock Configuration In Use

Link Status :

Current Link speed : 2.5Gb/s
Current Link Width : x1

[Michaelhz]

win 7 hardware manager screenshot (please excuse the bad quality)

[Michaelhz]

Now tested with intel onboard AHCI-Controller and one WD20EZRX. Win 7 installed smoothly, bios was switched to AHCI-Mode.
So the HD's are running in AHCI-mode (see also the win7-screenshot)!!!
I can do further analysis with this installation. Please advise!

[Michaelhz]

Meanwhile i have tested a third AHCI-Controller. It is a ASMedia-Chip based controller. PCI.exe's output is the following:

Bus 3 (PCI Express), Device Number 0, Device Function 0
Vendor 1B21h Unknown
Device 0612h Unknown
Command 0107h (I/O Access, Memory Access, BusMaster?, System Errors)
Status 0010h (Has Capabilities List, Fast Timing)
Revision 01h, Header Type 00h, Bus Latency Timer 00h
Self test 00h (Self test not supported)
Cache line size 64 Bytes (16 DWords)
PCI Class Storage, type Serial ATA (AHCI 1.0)
Subsystem ID 10601B21h Unknown
Subsystem Vendor 1B21h Unknown
Address 0 is an I/O Port : E800h..E807h
Address 1 is an I/O Port : E400h..E403h
Address 2 is an I/O Port : E000h..E007h
Address 3 is an I/O Port : D800h..D803h
Address 4 is an I/O Port : D400h..D41Fh
Address 5 is a Memory Address (0-4GiB) : FEAFFC00h..FEAFFDFFh
System IRQ 17, INT# A
Expansion ROM of 64 KiB decoded by this card, currently disabled
New Capabilities List Present:

Message Signalled Interrupt Capability

MSI is disabled
MSI function can generate 32-bit addresses

Power Management Capability, Version 1.2

Does not support low power State D1 or D2
Does not support PME# signalling
Current Power State : D0 (Device operational, no power saving)

PCI Express Capability, Version 2

Device/Port? Type :

Legacy PCI Express Endpoint Device

Device Capabilities :

Unsupported Request Severity is Fatal

Device Status :

Correctable Error Detected

Link Capabilities :

Maximum Link speed : Unknown (02h)!!
Maximum Link Width : x1
Link Port Number : 1

Link Control :

Common Clock Configuration In Use

Link Status :

Current Link speed : Unknown (02)!!
Current Link Width : x1

With this adapter all 4 mentioned harddrives can operate in AHCI-mode.

First conclusion:
SO ALL DRIVES ARE DEFINITELY AHCI CAPABLE!

Second conclusion:
THERE IS AN ISSUE WITH INTEL ICH7 CONTROLLER, OS2AHCI and LARGE HD'S.

Observation:
Since Win7 has no problems to operate the big HD's on Intel ICH7, there is a

Third conclusion:
THERE IS AN ISSUE WITH OS2AHCI and LARGE HD'S. SO THIS BUG REPORT IS VALID

Further observation:
The ASMedia-Chip can run HD's which were partitioned and formatted with a different controller (e.g. a standard IDE controller).
The above mentioned Marvell controller behaves different. First you have to register the HD under the controllers bios. This changes the MBR of the drive, so all former data is lost. After registration the drive can be partitioned with LVM and formatted in a normal way.

Forth conclusion:
Different controllers expect different HD-geometry. I do not know, if this is AHCI compilant. Probably the big HD's MBR causes problems also to Intel ICH7

My presumption:
AHCI-controllers for other operating systems do some transition/filtering to understand big HD's geometry.

[Michaelhz]

Screenshot shows the 3TB drive running with OS2AHCI

[David Azarewicz]

The description of this it is "OS2AHCI can not operate on large Disks (2 TB)". OS2AHCI has absolutely no problem operating 2TB disks so this ticket is being closed.

Also, this ticket contains way to much pollution to even be considered.

ALWAYS read the wiki before opening a ticket.

DO NOT post screen shots of anything other than trap screens unless requested by the developer.

DO NOT post comparisons with anything regarding Windows. Windows works differently and is not relevant to OS/2 issues. Posting this type of information is totally worthless and only makes it more difficult to help you.

DO NOT post information about different configurations in a ticket unless requested by the developer.

NEVER argue with the developer. Doing so will get your ticket ignored and/or closed. This is an open source project. If you are so sure you know better, go get the source and have at it.

[Michaelhz]

Replying to dazarewicz:

NEVER argue with the developer. Doing so will get your ticket ignored and/or closed. This is an open source project. If you are so sure you know better, go get the source and have at it.

How to do w/o OS/2 DDK?