SinoBreizh

Thanks for confirming it. With the broken GUI for self tests, I was worried Unraid's management of NVMe drives had underlying issues that no one talked about. Into the pool it goes then!

That's about as expected for the SMART data, which is fine. What I'm worried about is that Unraid won't handle NVMe health (no alerts, regular self tests, etc), and the broken GUI seems to indicate that NVMe support was indeed an afterthought. I can't find any information on the topic; it seems like people just wing it and hope for the best. Manually running scrub every once in a while can't possibly be the expected way to manage disk health? Especially given how well Unraid handle drive health otherwise, for Array disks and Cache.

Hello, I've just added a 1Tb Crucial P1 as a cache drive to my 6.12.3 setup. I've used the preclear plugin to validate the drive before assigning it to cache. I wanted to run a final short SMART self test, but to my surprise, the button, while clickable, does nothing. Same for the long self test. (See "Self Test" screenshot) The only way I was able to get a SMART report was through the "smartctl -a" command. (See "Result" screenshot) Now I have a vague knowledge of the fact that NVMe drives, while providing "SMART" data, usually do not adhere to traditional formatting of SMART data in the form of attributes. This could explain why the attributes tab is empty, save for a single "flag" column. (See "Attributes" screenshot) But that does not explain why Unraid's interface is unable to run a SMART test on the drive, with broken buttons in the GUI. There also seems to be a very little info on the topic, save for a single reddit post from 3 months ago. TL;DR: I'm worried that Unraid will not natively keep track of SMART data, and notify me when things are out of line. The Crucial P1 is known to be a hot running drive with low endurance, making proper monitoring all the more important. Is Unraid's GUI monitoring of NVMe drives broken, or is there a deeper issue? Thanks in advance!

Makes perfect sense now. Thanks for taking the time to help!

Oh wow, this is embarassing. Just set the export to "yes", and it now correctly shows up in Windows Explorer natively. Out of curiosity, is this new behaviour compared to releases from early 2022? I don't recall having to manually go into share settings and set export to yes. It does make sense that it's off by default, it might just be my memory flaking. Thanks for the quick and simple answer regardless!

Hello, new Unraid user here, and first post in the forums. Quick disclaimer: I've read around a lot and did quite a bit of research trying to solve this, and I picked up on a few forum best practices, like attaching diagnostics; please do let me know if I can do anything to make it easier/simpler for others to help. The issue: After turning on network discovery, both my Windows 11 22H2 installs (one laptop over wireless, and one desktop over Ethernet) can properly see my server called TOWER (see attachment 1). Double clicking on it reveals no shares as it did in 6.9.x when I tried Unraid a few months ago (see attachment 2). Linking directly to \\TOWER\plexmedia in windows explorer leads to an error 0X80004005, which when diagnosed explains " 'TOWER' exists but Windows can't find 'plexmedia' ". As far as I can tell my path syntax is correct (see attachement 3 and 4 for plex docker paths, and shares list respectively), but even if it wasn't, it doesn't explain why the shares don't show up as folders in TOWER. Correct me if I'm wrong, but folders created by dockers at the highest possible mount point in an array are shares by default. All SMB share settings are set to default (see attachement 5). I am logged in to TOWER as a guest using "\" credentials in Windows' network credentials prompt. Things I have tried: Set cache preference to "No" on my plexmedia share. Not sure it helps, but intuitively I didn't want to mess with data on both the cache and the HDDs until I got everything set up. Installed UD (unassigned devices) plugin as per this post who seemed to have similar symptoms. Installing the UD plugin solved nothing. Side question: do I have to restart the server for certain plugins to come into effect? I have NOT forced SMB 1 functionality on Windows 11, as recommended by most users due to security vulnerabilities. I have NOT created any dedicated users in the Unraid GUI for my SMB shares, as I did not want to mess with more settings before fully understanding what I'm doing. Unraid GUI only has a root user, and I'm logged in as a guest "\" in Windows' network credentials prompt. Thanks in advance for your help, and let me know if you need more information. Best, tower-diagnostics-20221115-1539.zip