Basically it means the data it received was inconsistent. If you Acknowledge it, and it comes back, then you know it has gotten worse.ĬRC Errors are connection issues and not really a disk problem, but the disk counts these and keeps the count in its firmware. No point in letting a Warning just sit there and not do anything at all about it. Once acknowledged, it will not warn you again unless it changes. If it is not serious enough, you Acknowledge it by clicking on it in the Dashboard. If it is serious enough you replace the disk. When you do get a SMART warning, you need to make the warning go away. I have nothing notifying me in the Browser, and I get emails for Array Status, Notices, Warnings, and Alerts. You can control how different Notifications are given to you, SMART is important enough that you need to know about them even if you don't happen to open up the webUI. Rebuild of disk1 has started.īut are you getting those SMART warnings in email? I haven’t noticed any VM issues with Nvidia. Mar 25 21:23:13 Server2018 kernel: kvm_set_msr_common: 12094 callbacks suppressed Mar 25 21:21:59 Server2018 avahi-daemon: New relevant interface vnet0.IPv6 for mDNS. Mar 25 21:21:59 Server2018 avahi-daemon: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe00:2981. Mar 25 21:21:59 Server2018 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Not sure what this end of syslog stuff is, seems related to nvidia and VMs:
SMART for that disk looks OK and since emulated disk1 is mounted should be good to rebuild to that disk. 12TB disk (sdg) serial ending 0TGDM I assume was disk1.
0 kommentar(er)
