Disk Management not seeing new virtual disk

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
covanent
Posts: 3
Joined: Mon Jul 26, 2010 6:19 pm

Mon Jul 26, 2010 6:40 pm

Likely I'm doing something that's obviously wrong, but I can't see it. I ran Starwind 4.1 quite a bit last year and got somewhat familiar with it -- this new version is quite different. Anyway, here's the story. On a Windows 2008 R2 Hyper-V image, I have Starwind 5.4 (free) installed. I created a image file and loaded it. Everything looks like it's running fine, but when I go to the Windows Disk Management program and do a new scan, it doesn't see any new volume to initialize or format. Is there another step I need to take before it'll see it? I've tried rebooting to no avail.

There's nothing obviously special in the Windows Event Log, and from the Starwind log:

7/26 11:12:42.470 a94 S: SymId: 'ImageFile1': Assigned target name: 'iqn.2008-08.com.starwindsoftware:vp2k8r2c1.lab.net-serverdisk', alias 'serverdisk'
7/26 11:12:42.470 a94 IMG: SscPort_Create: Opening device 'ImageFile1', image file 'My Computer\C\Cluster\serverdisk.img', buffering=0, async=1, readonly=0.
7/26 11:12:42.470 a94 IMG: ImageFile_Create: 'C:\Cluster\serverdisk.img': type 0, geometry: sct 16, trks 32, cyl 4096, TotalSectors: 2097152
7/26 11:12:42.470 a94 IMG: ImageFile_Create: VendorId 'ROCKET ', ProductId 'IMAGEFILE ', Revision '0001', Serial 'B34C8B2A2816ABB5'
7/26 11:12:42.470 a94 Tgt: : parameter 'header', value '0'.
7/26 11:12:42.470 a94 Tgt: : parameter 'file', value 'My Computer\C\Cluster\serverdisk.img'.
7/26 11:12:42.470 a94 Tgt: : parameter 'buffering', value 'no'.
7/26 11:12:42.470 a94 Tgt: : parameter 'asyncmode', value 'yes'.
7/26 11:12:42.470 a94 Tgt: : parameter 'ImageSizeLow', value '1073741824'.
7/26 11:12:42.470 a94 Tgt: : parameter 'ImageSizeHigh', value '0'.
7/26 11:12:42.470 a94 Tgt: : parameter 'readonly', value 'no'.
7/26 11:12:42.470 a94 Tgt: : parameter 'CacheMode', value 'none'.
7/26 11:12:42.470 a94 Tgt: : parameter 'CacheSizeMB', value '0'.
7/26 11:12:42.470 a94 Tgt: : parameter 'CacheBlockExpiryPeriodMS', value '0'.
7/26 11:12:42.470 a94 S: iqn.2008-08.com.starwindsoftware:vp2k8r2c1.lab.net-serverdisk: 65536 session(s) allowed.
7/26 11:12:42.470 a94 conf: Target [0x000000000044E440] has been created. Device 'ImageFile1' is accessible as target 'iqn.2008-08.com.starwindsoftware:vp2k8r2c1.lab.net-serverdisk'.
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue Jul 27, 2010 8:04 am

Do you have ROCKET device visible at the client side in System -> Device Manager as a disk node?
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
covanent
Posts: 3
Joined: Mon Jul 26, 2010 6:19 pm

Tue Jul 27, 2010 2:56 pm

Nope. Under Device Manager | HOSTNAME | Disk Drives, the only entry is "Virtual HD ATA Device". Doing a "Scan for hardware changes" operation doesn't result in anything new found.
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue Jul 27, 2010 3:07 pm

OK, moving forward... Does iSCSI initiator show active connection to StarWind? What you see there?
covanent wrote:Nope. Under Device Manager | HOSTNAME | Disk Drives, the only entry is "Virtual HD ATA Device". Doing a "Scan for hardware changes" operation doesn't result in anything new found.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
covanent
Posts: 3
Joined: Mon Jul 26, 2010 6:19 pm

Tue Jul 27, 2010 7:32 pm

I have it figured out now -- as suspected, just missing an obvious step. I hadn't run the iSCSI Initiator yet, and once I did, everything fell into place. Thanks for the pointer.
User avatar
anton (staff)
Site Admin
Posts: 4010
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Tue Jul 27, 2010 8:19 pm

Oh, c'mon :)
covanent wrote:I have it figured out now -- as suspected, just missing an obvious step. I hadn't run the iSCSI Initiator yet, and once I did, everything fell into place. Thanks for the pointer.
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply