Description of problem: VCenter 6.0 vix vddk 6.0.1 The appliance is able to smart state itself which also resides on the same vcenter as the other guest that are unable to be scanned. The guest systems that raise the "No root filesystem found" are Rhel 7 guest with EXT4 filesytem that is spread across 3 disk. Normally / is on one disk, /swap is on a second and then user directories is on a third. [----] I, [2016-01-22T14:57:06.661604 #3031:ff5988] INFO -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(MiqQueue.put) Message id: [404000000281776], id: [], Zone: [ default], Role: [automate], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqAeEngine.deliver], Timeout: [3600], Priority: [20], State: [re ady], Deliver On: [], Data: [], Args: [{:object_type=>"ManageIQ::Providers::Vmware::InfraManager::Vm", :object_id=>404000000000505, :attrs=>{:event_type=>"vm_scan_abort", "VmOrTe mplate::vm"=>404000000000505, :vm_id=>404000000000505, "Host::host"=>404000000000001, :host_id=>404000000000001, "MiqEvent::miq_event"=>404000000005880, :miq_event_id=>404000000005880, "EventStream::event_stream"=>404000000005880, :event_stream_id=>404000000005880}, :instance_name=>"Event", :user_id=>404000000000002, :miq_group_id=>404000000000017, :tenant_id=>404000000000001, :automate_message=>nil}] [----] E, [2016-01-22T14:57:06.661711 #3031:ff5988] ERROR -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem. Reason:[No root filesystem found.] [----] I, [2016-01-22T14:57:06.678714 #3031:ff5988] INFO -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(VmScan#process_finished) job finished, Unable to mount filesystem. Reason:[No root filesystem found.] Version-Release number of selected component (if applicable): 5.5.0 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Assigning to add test case
*** Bug 1297022 has been marked as a duplicate of this bug. ***
Hi Hui, Please add verification steps. Thanks
This issue only happens when the root filesystem is ext4 and group descriptor size is 64: 1. Use RHEL-Server automated installer (Comment 21) to create a VM. The created VM should meet the above conditions. 2. Use command mount to verify the root filesystem is ext4. 3. Use command dumpe2fs to verify the group descriptor size (Comment 20). 4. Verify the fix
Hi Colin, Can you please provide more details around the automated install configuration like the kickstart file itself? Thanks
Created a VM with root filesystem ext4 and group descriptor size 64, SmartState Analysis Works Successfully. Verified in 5.6.0.11-rc2.2.20160614152915_f315c68
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348