Description of problem:
Smartstate analysis tasks for windows 2016 machines hosted in Azure fail with a message saying the letter for the root drive could not be determined.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Perform a startstate analysis on a windows 2016 server
Actual results: errors
Expected results: an analysis report
Entire error is as follows:
[----] E, [2017-01-13T15:36:19.261090 #4052:37b130] ERROR -- : Q-task_id([81e127fc-d99d-11e6-995a-005056917c36]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem. Reason:[Could not determine root drive letter.]
[----] I, [2017-01-13T15:36:19.272774 #4052:37b130] INFO -- : Q-task_id([81e127fc-d99d-11e6-995a-005056917c36]) MIQ(VmScan#process_finished) job finished, Unable to mount filesystem. Reason:[Could not determine root drive letter.]
[----] I, [2017-01-13T15:36:19.279075 #4052:37b130] INFO -- : Q-task_id([81e127fc-d99d-11e6-995a-005056917c36]) MIQ(VmScan#dispatch_finish) Dispatch Status is 'finished'
Satyajit, please retest this and see if we can reproduce it. Make sure test cases exists, etc. Please pull in Jeff if you need help with Azure.
I created the VM on Azure and setup data collection. It's named WS2016D1. I'll try it or find me if you need it.
I'm seeing the same thing. Will try a few other permutations, but here's my output. I tried with SSDs and HDDs. There is no obvious difference in the setups other than the OS.
Status = Error 01/26/17 20:20:01 UTC 01/26/17 20:18:56 UTC 01/26/17 20:18:38 UTC finished Unable to mount filesystem. Reason:[Could not determine root drive letter.] Scan from Vm WS2016SSA admin EVM Scanning completed.
Status = Ok 01/26/17 20:17:39 UTC 01/26/17 19:58:27 UTC 01/26/17 19:58:16 UTC finished Process completed successfully Scan from Vm WS2012R2SSA admin EVM Synchronization complete
Status = Error 01/26/17 19:56:56 UTC 01/26/17 19:56:10 UTC 01/26/17 19:56:00 UTC finished Unable to mount filesystem. Reason:[Could not determine root drive letter.] Scan from Vm WS2016D1 admin EVM Scanning completed.
Added Test Case to Polarion to make sure it's tracked going forward.
I think this is a RFE. Fairly sure 2016 runs Windows ReFS which is not supported, right?
(In reply to Dave Johnson from comment #8)
> I think this is a RFE. Fairly sure 2016 runs Windows ReFS which is not
> supported, right?
Yes, SSA doesn't support Windows ReFS, but we haven't proved that 2016 at default runs ReFS.
I have verified that none of the systems in question are using ReFS. Everything I created was NTFS by default. Physical and virtual. Hope this helps.
(In reply to Jeff Teehan from comment #10)
> I have verified that none of the systems in question are using ReFS.
> Everything I created was NTFS by default. Physical and virtual. Hope this
Are you able to reproduce the original issue?
Well, don't know what to say. It worked today using 126.96.36.199. :) Gotta love this job. At NetApp we had a Closed status called Cosmic, for issues just like these.
IP Addresses 10.1.0.12, 188.8.131.52
MAC Address 00-0D-3A-00-9D-22
Container Show VMM container information azure: 1 CPU (1 socket x 0 cores), 1792 MB
Platform Tools N/A
Operating System Show OS container information Windows Server 2016 Datacenter
Advanced Settings 0
Management Engine GUID 2eb7f3da-238f-11e7-917f-00155d06ac11
ID within Provider c9e72ccc-b20e-48bd-a0c8-879c6dbcbfbb\automation\microsoft.compute/virtualmachines\WS2016D1
Discovered Mon, 17 Apr 2017 16:59:12 +0000
Last Analyzed Thu, 20 Apr 2017 15:49:51 +0000
Now it's interesting. Did you get other scanning results? Such as
Win32 Services 0
Kernel Drivers 0
File System Drivers 0
Registry Entries 0
Oh yeah. Everything I had enabled, anyway.
Key Pairs N/A
Win32 Services 191
Kernel Drivers 315
File System Drivers 37
Registry Entries 0
The issue can not be reproduced, ticket closed. Please reopen if it happens again.