00:19:50.139 55 ERROR rvice Manager for service cinder-volume is reporting problems, not sending heartbeat. 00:19:40.138 55 ERROR rvice Manager for service cinder-volume is reporting problems, not sending heartbeat.
CANNOT INITIALIZE DRIVE IS NOT READY WINDOWS 10
00:19:30.136 55 ERROR rvice Manager for service cinder-volume is reporting problems, not sending heartbeat. Normally, may users would not adapt to format the drive when they encounter the drive cannot find the sector requested Windows 10 issue as it will cause data loss (Check Out This Way To Recover Files From Formatted Hard Drive).
CANNOT INITIALIZE DRIVE IS NOT READY DRIVER
00:19:20.135 55 ERROR Cannot complete RPC initialization because driver isn't initialized properly.: DriverNotInitialized: Volume driver not ready. In such events of hard drive uninitialized, the hard disk shows an unallocated space in the Disk Management thereby, you’re not able to access it as shown in the below image: As is shown in the image above, that Disk 1 is not initialized, therefore, making it difficult to access it. Type ' select disk ' (You need to select your disk that is listed here, here in the test, we need to select disk 2 for our scenario) Type ' attribute disk clear readonly '. Diskpart fix disk unknown not initialized. 00:19:20.134 55 ERROR cinder.utils Volume driver PureISCSIDriver not initialized Steps 2 - Type diskpart in the coming up cmd window. 00:19:20.133 55 INFO Initializing RPC dependent components of volume driver PureISCSIDriver (7.0.0) 00:19:19.886 55 ERROR PureDriverException: Missing 'purestorage' python module, ensure the library is installed and available. 00:19:19.886 55 ERROR raise exception.PureDriverException(msg) 00:19:19.886 55 ERROR File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/pure.py", line 236, in do_setup 00:19:19.886 55 ERROR File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 456, in init_host 00:19:19.886 55 ERROR Traceback (most recent call last): it reduces interfaces which may not be fully compliant and or faulty. This is the only method that works where issues occur when connecting drives any other way. | cinder-scheduler | overcloud-controller-no-ceph-2 | nova | enabled | up | T06:15:42.000000 | If that pc has an ide optical drive simply swap the drives over (master is end of ide cable, slave is middle connector) and try again to initialise drive.
| cinder-scheduler | overcloud-controller-no-ceph-0 | nova | enabled | up | T06:15:49.000000 | | cinder-scheduler | overcloud-controller-no-ceph-1 | nova | enabled | up | T06:15:45.000000 | | Binary | Host | Zone | Status | State | Updated At | (overcloud) ~]$ openstack volume service list The deployment completes successful without any errors but the status cinder-volume is down.