Migrating Boot Device fom SCSI to SATA

On 08/05/2012 4:03 PM, W wrote:
Unfortunately this is PCIe and I need PCI.

Maybe this, then?

Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102

On Tue, 08 May 2012 19:44:08 -0400, Yousuf Khan
wrote:

On 08/05/2012 4:03 PM, W wrote:
Unfortunately this is PCIe and I need PCI.

Maybe this, then?

Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102

If he needs eSATA I suppose he'll need an adapter (SATA to eSATA) with
that card. Also, it only runs at SATA-I speeds. Not sure if that will
be an issue or not but it's good to be aware.

"Yousuf Khan" wrote in message
...
On 08/05/2012 4:03 PM, W wrote:
Unfortunately this is PCIe and I need PCI.

Maybe this, then?

Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102

You can find 100 such cards on every retail web site. The point of my
question was to get recommendations for a specific card that someone had
experience with, specifically does the card have a BIOS configuration UI
that lives in the preboot environment so that I could explicitly enable the
card as a boot device.

It seems the world is filled with $25 eSATA cards that have minimal software
and minimal support. I would not mind spending $100 for something that is
top notch, extremely robust, and well supported in software and by email.

--
W

On May 8, 9:30*pm, "W" wrote:
"Yousuf Khan" wrote in message
Maybe this, then?

Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102

You can find 100 such cards on every retail web site. * The point of my
question was to get recommendations for a specific card that someone had
experience with, specifically does the card have a BIOS configuration UI
that lives in the preboot environment so that I could explicitly enable the
card as a boot device.

I only know for sure that the PCIe eSATA card that I pointed to first
does have its own BIOS, since I use that card. I don't know about the
second one, though.

According to one of the entries in that card's comments, they said
that they had to update the card's BIOS to get it to work with their
system, so that might indicate it's got some kind of a BIOS of its
own. But the commenter might actually be talking mistakenly about the
system BIOS rather than the card BIOS, hard to say.

It might be best to look for a PCI-SATA RAID card, as those would be
guaranteed to have their own BIOS. Something like this (it's much more
expensive than the previous one):

Newegg.ca - HighPoint RocketRaid1522A PCI SATA External Controller
Card
http://www.newegg.ca/Product/Product...82E16816115035

It seems the world is filled with $25 eSATA cards that have minimal software
and minimal support. * I would not mind spending $100 for something that is
top notch, extremely robust, and well supported in software and by email.

--
W

Yousuf Khan

On Tue, 8 May 2012 21:26:30 -0700 (PDT), YKhan
wrote:

On May 8, 9:30*pm, "W" wrote:
"Yousuf Khan" wrote in message
Maybe this, then?

Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102

You can find 100 such cards on every retail web site. * The point of my
question was to get recommendations for a specific card that someone had
experience with, specifically does the card have a BIOS configuration UI
that lives in the preboot environment so that I could explicitly enable the
card as a boot device.

I only know for sure that the PCIe eSATA card that I pointed to first
does have its own BIOS, since I use that card. I don't know about the
second one, though.

According to one of the entries in that card's comments, they said
that they had to update the card's BIOS to get it to work with their
system, so that might indicate it's got some kind of a BIOS of its
own. But the commenter might actually be talking mistakenly about the
system BIOS rather than the card BIOS, hard to say.

It might be best to look for a PCI-SATA RAID card, as those would be
guaranteed to have their own BIOS. Something like this (it's much more
expensive than the previous one):

Newegg.ca - HighPoint RocketRaid1522A PCI SATA External Controller
Card
http://www.newegg.ca/Product/Product...82E16816115035

It seems the world is filled with $25 eSATA cards that have minimal software
and minimal support. * I would not mind spending $100 for something that is
top notch, extremely robust, and well supported in software and by email.

I barely have the foggiest idea what the OP is looking for, but here's
a solution that uses the motherboard BIOS since it's just a pass-thru.
http://www.newegg.com/Product/Product.aspx?Item=N82E16812226003

YKhan wrote:
On May 8, 9:30 pm, "W" wrote:
"Yousuf Khan" wrote in message
Maybe this, then?
Newegg.ca - VANTEC 2-Port SATA II-150 PCI Host Card Model UGT-ST200
http://www.newegg.ca/Product/Product...82E16815102102
You can find 100 such cards on every retail web site. The point of my
question was to get recommendations for a specific card that someone had
experience with, specifically does the card have a BIOS configuration UI
that lives in the preboot environment so that I could explicitly enable the
card as a boot device.

I only know for sure that the PCIe eSATA card that I pointed to first
does have its own BIOS, since I use that card. I don't know about the
second one, though.

According to one of the entries in that card's comments, they said
that they had to update the card's BIOS to get it to work with their
system, so that might indicate it's got some kind of a BIOS of its
own. But the commenter might actually be talking mistakenly about the
system BIOS rather than the card BIOS, hard to say.

It might be best to look for a PCI-SATA RAID card, as those would be
guaranteed to have their own BIOS. Something like this (it's much more
expensive than the previous one):

Newegg.ca - HighPoint RocketRaid1522A PCI SATA External Controller
Card
http://www.newegg.ca/Product/Product...82E16816115035

It seems the world is filled with $25 eSATA cards that have minimal software
and minimal support. I would not mind spending $100 for something that is
top notch, extremely robust, and well supported in software and by email.

--
W

Yousuf Khan

The cards have an EEPROM, which holds Extended INT 0x13 code. If
that code is present, the BIOS reads in that code during POST.
And any disks off the card, can then be considered as boot
candidates. The EEPROM can also contain code, such as RAID
management code, so a user can create an array from the comfort
of their BIOS setup screen. So the code in the EEPROM on the
card, can provide two functions - Extended INT 0x13 for reading
sectors for boot purposes, as well as the ability to have
a "control panel in the BIOS" for setting up arrays.

There's an example here, of a card with an EEPROM on it. The
paper label stuck on the EEPROM, is for the manufacturer to keep
track of what kind of program was stored in it. With a lot of the
SIL3112 cards, customers spend most of their time changing the
code in there (as customers buy the "vanilla" card and want to
run a RAID array, or buy the "RAID" card and want to run the
ports in vanilla mode). To do that kind of flashing, you need
the flasher program, as well as the binary file with the code
in it, to do the updating. SiliconImage on their website, used
to provide such things. It's a distraction that I bet a lot
of customers could do without (i.e. find a solution where one
code performs all flavors). Even a switch or a jumper on the card,
would be better than having to screw around with flashers.

http://images10.newegg.com/NeweggIma...104-219-16.jpg

As far as I know, that code lives in "config space". And when the
code is loaded during POST, it is located below 640K, in a 128KB
area set aside for it. Once the system is booted, then it doesn't
really matter what happens in there. The VESA BIOS code copied
from the video card during POST, also lives in that 128KB area.

Even peripheral chips on the motherboard, have code modules
provided for them. The motherboard BIOS image is modular, and
is a miniature file system. As an example, a NIC chip can have
a PXE code module, so that the BIOS can "net boot" via the NIC.
With the appropriate BIOS tools, it's possible to review what
modules are present in the BIOS. For things like the PXE code
module, there is probably also a BIOS setting, to disable
that code module if you don't want it. On my motherboard, the
options a

Marvell Gigabit LAN [Enabled]
LAN Boot ROM [Disabled]

I can leave the so-called Boot ROM disabled on that, because
I have no devices on the network for serving up an OS image
to boot from.

Paul

On 05/07/2012 08:54 PM, W wrote:
wrote in message
...
On 05/07/2012 12:03 AM, W wrote:
wrote in message
...
On 05/06/2012 05:43 PM, W wrote:
Can someone recommend an eSATA PCI host adapter that has a built in
BIOS
that can be configured in a preboot environment to make the card the
boot
device on the system?

Ideally the card should have four eSATA ports and supports multiple
SATA
drives on each connection.

You missed the point.

If you cloned your old system to a raid
there will be no reference to the raid signature in boot.ini
as you were previously booting from a simple volume

Since the the boot adapter.

Although I know your system will not be able to boot until boot.ini
references the RAID signature, rather than a simple volume...I have no
idea how Windows actually assigns the signature.

What I am trying to explain is that I did NOT use Windows software RAID to
build the volume. I am using hardware RAID and Windows XP sees the RAID 5
array as a single Basic Disk with a single bootable Active Simple Partition.


That was obvious

Like I said if you had taken my advice you would have been up and
running days ago

sheesh
--
https://www.createspace.com/3707686

On 09/05/2012 1:01 AM, Char Jackson wrote:
On Tue, 8 May 2012 21:26:30 -0700 (PDT),
wrote:
On May 8, 9:30 pm, wrote:
It might be best to look for a PCI-SATA RAID card, as those would be
guaranteed to have their own BIOS. Something like this (it's much more
expensive than the previous one):

Newegg.ca - HighPoint RocketRaid1522A PCI SATA External Controller
Card
http://www.newegg.ca/Product/Product...82E16816115035

I barely have the foggiest idea what the OP is looking for, but here's
a solution that uses the motherboard BIOS since it's just a pass-thru.
http://www.newegg.com/Product/Product.aspx?Item=N82E16812226003

My assumption is that he's running some sort of an older board which
doesn't have any onboard SATA ports. It may not have any PCIe X1 ports
either, therefore he has to use a PCI SATA card instead.

Yousuf Khan

"philo" wrote in message
...
On 05/07/2012 08:54 PM, W wrote:
wrote in message
...
On 05/07/2012 12:03 AM, W wrote:
wrote in message
...
On 05/06/2012 05:43 PM, W wrote:
Can someone recommend an eSATA PCI host adapter that has a built in
BIOS
that can be configured in a preboot environment to make the card the
boot
device on the system?

Ideally the card should have four eSATA ports and supports multiple
SATA
drives on each connection.

You missed the point.

If you cloned your old system to a raid
there will be no reference to the raid signature in boot.ini
as you were previously booting from a simple volume

Since the the boot adapter.

Although I know your system will not be able to boot until boot.ini
references the RAID signature, rather than a simple volume...I have no
idea how Windows actually assigns the signature.

What I am trying to explain is that I did NOT use Windows software RAID
to
build the volume. I am using hardware RAID and Windows XP sees the RAID
5
array as a single Basic Disk with a single bootable Active Simple
Partition.


That was obvious

Like I said if you had taken my advice you would have been up and
running days ago

I don't find any advice from a user named philo in this thread. The first
post you made that appears in my newsreader software is a complaint.

I have advice from other users to run FIXMBR. I have users indicating I
may need to adjust boot.ini and some advice on how to examine the partition
table. I don't have any post explaining any procedure that would
automatically recreate or adjust boot.ini. Maybe you need to repost
something.

--
W

"Yousuf Khan" wrote in message
...
On 09/05/2012 1:01 AM, Char Jackson wrote:
On Tue, 8 May 2012 21:26:30 -0700 (PDT),
wrote:
On May 8, 9:30 pm, wrote:
It might be best to look for a PCI-SATA RAID card, as those would be
guaranteed to have their own BIOS. Something like this (it's much more
expensive than the previous one):

Newegg.ca - HighPoint RocketRaid1522A PCI SATA External Controller
Card
http://www.newegg.ca/Product/Product...82E16816115035

I barely have the foggiest idea what the OP is looking for, but here's
a solution that uses the motherboard BIOS since it's just a pass-thru.
http://www.newegg.com/Product/Product.aspx?Item=N82E16812226003

My assumption is that he's running some sort of an older board which
doesn't have any onboard SATA ports. It may not have any PCIe X1 ports
either, therefore he has to use a PCI SATA card instead.

Correct

--
W

W wrote:
"philo" wrote in message
...
On 05/07/2012 08:54 PM, W wrote:
wrote in message
...
On 05/07/2012 12:03 AM, W wrote:
wrote in message
...
On 05/06/2012 05:43 PM, W wrote:
Can someone recommend an eSATA PCI host adapter that has a built in
BIOS
that can be configured in a preboot environment to make the card the
boot
device on the system?

Ideally the card should have four eSATA ports and supports multiple
SATA
drives on each connection.
You missed the point.

If you cloned your old system to a raid
there will be no reference to the raid signature in boot.ini
as you were previously booting from a simple volume
Since the the boot adapter.
Although I know your system will not be able to boot until boot.ini
references the RAID signature, rather than a simple volume...I have no
idea how Windows actually assigns the signature.
What I am trying to explain is that I did NOT use Windows software RAID
to
build the volume. I am using hardware RAID and Windows XP sees the RAID
5
array as a single Basic Disk with a single bootable Active Simple
Partition.
That was obvious

Like I said if you had taken my advice you would have been up and
running days ago

I don't find any advice from a user named philo in this thread. The first
post you made that appears in my newsreader software is a complaint.

I have advice from other users to run FIXMBR. I have users indicating I
may need to adjust boot.ini and some advice on how to examine the partition
table. I don't have any post explaining any procedure that would
automatically recreate or adjust boot.ini. Maybe you need to repost
something.


You can review the thread in Google, if you have any doubts about
who posted what.

http://groups.google.com/group/micro...9eff4e9191f6da

Paul

On 05/09/2012 12:52 PM, W wrote:
wrote in message
...
On 05/07/2012 0ago

I don't find any advice from a user named philo in this thread. The first
post you made that appears in my newsreader software is a complaint.

I have advice from other users to run FIXMBR. I have users indicating I
may need to adjust boot.ini and some advice on how to examine the partition
table. I don't have any post explaining any procedure that would
automatically recreate or adjust boot.ini. Maybe you need to repost
something.



I did not post any complaints other than trying to figure out why you
just did not take the advice you were given and fix your MBR.
It is totally obvious you are not using s software RAID
and as I clearly stated ...if you cloned your "simple volume"
installation to a RAID it will be impossible to boot as boot.ini will
have no reference to the RAID signature


If you boot from your XP cd and go to the repair console
all you'd have to do is issue the command fixboot or possibly fixmbr

or else follow the link I gave you for other methods to rebuild your
boot configuration...

At any rate it would have been a simple enough process
but my first suggestion to perform a repair install might have been the
simplest way to go if you are not comfortable using the repair console.
(It would have taken a longer time though)


Now I know you wanted to manually edit your boot.ini file...
and that's a reasonable enough question...but honestly
I do not know how Windows assigns the RAID signature but I can tell you
it is not intuitive. Once you do it and have a look you'll see wht

--
https://www.createspace.com/3707686

"philo" wrote in message
...
On 05/09/2012 12:52 PM, W wrote:
wrote in message
...
On 05/07/2012 0ago

I don't find any advice from a user named philo in this thread. The
first
post you made that appears in my newsreader software is a complaint.

I have advice from other users to run FIXMBR. I have users indicating
I
may need to adjust boot.ini and some advice on how to examine the
partition
table. I don't have any post explaining any procedure that would
automatically recreate or adjust boot.ini. Maybe you need to repost
something.

I did not post any complaints other than trying to figure out why you
just did not take the advice you were given and fix your MBR.
It is totally obvious you are not using s software RAID
and as I clearly stated ...if you cloned your "simple volume"
installation to a RAID it will be impossible to boot as boot.ini will
have no reference to the RAID signature

The original advice was to use FIXMBR. But that doesn't modify boot.ini
does it? I assumed I might have to play with BOOTCFG /Rebuild for that.

In any case I appreciate the advise.

--
W

On 05/11/2012 06:46 PM, W wrote:
wrote in message
...
On 05/09/2012 12:52 PM, W wrote:
wrote in message
...
On 05/07/2012 0ago

I don't find any advice from a user named philo in this thread. The
first
post you made that appears in my newsreader software is a complaint.

I have advice from other users to run FIXMBR. I have users indicating
I
may need to adjust boot.ini and some advice on how to examine the
partition
table. I don't have any post explaining any procedure that would
automatically recreate or adjust boot.ini. Maybe you need to repost
something.

I did not post any complaints other than trying to figure out why you
just did not take the advice you were given and fix your MBR.
It is totally obvious you are not using s software RAID
and as I clearly stated ...if you cloned your "simple volume"
installation to a RAID it will be impossible to boot as boot.ini will
have no reference to the RAID signature

The original advice was to use FIXMBR. But that doesn't modify boot.ini
does it? I assumed I might have to play with BOOTCFG /Rebuild for that.

In any case I appreciate the advise.



This is the best link I could find


http://support.microsoft.com/kb/314058

--
https://www.createspace.com/3707686

On 5/11/2012 6:46 PM, W wrote:
The original advice was to use FIXMBR. But that doesn't modify boot.ini
does it? I assumed I might have to play with BOOTCFG /Rebuild for that.

No FIXMBR doesn't touch the boot.ini.

--
Bill
Gateway M465e ('06 era) - Thunderbird v12
Centrino Core Duo T5600 1.83GHz - 2GB - Windows XP SP2