ehfortin Posted May 24, 2012 Share Posted May 24, 2012 Hi, As for VMXNET which has been available for a long time in the Linux kernel, there is the equivalent named PVSCSI which give us the opportunity to use the "paravirtual" disk driver under VMware ESX which increase the performance under ESX (the paravirtual driver allow the guest OS to redirect the call to the ESX SCSI driver so we eliminate a layer which is always good performance wise). This has no impact on any other disks drivers in the kernel. Note that it has to be staticly linked (not a module) if you want to be able to boot on a disk with the paravirtual driver. Thank you. Quote Link to comment
c3 Posted May 24, 2012 Share Posted May 24, 2012 Really? Other than testing, most virtualized unRAID servers use pass-through controllers not vmware drivers. Quote Link to comment
ehfortin Posted May 24, 2012 Author Share Posted May 24, 2012 Hi, I know. But doing the passthrough force you to have a motherboard/chipset/cpu that allow this and they are not that common. You basically need component done for servers. I was not willing to invest that much money to run Unraid as a VM. So I'm using RDM and I've compiled a kernel with PVSCSI into it and it allow me to let VMware ESX manage the disks (and the hot-plug stuff that is supported with my LSI card) and to get maximum performance at the guest level. Let say it is just another alternative that is cheaper and only cost a recompile of the kernel with the appropriate switch enabled. If the information is useful to somebody, that's the goal. ehfortin Quote Link to comment
zoltran Posted May 25, 2012 Share Posted May 25, 2012 Really? Other than testing, most virtualized unRAID servers use pass-through controllers not vmware drivers. I think you may be a bit optimistic re passthru controllers. I think you'll find many of us do not do that due to various HW/SW limitations with controller passthru. I'd like to see the optimised vmware drivers as well Quote Link to comment
ehfortin Posted June 6, 2012 Author Share Posted June 6, 2012 If that can help to figure what I'm talking about, the pvscsi is the switch "CONFIG_VMWARE_PVSCSI" in the .config file. For anybody that want to compile this, that is under Device Drivers / Scsi device support / SCSI low-level drivers / VMware PVSCSI driver support when doing a "make menuconfig". Thank you. ehfortin Quote Link to comment
limetech Posted June 6, 2012 Share Posted June 6, 2012 If that can help to figure what I'm talking about, the pvscsi is the switch "CONFIG_VMWARE_PVSCSI" in the .config file. For anybody that want to compile this, that is under Device Drivers / Scsi device support / SCSI low-level drivers / VMware PVSCSI driver support when doing a "make menuconfig". Thank you. ehfortin Added in -rc5. Quote Link to comment
ehfortin Posted June 6, 2012 Author Share Posted June 6, 2012 Great! Thank you Tom! Quote Link to comment
BetaQuasi Posted March 26, 2013 Share Posted March 26, 2013 Sorry to bump an old thread - just wondering if this driver is still in the latest builds? It would appear not based on a bit of experimentation. Quote Link to comment
WeeboTech Posted March 26, 2013 Share Posted March 26, 2013 I think it's there. root@Tower:/# find /lib/modules -name '*pvscsi*' -ls 770 24 -rw-rw-rw- 1 root root 20816 Mar 23 13:53 /lib/modules/3.4.36-unRAID/kernel/drivers/scsi/vmw_pvscsi.ko root@Tower:/# modprobe vmw_pvscsi root@Tower:/# lsmod | grep v vmxnet 13606 0 vsock 37523 0 vmsync 2382 0 vmhgfs 41304 0 vmci 61521 2 vsock,vmhgfs vmblock 8557 0 vmw_pvscsi 12186 1 Quote Link to comment
BetaQuasi Posted March 26, 2013 Share Posted March 26, 2013 Thanks for the heads up - I'll be honest, I've exhausted the limit of my knowledge, all I can offer is that creating a .vmdk attached to a pv controller in VMware isn't showing up correctly in unRAID for assignment. Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 As BetaQ said, when adding a vmdk via SCSI controller you can see the drive however you can not mount it. In the unRaid GUI when the array is off, selecting it in the Cache ComboBox refresh`s the page and leaves the Cache ComboBox empty. Nothing in the SysLog. When using an IDE controller, it works... but the transfer rate is 15 MBs (when testing via NFS it is around 140MBs in my system) Also, worth noting: The drive shows 0 INFO in unMenu (sectors is 0, cylinders 0, etc...) I dont know if its true but I`m passing through a disk to unRaid using RDM. The controller for the RDM is SCSI (LSI LOGIC SAS to be exect) This might suggest that the SCSI is working... I`m not sure, I dont know how ESXi transfers the RDM. Quote Link to comment
BetaQuasi Posted March 29, 2013 Share Posted March 29, 2013 I'm doing the same for my cache drive - as far as I know though, RDM just presents the drive to the OS in the same fashion as it would if the drive was physically connected. Interesting point though - you said that NFS is around 140MB/s? Just to confirm, that's using an IDE .vmdk on a NFS datastore? (same as Johnm does I believe.) If this is the case, then I'm going to rearrange things a bit and export some space on my ZFS pool as NFS and try that instead. Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 I'm doing the same for my cache drive - as far as I know though, RDM just presents the drive to the OS in the same fashion as it would if the drive was physically connected. Interesting point though - you said that NFS is around 140MB/s? Just to confirm, that's using an IDE .vmdk on a NFS datastore? (same as Johnm does I believe.) If this is the case, then I'm going to rearrange things a bit and export some space on my ZFS pool as NFS and try that instead. Sorry... The 140 MBs is a NFS zfs share tested using a NFS mount in unRaid (mount -t nfs ....) There were no vmdk. I used the mount to isolate the problem. Quote Link to comment
WeeboTech Posted March 29, 2013 Share Posted March 29, 2013 Thanks for the heads up - I'll be honest, I've exhausted the limit of my knowledge, all I can offer is that creating a .vmdk attached to a pv controller in VMware isn't showing up correctly in unRAID for assignment. It may have something to do with how you setup the RDM. Here's some screen captures of what I've just done. I removed the IDE configuration and changed the RDM to pvscsi. There's some interesting data here. But what it does reveal is you can get smart access with the -z switch. The downside is the drives all look like spin down in unRAID and hdparm spin up/down commands do not work. This is a quick script in ESX 5.1 to make the RDM. Notice my other attempts. /vmfs/volumes/514faeac-5c793c1f-32c8-28924a2f176c/RDMS # cat rdmdisk.sh vmkfstools -z /vmfs/devices/disks/vml.0100000000202020202020202020202020533145303037544c535432303030 ST2000DM0012D9YN164.vmdk -a pvscsi # vmkfstools -r /vmfs/devices/disks/vml.0100000000202020202020202020202020533145303037544c535432303030 ST2000DM0012D9YN164.vmdk -a pvscsi # vmkfstools -r /vmfs/devices/disks/vml.0100000000202020202020202020202020533145303037544c535432303030 ST2000DM0012D9YN164.vmdk -a ide Here I am testing things out on unRAID. root@unRAID3:~# mkdir /mnt/sdb1 root@unRAID3:~# mount /dev/sdb1 /mnt/sdb1 root@unRAID3:~# ls -l /mnt/sdb1 total 65616 -rw-rw-rw- 1 root root 67121400 2013-03-14 14:46 linux-3.4.36.tar.xz drwxrwxrwx 3 root root 80 2013-03-24 23:58 src/ root@unRAID3:~# dd if=/dev/zero of=/mnt/sdb1/test.dd bs=1024 count=102400 102400+0 records in 102400+0 records out 104857600 bytes (105 MB) copied, 0.673928 s, 156 MB/s root@unRAID3:~# dd if=/dev/zero of=/mnt/sdb1/test.dd bs=1024 count=1024000 1024000+0 records in 1024000+0 records out 1048576000 bytes (1.0 GB) copied, 7.45521 s, 141 MB/s root@unRAID3:~# dd if=/dev/zero of=/mnt/sdb1/test.dd bs=1024 count=10240000 10240000+0 records in 10240000+0 records out 10485760000 bytes (10 GB) copied, 74.978 s, 140 MB/s root@unRAID3:~# ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 2013-03-29 20:30 scsi-1ATA_ST2000DM001-9YN164_S1E007TL -> ../../sdb lrwxrwxrwx 1 root root 10 2013-03-29 20:30 scsi-1ATA_ST2000DM001-9YN164_S1E007TL-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-03-29 20:30 usb-Generic-_USB3.0_CRW_-0_000000002318-0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-03-29 20:30 usb-Generic-_USB3.0_CRW_-0_000000002318-0:0-part1 -> ../../sdc1 root@unRAID3:~# hdparm -t /dev/sdb /dev/sdb: Timing buffered disk reads: 420 MB in 3.01 seconds = 139.74 MB/sec root@unRAID3:~# hdparm -i /dev/sdb /dev/sdb: HDIO_GET_IDENTITY failed: Invalid argument root@unRAID3:~# smartctl -a /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DM001-9YN164 Serial Number: S1E007TL Firmware Version: CC4C User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Fri Mar 29 20:34:51 2013 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ Register values returned from SMART Status command are: ERR=...., SC=...., LL=...., LM=...., LH=...., DEV=...., STS=.... SMART overall-health self-assessment test result: PASSED Warning: This result is based on an Attribute check. General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 231) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 62521000 3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 93 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2558926 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4517 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 41 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 066 063 045 Old_age Always - 34 (Min/Max 29/35) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 37 193 Load_Cycle_Count 0x0032 081 081 000 Old_age Always - 38050 194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 17 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 198 000 Old_age Always - 3 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 182042188843441 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 27871089219723 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 430224933999 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 118 - # 2 Extended offline Aborted by host 20% 114 - # 3 Short offline Completed without error 00% 111 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@unRAID3:~# hdparm -I /dev/sdb /dev/sdb: ATA device, with non-removable media Model Number: ST2000DM001-9YN164 Serial Number: S1E007TL Firmware Revision: CC4C Transport: Serial, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) cache/buffer size = unknown Nominal Media Rotation Rate: 7200 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = ? Advanced power management level: 128 Recommended acoustic management value: 208, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters * unknown 76[15] DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT LBA Segment Access (AC2) unknown 206[7] unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 222min for SECURITY ERASE UNIT. 222min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c50046edc72f NAA : 5 IEEE OUI : 000c50 Unique ID : 046edc72f Checksum: correct root@unRAID3:~# hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00 00 09 0c 00 00 00 00 00 00 00 00 00 00 40 50 Mar 29 20:37:06 unRAID3 emhttp: Spinning down all drives... Mar 29 20:37:06 unRAID3 kernel: mdcmd (15): spindown 1 root@unRAID3:~# hdparm -C /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00 00 09 0c 00 00 00 00 00 00 00 00 00 00 4 50 drive state is: standby Mar 29 20:38:31 unRAID3 emhttp: Spinning up all drives... Mar 29 20:38:31 unRAID3 kernel: mdcmd (16): spinup 1 root@unRAID3:~# hdparm -C /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00 00 09 0c 00 00 00 ff 00 00 00 00 00 00 40 50 drive state is: standby root@unRAID3:~# ls -l /mnt/sdb1 total 10315616 -rw-rw-rw- 1 root root 67121400 2013-03-14 14:46 linux-3.4.36.tar.xz drwxrwxrwx 3 root root 80 2013-03-24 23:58 src/ -rw-rw-rw- 1 root root 10485760000 2013-03-29 20:33 test.dd root@unRAID3:~# rm /mnt/sdb1/test.dd root@unRAID3:~# sync root@unRAID3:~# hdparm -S 242 /dev/sdb /dev/sdb: setting standby to 242 (1 hours) SG_IO: bad/missing sense data, sb[]: 70 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 00 00 09 0c 00 00 00 f2 00 00 00 00 00 00 40 50 Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 Well I did some digging and I found something, I think. First I added a new SCSI vmdk drive to unraid, this added in turn a new LSI Logic SAS controller. Power the unRaid VM, stopped array, set the new drive as cache... page refresh and Cache is unassigned. (nothing new) So I went to CLI and start "FDISK" set a new partition to the SCSI vmdk I just created. Commited the partition table and crossed hands.. all good. formatted to reiserfs using unMenu, mounted as writable and off we go to Midnight commander. Did some file copy and the speed is ~80 MB/s which is good, a solid copy for WD Green drive. All this speech to say that the PVSCSI is not the source for the problem. I can do a wild guess: The drive name in the Cache ComboBox is: (sdb) 104857600 An IDE (or any other physical drive) name looks like this: VMware_Virtual_IDE_Hard_Drive_00000000000000000001 (hda) 52428800 in /boot/config/disk.cfg there is a cacheId attribute. This shows VMware_Virtual_IDE_Hard_Drive_00000000000000000001 when an IDE vmdk is set. Notice it shows the text description before the parentheses?. The SCSI vmdk does not have any description.... it does a whitespace... Now i`m not much of an unRaid setup expert but it might be the issue. I`ll keep on digging. EDIT: There problem might also relate to "/usr/src/linux/drivers/md/md_private.h" which is the source code for creating the "super.dat" file. The lack of logging into SysLog makes it hard to debug. Quote Link to comment
gfjardim Posted March 29, 2013 Share Posted March 29, 2013 shlomiassaf, This happens because udev cannot create the right link to the vmdk disk due to the absent of an unique string capable of identify the disk. There are no serial or model numbers that can be used to create an unique link in the /dev/disk/by-uuid dir, and unRAID uses these links to detect array disks. IDE-type virtual disks have emulated serial numbers, therefore udev rules are applied and links are created; SCSI-type virtual disks don't have emulated serial numbers, and udev rules fail. Quote Link to comment
WeeboTech Posted March 29, 2013 Share Posted March 29, 2013 I'm using pvscsi with unRAID basic and this is what I see root@unRAID3:~# ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 2013-03-29 20:30 107d2d92-1cba-4da0-b104-86c4be7eaec9 -> ../../sdb1 lrwxrwxrwx 1 root root 10 2013-03-29 20:30 88D0-3575 -> ../../sdc1 lrwxrwxrwx 1 root root 10 2013-03-29 20:30 9431-4C95 -> ../../sda1 I can't check into the cache naming right now since I'm still using unRAID basic. Once I get my keys authorized, I'll look further. I think you can set the trace level higher for the md driver with . /root/mdcmd set md_trace 5 Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 shlomiassaf, This happens because udev cannot create the right link to the vmdk disk due to the absent of an unique string capable of identify the disk. There are no serial or model numbers that can be used to create an unique link in the /dev/disk/by-uuid dir, and unRAID uses these links to detect array disks. IDE-type virtual disks have emulated serial numbers, therefore udev rules are applied and links are created; SCSI-type virtual disks don't have emulated serial numbers, and udev rules fail. I have a UID for the SCSI drive: root@Storage:~# ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 65492fc7-1e83-4354-a9fe-587f94f8f8af -> ../../sdf1 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 46e43f9d-5bcd-44dc-86b8-ff66ff391243 -> ../../sde1 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 641fb8bc-71a7-41fd-b9aa-92b4ab3ddeef -> ../../sda1 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 8e3b962e-37ee-45d7-93db-2e71c28ee8e6 -> ../../sdd1 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 B037-5FB3 -> ../../sdc1 lrwxrwxrwx 1 root root 10 2013-03-30 00:12 f6bc33c6-cf9c-452c-a238-68c8d10c78c7 -> ../../sdb1 sdb1 is the SCSI vmdk. Quote Link to comment
WeeboTech Posted March 29, 2013 Share Posted March 29, 2013 What do you have in /dev/disk/by-id ? Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 What do you have in /dev/disk/by-id ? I have all of my physical drives (including serial). I also have my RDM drive lrwxrwxrwx 1 root root 10 2013-03-30 00:12 scsi-1ATA_WDC_WD10EARX-00PASB0_WD-WCAZAJ999999-part1 -> ../../sda1 The IDE vmdk is there: lrwxrwxrwx 1 root root 9 2013-03-30 00:12 ata-VMware_Virtual_IDE_Hard_Drive_00000000000000000001 -> ../../hda The unRaid usb is there as well. No sign for the SCSI VMDK.... Quote Link to comment
WeeboTech Posted March 29, 2013 Share Posted March 29, 2013 Is the SCSI VMDK an RDM pass through or a virtual .vmdk file? See where I show the 3 commands I used to get the pvscsi drive to be detected. The one that is un commented worked. I'm using pvscsi, not lsi. vmkfstools -z /vmfs/devices/disks/vml.0100000000202020202020202020202020533145303037544c535432303030 ST2000DM0012D9YN164.vmdk -a pvscsi Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 Is the SCSI VMDK an RDM pass through or a virtual .vmdk file? See where I show the 3 commands I used to get the pvscsi drive to be detected. The one that is un commented worked. I'm using pvscsi, not lsi. vmkfstools -z /vmfs/devices/disks/vml.0100000000202020202020202020202020533145303037544c535432303030 ST2000DM0012D9YN164.vmdk -a pvscsi RDM works fine in unRaid, I use it for a disk connected to the MB. The porpuse is to attache a SCSI vmdk to unRaid and use it as a Cache drive. The vmdk storage is a ZFS array which shares access via NFS... no RDM here. Quote Link to comment
shlomiassaf Posted March 29, 2013 Share Posted March 29, 2013 Connecting an IDE & SCSI disks to windows and running "wmic diskdrive" shows some info. First, all SCSI drives have model name and Caption. SCSI does not have a serial number, IDE does but it does not show in the description (e.g drive select ComboBox) SCSI has a signature property with numeric value (eg. 730806924 ) in IDE its 0. The info shown in the ComboBox is taken from a property called "PNPDeviceID" For IDE: IDE\DISKVMWARE_VIRTUAL_IDE_HARD_DRIVE___________00000001\5&4E95D23&0&0.0.0 The bold is what I see in the ComboBox. For SCSI: SCSI\DISK&VEN_VMWARE&PROD_VIRTUAL_DISK\5&174A0EAF&0&000000 The bold is what changes between disks... the 2nd drive I have added has 000100 I dont have ideas.... I will appriciate any help from experts... Quote Link to comment
BetaQuasi Posted March 30, 2013 Share Posted March 30, 2013 Great work shlo, it appears between what you have done and gfjardim's comments, we at least know the root cause of the issue. This is way beyond my knowledge though - hopefully someone can assist, like you say! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.