Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Host unable to see HDD after booting into VP

Updated: 22 May 2010 | 3 comments
Labadmin's picture
0 0 Votes
Login to vote

SGC 11.0.2.1573

We have recently deployed some Dell PE R300 with SATA drives that are controlled by a LSI SAS controler  (No that is not a typo yes it is a SAS controler managing SATA drives)
The problem is that after a number of re-images tasks using SGC  an number of hosts during post will throw up a controler error and will not discover the disks. move the HDD to a know good machine and the same result.
if we wipe the disk of all parttitons and reload the image it will work fine for a while and then the same thing will happen. This is not a HDD or controller issus as we have had replacments and still it happens.

We can only assume that when the host boots to VP and re-writes the mbr something is getting corrupted and not allowing the SAS controler to see the drive infromation?

We would moving to a fixed GBP solev this issue?

Thanks

discussion Filed Under:

Comments

EdT's picture
22
Sep
2009
0 Votes 0
Login to vote

Driver version

Just a thought - are you using the latest available LSI SAS driver for your boot system?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Labadmin's picture
22
Sep
2009
0 Votes 0
Login to vote

We are using the latest

We are using the latest firmware from Dell,   have tried to find firmware direct from LSI but nothing is compatable I can anly assume dell frags the chipset some how.
We are fairly sure is is not a hardware issue and we have 16 servers and this only affects on average four clients per task.

EdT's picture
22
Sep
2009
0 Votes 0
Login to vote

I'm asking about driver, not firmware

I am checking if you are using the latest LSI SAS drivers (not firmware) as native WinPE does not support LSI if I recall correctly.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.