Custom Query (34 matches)

The following scenario we have:

A machine that runs in legacy and AHCI mode in the BIOS. We switch the machine to legacy mode and run with Danis506.add version 1.8.9.

On a 1 .5. TB driver I installed boot manager first. Then I create a primary 200000 MB partition. Then the rest of the drive gets allocated by a logical partition of about 1.3 TB. Both partitions are added to the IBM boot manager. I can format the volumes and they are also listed in the installer as being volumes to which eComStation can be installed.

Then when I switch the BIOS to AHCI mode and load OS2AHCI.ADD driver (version 1.12) everything seems to work just fine!

But when I get to the installer page of eCS 2.1 I get the message no instable volumes where found and that the disc manager will be started (minilvm).

In the table where it says "notes" (the last column to the right in minlvm) it normaly mentions "Bootable " if a volume is added to the boot manager. Now with the AHCI driver loaded does "bootable" flags are gone. If I again load the system in legacy mode and with the DANIS506.ADD driver the bootable flags are displayed again in minilvm.

LVM does not give any error message when its get started. Attached is danis506.txt which is the output of lvm /startlog:. And OS2AHCI.txt which was created with the OS2AHCI.ADD loaded.

So it seems the LVM code is not able to read a portion of the disc. I presume the flags that tell bootmanager what partitions are stored in the bootmanager partition which is at the beginning of the disc. Is this some kind of geometry problem ?

While testing for bug 4 I booted of the eCS 2.1 CD ROM with the OS2AHCI.ADD loaded.

When I then inserted a DFsee in the CD ROM drive and went to drive S: on the command line and typed DIR I still got to see the old content of the eCS install CD (eCS 2.1 CD #1).

I don't know if this is a problem of this computer specifically system or the AHCI driver in general.

Bug opened in the eComStation bugtracker. Customer pointed to this bug to follow it.

Running at:

• VxT capable machine i3 with Windows 7 64bits
• VirtualBox? 4.0.6 (Windows 7 Host)

When changing the settings on the Virtual Machine Storage (Screenshot 1) to use AHCI HDD and CDROM the boot procedure hangs on OS2CDROM.DMD This bug was reported the eComStation bugtracker

The Boot settings get change to Virtual Machine (Screenshot 2) and turn AHCI mode (Screenshot 3).

• It hangs at OS2CDROM.DMD (Screenshot 4)
• It hangs at JJCDROM.DMD (Screenshot 5)
• It hangs at old OS2CDROM.DMD (Screenshot 6)

The workarround is to do not use AHCI SATA DRIVERS on VirtualBox?, but this bug report can be usefull to fix OS2AHCI and OS2CDROM.