ChatNoir

It would be helpful if you could create a bug report with this information and your diagnostics. https://forums.unraid.net/bug-reports/prereleases/

If I was to guess, probably a larger write capacity ? You might want to check on the datasheet.

Generally for cybermonday.

Lets move to General Support, Forum Feedback is clearly not the place for those discussions.

Thanks for sharing, it could help someone in the future. 👍🏻

On the Main page, click the disk name, change the spindown delay to 'Never', Apply, the go to the 'Self-Test' tab and 'Start' the 'SMART extended self-test' There is no hard rule. But for me : any drive with more than a single digit of errors total on important attributes is a disk at risk and that I would keep a close eye on. any important attribute with more than a single digit, I would keep a replacement disk ready. Some attribute might make me replace ASAP. On WD drives, I would keep an eye on : Raw_Read_Error_Rate Reallocated_Sector_Ct Reallocated_Event_Count Current_Pending_Sector Offline_Uncorrectable Multi_Zone_Error_Rate Other brand do things differently (especially Seagate with Raw Errors).

Parity 1 looks pretty bad. IDs 1;198;200 would be big no-nos for me. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 36 3 Spin_Up_Time POS--K 173 167 021 - 6308 4 Start_Stop_Count -O--CK 100 100 000 - 99 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 009 009 000 - 66543 10 Spin_Retry_Count -O--CK 100 253 000 - 0 11 Calibration_Retry_Count -O--CK 100 253 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 98 192 Power-Off_Retract_Count -O--CK 200 200 000 - 48 193 Load_Cycle_Count -O--CK 176 176 000 - 74667 194 Temperature_Celsius -O---K 121 100 000 - 29 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 2 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 9Parity 2 is not great either. Less bad, but still bad. ID 1 is lower and 198+200 are at 0, but 92 realallocated sectors feels like a lot. ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 6 3 Spin_Up_Time POS--K 161 143 021 - 8941 4 Start_Stop_Count -O--CK 100 100 000 - 313 5 Reallocated_Sector_Ct PO--CK 188 188 140 - 92 7 Seek_Error_Rate -OSR-K 100 253 000 - 0 9 Power_On_Hours -O--CK 001 001 000 - 91204 10 Spin_Retry_Count -O--CK 100 100 000 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 276 192 Power-Off_Retract_Count -O--CK 200 200 000 - 143 193 Load_Cycle_Count -O--CK 134 134 000 - 200636 194 Temperature_Celsius -O---K 119 093 000 - 33 196 Reallocated_Event_Count -O--CK 178 178 000 - 22 197 Current_Pending_Sector -O--CK 200 199 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 194 000 - 0WD-WCAVY1555288 also has some Raw_Read_Errors. I would keep an eye on it. The other drives seem OK.

Hi, SMART errors are not "fixable". Some are not important and can just be acknowledged, other are serious and denote of a serious disk problem. If you provide your diagnostics, we can help you decide what to do. It should unless I am missing something. However there might be speed limitations (TBC). You should find that here :

More info on your system will help. But it looks like maybe the GPU takes most PCIe lanes and the HBA has not any or not enough for it to initialize or being seen by the OS ?

But this is to be expected since the global credentials are managed by the Plex infrastructure and the server is a client among others. I don't really see how it could be otherwise. For anyone wanting something entirely free of any third party, sure Plex is not a good choice. But I still think that they offer a valuable service for my use-case.

For this, you should contact support.

If it is just some SATA SSDs, maybe they don't need to be on the HBA and can be attached to the motherboard. That would simplify your use case.

That would be there : https://forums.unraid.net/bug-reports/stable-releases/

I think it's the Cat Conspiracy ! They are everywhere, especially in our developers' homes.

That's what beta are for, finding bugs on a larger HW and use case base than what can be tested internally at Limetech We only see the bug parts in the bug report section, not any users that have no bugs and everything working fine (true for the whole forum, not just the bug report section though) But as started :

Hi, your diagnostics might provide more information.

its probably not simple to have a reliable number to provide in general its getting more and more complex with multiple share moving files from one pool to the Array or the other way around What to show then ? and more importantly, I think that 95% of people run their mover on a server downtime and don't care much. For me it runs while I am sleeping, so it take the time it needs. All this put together, probably make a high effort low reward task and probably for a low percentage of the userbase.

You should probably define : best (cost, performance, energy economies, etc.) your budget what you expect from the NAS

Do you mean secure boot active on a VM ? Or on the server itself ?

There are new bug reports created for b2 and older ones closed since its release. So, some people are trying it.

It's probably more relevant in the plugin's support page :

In the last video, they stated that work on improving the UI was prioritized as a way to facilitate the addition of multiple arrays in the future.

Since you seem to be in the US, did you check the ebay store TheArtofServer ?

To expand on JorgeB's answer : ReiserFS is EoL and will not be supported in future linux releases.

This has always been the case, it's not related to the new license scheme.