PowerFlex 3.X: Impossibile aggiungere volumi al servizio esistente

Summary: Quando un volume viene rimosso da un servizio PowerFlex Manager (PFxM) e viene effettuato un tentativo di aggiungerlo di nuovo, l'operazione non riesce con il messaggio "Si è verificato un errore durante l'elaborazione dei componenti di storage". In questo caso, questo errore è dovuto a dati VMFS (Virtual Machine File System) non aggiornati che risiedono sul volume. Una volta confermato che questi dati sono inutilizzati, rimuoverli e riprovare l'operazione. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Quando il asmManager.log viene esaminato in PFxM, potrebbero essere visualizzate voci come quelle riportate di seguito.

INFO  [2022-12-07T09:18:13.504666] 12352: service_deployment.rb:1255:in `block in process_components': An error occurred during the processing of storage components.
ERROR [2022-12-07T09:18:13.506285] 12352: service_deployment.rb:622:in `process': sudo puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/resources/<VCENTER_NAME>.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/resources --always-override <VCENTER_NAME> failed; output in /opt/Dell/ASM/deployments/8a97e98a84e8277f0184e8548ffc0f6d/<VCENTER_NAME>.outERROR [2022-12-07T09:18:13.506466] 12352: service_deployment.rb:623:in `process': ["/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:384:in `block in run_command_streaming'", "/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:212:in `popen_run'", "/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:102:in `popen3'", "/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:352:in `block in run_command_streaming'", "org/jruby/RubyIO.java:1171:in `open'", "/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:351:in `run_command_streaming'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1575:in `block in process_generic'", "/opt/asm-deployer/lib/asm/private_util.rb:1079:in `block in wait_until_available'", "/opt/asm-deployer/lib/asm.rb:502:in `wait_on_counter_threshold'", "/opt/asm-deployer/lib/asm/private_util.rb:1078:in `wait_until_available'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1518:in `process_generic'", "/opt/asm-deployer/lib/asm/type/base.rb:578:in `process_generic'", "/opt/asm-deployer/lib/asm/provider/elementmanager/scaleio.rb:4099:in `create_batch_scaleio_datastores'", "/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `block in process_multiple_volumes'", "org/jruby/RubyArray.java:1779:in `each_slice'", "/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `process_multiple_volumes'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1979:in `process_multi_scaleio_storage'", "/opt/asm-deployer/lib/asm/service_deployment.rb:1320:in `block in create_multi_components_thread'"]


Nel exception.log, vediamo:

#<RuntimeError: sudo puppet asm process_node --debug --trace --filename /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/resources/<VCENTER_NAME>.yaml --run_type apply --statedir /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/resources --always-override <VCENTER_NAME> failed; output in /opt/Dell/ASM/deployments/8a97e98a84e8277f0184ec2d50f40958/<VCENTER_NAME>.out>
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:384:in `block in run_command_streaming'
/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:212:in `popen_run'
/opt/jruby/9.1.17.0/lib/ruby/stdlib/open3.rb:102:in `popen3'
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:352:in `block in run_command_streaming'
org/jruby/RubyIO.java:1171:in `open'
/opt/jruby/9.1.17.0/lib/ruby/gems/shared/gems/dell-asm-util-0.1.0/lib/asm/util.rb:351:in `run_command_streaming'
/opt/asm-deployer/lib/asm/service_deployment.rb:1575:in `block in process_generic'
/opt/asm-deployer/lib/asm/private_util.rb:1079:in `block in wait_until_available'
/opt/asm-deployer/lib/asm.rb:502:in `wait_on_counter_threshold'
/opt/asm-deployer/lib/asm/private_util.rb:1078:in `wait_until_available'
/opt/asm-deployer/lib/asm/service_deployment.rb:1518:in `process_generic'
/opt/asm-deployer/lib/asm/type/base.rb:578:in `process_generic'
/opt/asm-deployer/lib/asm/provider/elementmanager/scaleio.rb:4099:in `create_batch_scaleio_datastores'
/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `block in process_multiple_volumes'
org/jruby/RubyArray.java:1779:in `each_slice'
/opt/asm-deployer/lib/asm/provider/volume/flexos.rb:200:in `process_multiple_volumes'
/opt/asm-deployer/lib/asm/service_deployment.rb:1979:in `process_multi_scaleio_storage'
/opt/asm-deployer/lib/asm/service_deployment.rb:1320:in `block in create_multi_components_thread'


Se accediamo a /opt/Dell/ASM/deployments/<JOB_ID>/ ed esaminiamo <VCENTER_NAME.out>, vediamo voci simili a quelle riportate di seguito.

Error: /Stage[main]/Asm::Resource_wrapper/Asm::Fcdatastore[x.x.local:<DATASTORE_NAME>]/Esx_datastore[x.x.local:<DATASTORE_NAME>]/ensure: change from 'absent' to 'present' failed: Unable to perform the operation because the following exception occurred:- 
 Existing VMFS partition on disk, cannot create datastore on /vmfs/devices/disks/eui.5c3e682f06560c0fc6afcb0e00000010
Debug: Asm::Fcdatastore[x.x.local:<DATASTORE_NAME>]: Resource is being skipped, unscheduling all events
Debug: Datastore not found with id: c6afcb0e00000010 searching on datastore name: <DATASTORE_NAME>
Debug: Creating VMFS volume <DATASTORE_NAME> on device eui.5c3e682f06560c0fc6afcb0e00000010
Error: Unable to perform the operation because the following exception occurred:- 
 Existing VMFS partition on disk, cannot create datastore on /vmfs/devices/disks/eui.5c3e682f06560c0fc6afcb0e00000010
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/errors.rb:157:in `fail'

Cause

Se il disco è stato precedentemente utilizzato in PFxM, è molto probabile che sia stato rimosso in modo improprio se i dati VMFS rimangono.

Resolution

Rimuovere i dati VMFS esistenti dal disco in vCenter.
Riprovare il deployment o aggiornare i dettagli del servizio.
Una volta visualizzato tutto in verde in PFxM, tentare di aggiungere nuovamente i volumi.

Affected Products

PowerFlex rack, PowerFlex Appliance
Article Properties
Article Number: 000206418
Article Type: Solution
Last Modified: 01 Dec 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.