Georg

Thank you for your reply! I tried that one a while a go but never got it to work. I will git it a second try then. Thank you for the heads up! That may be a big issue since there may be 10x that amount of files on there. I will give it a read. I do have krusader for the rare cases i need it but both would not help the indexing need for windows.

Hello I am using windows 10 while accessing unraid via a network share. By now the system grew to a huge number of files and many drives. As a result real time searches, as forced by windows, take ages. Is there a solution and preferably one that is realizable for a beginner? Unfortunately the discussions I have found are rather old and/ or mostly not in connection with a network share. So far I learned that Windows does not index network shares and there is nothing for a Windows sided indexing unless you use an external file manager which I am a bit reluctant to do since I mostly like the one windows provides. The server sided solutions for indexing are often outdated discussions or seem to be regarding a search within unraid or a file manager docker but not for users accessing files via e.g. a windows network share. I don't mind where it is indexed but I just would like to have a faster search result on windows. As a last resort, is there a better file manager for windows I have missed? On the side, is it really that infrequent that people use a similar setup as me? Am I missing something? Thank you in advance!

So now that there were talks over years, when can we expect it? Are we talking a few months or rather >1-2 years. Already looking forward to it

Have ordered another cable now. Thx for the help Oh, that explains the difference in some cables... Well I see that as a plus and anyway it will be until I need to connect the other disks. By then I anyway need to free up a slot or buy a bigger hba card.

Thank you for your answer. 1) I think I should go for that on then an try another source. 2) Yes they are all connected. Or do you have a bios setting in mind that could case it to not being recognized?

Sorry I have missed, that you have answered. My backplane is an SAS846A. The ones with an expander have an EL1 or 2 instead of the A. The "A" version has 6 SFF8087 connectors, each connecting to 4 drives. My HBA only has 4 connectors (=16 drives). The remaining 8 drives are not yet connected. At least as a mid term solution I wanted to use the reverse breakout sata (MB) to SFF8087 (backplane) cable for four of the remaining drives. Unfortunately they are not even recognized by the bios. I think I was able to test everything but the cable itself without any issues. As I don't think the cable is already broken I don't know where else the problem could be. BPN-SAS-846A.pdf

Not quit sure if I get your point right but when the same drive is connected with a plain sata cable it works. Meaning the MB would accept the drive as such and the sata port and the drive is working.

Hi all, My system consists of a 24 bay case with an SAS846A Backplane. 15 of the drives are connected via LSI 9300-16i and are in use. As I need to connect more drives to the MB I have ordered a reverse breakout sata to SFF8087 cable (4 sata at MB and SFF8087 at backplane). Unfortunately the bios does not recognize any of the disks attached with that cable. The port of the backplane connected to the HBA works. Also the sata ports work with other drives. The only idea I have is a cable issue or something with the bios settings. Any idea if i have to change settings in the bios or where the mistake could be? The cable is the correct one right? I am using the AsRock X470 Taichi Ultimate and an AMD Ryzen 7 2700X.

Sorry for the long time... I have successfully updated the HBA card, thinking at first that this was the solution but it wasn't... I also tried another PSU, switching drives around, changing cables. By doing so, I think, I could narrow down the error to one SFF8643 port of the SAS 9300 i16. In that plug it is always the first bay/hdd of the four which has the error. I also got the impression that it occurs more often when writing to that disk than when reading from it but this might be wrong. Do you think there is a way to further trouble shoot that error?

First of all thank you for your answer! Well not easy but I could use the one from my PC. I think I will first try to update the SAS 9300 16i as it should be done anyway. Do you coincidentally have some tips for that? How likely is it that I kill the card when having no experience with it at all?^^ (I would try to follow that thing https://www.broadcom.com/support/knowledgebase/1211161501344/flashing-firmware-and-bios-on-lsi-sas-hbas) I will probably try it on the weekend. When switching the PSU, would you suggest a specific test or should I just try, use it and see what happens? The one installed is a Corsair HX850i and te one currently in my PC is a Corsair RM750x.

Hi all, I have some weird disk errors that occur when I for instance start to copy files with the windows explorer onto a network share or otherwise use the system. It is not exactly logical to me what triggers the error. They happen usually on multiple disks at the exact same time and it does not seem to affect the system to hard but usually resulting in a copy error. After a restart they are obviously deleted but reoccur again. I am also not sure whether it is is connected to reaching a high water level mark. In those cases I get the following windows copy error: Do you know how to avoid this kind of error? Each time a high water level is reached I have to at least once stop and restart the array to be able to start the copying process again. Shouldn't it normally switch automatically to another disc? A third thing which may could play a role in this is that I sometimes see this and are then subsequently not able to view the log file: Those errors have happend several times now, so I have multiple diagnostic files: atlas-diagnostics-20191128-2305.zip atlas-diagnostics-20191125-2006.zip Thanks in advance! Regards, Georg

Unfortunately not. I don't even know where to start... From what I have read in forums and all, it gives me the impression that it appears if Linux (unraid) and a X version of a Ryzen processor come together. Please keep me up do to date in case you find a solution. It kinda makes me worried whether the CPU gets sufficient cooling. As the MB reads them correct, I guess the fan is not affected.

Thanks for your reply! I had a look again and after searching every single f...... folder I have finally found it: Advanced / AMD CBS / NBIO Common Options / MB Configuration / IOMMU --> enable AsRock did a good job in hiding it!

Hi all, Unfortunately I don't know any further and google could not help... In the bios I have enabled SVM Mode (CPU configuration) as well as SR-IOV (Onboard device configuration) but Unraid still gives me an IOMMU disabled: Is there an option called "IOMMU" I have to enable additionally? If yes where? I have also noticed that there are no IOMMU groups shown in system devices (this may happen after unraid recognize IOMMU as enabled?) Thank you for helping in advance! Georg

Sorry i did not get that you have answered. Could be but then the separator is not always transferred: (I have set the CPU as cpu temp and the smbus master as MB temp) Also the bios states different temperatures. Even if I read it wrong it does not move at all. From right after the start to continues loads of 50% it always says -62.5 C. Also because of: I understand that maybe not all the sensors are connected/ used but the CPU one? In the system is also an Avago SAS 9300-i16 card. I was not able to find out if it has a temp sensor or how it is called. Does someone know something? Thanks a lot, Georg