@snafu Sorry not to have gotten back sooner, just wanted to give you an update that as of Rockstor 3.8-14.02 testing channel updates the following code change as previously referenced are now included.
Just to let you know as this thread lead to that change. Upon our smartctl version being able to support nvme devcies then the exclusion for nvme can be removed. So at least for now we shouldn’t have any more smartctl --info probes cluttering up the logs on these types of devcies.
There is also another thread in the forum where @f_l_a has reported the same smartctl version problem regarding nvme support and had a good, but unfortunately unsuccessful attempt to install a newer version, but did make some headway on retrieving serial numbers from these devices using specific nvme tools:
The rogue smartctl --info calls however are the least of our problems and I appreciate this, but just to let you know that your input has already helped here.
Unfortunately I haven’t managed to look further into your problem specifically which seems to revolve around having a null entry for the serial field in your nvme0n1p3 db entry. This should not be possible and would definitely point at a bug in the code somewhere. Probably caused by not accounting properly for the nvme drive as it appeared, either before or after the udev rules. If you are game (and this is risky) you could try just deleting that entry in the db directly. It should just be re-created on the next disk Rescan but could leave your system in an unstable state. Also as from the referenced update Rockstor now uses by-id names so it is particularly important to get those right via the udev rules but should also hopefully help with seeing what is going on.
Thanks for providing such a wealth of info, it is bound to help with nvme support in the future.