ThinkStation SAS SCSI



Tags: ThinkStation

Similar Questions

  • Add disk Workflow fails when you use the LSI Logic SAS SCSI controller

    I'm in vCenter Orchestrator 4.0.1

    When you try to run the workflow work add drive on a virtual machine that uses the LSI Logic SAS SCSI controller I get an error no controller found.

    This workflow is under: library-> VIM 3-> Virtual Machine Management-> device management

    The workflow add disk supports the LSI Logic SAS controller?  If this is not the case, no idea of how to create my own custom adds workflow to disk that would work with this controller?

    Thank you!

    Which plugin you have configured to talk to your Virtual Center? the plugin 3.5 or 4.0 plugin? If you have used the plugin 4.0, you must use the library-> VC-> * workflow so that the correct objects get used.

  • New hard drive fails on Windows Server 2008 VM with LSI Logic SAS SCSI controller

    When I try to add a new hard disk to a virtual computer with the cmdlet New-disk hard of a Windows Server 2008 virtual computer, I get the following error:

    New-hard drive: 18/01/2010-14:59:48 New-B8EDFDDF-ACF6-43AC-B111-51D332290FC7 hard drive for the entity vm-315 failed with the following message: "Number of virtual devices exceeds the maximum for a given controller."
    On line: 1 char: 13
    + new hard drive & lt; & lt; & lt; & lt; VM - $vm [5] - capacityKB 4194304
    + CategoryInfo: InvalidArgument: (vm - 315:String) , ViError
    + FullyQualifiedErrorId: Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed, VMware.VimAutomation.Commands.NewHardDisk

    When assigning a different virtual machine, for example the parallel LSI Logic Controller, it is not a problem at all. When I add additional disks using the VI Client, there also no problem, regardless of the SCSI controller I use.

    Someone had this problem as well? Y at - it a known solution?

    Hi rengelen,

    I admit that I was pretty murky about when the fix will be available. The thing is that VMware has a policy that employees should not mention liberation time unless we are certain that we can keep his promise of 100%. Hence statemens as 'will be available in a future release.

  • SAS Logic Controller / update of the virtual hardware

    so I did experiments with virtual hardware, logic SAS SCSI Controller in the virtual machine and enhance network drivers.

    First it is just me, or is this a VERY intensive upgrade, you must install the NEW vmtools, then stop, then upgrade the hardware (this is why I have experimented with the realization of the upgrade, and then Tools, which works very well).  However, using even a NEW CD of Windows install (2003) and the floppy disk controller, the SAS drive is not recognized.  I can add it during the 'press F6 for new controller... ". "blah blah blah... but he said some people found hard drives, as well as change the controller, despite having installed drivers with the tools of the NEW virtual machine still cause the OS to blue screen, inaccessible device.

    So now the question arises, someone understood what driver to use for this?  They should be, but they do not seem to work, FTM

    SAS controller is also required for the Windows Clustering 2008 because the old LSI adapter will not work (lack of support for SCSI-3).

  • ESX 3.5 SAS-map & eSATA drive

    We have a server IBM xSeries 336 which must lead more space. It's a test machine, so best performance and reliability is not necessary, we just need more space for the virtual machines.

    I think to get card-SAS Adaptec RAID 2045 and attach a disk external eSATA to it with mini SAS to eSATA cable. Would this work? I know that ESX doesn't really support sata but the card is at least on the supported list. ESX sees as SAS/SCSI or SATA drive and I was able to use it as a space vmfs?

    Thank you.

    Hello

    That's right!

    Best regards

    Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, url = http://www.virtualizationpractice.comvirtualization practical analyst [url]
    "Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security' VMware vSphere (TM) and Virtual Infrastructure Security: securing the virtual environment ' [url]
    Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]
    [url =http://www.astroarch.com/wiki/index.php/Blog_Roll] SearchVMware Pro [url] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links Top security virtualization [url] links | URL = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcast Virtualization Security Table round Podcast [url]

  • HP Pavilion dv6-6185tx: could you tell me the bus type of the hard drive (HDD) of HP Pavilion dv6-6185tx

    Hi, I would like to Exchange SSD for my PC, HP Pavilion dv6-6185tx. However, I couldn't find the but type (for example, SATA, SAS, SCSI, or IDE ect...) of this model on the Web site.

    If anyone knew that, please tell me, thank you very much!

    SATA, 9.5 mm or thinner SATA SSD will fit.

  • Windows 2008 Server Installer is not detect RAID5

    Hey everybody,

    So I tried to install Windows Server 2008 (not R2) on a Dell PowerEdge 2650 spare part, but when you are prompted to choose an installation location that nothing shows, at the bottom of the window, it is said "no hard disk found. "Click on load a driver.

    So I download drivers RAID SAS, SCSI and RAID SCSI disk on Dell website and put them on a USB key and windows does not recognize the drivers.

    It makes me crazy, I tried all the suggestions found online and not working

    Any help is greatly appreciated.

    * edit *.

    also have pictures of the BIOs settings and the RAID parameters if it helps someone

    During the RAID, also initialize the logical drive?

    Your system (BIOS, ESM, PERC) firmware is up to date? There is a very good chance that you will need the latest firmware for drivers to work.

    You should use this driver:
    http://downloads.Dell.com/SCSI-RAID/ADAPTEC_PERC3-DI_A01_R192965.exe

    You must download and run the file to extract the content before using.

  • This version of 5.5 U1 is vulnerable to the software? 1892794

    Hello

    I saw that there is a patch for 5.5 U1 to HeartBleed (ESXi550-201404001), we run build 1892794.  Research on the portal of the patch, this contains the following hotfixes:

    ESXi550-201407405-BG

    KO 2077411

    Critical bug fix

    Esx-base updates

    ESXi550-201407401-BG

    KO 2077407

    Critical bug fix

    Tools-light updates

    ESXi550-201407403-BG

    KO 2077409

    Fixed an Important bug

    Misc-drivers updates

    ESXi550-201407402-BG

    KO 2077408

    Fixed an Important bug

    Megaraid sas scsi updates

    ESXi550-201407404-BG

    KO 2077410

    Fixed an Important bug

    Esx-base updates

    ESXi550-201407101-SG

    KO 2077414

    Criticism of security

    Tools-light updates

    ESXi550-201407102-SG

    2077415 KB

    Important safety

    This suggests that the patch is NOT included in this version, but I learned that some of these bugs are cumulative and include patches.  Which is correct?

    Thank you

    Hello Dan,.

    Yes VMware fixes are cumulative so with build 1892794 you are already patched for the vulnerability of the software.

    Patch ESXi550-201404001 will take you to the version 1746018 which are already on the vulnerability of HB.

    Patch ESXi550-201404020 will take you to the version 1746974 which are already on the vulnerability of HB.

    ESXi 5.5 Patch 2 2014-07-01 1892794 Ok
    ESXi 5.5 Patch Express 4 2014 06-11 1881737 Ok
    ESXi 5.5 Update 1 has 2014-04-19 1746018 Ok
    ESXi 5.5 Express Patch3 2014-04-19 1746974 Ok
    ESXi 5.5 Update 1 2014 03-11 1623387 Vulnerable

    For the latest security patches, see this article:

    VMware KB: Security of VMware connection guidelines for ESXi and ESX

    So if you want the latest patch of security (for ESXi 5.5) go to the Patch ESXi550-201410101-SG this will update only the VIB esx-base and bring your host to the build 2093874.

    Or update the image with Patch version ESXi550-201410001 (including SG above) which will bring you to the last build real 2143827. (5.5 Patch3 ESXi)

  • Add copied hard disk (VMDK) on a virtual machine

    I'm new to PowerCLI and can't seem to find information on this "new" process

    I'm looking to automate the addition of a cloned hard disk (VMDK) VM (1) to an another VM (2) existing.  I figured out how "Hard drive copy" VM1 VM2 data store, but can't the formula to VM2.

    To copy the disc, I use the following command:

    $vm1 = "name of vm1.

    $vm2 = "name ofthe virtual machine 2 .

    $ds = "datastor" e

    Get-disk hard - VM $vm1 | Where {$_.} CapacityGB - lt 10} | Copy-hard drive - DestinationPath ' [$ds] vm2 $/ $vm2 - 2.vmdk '-Force

    In fact, here is what it looks like:

    Get-disk hard - VM System1. Where {$_.} CapacityGB - lt 10} | Copy-hard drive - DestinationPath "[NFS2] System2/System2 - 2.vmdk '-Force

    MISTLETOE we do today via vCenter is - change the s parameter > Hardware tab > Add > hard drive > use an existing virtual disk > Browse > check the virtual device node (SCSI 0: (x) - and it works.)  I can start VM2 and the Windows operating system works very well and everyone is happy.

    To set the hard drive via PowerCLI, I use the following command:

    New-disk-hard - VM $vm2 - DiskPath "[$ds] $vm2/vm2 $-2.vmdk»

    In fact, here is what it looks like:

    New- hard drive - VM System2 - DiskPath ' [NFS2] System2/System2-2.vmdk '

    When I run the command, I see vCenter 'work' and then error with Incompatible device support specified for the device '0'.  I have ready many forums reporting the error when you perform a RDM or tries to add a secondary SCSI controller, I don't want to do.

    A few things to note:

    Must be on the default 0 (Virtual LSI Logic SAS) SCSI controller

    Virtual device node must be SCSI 0:2 (it would be a third drive on the system)

    The data store is a different data store that the other disks attached to VM2 (discs 1 and 2 are on NFS1, new drive would be on NFS2).

    When I first copy the disc, it indicates the persistence as unknown, do not know if this is a factor. Any help would be appreciated.

    ESXi, 5.0 Update 1 (5.0.0,821926)

    PowerCLI 5.5 Release 2

    Thank you

    SC

    Lol, I'll type slowly

    No, I'm afraid that we cannot change the API, or the coding behind the cmdlet.

    But we can call the APIs directly from PowerCLI, something like this for example

    function add-HD {  param($VMname, $Filename, $Controller)
    
      $dsName = $Filename.Split(']')[0].TrimStart('[')
    
      $vm = (Get-VM $VMname).ExtensionData  $ds = (Get-Datastore -Name $dsName).ExtensionData
    
      foreach($dev in $vm.config.hardware.device){    if ($dev.deviceInfo.label -eq $Controller){      $CntrlKey = $dev.key    }  }  $Unitnumber = 0  $DevKey = 0
    
      foreach($dev in $vm.config.hardware.device){    if ($dev.controllerKey -eq $CntrlKey){      if ($dev.Unitnumber -gt $Unitnumber){$Unitnumber = $dev.Unitnumber}      if ($dev.key -gt $DevKey) {$DevKey = $dev.key}    }  }
    
      $spec = New-Object VMware.Vim.VirtualMachineConfigSpec  $spec.deviceChange = @()  $spec.deviceChange += New-Object VMware.Vim.VirtualDeviceConfigSpec  $spec.deviceChange[0].device = New-Object VMware.Vim.VirtualDisk  $spec.deviceChange[0].device.backing = New-Object VMware.Vim.VirtualDiskFlatVer2BackingInfo  $spec.deviceChange[0].device.backing.datastore = $ds.MoRef  $spec.deviceChange[0].device.backing.fileName = $Filename  $spec.deviceChange[0].device.backing.diskMode = "independent_persistent"  $spec.deviceChange[0].device.key = $DevKey + 1  ## The UnitNUmber SCSIID 7 is reserved for the Controller - so ignore it and skip to 8.  if ($Unitnumber -eq 6) {$Unitnumber = $Unitnumber + 1}  $spec.deviceChange[0].device.unitnumber = $Unitnumber + 1  $spec.deviceChange[0].device.controllerKey = $CntrlKey  $spec.deviceChange[0].operation = "add"  $vm.ReconfigVM_Task($spec)}
    
    Add-HD -VMname "System2" -FileName "[NFS2] System2/System2-2.vmdk" -Controller "SCSI Controller 0"
    

    I created a function called Add - HD, which will do more or less the same thing, just as the cmdlet New-hard drive when it is used with the name parameter file, but instead to call the cmdlet, the function calls the API ReconfigVM_Task directly.

    The downside of this is that we will have to compile the parameter passed to this method.

    In fact, most of the PowerCLI cmdlets do exactly the same thing, they call the API methods.

    You can view these calls when you draw a cmdlet with the tool of Onyx .

  • Create a virtual machine from una Máquina física

    Buenas tengo a PC con windows vista 32bits y intento con virtualizar VMWare, vcenter converter standalone, para eso he cogido Máquina física y he pinchado UN segundo disco, he abierto el programa VMWare vcenter converter standalone y he hecho lo siguiente:

    PASO 1: Machine Convert: this local machine (Origen)

    PASO 2: Destination: here he against the ruta donde quiero save the imagen y well he probado an exportar-lo para vmware player 2.5 y también he repetido el paso para vmware workstation 6.5.X

    PASO 3: customise the config, donde he marcado las options than in el siguiente pantallazo muestro

    Dibujo2222222.jpg

    Con todo esto to me genera el archivo used despues of than quiero import en otra Máquina

    Ahora OCOG maquina donde quiero import dicha imagen física y he probado lo siguiente:

    Option 1: open el vmware y hacer file == > open, cojer imagen anterior tal cual y run - the

    Option 2: open the vmware vcenter converter program is run the option of 'set machine', donde el ORIGEN economics y our crea en otra vidéoconférence otra imagen supposedly "reconfigurandola" para adaptar - a Máquina dicha.

    Option 1 the opcion como con tanto 2 al correr imagen sale el windows vista logo y despues sale me el pantallazo AZUL diciendome than verifique if he wont algun device recently etc etc etc... y but that arrival Coupling Nut a hacer a chkdsk /f (el qual he probado a hacer desde entering her recuperacion consoled) y me said that no podia por hacerlo algun reason.

    Con todo esto, alguien me could hechar una mano, o Yes alguna sugerencia o consejo?

    Gracias,.

    What tenes el equipo original disco? Como you Le Diego el archivo boot.ini indica al bootloader a Quebec n tiene than ir a buscar los archivos inicio del sistema operating system.

    For example if in el equipo original tenemos UN disco SAS, SCSI o algo por el estilo Máquina virtual definimos UN disco IDE if the boot.ini no to change the Máquina en virtual durante el proceso of conversion you can than este quédé apuntando UN do disco SAS luego no encuentra ago than what defined tenes are UN disco IDE in the virtual.

    Para mi can come por ese lado. Of todas formas you pido what pegues una captured of the led error pantalla para as lo mas clearly identify pruned.

    Best wishes / Saludos

    Por don't favor no olvides calificar las responses you valiosos ayuda o were should

    Please, do not forget the points of call of the "useful" or "correct" answers

    ________________________________________
    Nicolas Solop

    VMware vExpert 2010 - VCP 410 - VCP 310 - VAC - VTSP

    My Business Blog (Blog of the Wetcom group)

    Follow me on Twitter

    My Linkedin profile

    Join the Virtualizacion en Español group in LinkedIn

  • Material minimo o como "sonar" con instalar ESXi 4.0 ESX 4.0 en o a PC...

    Hola,

    Alguien to ha sown not con the situation of querer vSphere test pero no material of UN disponer "como Dios Manda?"   (todos los servidores estan occupied y en con production ESX 3.5update3... y sin vistas a actualizarse a Vsphere...)

    Se that can reach a "instalar" ESX VMWare Workstation dentro o VMWare Server ( http://xtravirt.com/ http://xtravirt.com/xd10072 ) pero the idea o el objetivo are coming has a PC of montar con el material minimum necessary (CPU x 64, a 2 GB of RAM mimino, nightclubs, SATA, SAS, SCSI,...)

    ES posible? Alguien lo ha hecho y sabe exactamente material minimum necessary hay than tener para montar o ESXi ESX 4.0?

    The tests las estoy realizando con an Acer PC Veriton M410 ADM64, 3 GB of RAM, 200 GB SATA HD, Ethernet 10/100/1000 y al lanzar the instalacion of ESXi 4.0 llega a momento that appears el siguiente error:

    -Cannot load the tmp

    -Failed to load lvmdriver

    Gracias.

    Gracias.

    Buenas tardes Krax,

    El siguiente enlace can serte utility are only covers muy detalladamente the instalacion of vSphere 4 tanto como Workstation molten. Also el tema of the stupid red card las easy incursions can reach has hacer funcionar. http://punchingclouds.com/?p=779. El of He present arrancar ESX con 768 MB of RAM tal y como is comenta en information del enlace.

    Ojo, hay par UN of errata, the street vmx seria en Sección segunda:

    Monitor.virtual_exec = "hardware".

    Monitor.virtual_mmu = "hardware".

    Monitor.Control.enable_svm = 'true '.

    Monitor.Control.restrict_backdoor = 'true '.

    VMX.allownested = true '.

    Al hacer copy & paste las dobles comillas you pueden dar algun disgustillo... Pero works fairly well.

    Espero sea of utility.

    Kind regards

    Alejandro.

  • ESXi on SD card and virtual machines on a NAS raid-6, performance?

    Hello!

    I'm planning an ESXi with HP Proliant DL380 G6 environment, which I already have.

    The server has an internal port SD card and according to this article , it is supported to run ESXi from an internal SD card.

    1ST QUARTER

    Someone hwo as tried this, what of the downside to this, except the redundancy on the SD card. I had a hard time finding comments on this

    Q2

    I intend to run virtual machines on a NAS via iSCSI, (thecus N8800, have another thread on the subject to know if it would work or not here)

    With this config I don't need any HD in the DL380.

    However, I do not know if a good high-performance NAS is good enough for my VMs and if maybe I need to run the OS on internal disks with higher performance.

    First of all, my plan was to run the OS partitions on a raid with internal 10 k SAS drives. And have all the data on the NAS partitions.

    But since I'm the new implementation of ESXi on SD or USB I think about the ability to run the DL380 without HD

    But, as noted above, is it possible that there is performance enough for that.

    Having in mind that my environment is and will be VERY LOW, we speak up seven windows server 2008 and totally 150 users.

    But I still haven't any idea if theres a chance that my 7 virtual machines running windows server 2008 will be capped at a lot by running NAS. The Nas will take place with eight 7.2 k RPM Sata disks, they are high of preforming sata drives, but not yet a SCSI raid. I have the ability to run a raid 10 on it instead of 6 and I will consider and try how much better performance, he gives me. 1 TB sata drives are 70% less expensive than the 300 GB 2.5 '' SAS 10 k disks.

    Yes, there is a good reason THAT SATA is less expensive than SAS.  SATA drives do not have the same command line than to use SAS drives, more the bottom of basket on SATA relies on the CPU, SAS can unload it on DEMAND.  The discs themselves seem to be competitive, but they are a far cry from the performance of SAS/SCSI, you get good performance until you start to make the e/s simultaneous sessions and hit heavily then you'll start to see performance degrades

    If do you some tests and that you are happy with it, still great.  I really hope it works well.  RAID 10 can be a good idea with SATA, which can help to compensate for this loss of performance.

    The PIN number is the best way to get the best performance, the physical drives of player throw you into a RAID of any kind the better you will be.

    Seagate Barracuda ES. 2-1 TB - 3.5 "- SATA-300 - 7200 tours min - lunch: 32 MB"

    vs SAS 15 K (that's 2 x the IOPS/sec)

  • 2008 clustering

    Good evening

    Does anyone know if ESXi 4 includes support for the unit of SAS SCSI-3 needed for the creation of Windows 2008 Clusters?  Also, it seems that the new version will be released May 21?  I just want to clarify these points like that on which way to go with a project I work on order.

    Thank you in advance.

    Welcome to the forums,

    No official date has been announced. vSphere licenses 4 will be available from that date, but I have not seen the ad. I also have not personally seen an official announcement on the scsi-3 part but I found this pdf file.

    see page 20

    Duncan

    VMware communities user moderator

    -

  • Create the virtual machine with the type of controller SCSI LSI logic SAS with PowerCLi

    Hey guys,.

    IM the difficulty to create a virtual machine with the type of controller SCSI to "LSI Logic SAS". The cmdlet New - VM im struggling to find where to create the type of controller?

    If you create a virtual machine without specifying a disk it will create a 4 GB SCSI type thick (0:0) hard drive 1 with 0 Parrall default BusLogic SCSI controller.

    What im wanting to do is to create a disk hard which is thin Prov. and create SCSI LSI logic SAS controller is set to.

    New-VM -name VMSTORE23 -$vmhost $esxhost MemoryMB- 4096 NumCpu- 2 -NetworkName "Vlan 6 Machine Virtual Network" | Get-NetworkAdapter | Set-NetworkAdapter -Type Vmxnet3 -MacAddress '00:50:56:00:00:21' -confirm:$false

    I have recived of aid by some LucD who helped direct the value of the network card in the New - VM cmdlet as follows. But I'm not able to add a hose for hard disk also like:

    | Get-hard drive | Together-hard drive - Datastore $datastore - slim StorageFormat

    And I have no idea how change the type of SCSI conroller or create it with the correct configuration?

    Any help would be great,

    Thanks in advance

    Eddie

    Greetings, steddyeddie-

    You should be able to use Set - hard drive and SCSI controller Set cmdlets to set the storage format of your hard drive and the SCSI controller type, respectively.  You were close to on the part of game - hard drive .  Try something like:

    ## get the VM object $vmVMSTORE23 = Get-VM VMSTORE23 ## set the harddisk storageformat to thin$vmVMSTORE23 | Get-HardDisk | Set-HardDisk -StorageFormat Thin ## set the SCSI controller type$vmVMSTORE23 | Get-ScsiController | Set-ScsiController -Type VirtualLsiLogicSAS
    

    It could pack in to your existing order to keep it as a good word, but for readability.

    Enjoy

  • Change the type of scsi controller / windows7Server64Guest and LSI Logic SAS

    Hello

    I would like the parallel to sas LSI Logic scsi LSI logic controller type.

    the reason is this colleague has created an image of windows 2008 R2 and I want to install the machine in script.

    He used LSI Logic SAS.

    When I used PowerCLi for create a new virtual machine with the existing drive, he created with the LSI Logic parallel...

    (of course I change it manually, but I would like to completely automate the installation)

    could someone help me on this?

    Thank you very much in advance

    Fred

    Have you ever watched the SCSI adapater to paravirtual with PowerCLI change ?

    Instead of the VMware.Vim.ParaVirtualSCSIController you select the VMware.Vim.VirtualLsiLogicSASController object.

    Let me know that make you it work if I can post a sample.

    ____________

    Blog: LucD notes

    Twitter: lucd22

Maybe you are looking for