XXHighEnd

Ha, Ha,

there are problems here to connect an external eSata drive. The BIOS rejects to organize the two drives (RAM OS + external)

Any idea?
Thanx

Joachim

Hi there Joachim,

The BIOS I was talking about is for the X99M board. You talk about your X79(M) (I assume).

Can you be more specific about what you mean ?
So, I can understand that both the RAM OS Disk and something connected to eSata does not work. But the RAM OS disk can have been booted from a dozen or so permutations and to that can be added that the disk is still in the drive or not (4 more possibilities).

You could even mean that the RAM OS Disk can not boot from eSata (no idea about that but in that case it can only be about being able to boot over eSata and is not related to RAM OS etc.).

So I really don't know what situation you are talking about, plus it seems very tough for me to grasp what could be going on and how the RAM OS Disk can be related (read : I think not at all ;)).

Let me know !
Peter

Hi Peter,

correct. The RAM-OS using alone everything works fine. Connecting an additional eSata drive the system is stuck during booting. Changes in the Bios don't help.

I will install new drivers from the Asrock site for the mobo and will see.

On an other PC the eSata drive is recognized by the system during booting and works fine.

Joachim

Joachim,

I'd say that when the RAM OS Disk is not in there (but whatever is hooked up to your eSata indeed is during booting) - the same happens ?
Aha, you can't test that eh ?
haha

Again I don't see how this is related to the RAM OS Disk. Put another bootable disk in there to check ...

Regards,
Peter

I don't know if this is related, but I ran through a strange situation a few days ago.

My motherboard (Asus Sabertooth X79, from 2012) has two Esata ports (one also carries "power", the other is standard_. The 2 of them are not from Intel.

If I try to boot from any of them:
a) With a regular OS drive = Works (Windows 8 "plain vanilla")
b) With os-ram drive in base disk mode (Win 10) = does not work
c) With os-ram drive in ram mode = Works, but can't reconnect it to save settings at the end of the session.

Edit: It has been a long time since I have tried these 2 ports. I never tried them with a Win 10 standard drive.

I have no driver problem with the controller that manages these 2 ports with a regular OS drive, but it does not seem to be compatible with the os-ram drive when the OS is loaded as a base OS (not in ram).

Alain

Side notes:
- The 2 Esata ports are from AsMedia (sata 6gbit)
- My external connection works, because I wanted to have Sata 2 speed only (...), so the third connection is through an internal sata connection, to an Esata plaque at the rear. At the time I also wanted a third external drive,

Alain

Alain, good points you make there !

I can indeed imagine that booting from the OS BASE requires a quite standard (Windows) driver setup, which does not work everywhere and always. To me this looks a bit similar to (at least me) not being able to boot into the RAM OS from fast USB3. This, while booting into a normally set up OS just works.

Side note : possibly I only confuse now, because the boot from RAM is something else again, which thus in your eSata situation works (and this, while I did not even try the BASE boot from USB3).

> c) With os-ram drive in ram mode = Works, but can't reconnect it to save settings at the end of the session.

This could typically be a driver problem;
The other day I had some Inter-whatever-suite installed, and there was no way I could re-attach the RAM OS Disk. In this case the credo could be : have it as (Windows) standard as possible; what happens in there is quite "low level technical" and I think it can go wrong quickly.

Peter

Peter,

I don't know why I haven't tried these 2 external Esata ports before with the os-ram drive. I was lucky to have that Esata back plate. I have it as an accessory from an external HDD enclosure kit.

If you type "Esata back plate" in Google, you will have a good idea...

Alain

Alain, this is getting too off topic now. Start a new topic if you want ... but this is not eSATA at all. That is SATA bringing to the back of a PC ... (SATA is only for a very limited length (say 30-40cm); eSATA is for maybe 1m50 (I just name something).
Also, eSATA ports will not just be in a random place on the MoBo (like SATA). They always have an official connection at the back of the MoBo (PC).

Peter

Sorry to contradict you, but the two Esata ports are not from Intel and no one of them works with the os-ram drive in BASIC mode (not from ram) with Win 10... That is why I suggested to add a back plate that is Esata externally, but connected to a bug standard internal sata from the motherboard.

Alain

Hi,

the problem is not related to the RAM-OS, it's the BIOS/motherboard. I will check and update the motherboard drivers.

Joachim

He, he

strange, very strange.

The recommended Sata3 driver for the controller is not loaded into the OS (device manager), but, (external eSata3 drive is "OFF")

switching the external eSata3 drive during a running W10 "ON" the system recognizes the eSata drive and music files are available.

MannohMann.

Joachim

Hi Joachim,

Strange indeed :) I have 3 different brands of sata controllers on my motherboard... Go figure...

Alain

Joachim,

Can't this be a Windows 10 (driver) quirck ?
Easy to try with Windows 8 on the RAM OS Disk.

Otherwise I am sorry to say that I just don't have experience with the eSATA port on that PC. I just never needed it.
I don't think I have an eSATA disk (enclosure etc.) laying around either, otherwise I would try it for you ...

Regards,
Peter

Hi,
the answer is yes. In every WIN10 OS a different driver is loaded, but as long as it works with this routine everything is fine for me.

Joachim

So, solved for you ?

Hi,

yes.
Another possibility would be to install an Asmedia (controller) driver from 2013 or an Intel driver from the Asrock site for this mobo, but nobody knows how that will work. He, he.

The RAM-OS PC is running around the clock now and this scenario is a solution I can live with.
Thanx.

Joachim

Hi,

found out today, that in the BIOS (X79 chipset) under (South Bridge) "Storage configuration" all remaining eSata's connections shall be disabled, otherwise the external eSata drive will not be recognized by the running W10 OS.

Joachim

The fun thing is that if the "ram" load is effective, loading Windows in ram and booted from ram - all should be ok. It's only when one tries to "attach" the drive that something will be wrong (it will not connect)...

Alain