unraidun

Can confirm this solved the problem. I was also unable to play files in VLC (other media players worked fine). But as soon as I touched a file, VLC suddenly started working. Did you end up writing a script to recursively scan all directories and touch all files? Mind sharing?

Hah fair point I was kinda hoping it was just that simple. Is 6.8.2 (a little over a year old) really that "insecure"? It's been on my todo list for sure. If anyone else confirmed that the latest version DOES indeed keep unspun drives unspun when waking from sleep, that would definitely be more motivation for me to do the update.

Unraid 6.8.2 using Dynamix S3 Sleep, ALL my drives come back up spinning on wake. Even if I manually spin them down before sleep. Is there any alternative way to ensure unused/unspun drives don't spin up on wake (it just seems wasteful). Thanks

Having same problem (Your input can't be opened). Only happens when trying to stream a file off a read only share with VLC (other media players work fine). It's almost like VLC is trying to write to the file/share maybe? Has anyone found a resolution yet? *when setting VLC messages to debug mode, this is the only interesting thing I see... No idea what to do with that information (or if it's even relevant).

*Forgot to mention, this is JBOD and NOT part of the array. These are for some spare junk drives I have. *and that's a concerning thought about the drives still generating heat even while sleeping... Can anyone confirm/deny? The data on these disks isn't critical, but still... Or perhaps somebody can recommend a better way to utilize these 4 spare disks I have (needs to be external USB)?

I have one of these 4 bay sata enclosures... https://www.amazon.com/gp/product/B003X26VV4/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 And UnRaid just sent me an alert that a disk was warm (47c). I went and checked, and the bay was in SLEEP mode (orange lights, no fans spinning, so it was definitely asleep). And at least the disk on the top (the only one I could reach) felt cool. The exact same thing happened the other day (although the bay was awake, just not in use). Here's the really odd thing - I pointed a big room fan at the box (with the front cover open), and about 5 minutes later, unraid said that the drive in question had returned to 'safe' temperature. Also, I've NEVER been able to see the actual temps of the drives (in my unassigned devices section, I just get a * for all the temps), so I don't know how unraid was even reading the temps (especially while the bay was sleeping). A failing sensor/false positive was my first guess, but anyway to troubleshoot this and figure out what's for sure going on? Or at least figure out why unaid isn't reporting the temps in my dashboard? Thanks

That app looks great, but still haven trouble. I went into bios and set "Power On By PCI-E/PCI" to enabled (that was the only thing that made mention of WOL). Confirmed that ethtool shows "Wake-on: g". Unraid 6.8.2. WakeMeOnLan shows the correct On/Off status for my server (so I know I have the ip/mac right). But the app is still unable to wake from sleep (only way to wake is with keyboard). For the properties section I only have the ip/mac, do I need to configure anything for the broadcast or port number? *and both machines are on the same subnet so I don't think its a routing issue... I can ping it when its awake

I imagine a lot of people are running a Windows workstation with a second Unraid box as a media store, so how do you guys wake your sleeping Unraid server? Is there something built into Windows (10), or a simple script, or a 3rd party app, etc...? Thanks

*yup looks like the 'is parity already valid' check box doesn't even exist unless you're adding a Parity drive. Just added the pre cleared drives and everything looks good. Marking as Solved.

Ahhh ok I was indeed adding a new parity disk. So it's doing a parity sync now, but I still have a couple un assigned drives (pre cleared) waiting to be added. So when the parity sync is finished, you're saying I can safely check the 'skip the parity sync' check box when adding the remaining (non parity) drives?

I'm pretty sure the answer to this question is "yes", but is it safe to skip the parity check/sync when adding a new disk to your array IF the disk is already pre cleared? The parity (even in a dual parity drive setup) should be unchanged if the new drive being added to the array is all zeros, right? Thanks.

Bleh... Well decided that the above tutorial was the only option available, but it also looks like it's missing something. The very first step (run sensors-detect) doesn't contain anything about "#----cut here---- # Chip drivers". A little googling seems to suggest maybe I need to add 'coretemp' drivers to /etc/modules? Confirm/deny? And if so, how? Has anyone been able to successfully implement the above tutorial?

Plugin looks great, just had a few questions... - I assume there is one hash file per actual file? And we can specify where these hashes are stored (so they can be backed up?). - What does the performance impact look like? Let's say we add a 1 gig file to a typical 200MB/sec hard disk. How long will it take to generate the hash (assume this happens automatically behind the scenes)? How long will it take to validate that same file? - Any differences between this and btrfs scrub (in terms of detecting file corruption/early drive failure)? Thanks

Ordered 2x of the Asmedia 106X, but doesn't look like they will get here for a few weeks at least... If anyone has any other 2-4 port pcie x1 cards they recommend let me know...

Yup seems to be working fine so far (although I've yet to actually build my array, still just pre clearing 100TB of disks). Just make sure you either build your flash drive with UEFI support (click the hidden tick box in the unraid flash maker wizard) or enable the CSM legacy features when trying to boot your unraid flash. The only concern with this board is the limited PCIe slots (assuming you want to add a 10g nic), however I think these PCIe x1 sata expansion cards could solve that problem (assuming you need more than 8 sata ports). Thanks! That comparison is very helpful. So it sounds like the main problem with the Marvel cards relates to having IOMMU enabled, but in RobJ's post he hinted at a potential patch to fix it? Can anyone confirm this is no longer an issue? Ordering two of those 9215's (which according to your tests, would give me 200MB if I only used two ports), would give me exactly what I need...