why the status is infeasible/solved
The status is Inaccurate solved, not Infeasible solved. This might be a result of poor numerical scaling of the input data, perhaps as a result of poor choice of units for the problem. Try to change units so that all non-zero input data is within a small number of orders of magnitude of 1.
You can also try using Mosek as solver. if that is not available to you, follow the advice at CVXQUAD: How to use CVXQUAD's Pade Approximant instead of CVX's unreliable Successive Approximation for GP mode, log, exp, entr, rel_entr, kl_div, log_det, det_rootn, exponential cone. CVXQUAD's Quantum (Matrix) Entropy & Matrix Log related functions
How to identify that poor scaling of input data has been fed to the solver??
How do I scale input data so that selected solver can solve the problem without any status like inaccurate/solved??
Try to change units so that all non-zero input data is within a small number of orders of magnitude of 1, what it means??
For instance, instead of using volts as a unit and having input data of 1e-11 (volts), try using picovolts and make that input data 10 (picovolts).
If your input data has an exponent greater than 6 or less than -6, that is probably bad scaling. it is better yet to keep the exponent to -3 and 3. if the span between greatest and smallest exponent is more than 8, that’s probably bad.
These are not hard and fast rules.
Mosek provides warnings when the input data appears to be very badly scaled (when it is even somewhat more badly scaled than my recommendations above).
Mosek and Gurobi can tolerate somewhat worse scaling than the other solvers which can be called by CVX, on account of their more numerically robust implementations. But even if using a numerically robust solver, it is still a good idea to have well-scaled input data.
You can read 8.2 Addressing numerical issues — MOSEK Optimization Toolbox for MATLAB 10.2.3