(Solved) Boot failure: Drive containig VeloSSD is not available

vbimport

#1

Hello,

after installing VeloSSD 2.0.0.8 on Win XP and cerating one SSD-cache i get this boot failure from VeloSSD bootsector: The Device containing VeloSSD is not available. Please conneet it and start again.

To fix this boot failure i have to recover original Win XP bootsector (Win XP Recovery Console with fixboot).

It seems to me that VeloSSD bootsector can’t find the harddrive or the ssd-drive.


#2

Hi,
this happens when the ssd is not connected at boot time.
Have you disconnected the device ?
Does the Bios recognize the SSD ?
If the Bios has recognized the SSD you can not get that message.

If you need to recover then there is an explanation of how to do it
correctly for Windows7, please follow it:

For Windows XP:
Boot from Install medium,
select recovery console,
type : fixboot
type: y
type:exit
System reboots.
Remove the cache volume from within the VeloSSD Application.


#3

[QUOTE=EliteBytes;2649901]this happens when the ssd is not connected at boot time.
Have you disconnected the device ?
Does the Bios recognize the SSD ?[/QUOTE]

No, i have NOT disconnected the SSD (it’s inside of PC case).
Yes, BIOS boot-screen and BIOS settings show the SSD, see BIOS-hardcopy.
SATA1 HDD: 3H-SAMSUNG…
SATA2 SSD: 3S-OCZ-PETROL
SATA3 DVD: 4M-TSSTcorp…

[QUOTE=EliteBytes;2649901]If the Bios has recognized the SSD you can not get that message.[/QUOTE]
Hmmm, so what else might be the problem?



#4

Thanks for the additional info.
This will help a lot
to investigate this problem.
All i can see now is that the primary Disk has some empty
space at the start. That can not be the reason,
but we´ll check that configuration.
And report back what we have found.


#5

[QUOTE=jgrob;2649900]VeloSSD 2.0.0.8 on Win XP[/QUOTE]
I have tested the newly released version 2.0.0.9 too and the problem still exists.


#6

Hello jgrob,

correct, we´d posted it if we had fixed it.
Right now we are preparing a version with gui enhancements
to allow Write through / Write back operation
be selectable by the user. Look:

We will test Xp with an empty first partition,
btw. Is the empty space parttioned or unpartitioned ?
Please be patient 1 or 2 days.



#7

[QUOTE=EliteBytes;2650805]btw. Is the empty space parttioned or unpartitioned ?[/QUOTE]

The empty space ist unpartitionet. More details show Microsoft DiskPart.


Microsoft DiskPart Version 5.1.3565
 
DISKPART> list volume
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     E                       DVD             0 B
  Volume 1     C   System_C     NTFS   Partition    501 GB  OK         System
  Volume 2     D   Daten_D      NTFS   Partition    198 GB  OK
  Volume 3     V   SSDCache     NTFS   Partition     60 GB  OK
  Volume 4     H                       Wechselmed      0 B
  Volume 5     I                       Wechselmed      0 B
  Volume 6     J                       Wechselmed      0 B
  Volume 7     K                       Wechselmed      0 B
 
DISKPART> list disk
  Datentr.  Status      Größe    Frei     Dyn  GPT
  --------  ----------  -------  -------  ---  ---
       0    Online       699 GB   102 MB
       1    Online        60 GB      0 B
 
DISKPART> select disk 0
Datenträger 0 ist der derzeit gewählte Datenträger.
 
DISKPART> detail disk
SAMSUNG HD753LJ
Datenträger-
kennung     : 08FD41F9
Typ         : IDE
Bus         : 0
Ziel        : 0
LUN-Kennung : 0
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 1     C   System_C     NTFS   Partition    501 GB  OK         System
  Volume 2     D   Daten_D      NTFS   Partition    198 GB  OK
 
DISKPART> list partition
  Partition      Typ               Größe    Offset
  -------------  ----------------  -------  -------
  Partition 1    Primär             501 GB   102 MB
  Partition 2    Primär             198 GB   501 GB
 
DISKPART> select partition 1
Partition 1 ist die derzeit gewählte Partition.
 
DISKPART> detail partition
Partition 1
Typ      : 07
Versteckt: Nein
Aktiv    : Ja
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1     C   System_C     NTFS   Partition    501 GB  OK         System
 
DISKPART> select partition 2
Partition 2 ist die derzeit gewählte Partition.
 
DISKPART> detail partition
Partition 2
Typ      : 07
Versteckt: Nein
Aktiv    : Nein
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2     D   Daten_D      NTFS   Partition    198 GB  OK
 
DISKPART> select disk 1
Datenträger 1 ist der derzeit gewählte Datenträger.
 
DISKPART> detail disk
OCZ-PETROL
Datenträger-
kennung     : 1B9D0716
Typ         : IDE
Bus         : 0
Ziel        : 1
LUN-Kennung : 0
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3     V   SSDCache     NTFS   Partition     60 GB  OK
 
DISKPART> select partition 1
Partition 1 ist die derzeit gewählte Partition.
 
DISKPART> detail partition
Partition 1
Typ      : 07
Versteckt: Nein
Aktiv    : Nein
  Volume      Bst  Bezeichnung  DS     Typ         Größe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3     V   SSDCache     NTFS   Partition     60 GB  OK
 
DISKPART> exit


#8

you are lucky,
we made a clone of your disks
layout and installed VeloSSD.
It hangs at the very first boot stage.

We investigate this further tomorrow.
Seems we have found a point of failure.


#9

[QUOTE=EliteBytes;2650914]
It hangs at the very first boot stage.

We investigate this further tomorrow.
Seems we have found a point of failure.[/QUOTE]

I have tested version 2.0.1.0 RC release date 23.08.2012 and the problem still exists.


#10

I have done some further testing.

Moving the system partiton c: to the hdd beginning (removing unpartitioned space) does not help. Therefore it looks like more an issue with BIOS an less an issue with partition layout to me.

Maybe you have noticed the slight unusual BIOS drive enumeration (see BIOS hardcopy above).
SATA1 is 3M -> Port 3 Master
SATA2 is 3S -> Port 3 Slave
SATA3 is 4M -> Port 4 Master
SATA4 is 4S -> Port 4 Slave

Port 1 Master, Port 1 Slave, Port 2 Master and Port 2 Slave seems to be reseved for legacy PATA ports.


#11

Hello Elitebytes Support,

i have done more testing.

Switching SATA transfer mode in BIOS from IDE to AHCI and installing NVIDIA nForce SATA AHCI drivers v11.1.0.43 for Win XP does not help.

By now i feel certain, that VeloSSD bootsector is not able to detect the harddrive/ssddrive by the use of BIOS calls.

Are you still working on this issue?


#12

We made a little break due to heavy work load.
But the original situation with 100 spare place in front is
being worked at right now.


#13

Hello Elitebytes Support,

[QUOTE=EliteBytes;2652785]But the original situation with 100 spare place in front is being worked at right now.[/QUOTE]

The spare place in front seems not to be the main problem to me.
Please see also post #10 “Moving the system partiton c: to the hdd beginning (removing unpartitioned space) does not help”.


#14

Hi JGrob,
I understand, searching for the board in the internet showed the following:

-it is >4 year old board.
-the Bios Revision you seem to have is old too V1.116 versus V3.0 (!)

it does not get sold nomore. So the option to buy and test with it doesn´t exist.

The original post however gave us something to check out with.


#15

Hello EliteBytes Support,

[QUOTE=EliteBytes;2652787]-it is >4 year old board.
-the Bios Revision you seem to have is old too V1.116 versus V3.0 (!)[/QUOTE]

I have testet BIOS version v1.16 (does not support AHCI) and BIOS versions v2.0S and v3.0T (both with AHCI support).

Since only BIOS v1.16 does allow CPU and case fan speed adjustment i kept this version.

All in all newer BIOS versions does not help.


#16

Hello Elitebytes Support,

by now i feel certain, that VeloSSD bootsector is not able to detect the harddrive/ssddrive by the use of BIOS calls (tested with BIOS v1.16 IDE, v2.0S IDE, v2.0S AHCI, v3.0T IDE and v3.0T AHCI).

Are you still working on this issue?


#17

Hello,
For the upcoming version 2.0.1.3 update we test a lot of Storage scenarios,
including your one. So, yes.


#18

Hello EliteBytes,

i have tested version 2.0.1.4 and i am sad to tell that the problem still exists:
“The Device containing VeloSSD is not available. Please conneet it and start again.”

Are you aware that this might be NO problem with disk layout or storage scenario BUT maybe VeloSSD bootsector is not able to detect the harddrive/ssddrive by the use of bios calls?


#19

i have tested version 2.1.0.0 and i am glad to tell that the problem seems to be fixed.


#20

[QUOTE=jgrob;2681951]i have tested version 2.1.0.0 and i am glad to tell that the problem seems to be fixed.[/QUOTE]

Good to hear that they managed to sort your problem eventually.

Thanks for taking the time to report back as I know everyone here likes to see problems getting resolved.

[B]Wombler[/B]