SCSI LUN DisplayName update

Hey people,

I'm trying to to bulk update (data warehouses and RDM) scsi LUN names that attended my ESXi cluster. I can get the information I need using the following (the example lists a unique device based on the canonical name of filtering):

$esxName = 'myserver.mydomain.com '.

$esx = get-VMHost $esxName | Get-View

$scsiLun = $esx. Config.StorageDevice.ScsiLun | where {$_.} {LunType - eq 'disc' - AND $_.canonicalName.substring (32) - eq "3000"}

Write-Host $scsiLun.CanonicalName $scsiLun.DisplayName

I want to update the DisplayName property. I tried $scsiLun.Set_DisplayName ("test"), but it does not apply correctly.

Does anyone have any suggestions?

See you soon!

I put myself up against by the script in your first post.

It is not the CanonicalName you want to change, but the DisplayName property.

Since you mentioned that you did via vSphere client, I realized what you were trying to do.

Yes, this can be done.

Use something like this

$esxName = 
$esx = Get-VMHost $esxName | Get-View
$storSys = Get-View $esx.ConfigManager.StorageSystem
$esx.Config.StorageDevice.ScsiLun | where {$_.LunType -eq "disk"} | %{
     $storSys.UpdateScsiLunDisplayName($_.Uuid, $_.DisplayName + " test")
}

This script only adds the suffix 'test' to the existing value.

____________

Blog: LucD notes

Twitter: lucd22

Tags: VMware

Similar Questions

PowerCLI script to update SCSI LUN DisplayName

Hello
I'm looking for the powercli command to use to be able to change the display name for the (storage) devices based on the canonical name (naa.*).
I have a script that allows you to capture the DisplayName of the device and CanonicalName configured for a devices using vCenter, but I wasn't able to write a new DisplayName for devices using PowerCli.
When we use vCenter to update the DisplayName property of devices, an order of "Update unit logic SCSI display name number" is displayed.
I'm looking for a way to use PowerCli for updating this DisplayName in the same way that we do manually in vCenter, based on the devices for example CanonicalName.
I have hundreds of devices to rename and need a script to do this.
Thank you in advance for your help.
Stephan Olczak

Of course, I found that the master of the masters, Luc D, already posted the correct script in 2010 (thread 261045).

Topic closed.

get support scsi LUNS for the data store?

I've been delving into the different classes available to HostSystem.queryHostConnectionInfo () and none of the properties appear to contain the id of naa I see when I look at LUNS on an HBA. How do you get to LUN support for a data store?

Figured it out. For anyone else who wants to know:

I created two actions, one to return a hash of the id of naa-online data store object and another action to return a hash of the naa-online drive scsi id

// actions
//getDatastoresKeyedByLUN
var o_diskHash = new Properties();

for each (var scsiDisk in u_host.config.storageDevice.scsiLun)
{
  //System.log("-> LUN: " + scsiDisk.canonicalName);
  for each (var dataStore in u_host.datastore)
  {
  if (dataStore.info.hasOwnProperty("extent"))
  {
  for each (var scsiDiskPartition in dataStore.info.vmfs.extent)
  {
  if (scsiDiskPartition.diskName == scsiDisk.canonicalName)
  {
  o_diskHash.put(scsiDisk.canonicalName, dataStore);
  }
  }
  }
  }
}

return o_diskHash;

// getScsiDisksKeyedByLUN
var o_diskHash = new Properties();

for each (var scsiDisk in u_host.config.storageDevice.scsiLun)
{
  o_diskHash.put(scsiDisk.canonicalName, scsiDisk);
}

return o_diskHash;

// in workflow
for each (var can in dstoreMap.keys)
{
  System.log(dstoreMap.get(can).name + "(" + lunMap.get(can).canonicalName + ")");

}

Manually load balancing / setting of the LUN paths.

I am wanting to manually load balance my Lun, there are 4 paths, and I want to cycle each round logic unit through the other way and back loop number. Am on vSphere 4 Update 1.
Browsing the web I found these two articles provide the code I'm after but the two error for me.
http://vmjunkie.WordPress.com/2009/01/29/balancing-LUN-paths-on-your-ESX-hosts-with-PowerShell/
http://doitsmarter.blogspot.com/
-
1. Check with the user
$vc = Read-Host "Please enter the name of the vCenter server:
$uname = Read-Host "Please enter the user name to connect to vCenter server:
$upass = Read-Host "Please enter the password that is associated:
$clusterName = Read-Host "Please enter the name of the Cluster:
Write-Host "Connection to the server vCenter $vc, please wait." - black BackgroundColor - ForegroundColor white
SE connect-VIserver $vc - user $uname - password $upass | Out-Null
###
1. Recover clustered ESX hosts
$VMHosts = get-Cluster $clusterName | Get-VMHost
1. Run through this loop for each host in the cluster
foreach ($VMHost to $VMHosts)
{
$luns = @($VMHost | get-scsilun-luntype disque | where-object {$_.) {ConsoleDeviceName-like ' / vmfs/devices/drives/vml * "} | Sort-Object CanonicalName)
$firstLUNPaths = get-ScsiLunPath $luns [0]
$numPaths = $firstLUNPaths.Length
$count = 0
foreach ($lun to $luns)
{
If ($count - ge $numPaths)
{
$count = 0
}
$paths = get-ScsiLunPath - ScsiLun $lun
$lun | Game-ScsiLun - MultipathPolicy fixed PreferredPath - $paths [$count]
$count += 1
1. Sleep 30 seconds to avoid saturation of the picture.
Start-Sleep - 30 seconds
}
}
-
Initially, I found the script stumbled upon the $luns [0] which means the value is null or empty. I replaced vml with naa. Now, I got "one or several mandetory missing settings SCSI LUN". An error with the syntax, but I'm not able to establish that, I guess.
Now, if I run certain commands on the command line I find I'm out usable. But by channeling the same row in a table or the variable, then the Write-Host of the content, I see "VMware.VIMAutomation.ViCore.Impl.V1" (and so on).
Judging by the dates of the blog posts that I am of the opinion the latest PowerCLI (v4 build 264274) can return the information in a different way, I'm wrong with my assumption?
Can you guess what will be my next question? How could I do that now?
Any help is appreciated and rewarded (in points not beer).
Thank you
Darren.

The "vml", "naa"... depends on the type of storage are your LUNs.

The problem with this statement is that you must specify the parameter - Scsilun.

This can be a positional parameter (without - Scsilun), but then it has to come in position 2.

See the page Get-ScsiLunPath .

Try the attached script.

I changed this line and it works for me.

____________

Blog: LucD notes

Twitter: lucd22

LUN ID

Hello
I want to check in Orchestrator each LUN has the same ID on each connected to hosts.
But I can't find the ID of anywhere.
Can someone help me with this?
I have this code, but it's not the outcome I want:
```
var scsiLuns = host.configManager.storageSystem.storageDeviceInfo.scsiLun;
for each (var lun in scsiLuns) {
  System.log("lun.canonicalName: " + lun.canonicalName);
  System.log("lun.RuntimeName: " + lun.RuntimeName);
  System.log("lun.capabilities: " + lun.capabilities);
  System.log("lun.descriptor: " + lun.descriptor);
  System.log("lun.deviceName: " + lun.deviceName);
  System.log("lun.deviceType: " + lun.deviceType);
  System.log("lun.displayName: " + lun.displayName);
  System.log("lun.durableName: " + lun.durableName);
  System.log("lun.dynamicProperty: " + lun.dynamicProperty);
  System.log("lun.dynamicType: " + lun.dynamicType);
  System.log("lun.key: " + lun.key);
  System.log("lun.lunType: " + lun.lunType);
  System.log("lun.model: " + lun.model);
  System.log("lun.operationalState: " + lun.operationalState);
  System.log("lun.queueDepth: " + lun.queueDepth);
  System.log("lun.revision: " + lun.revision);
  System.log("lun.scsiLevel: " + lun.scsiLevel);
  System.log("lun.serialNumber: " + lun.serialNumber);
  System.log("lun.standardInquiry: " + lun.standardInquiry);
  System.log("lun.uuid: " + lun.uuid);
  System.log("lun.vendor: " + lun.vendor);
  System.log("lun.vStorageSupport: " + lun.vStorageSupport);


  System.log ("########################################################################################");
}
```
[10:48:35.564 2015-03-02] [I] lun.canonicalName: naa.60050768018086e43000000000000067
[10:48:35.564 2015-03-02] [I] lun. RuntimeName: undefined
[10:48:35.564 2015-03-02] [I] lun.capabilities: DynamicWrapper (Instance): [VcScsiLunCapabilities]-[class com.vmware.vim.vi4.ScsiLunCapabilities] - VALUE: com.vmware.vim.vi4.ScsiLunCapabilities@4d0
[10:48:35.580 2015-03-02] [I] lun.descriptor: DynamicWrapper (Instance): [VcScsiLunDescriptor]-[class com.vmware.vim.vi4.ScsiLunDescriptor] - VALUE: com.vmware.vim.vi4.ScsiLunDescriptor@a638ae2a,DynamicWrapper (Instance): [VcScsiLunDescriptor]-[class com.vmware.vim.vi4.ScsiLunDescriptor] - VALUE: com.vmware.vim.vi4.ScsiLunDescriptor@482ac68f,DynamicWrapper (Instance): [VcScsiLunDescriptor]-[class com.vmware.vim.vi4.ScsiLunDescriptor] - VALUE: com.vmware.vim.vi4.ScsiLunDescriptor@62c80116
[10:48:35.580 2015-03-02] [I] lun.deviceName: /vmfs/devices/disks/naa.60050768018086e43000000000000067
[10:48:35.580 2015-03-02] [I] lun.deviceType: disc
[10:48:35.580 2015-03-02] [I] lun.displayName: IBM Fibre Channel disk (naa.60050768018086e43000000000000067)
[10:48:35.580 2015-03-02] [I] lun.durableName: DynamicWrapper (Instance): [VcScsiLunDurableName]-[class com.vmware.vim.vi4.ScsiLunDurableName] - VALUE: com.vmware.vim.vi4.ScsiLunDurableName@12d5c
[10:48:35.580 2015-03-02] [I] lun.dynamicProperty: null
[10:48:35.580 2015-03-02] [I] lun.dynamicType: null
[10:48:35.658 2015-03-02] [I] lun.key: key - vim.host.ScsiDisk - 020001000060050768018086e43000000000000067323134352020
[10:48:35.658 2015-03-02] [I] lun.lunType: disc
[10:48:35.658 2015-03-02] [I] lun.model: 2145
[10:48:35.658 2015-03-02] [I] lun.operationalState: ok
[10:48:35.658 2015-03-02] [I] lun.queueDepth: null
[10:48:35.658 2015-03-02] [I] lun.revision: 0000
[10:48:35.658 2015-03-02] [I] lun.scsiLevel: 6
[10:48:35.658 2015-03-02] [I] lun.serialNumber: not available
[10:48:35.658 2015-03-02] [I] lun.standardInquiry: 0,0,6,50,104,24,16,2,73,66,77,32,32,32,32,32,50,49,52,53,32,32,32,32,32,32,32,32,32,32,32,32,48,48,48,48,50,49,52,53,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[10:48:35.658 2015-03-02] [I] lun.uuid: 020001000060050768018086e43000000000000067323134352020
[10:48:35.658 2015-03-02] [I] lun.vendor: IBM
[10:48:35.658 2015-03-02] [I] lun.vStorageSupport: vStorageSupported
[10:48:35.658 2015-03-02] [I] ########################################################################################

Hello

You can try the following code:
```
var topologyPaths = host.configManager.storageSystem.storageDeviceInfo.plugStoreTopology.path;
for each (var topologyPath in topologyPaths) {
    System.log("topologyPath.lunNumber: " + topologyPath.lunNumber);
}
```
I don't have a proper environment to check, but looking at the API it should work.

Paths multiple settings for a specific LUN

Hello
I'm a workflow in Orchestrator automatically add a new data store in a cluster.
This set works but I have set the parameters of Multipath for this specific to Round Robin on each host LUN.
I created the code that affects all LUNS Round Robin, but it must be for this specific LUN only.
Can someone help me with this?
It's the current code I have:
```
var mpp = new VcHostMultipathInfoLogicalUnitPolicy() ;
mpp.policy = "VMW_PSP_RR";

for each (var host in hosts) {
  for each (var lun in host.config.storageDevice.multipathInfo.lun) {
  var id = lun.id;
  host.configManager.storageSystem.setMultipathLunPolicy(id, mpp);
  }
}
```
I have the "naa", so I can do the check, but I can't do the "naa" of the multipathInfo.
I tried to use:
lun.lun.displayName
lun.lun.canonicalName
lun.lun.deviceName
But it gives 'undefined' output
Example of output:

[11:12:18.346 2013-12-27] [D] LUN.id: 020003000060050768018086e430000000000003f1323134352020

[11:12:18.346 2013-12-27] [D] LUN. MON: key - vim.host.ScsiDisk - 020003000060050768018086e430000000000003f1323134352020

[11:12:18.346 2013-12-27] [D] LUN. LUN.displayName: undefined

[11:12:18.346 2013-12-27] [D] LUN. LUN.canonicalName: undefined

[11:12:18.346 2013-12-27] [D] LUN. LUN.deviceName: undefined

Hello

I can't get the details that you listed at the bottom of your message, too!

But when you have a quick glance at the LUN ID you extracted, you can see that the naa.XXX is included in there.

So I think it should be possible to extract this number, here is a small example of my environment:

Lun.ID = 0200bf000060060e8016546b000001546b00006abf4f50454e2d56

NAA = naa. 60060e8016546b000001546b00006abf

Extraction:
```
var myNaa = lun.id.slice(10,42);
System.log("My Naa: naa." + myNaa);
```
In your code, it might be something like this:
```
var mpp = new VcHostMultipathInfoLogicalUnitPolicy() ;
mpp.policy = "VMW_PSP_RR";
for each (var host in hosts) {
  for each (var lun in host.config.storageDevice.multipathInfo.lun) {
    var id = lun.id;
    var myNaaExtract = lun.id.slice(10,42);
    if(myNaaExtract.search("60060e8016546b000001546b00006abf")!= -1) {
      System.log("Found the matching NAA...");
      host.configManager.storageSystem.setMultipathLunPolicy(id, mpp);
    }
  }
}
```
You may need to change the 'slice' to correspond with your table (using other numbers 10 and 42) and of course online 7 "id naa".

I hope this helps for you...

Kind regards

Marc

How to get the runtimename of the Monday using iscsi LUNs

Hello
IIS there a way to get the name of length of scsi LUNS being given the lun id?
For example, please take a look at the attached capture where I want to get the identifier (identifier of naa) in view of the number of LUNs, say 11 (the first line of the snapshot)
Thank you!

That you will get the link between the identifier and the Monday
```
Get-VMHost MyEsx |
Get-ScsiLun |
Select CanonicalName,
    @{N="LunID";E={[int](Select-String ":L(?\d+)$" -InputObject $_.RuntimeName).Matches[0].Groups['LunID'].Value}}
```

How to find if a scsi disk can be used as a ROW or only use not vsphere CLI.

Hi, I want to know if the SCSI disk can be used as RDM and a remote computer running vSphere CLI.
I tried to use 'vicfg-scsidevs - l', but it doesn't have the required information list
===============================================
Here is sample out put
MPX.vmhba0:C0:T1:l0
Device type: disk
Size: MB 69459
Full name: disk space from VMware (mpx.vmhba0:C0:T1:L0)
Plugin: NMP
Device console: /vmfs/devices/disks/mpx.vmhba0:C0:T1:L0
Devfs Path: /vmfs/devices/disks/mpx.vmhba0:C0:T1:L0
Seller: VMware model: Block device Revis: 1.0
SCSI level: 2 is nickname: status:
: RDM Capable is removable:
Other names:
VML.0000000000766d686261303a313a30
empty fields "Is Capable RDM" here.
=======================================================
When I executed the command 'esxcfg-scsidevs - l' on an ESX Server, he gave me the necessary info.
MPX.vmhba0:C0:t0:l0
Device type: Direct access
Size: 138919 MB
Full name: disk space from VMware (mpx.vmhba0:C0:T0:L0)
Plugin: NMP
The console device: / dev/cciss/c0d0
Devfs Path: /vmfs/devices/disks/mpx.vmhba0:C0:T0:L0
Seller: VMware model: Block device Revis: 1.0
: SCSI 2 is Pseudo: false status: on
: RDM Capable false is removable: false
Is Local: true
Other names:
VML.0000000000766d686261303a303a30
So is it possible for vSphere CLI through which we can tell if the SCSI disk device can be used as ROW or NOT?
and what parameter defined as capable of RDM?
Thank you
Chandra Sekhar P.

Hi Chandra,

In order to get the SCSI LUNS that can serve as RDM, you must use the QueryConfigTarget method. This method is defined on EnvironmentBrowser. You need to recover some EnvironmentBrowser object ComputeResource the HostSystem where the virtual machine is created. The configTarget.ScsiDisk returned after the method call contains the logic unit number information that is capable of RDM.

I hope this helps!

Neha

Remote SCSI via the perl SDK

I understand that there are ways to get information about the investigation of SCSI LUNS via the SDK and rCLI.
In particular, the class ScsiLun: http://www.VMware.com/support/developer/VC-SDK/visdk400pubs/ReferenceGuide/Vim.host.ScsiLun.html#field_detail
But I don't see any way for a user (from the vMA) to go to the next step and send custom object ScsiLun SCSI commands. Someone at - he found a way to send a SCSI CDB custom unit number logic of an ESX SCSI host remotely from a computer using the SDK provided by VMware?
VDDK seems to only allow access to the low-level vmdk files, but does not have access beyond. VDDK can be a solution with a RDM vmdk file cards, but does not provide the same level of access to a logical unit number which has a VMFS partition.
What would be nice, is to have methods on the object ScsiLun allowing at least read() calls to appear.

Is not possible. VDDK primary use case is to allow users to manipulate and manage the VMDK (s) for a given virtual machine, it does nothing with the storage array. The vSphere API allows you to perform basic and the configuration of your VMware infrastructure management and base operations around the storage system under such as creating new VMFS volumes or resignaturing/re-mounting a volume snapshot, which is as much as the API exposed in terms of storage void System. If you want more integration and control of the storage subsystem, then you will probably need to look at vStorage API for integration of table better known under the name of VAAI and only sellers of table I know that it is taking part in this program is the type of EMC, NetApp and Dell. So unless you work for them, you probably won't be able to get access to the internal API allowing then storage vendors hang their respective API

What you trying to do sounds like this should be done from the point of view of the storage provider and perhaps they have APIs that you can leverage to make your reads/writes, but a large part of this work is already being developed by the big 3 and I am sure that other vendors will join as VAAI becomes more popular and mainstream in order to unload the processes in the data mover in it VMkernel on the storage array.

=========================================================================

William Lam

VMware vExpert 2009

Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

Twitter: @lamw

repository scripts vGhetto

Introduction to the vMA (tips/tricks)

Getting started with vSphere SDK for Perl

VMware Code Central - Scripts/code samples for developers and administrators

VMware developer community

If you find this information useful, please give points to "correct" or "useful".

EMC Ex3 - 40f, Qlogic ISP 2432 and RHEL 4 x86_64

I have a blade of 1855 w / daughter CF card. The OS is RHEL AS 4 update 5 x86_64. I recently installed this OS and have it connected to an EMC3 40f, which presents this host w / 100GB RAID5 LUN. First of all, I did this: (orders in "BOLD", released in BLUE)

1. register with RHN

2 up2date rpm-build redhat-config-RPM

3. up2date - get-source kernel

4. rpm-ivh /var/spool/up2date/kernel*.src.rpm

5. cd/usr/src/redhat/SPECS

6 rpmbuild - bp - target = x86_64 kernel - 2.6.spec

7. cp-a /usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9/usr/src

8. ln-s /usr/src/linux-2.6.9 usr

The steps above were made so that these steps should compile without any problem

9 tar - xvf qla2xxx - v8.01.00 - 3dkms.tar.gz

10. rpm-ivh dkms - 2.0.5 - 1.noarch.rpm

11 rpm - ivh qla2xxx - v8.01.00 - 3dkms.noarch.rpm

Step 11 will produce the following:

Preparing... ########################################### [100%]
1:qla2xxx ########################################### [100%]

Create a symbolic link /var/lib/dkms/qla2xxx/v8.01.00/source->
/usr/src/qla2xxx-V8.01.00

DKMS: Add Completed.

Construction of module to the kernel running has been ignored since the
for this kernel kernel sources does not appear to be installed.

Hmm... I thought that I just added the CBC core following steps 1 through 8. These steps are listed here: http://kbase.redhat.com/faq/FAQ_85_5109.shtm

I also installed the EMCPower. Linux - 5.0.0 - 157.rhel.x86_64.rpm under the default location. It has now SANsurferCLI and SANsurfer (gui).

When I rebooted the machine, I see dmesg:

HBA QLogic Fibre Channel adapter driver
ACPI: PCI Interrupt 0000:02:00.0 -> GSI 16 (level, low)-> IRQ 169
qla2400 0000:02:00.0: found an ISP2432, irq 169, the iobase 0xffffff0000014000
qla2400 0000:02:00.0: PCI configuration space...
PCI: The timer setting of latency of the device 0000:02:00.0 to 64
qla2400 0000:02:00.0: NVRAM configuration settings...
qla2400 0000:02:00.0: audit loaded RISC code...
qla2400 0000:02:00.0: allocated (1061 KB) to dump the firmware...
qla2400 0000:02:00.0: waiting for LIP finish...
qla2400 0000:02:00.0: LIP reset occurred (f7f7).
qla2400 0000:02:00.0: LOOP UP detected (2 Gbps).
qla2400 0000:02:00.0: topology - (F_Port), loop 0 host address 0 x
SCSI1: qla2xxx
qla2400 0000:02:00.0:
Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.0 hdma + host # 1, fw = 4.00.23 =
Seller: DGC model: LUNZ Rev: 0324
Type: Access Direct ANSI SCSI Revision: 04
qla2400 0000:02:00.0: scsi(1:0:0:0): activated tagged depth of queue lines, 32.
SDB: READ CAPACITY failed.
SDB: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDB: asking cached data failed
SDB: assuming drive cache: write through
SDB: READ CAPACITY failed.
SDB: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDB: asking cached data failed
SDB: assuming drive cache: write through
SDB:end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
end_request: i/o error, dev sdb, sector 0
Buffer I/O error on device sdb, logical block 0
Failed to read the partition table
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg2 at scsi1, channel 0, id 0, lun 0, type 0
Seller: DGC model: LUNZ Rev: 0324
Type: Access Direct ANSI SCSI Revision: 04
qla2400 0000:02:00.0: scsi(1:0:1:0): activated tagged depth of queue lines, 32.
SDC: READ CAPACITY failed.
SDC: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDC: asking cached data failed
SDC: assuming drive cache: write through
SDC: READ CAPACITY failed.
SDC: State = 1, message = 00, host = 0, driver = 08
Current SD: sense key illegal request
Additional detection: logical unit not supported
SDC: asking cached data failed
SDC: assuming drive cache: write through
SDC:end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
end_request: error e/s, dev SDC, sector 0
Buffer I/O error on device DSC, logical block 0
Failed to read the partition table
Attached scsi disk SDC at scsi1, channel 0, id 1, lun 0
Attached scsi generic sg3 at scsi1, id 1, channel 0, lun 0, type 0
ACPI: PCI Interrupt 0000:02:00.1 -> 17 of GSI (low)-> IRQ 193
qla2400 0000:02:00.1: found an ISP2432, irq 193, the iobase 0xffffff0000016000
qla2400 0000:02:00.1: PCI configuration space...
PCI: The timer setting of latency of the device 0000:02:00.1 to 64
qla2400 0000:02:00.1: NVRAM configuration settings...
qla2400 0000:02:00.1: audit loaded RISC code...
qla2400 0000:02:00.1: allocated (1061 KB) to dump the firmware...
qla2400 0000:02:00.1: waiting for LIP finish...
qla2400 0000:02:00.1: cable is disconnected...
SCSI2: qla2xxx
qla2400 0000:02:00.1:
Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.1 hdma + host # 2, fw = 4.00.23 =
Insert the floppy driver for 2.6.9 - 55.ELsmp
Floppy drive (s): fd0 is 1.44 M
floppy0: not found floppy disk controller

However, when I run the SANsurferCLI, it shows no. HBA connected. I cannot fdisk the LUN. I get:

[root@xxx ~] # fdisk/dev/sdb

Unable to read/dev/sdb

[root@xxx ~] # mkfs - v-j/dev/sdb
mke2fs 1.35 (February 28, 2004)
/ dev/sdb whole device, is not just a partition.
Still? (y, n) y
WARNING: could not delete sector 2: try to write the file system blocks resulted in brief writing
Filesystem label =.
OS type: Linux
Block size = 4096 (log = 2)
Fragment size = 4096 (log = 2)
131072 inodes, 262144 blocks
13107 blocks (5.00%) reserved for the super user
First data block = 0
Maximum filesystem blocks = 268435456
8 groups of block
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840 229376

WARNING: could not read block 0: try to read the file system block resulted in short read
WARNING: could not delete sector 0: try to write the file system blocks resulted in brief writing
Writing inode tables: fact
Creating the journal (8192 blocks): fact
Writing Superblocks and filesystem accounting information:
Attention, was struggling to write to superblocks.done

This file system will be automatically checked all 38 media or
180 days, whichever comes first. Use tune2fs - c or-i to substitute.

I expect that to happen. Included here for clues:

[root@xxx ~] # mount/dev/sdb/san/01 /
/ dev/sdb: input/output error
Mount: / dev/sdb: cannot read the superblock

The output of/proc/scsci/qla2xxx/1:

[root@xxx qla2xxx] # 1
QLogic PCI with Fibre Channel for QME2462 host adapter:
4.00.23 firmware version , Driver version 8.01.04 - d8
INTERNET SERVICE PROVIDER: ISP2432
Ask the queue = 0 x 215580000, queue response = 0x215d10000
Ask account queue = 4096, the response queue = 512 count
Total number of active orders = 0
Total number of interruptions = 12855
Device queue depth = 0 x 20
Number of entries free request = 3592
Number of time-outs of the mailbox = 0
Number of ISP abandons = 0
Number of the loop = 0 Resync
Number of retries for empty slots = 0
Number of requests in pending_q = 0, retry_q = 0, done_q = 0, scsi_retry_q = 0
Adapter: loop State host = , flags is 0x1e03
DPC flags = 0 x 4000000
Flags MBX = 0 x 0
Link down Timeout = 045
Port down retry = 045
Number of connection attempts = 045
Dropped orders retried with image (s) = 0
Product ID = 0000 0000 0000 0000

The SCSI device information:
SCSI-qla0-adapter-node = 200000e08b9b8968;
SCSI-qla0-adapter-port = 210000e08b9b8968;
Qla0-SCSI-target - 0 = 5006016941e07929;
Qla0-SCSI-target - 1 = 5006016041e07929;

FC Port information:
SCSI-qla0-port-0 = 50060160c1e07929:5006016941e07929:c302ef:81;
SCSI-qla0-port-1 = 50060160c1e07929:5006016041e07929:c303ef:82;

Information about the SCSI LUN:
(Id: Lun) *-indicates the logical unit number is not registered with the operating system.
(0: 0): total reqs 12595 pending reqs 0, flags 0x0, 0:0:81 00
(1: 0): flags of reqs total 130, in anticipation of reqs 0, 0 x 0, 0:0:82 00

So can someone indicate on WHAT I'm doing wrong? I am open to reinstall the operating system for the same version (LIKE 4u5 x86_64).

Thank you.

Why Get-ScsiLun RuntimeName field is always empty in PowerCLI 6.0 and how do I get a Monday, now?

I used PowerCLI 6.0 Release 2 and tests my 5.5 scripts to make sure they still work ok with 6.0.
The more I watch this more I think it's a problem of ESXi 6.0 - (ESXi 6.0 Update 1)
I used a good script by Luc relaxing that tells you how to get a Monday using PowerCLI
The realization of a New VIProperty called Monday - notes LucD
This script is dependent on the RuntimeName field that is returned by the Get-ScsiLun cmdlet, which is now always empty in PowerCLI 6.0.
Is there another way to get the Monday?
I see the (s) Monday when I VI Client in the host and the look on the storage adapters.
Basic steps:
$scsiList = get-vmHost - vm $vmName | Get-scsiLun
$scsiList | Select RuntimeName
$scsiList | FL
RuntimeName always comes back empty, where it is used to look like vmhba0:C2:T0:L11
where L11 is the Monday
Screenshot is closed.
Thank you
Maureen

This seems to be a bug on the side of ESXi, so I came up with an ugly workaround that is attached.

I used the get-scsiLunPath cmdlet, which also has the LUN IDS integrated in the name field. It returns a list of objects, but the logical unit number ID is always the same in each of the LUNPath objects in my environment, so it works.

When the bug is fixed, workaround is skipped.

Overview:

Get all SCSI LUNS for a given server/host

If the length of the RuntimeName field is 0, do workaround

for each number of logic extracted from the server unit, call Get-SCSiLunPath | Select - 1 first; don't need the entire list

Out of the logic of the end of the name unit number ID and convert them into int

work: compare found LUN ID to the one I am looking for and save it.

RDM to delete and recreate the mapping of RDM file and fix

Hello
I wrote the following script, but it works fine except it does not create the mapping of RDM file.
If I comment out the following lines, it works fine.
$fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)
$spec.deviceChange [0] .fileOperation = "crΘer".
Here is the code below
Replace-VM-RDM function {}
Param ($scsiid, $rdmname, $vmname, $filename)
< #.
Convert SCSI address in Vmware format
# >
$scsicontroller = $null
$scsiid_split = $null
$scsiid_split = $scsiid.split(":")
$scsicontroller =($scsiid_split[0])
# SCSI VMware in the GUI controller ID is a number greater than the real controller id
$scsicontroller = [int] $scsicontroller + 1
# Vmware waiting conntroller with 4-character id
$scsicontroller =($scsicontroller.) (ToString()) + "000".
$scsicontroller
# SCSI LOGICAL UNIT NUMBER
$scsilun = $null
# VMware SCSI LUN ID in the GUI is a higher number than the id real lun
$scsilun = [int]($scsiid_split[1]) #+ 1
###
$vm = get-VM-name '$vmname ' | Get-View
IF (!) (($filename))) {}
$RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"
$filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))
}
$esx is get-view $vm. Runtime.Host
< #.
Download CanonicalName RDM Lun
# >
$rdmCanonicalName = $null
$rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)
$rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)
foreach ($dev in $vm. Config.Hardware.Device) {}
If (($dev.)) GetType()). {Name - eq "VirtualDisk")}
If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)
($dev.Backing.CompatibilityMode-eq "virtualMode")) {}
If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}
# Remove the hard drive
$hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}
$hd | Remove-hard drive - confirm: $false
Write-Host "file name:" $dev.backing.fileName "
Write-Host "Disk Mode:" $dev.backing.diskMode
$dev.backing.deviceName
$dev.backing.lunUuid
$DevKey = $dev.key
$CapacityInKB = $ dev. CapacityInKB
$fileMgr = get-View (view Get ServiceInstance). Content.fileManager
$datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)
foreach ($disk in $vm. LayoutEx.Disk) {}
if($Disk.) Key - eq $dev. Key) {}
foreach ($chain in $disk. {String)
foreach ($file in $chain.) FileKey) {}
$name = $vm. LayoutEx.File [$file]. Name
$fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)
}
}
continue
}
}
}
}
Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}
}
}
#$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works
$spec = $null
$spec = new-Object VMware.Vim.VirtualMachineConfigSpec
$spec.deviceChange = @)
$spec.deviceChange += new-Object VMware.Vim.VirtualDeviceConfigSpec
$spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device
$spec.devicechange [0].device.capacityInKB = $CapacityInKB
$spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo
$spec.deviceChange [0].device.backing.fileName = $filename
$spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".
$spec.deviceChange [0].device.backing.diskMode = «»
$spec.deviceChange [0].device.backing.lunUuid = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). UUID)
$spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo
$spec.deviceChange [0].device.connectable.startConnected = $true
$spec.deviceChange [0].device.connectable.allowGuestControl = $false
$spec.deviceChange [0].device.connectable.connected = $true
# Take the next unused volume for HD key
$spec.deviceChange [0].device.key = $DevKey + 1
# 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.
If ($scsilun - eq 6) {$scsilun = $scsilun + 1}
# Take the next unit for the HD number
$spec.deviceChange [0].device.unitnumber = $scsilun
# Key device for the SCSI controller
$spec.deviceChange [0].device.controllerKey = $scsicontroller
# Create vmdk file
$spec.deviceChange [0] .fileOperation = "crΘer".
$spec.deviceChange [0] .operation = 'Add '.
$vm = get - View (Get - VM $VMname) USER.USER
$vm. ReconfigVM_Task ($spec)
}
Replace-VM-RDM $vmname $scsiid $rdmname $filename

I am working, it just need to reorganization and then the Devicename was wrong.

Here's the script working.

Replace-VM-RDM function {}

Param ($scsiid, $rdmname, $vmname, $filename)

<>

Convert SCSI address in Vmware format

#>

$scsicontroller = $null

$scsiid_split = $null

$scsiid_split = $scsiid.split(":")

$scsicontroller =($scsiid_split[0])

# SCSI VMware in the GUI controller ID is a number greater than the real controller id

$scsicontroller = [int] $scsicontroller + 1

# Vmware waiting conntroller with 4-character id

$scsicontroller =($scsicontroller.) (ToString()) + "000".

$scsicontroller

# SCSI LOGICAL UNIT NUMBER

$scsilun = $null

# VMware SCSI LUN ID in the GUI is a higher number than the id real lun

$scsilun = [int]($scsiid_split[1]) #+ 1

###

$vm = get-VM-name '$vmname ' | Get-View

IF (!) (($filename))) {}

$RDMFile = $rdmname.split("") [0] + "_RDM.vmdk"

$filename = (($vm.)) (Config.Files.VmPathName). Replace("$vmname.vmx","$RDMFile"))

}

$esx is get-view $vm. Runtime.Host

<>

Download CanonicalName RDM Lun

#>

$rdmCanonicalName = $null

$rdmCanonicalName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). CanonicalName)

$rdmDevicePath = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

foreach ($dev in $vm. Config.Hardware.Device) {}

If (($dev.)) GetType()). {Name - eq "VirtualDisk")}

If (($dev.Backing.CompatibilityMode-eq "physicalMode") - or)

($dev.Backing.CompatibilityMode-eq "virtualMode")) {}

If (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {}

# Remove the hard drive

$hd = get-disk hard $vm.name | where {$_.} Filename - eq $dev. Backing.FileName}

$hd | Remove-hard drive - confirm: $false - DeletePermanently

Write-Host "file name:" $dev.backing.fileName "

Write-Host "Disk Mode:" $dev.backing.diskMode

$dev.backing.deviceName

$dev.backing.lunUuid

$DevKey = $dev.key

$CapacityInKB = $ dev. CapacityInKB

<#$fileMgr =="" get-view="" (get-view="">

$datacenter = (get-View (Get - VM $VMname |)) Get-Datacenter) USER.USER) .get_MoRef)

foreach ($disk in $vm. LayoutEx.Disk) {}

if($Disk.) Key - eq $dev. Key) {}

foreach ($chain in $disk. {String)

foreach ($file in $chain.) FileKey) {}

$name = $vm. LayoutEx.File [$file]. Name

$fileMgr.DeleteDatastoreFile_Task ($name, $datacenter)

}

}

continue

}

}#>

}

}

Else if (($dev.)) ControllerKey - eq "$scsicontroller") - and ($dev. UnitNumber - eq "$scsilun")) {Write-Host "Selected SCSI address [$scsiid] is not a RDM"}

}

}

#$hd1 = New-disk hard - VM $vmname - DeviceName $rdmDevicePath - DiskType RawPhysical # this line works

$spec = $null

$spec = new-Object VMware.Vim.VirtualMachineConfigSpec

$spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

$spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

# Create vmdk file

$spec.deviceChange [0] .fileOperation = "crΘer".

$spec.deviceChange [0] .operation = 'Add '.

$spec.deviceChange = new-Object VMware.Vim.VirtualDeviceConfigSpec [] (1)

$spec.deviceChange [0] = new-Object VMware.Vim.VirtualDeviceConfigSpec

$spec.deviceChange [0] .operation = 'Add '.

$spec.deviceChange [0] .fileOperation = "crΘer".

$spec.deviceChange [0] = new-Object VMware.Vim.VirtualDisk .device

$spec.deviceChange [0].device.key = - 100

$spec.deviceChange [0].device.backing = new-Object VMware.Vim.VirtualDiskRawDiskMappingVer1BackingInfo

$spec.deviceChange [0].device.backing.fileName = "$filename".

$spec.deviceChange [0].device.backing.deviceName = (($esx.)) Config.StorageDevice.ScsiLun | where {$_.} DisplayName - eq $rdmname}). DevicePath)

$spec.deviceChange [0].device.backing.compatibilityMode = "physicalMode".

$spec.deviceChange [0].device.backing.diskMode = «»

$spec.deviceChange [0].device.connectable = new-Object VMware.Vim.VirtualDeviceConnectInfo

$spec.deviceChange [0].device.connectable.startConnected = $true

$spec.deviceChange [0].device.connectable.allowGuestControl = $false

$spec.deviceChange [0].device.connectable.connected = $true

# Key device for the SCSI controller

$spec.deviceChange [0].device.controllerKey = [int] $scsicontroller

# 7 SCSIID UnitNUmber is reserved for the controller - then go to 8.

If ($scsilun - eq 6) {$scsilun = $scsilun + 1}

# Take the next unit for the HD number

$spec.deviceChange [0].device.unitnumber = [int] $scsilun

$spec.deviceChange [0].device.capacityInKB = [int] $CapacityInKB

$vm = get - View (Get - VM $VMname) USER.USER

$vm. ReconfigVM ($spec)

}

Replace-VM-RDM $vmname $scsiid $rdmname $filename

Failure of the Areca 1212

After a few months under a server supermicro esxi4.1 with an areca raid controller errors appear after POSD 1212:
The disks are RAID 1.
Any help attended.
WARNING: LinScsi: SCSILinuxAbortCommands: failure, ARECA ARCMSR Driver SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202 for vmhba2 [0 m
[(7 m 66: 16:44:51.630 cpu0:10101331)] WARNING: arcmsr5: abandon the device command (0xe01fc00) to id scsi lun 0 = 0 = [0 m
[(7 m 66: 16:44:51.630 cpu0:10101331)] WARNING: LinScsi: SCSILinuxAbortCommands: failure, ARECA ARCMSR Driver SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202 for vmhba2 [0 m
[(7 m 66: 16:44:51.843 cpu0:10101331)] WARNING: arcmsr5: abandon the device command (0xe030400) to id scsi lun 0 = 0 = [0 m
[(7 m 66: 16:44:51.843 cpu0:10101331)]
and
WARNING: LinScsi: SCSILinuxAbortCommands: failure, ARECA ARCMSR Driver SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202 for vmhba2 [0 m
[(7 m 66: 16:45:19.941 cpu1:4161)] WARNING: LinScsi: SCSILinuxAbortCommands: failure, ARECA ARCMSR Driver SATA/SAS RAID ControllerDriver Version 1.20.00.15.vmk.100202 for vmhba2 [0 m
[(7 m 66: 16:45:19.941 cpu1:4161)] WARNING: arcmsr5: abandon the device command (0xe02e800) to id scsi = 0 lun = 1 [0 m
66:16:45:21.018 cpu0:4098) arcmsr5 < 5 >: = "0x0x4100b50e9400" Sri Bccp got the command aborted
66:16:45:21.018 cpu0:4098) arcmsr5 < 5 >: Sri get a command made illegal BCC acb = BCC = "0x0x4100b50e9400" ccbacb = "0x0x41000b813588" startdone "0x0x41000b813588" = 0 x 0 = 41 ccboutstandingcount
[(31; 1 m 66: 16:45:21.018 cpu0:4098)] WARNING: LinScsi: SCSILinuxCmdDone: attempt to double completion [0 m
66:16:45:21.019 cpu0:4098) Backtrace current CPU # 0, worldID = 4098, ebp = 0x417f800179a8
66:16:45:21.019 cpu0:4098) 0x417f800179a8: stack of PanicLogBacktrace@vmkernel:nover+0x18 [0x4180278577b5]: 0x417f800179d8, 0x417f8
66:16:45:21.019 cpu0:4098) 0x417f80017ae8: PanicvPanicInt@vmkernel:nover+0x1ab stack [0x4180278579f4]: 0x417f80017bd8, 0 x 4180278
66:16:45:21.020 cpu0:4098) 0x417f80017af8: Panic_vPanic@vmkernel:nover+0x18 stack [0x418027857fdd]: 0 x 3000000008, 0x417f80017be8
66:16:45:21.020 cpu0:4098) 0x417f80017bd8: stack of vmk_Panic@vmkernel:nover+0xa1 [0x41802788a572]: 0x24c0, 0xd0b50e9400, 0x417f800
66:16:45:21.021 cpu0:4098) 0x417f80017c48: SCSILinuxCmdDone@esx:nover+0x2c1 stack [0x418027c6a35e]: 0 x 0x418027d78e38, 0 x 410, 202
66:16:45:21.021 cpu0:4098) 0x417f80017c88: stack of arcmsr_interrupt@esx:nover+0x241 [0x418027d78df6]: 0xd000000023, 0x418027d78e38
66:16:45:21.021 cpu0:4098) 0x417f80017cc8: stack of Linux_IRQHandler@esx:nover+0x77 [0x418027c7bd38]: 0xd0, 0x417f80017d08, 0x417f8
66:16:45:21.021 cpu0:4098) 0x417f80017d58: stack of IDTDoInterrupt@vmkernel:nover+0x348 [0 x 418027832201]: 0x4100b6030150, 0x417f800
66:16:45:21.022 cpu0:4098) 0x417f80017d98: IDT_HandleInterrupt@vmkernel:nover+0x85 stack [0x4180278324da]: 0x2637d9eee01956, 0x4
66:16:45:21.022 cpu0:4098) 0x417f80017db8: stack of IDT_IntrHandler@vmkernel:nover+0xc4 [0x418027832e2d]: 0x417f80017ec0, 0x418027a
66:16:45:21.022 cpu0:4098) 0x417f80017dc8: stack of gate_entry@vmkernel:nover+0x46 [0x4180278da747]: 4018 x 0 0 x 4018, 0 x 0 0 x 0 0 x 0
66:16:45:21.023 cpu0:4098) 0x417f80017ec0: Power_HaltPCPU@vmkernel:nover+0x27d stack [0x418027aacb36]: 0x417f80017f70, 0 x 1 0 x 26
66:16:45:21.023 cpu0:4098) 0x417f80017fd0: CpuSchedIdleLoopInt@vmkernel:nover+0x985 stack [0x4180279cbe1e]: 0x417f80017ff0, 0x41
66:16:45:21.024 cpu0:4098) 0x417f80017fe0: CpuSched_IdleLoop@vmkernel:nover+0x15 stack [0x4180279d15ee]: 0x417f80017ff8, 0 x 0, x 0
66:16:45:21.024 cpu0:4098) 0x417f80017ff0: HostPCPUIdle@vmkernel:nover+0xd stack [0 x 418027834916]: 0x0, 0x0, 0x0, 0x0 0 x 0
66:16:45:21.024 cpu0:4098) 0x417f80017ff8: [0x0] < unknown > battery: 0x0, 0x0, 0x0, 0x0 0 x 0
66:16:45:21.025 cpu0:4098) [45 m [33; 1mVMware ESXi 4.1.0 [Releasebuild-260247 X86_64] [0 m]
66:16:45:21.025 cpu0:4098) failed to REACHED vmkdrivers/src_v4/vmklinux26/vmware/linux_scsi.c:2190--PAS
CR0 66:16:45:21.025 cpu0:4098) = 80010039 cr2 = cr3 0 x 0 x 0 = 0x10ce1000 = 0x16c cr4
66:16:45:21.025 cpu0:4098) pcpu:0 world: 4098 name: "idle0 (I).
66:16:45:21.025 cpu0:4098) pcpu:1 World: 7146 name: "Oba-vmware_bas' (U)
@BlueScreen: failure in the vmkdrivers/src_v4/vmklinux26/vmware/linux_scsi.c:2190--NE NOT REACHED
Start Code 66:16:45:21.025 cpu0:4098): uptime VMK 0 x 418027800000: 66:16:45:21.025
66:16:45:21.025 cpu0:4098) 0x417f80017af8: stack of Panic_vPanic@vmkernel:nover+0x13 [0x418027857fd8]: 0 x 3000000008
66:16:45:21.026 cpu0:4098) 0x417f80017bd8: stack of vmk_Panic@vmkernel:nover+0xa1 [0x41802788a572]: 0x24c0
66:16:45:21.026 cpu0:4098) 0x417f80017c48: stack of SCSILinuxCmdDone@esx:nover+0x2c1 [0x418027c6a35e]: 0 x 202
66:16:45:21.026 cpu0:4098) 0x417f80017c88: stack of arcmsr_interrupt@esx:nover+0x241 [0x418027d78df6]: 0xd000000023
66:16:45:21.027 cpu0:4098) 0x417f80017cc8: stack of Linux_IRQHandler@esx:nover+0x77 [0x418027c7bd38]: 0xd0
66:16:45:21.027 cpu0:4098) 0x417f80017d58: stack of IDTDoInterrupt@vmkernel:nover+0x348 [0 x 418027832201]: 0x4100b6030150
66:16:45:21.027 cpu0:4098) 0x417f80017d98: stack of IDT_HandleInterrupt@vmkernel:nover+0x85 [0x4180278324da]: 0x2637d9eee01956
66:16:45:21.028 cpu0:4098) 0x417f80017db8: stack of IDT_IntrHandler@vmkernel:nover+0xc4 [0x418027832e2d]: 0x417f80017ec0
66:16:45:21.028 cpu0:4098) 0x417f80017dc8: stack of gate_entry@vmkernel:nover+0x46 [0x4180278da747]: 0 x 4018
66:16:45:21.028 cpu0:4098) 0x417f80017ec0: stack of Power_HaltPCPU@vmkernel:nover+0x27d [0x418027aacb36]: 0x417f80017f70
66:16:45:21.029 cpu0:4098) 0x417f80017fd0: stack of CpuSchedIdleLoopInt@vmkernel:nover+0x985 [0x4180279cbe1e]: 0x417f80017ff0
66:16:45:21.029 cpu0:4098) 0x417f80017fe0: stack of CpuSched_IdleLoop@vmkernel:nover+0x15 [0x4180279d15ee]: 0x417f80017ff8
66:16:45:21.030 cpu0:4098) 0x417f80017ff0: stack of HostPCPUIdle@vmkernel:nover+0xd [0 x 418027834916]: 0x0
66:16:45:21.030 cpu0:4098) 0x417f80017ff8: [0x0] < unknown > battery: 0x0
kernelGSbase:0 x FSbase:0 x GSbase:0 x 418040000000 66:16:45:21.038 cpu0:4098 0 0)
66:16:45:21.018 cpu0:4098) LinScsi: SCSILinuxCmdDone: attempted end double
0:00:00:28.899 cpu1:4825) Elf: 3028: Kernel module arcmsr was loaded, but doesn't have a signature attached
Coredump on the disk.
1 1 location.
message storage on vmhba32: result of the sales order of bulk = 0
message from USB storage on vmhba32: result 0 x 1 data transfer in bulk
0:00:00:46.061 cpu0:5552) ScsiScan: 1059: path 'vmhba1:C0:T0:L0': seller: "TEAC" model: Rev 'DV - 28 s-W': ' 1. 2 '
0:00:00:46.061 cpu0:5552) ScsiScan: 1062: path "vmhba1:C0:T0:L0": Type: 0 x 5, rev ANSI: 5, TPGS: 0 (none)
0:00:00:46.063 cpu0:5552) ScsiUid: 273: "vmhba1:C0:T0:L0" path does not support VPD device Id page.
0:00:00:46.072 cpu0:5552) VMWARE SCSI Id: could not get the disc for vmhba1:C0:T0:L0 id
0:00:00:46.073 cpu0:5552) ScsiScan: 1059: path 'vmhba2:C0:T16:L0': seller: "Areca" model: "RAID controller" Rev: "R001".
0:00:00:46.073 cpu0:5552) ScsiScan: 1062: path "vmhba2:C0:T16:L0": Type: 0 x 3, ANSI rev: 0, TPGS: 0 (none)
[(7 m 0: 00:00:46.073 cpu0:5552)] WARNING: ScsiScan: 116: path 'vmhba2:C0:T16:L0': unsupported pre SCSI-2 (ansi = 0) [0 m unit
0:00:00:46.073 cpu0:5552) ScsiScan: 1059: path 'vmhba2:C0:T0:L0': seller: "Areca" model: "ARC-1212-FLIGHT #000' Rev:"R001"
0:00:00:46.073 cpu0:5552) ScsiScan: 1062: path "vmhba2:C0:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)
0:00:00:46.073 cpu0:5552) ScsiScan: 1059: path 'vmhba2:C0:T0:L1': seller: "Areca" model: "ARC-1212-FLIGHT #001' Rev:"R001"
0:00:00:46.073 cpu0:5552) ScsiScan: 1062: path "vmhba2:C0:T0:L1": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)
0:00:00:46.075 cpu0:4493 usb storage device) (strangled 0) WARNING on vmhba32 (SCSI cmd INVESTIGATION): compensation endpoint for hose 0xc0008280 halt
message from USB storage on vmhba32: scsi cmd done

I sent a few requests to Areca for support and they came back today teach me update me my drivers of vmware and has reported me on its Web site. The page shows the driver as a 4.0 driver drivers but it installed:

This is the driver I have installed:

http://www.areca.us/support/s_vmware/esx_4/VMware-ESX-drivers-SCSI-arcmsr-400.1.20.00.15.VMK.110418.zip

I'll check back with an update if it breaks down or is stable. I have reactivated the NCQ too.

error 0x0000007B (0xf78a2524, 0xC0000034, 0x00000000, 0x00000000) after the installation of the new RAM

I get the BSOD when booting with the STOP: 0x0000007B (0xf78a2524, 0xC0000034, 0x00000000, 0x00000000) message. The computer is a Dell Dimension 8400. I installed the new ram to find this message and we tried him swinging back the RAM on the former with the problem still persists.

Hello

Very good chance you loosened a cable or connection when you replaced the
memory.

Check with Dell Support, their drivers and documentation online and ask in the Dell
forums for known issues.

Dell support
http://support.Dell.com/

Dell support drivers - product manual & warranty Info (left side) - and much more
http://support.Dell.com/support/index.aspx?c=us&l=en&s=DHS

Dell forums
http://en.community.Dell.com/forums/
================================================================

Check the disk for malware:

Create a Bootable CD with the Trinity Rescue Kit - free - which comes with 5 antivirus programs
Integrable Hirem is another choice - more can be found using Google.

Trinity Rescue Kit - download on top right of the page
http://trinityhome.org/home/index.php?wpid=1&front_id=12

CD of Hirem boot is another good choice
http://www.hirensbootcd.NET/Download.html
http://www.hirensbootcd.NET/CD-contents/138-HBCD-111.html

===================================================================

You can also save the data and re-install Windows 7. The hard drive can be set
another computer as a 2nd drive (the best) or in an external USB enclosure. Either would allow
allows you to copy the data to removable media such as CD, DVD or other USB drives.

Or you can use a boot Ubuntu CD to back up data.

Use Ubuntu Live CD to backup files from your Windows computer dead
http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer

===================================================================

For slightly more:

BCCode: 7B 0x0000007B<-- read="" this="">

INACCESSIBLE_BOOT_DEVICE bug control has a value of 0x0000007B. This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup.

Important information if you have received a STOP Code

If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer connect with Support.

If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

The following actions could prevent a mistake like this does not happen:
1. Download and install updates for your computer from Windows Update device drivers.
2. Scan your computer for computer viruses.
3. Check your hard drive for errors.
Cause

Bug INACCESSIBLE_BOOT_DEVICE control often occurs due to a failure of the boot device. During the initialization of the I/O system, the boot device driver could have no initialize the boot device (usually a hard drive). Initialization of file system may have failed because it does not recognize the data on the boot device. In addition, repartition the system partition or installing a new SCSI adapter or disk controller could encourage this error.

This error can also occur because of incompatible disc material. If the error occurred in the initial configuration of the system, the system have maybe installed on an unsupported drive or a SCSI controller. Some controllers are supported only by the drivers that are in the library of drivers Windows (WDL). (These drivers require the user to perform a custom installation.)

Resolution

This error always occurs during the startup of the system. This error often occurs before the debugger connection, kind of debugging can be difficult, if not impossible.

Fix a defective boot device: If a boot device is at fault, you must change the boot options. For more information changing these options, see Software Configuration on the target computer.

Solve a problem of incompatible hard disk: If the installation program automatically detects the controller, you may have to skip the detection and the disc of the specific manufacturer allows to load the driver. Also, check the availability of updates for the firmware of the system BIOS and SCSI controller. Updates of this kind are usually available on the website or BBS of the hardware manufacturer.

Delete all material recently added, especially of hard disks or controllers, to see if the error is resolved. If the problematic material is a hard drive, the firmware version of the drive may be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you have removed another material element and the error is resolved, conflicts of port IRQ or i/o likely exist. Reconfigure the new device according to the manufacturer's instructions.

Confirm that the hard disk drivers, hard disk controllers and SCSI adapters are listed in the list of the products tested Microsoft Windows market.

If you have recently added a driver, restart your computer, and then press F8 to character-based menu that displays the choice of operating system. In the menu of Advanced Options , select the last known good Configuration option. This option is most effective when you add a single driver or service at a time.

In addition, check your computer for viruses using any update, commercial software that examines the Master Boot Record of the disk hard antivirus. All systems of Windows files can be infected by viruses.

This error can also occur due to corruption of the hard drive. Run Chkdsk /f /r on the system partition. You must restart the computer before the start of the analysis of disk. If you cannot start the computer due to the error, use the Recovery Console and run Chkdsk/r.

If you cannot start the system in the last known good configuration, you should try to boot from the Windows CD. Then, you can run Chkdsk from the Repair Console.

Warning If your system partition is formatted with the FAT file system the long file names that use the Windows operating system could be damaged if you use Scandisk or another MS-DOS-based disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

If your system has SCSI adapters, contact the card manufacturer for updated Windows drivers. Try to disable sync negotiation in the SCSI BIOS, check the wiring and the SCSI ID of each device and confirming the proper termination. For IDE devices, define the IDE port integrated as primary only. Also check each IDE device for setting good master/subordinate/stand alone . Try to remove all IDE devices except for the hard drives. Finally, check the system log in Event Viewer for additional error messages that might help identify the device or driver that generated the error.

BCCode: 7B 0x0000007B<-- read="" this="">
* 1138.html? order = votes http://www.faultwire.com/solutions-fatal_error/Check-for-viruses-on-your-Computer-0x0000007B-

=================================================================

If you do not have a Windows 7 disc, you can borrow a friends because they are not a copy
protected. The manufacturer of your system will also sell the physical DVD cheap since you already
Clean Windows. You can also do an ERD on another computer.

Try the Startup Repair - (if at anytime, benefit you from some, but not full access coming to Windows
return and then try to startup repair.)

How to start on the System Recovery Options in Windows 7
http://www.SevenForums.com/tutorials/668-system-recovery-options.html

What are the system recovery options in Windows 7?
http://Windows.Microsoft.com/en-us/Windows7/what-are-the-system-recovery-options-in-Windows-7

Try the disk Options recovery or Windows 7 startup repair.

How to run a startup repair in Windows 7
http://www.SevenForums.com/tutorials/681-startup-repair.html

Also from the command PROMPT on the Console (if possible) recovery or a Windows 7 disc

Start - type in the search box - find command top - RIGHT CLICK – RUN AS ADMIN

sfc/scannow

How to fix the system files of Windows 7 with the System File Checker
http://www.SevenForums.com/tutorials/1538-SFC-SCANNOW-Command-System-File-Checker.html

Then run checkdisk (chkdsk).

How to run check disk in Windows 7
http://www.SevenForums.com/tutorials/433-disk-check.html

Retry After Chkdsk startup repair.

If after those you can try the system restore to fashion without failure or the valuation or Windows 7
disc.

How to do a system restore in Windows 7
http://www.SevenForums.com/tutorials/700-system-restore.html

--------------------------------------------------------------------

If you need to repair disks - these help repair Windows not re-install.
Often an ERD will help you when the recovery disk is not - use OPTION 2 to
make the disc.

How to create a Windows 7 system repair disc
http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

======================================

If necessary:

What to do if Windows does not start correctly
http://Windows.Microsoft.com/en-us/Windows-Vista/what-to-do-if-Windows-wont-start-correctly

How to start on the System Recovery Options in Windows 7
http://www.SevenForums.com/tutorials/668-system-recovery-options.html

What are the system recovery options in Windows 7?
http://Windows.Microsoft.com/en-us/Windows7/what-are-the-system-recovery-options-in-Windows-7

How to do a repair installation to repair Windows 7
http://www.SevenForums.com/tutorials

I hope this helps.

Computer not starting and I get an error message

After that I ran the microsoft of what free security scan it found some files that were Trojan horses that he couldn't get rid of, so I deleted manually solve them some of the problems that I had. The end of the analysis told me to restart my computer so I did. But now it will not start and I get an error message that says: "a problem has been detected and windows has shut down to prevent damage to your computer. Then he told me to check the virus and to ensure that it is configured correctly and run the CHKDSK command to check the alteration of the hard disk and restart my computer. How am I supposed to do all this if I can't even start up? I tried to go into safe mode, but the same screen comes up. He gives this technical information at the end of the message. STOP: 0x0000007B (0xF79E4524, 0xC0000034, 0x00000000, 0x00000000) if someone could help me it would be so awesome thank you.

Hello

Check the disk for malware:

Create a Bootable CD with the Trinity Rescue Kit - free - which comes with 5 antivirus programs
Integrable Hirem is another choice - more can be found using Google.

Trinity Rescue Kit - download on top right of the page
http://trinityhome.org/home/index.php?wpid=1&front_id=12

CD of Hirem boot is another good choice
http://www.hirensbootcd.NET/Download.html
http://www.hirensbootcd.NET/CD-contents/138-HBCD-111.html

Scan a Windows PC for viruses from a Ubuntu Live CD
http://www.howtogeek.com/HOWTO/14434/scan-a-Windows-PC-for-viruses-from-a-Ubuntu-Live-CD/

===================================================================

You can also save the data and re-install Windows 7. The hard drive can be set
another computer as a 2nd drive (the best) or in an external USB enclosure. Either would allow
allows you to copy the data to removable media such as CD, DVD or other USB drives.

Or you can use a boot Ubuntu CD to back up data.

Use Ubuntu Live CD to backup files from your Windows computer dead
http://www.howtogeek.com/HOWTO/Windows-Vista/use-Ubuntu-Live-CD-to-backup-files-from-your-dead-Windows-computer

===================================================================

For slightly more:

BCCode: 7B 0x0000007B

INACCESSIBLE_BOOT_DEVICE bug control has a value of 0x0000007B. This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup.

Important information if you have received a STOP Code

If you have received a blue screen error, or stop code, the computer stopped abruptly to protect against data loss. A hardware device, its driver or software might have caused this error. If your copy of Windows is shipped with your computer, contact your computer manufacturer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or the manufacturer of your computer connect with Support.

If you have experience with computers and try to recover from this error, follow the steps in the Microsoft article solution STOP (blue screen) errors in Windows.

The following actions could prevent a mistake like this does not happen:
1. Download and install updates for your computer from Windows Update device drivers.
2. Scan your computer for computer viruses.
3. Check your hard drive for errors.
Cause

Bug INACCESSIBLE_BOOT_DEVICE control often occurs due to a failure of the boot device. During the initialization of the I/O system, the boot device driver could have no initialize the boot device (usually a hard drive). Initialization of file system may have failed because it does not recognize the data on the boot device. In addition, repartition the system partition or installing a new SCSI adapter or disk controller could encourage this error.

This error can also occur because of incompatible disc material. If the error occurred in the initial configuration of the system, the system have maybe installed on an unsupported drive or a SCSI controller. Some controllers are supported only by the drivers that are in the library of drivers Windows (WDL). (These drivers require the user to perform a custom installation.)

Resolution

This error always occurs during the startup of the system. This error often occurs before the debugger connection, kind of debugging can be difficult, if not impossible.

Fix a defective boot device: If a boot device is at fault, you must change the boot options. For more information changing these options, see Software Configuration on the target computer.

Solve a problem of incompatible hard disk: If the installation program automatically detects the controller, you may have to skip the detection and the disc of the specific manufacturer allows to load the driver. Also, check the availability of updates for the firmware of the system BIOS and SCSI controller. Updates of this kind are usually available on the website or BBS of the hardware manufacturer.

Delete all material recently added, especially of hard disks or controllers, to see if the error is resolved. If the problematic material is a hard drive, the firmware version of the drive may be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you have removed another material element and the error is resolved, conflicts of port IRQ or i/o likely exist. Reconfigure the new device according to the manufacturer's instructions.

Confirm that the hard disk drivers, hard disk controllers and SCSI adapters are listed in the list of the products tested Microsoft Windows market.

If you have recently added a driver, restart your computer, and then press F8 to character-based menu that displays the choice of operating system. In the menu of Advanced Options , select the last known good Configuration option. This option is most effective when you add a single driver or service at a time.

In addition, check your computer for viruses using any update, commercial software that examines the Master Boot Record of the disk hard antivirus. All systems of Windows files can be infected by viruses.

This error can also occur due to corruption of the hard drive. Run Chkdsk /f /r on the system partition. You must restart the computer before the start of the analysis of disk. If you cannot start the computer due to the error, use the Recovery Console and run Chkdsk/r.

If you cannot start the system in the last known good configuration, you should try to boot from the Windows CD. Then, you can run Chkdsk from the Repair Console.

Warning If your system partition is formatted with the FAT file system the long file names that use the Windows operating system could be damaged if you use Scandisk or another MS-DOS-based disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

If your system has SCSI adapters, contact the card manufacturer for updated Windows drivers. Try to disable sync negotiation in the SCSI BIOS, check the wiring and the SCSI ID of each device and confirming the proper termination. For IDE devices, define the IDE port integrated as primary only. Also check each IDE device for setting good master/subordinate/stand alone . Try to remove all IDE devices except for the hard drives. Finally, check the system log in Event Viewer for additional error messages that might help identify the device or driver that generated the error.

BCCode: 7B 0x0000007B<-- read="" this="">
* 1138.html? order = votes http://www.faultwire.com/solutions-fatal_error/Check-for-viruses-on-your-Computer-0x0000007B-

=================================================================

If you do not have a Windows 7 disc, you can borrow a friends because they are not a copy
protected. The manufacturer of your system will also sell the physical DVD cheap since you already
Clean Windows. You can also do an ERD on another computer.

Try the Startup Repair - (if at anytime, benefit you from some, but not full access coming to Windows
return and then try to startup repair.)

How to start on the System Recovery Options in Windows 7
http://www.SevenForums.com/tutorials/668-system-recovery-options.html

What are the system recovery options in Windows 7?
http://Windows.Microsoft.com/en-us/Windows7/what-are-the-system-recovery-options-in-Windows-7

Try the disk Options recovery or Windows 7 startup repair.

How to run a startup repair in Windows 7
http://www.SevenForums.com/tutorials/681-startup-repair.html

Also from the command PROMPT on the Console (if possible) recovery or a Windows 7 disc

Start - type in the search box - find command top - RIGHT CLICK – RUN AS ADMIN

sfc/scannow

How to fix the system files of Windows 7 with the System File Checker
http://www.SevenForums.com/tutorials/1538-SFC-SCANNOW-Command-System-File-Checker.html

Then run checkdisk (chkdsk).

How to run check disk in Windows 7
http://www.SevenForums.com/tutorials/433-disk-check.html

Retry After Chkdsk startup repair.

If after those you can try the system restore to fashion without failure or the valuation or Windows 7
disc.

How to do a system restore in Windows 7
http://www.SevenForums.com/tutorials/700-system-restore.html

--------------------------------------------------------------------

If you need to repair disks - these help repair Windows not re-install.
Often an ERD will help you when the recovery disk does not work.

Download Windows 7 system recovery discs - charge now $9.75 for ISO
images to make the discs.
http://NeoSmart.net/blog/2009/Windows-7-system-repair-discs/

How to create a Windows 7 - free system repair disc
http://www.SevenForums.com/tutorials/2083-system-repair-disc-create.html

======================================

If necessary:

What to do if Windows does not start correctly
http://Windows.Microsoft.com/en-us/Windows-Vista/what-to-do-if-Windows-wont-start-correctly

How to start on the System Recovery Options in Windows 7
http://www.SevenForums.com/tutorials/668-system-recovery-options.html

What are the system recovery options in Windows 7?
http://Windows.Microsoft.com/en-us/Windows7/what-are-the-system-recovery-options-in-Windows-7

How to do a repair installation to repair Windows 7
http://www.SevenForums.com/tutorials

I hope this helps.

Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

SCSI LUN DisplayName update

Similar Questions

Maybe you are looking for