Marshalleq

LOL, now there's a scary thought! Bring on devops!

@trurl @ken-ji @bonienl Thanks for your replies - all your points are good ones. This was a very very long thread and I read probably too much of it. What jumped out at me were some poor people panicking and either negatively misinterpreting the results or over expecting the plugin like it's a miracle cure. Sometimes I think we forget that not everyone (possibly even most on here) do not have IT as a first job (like at least two of us seem to) and can take thinks a little too literally or not have the background to interpret the results. e.g. 'I read that I must preclear three times for every disk, it's not working and what do I do? Is my raid safe? Must I return my drive?! Panic!' someone said. That poor soul is more likely to lose data by not having enough Unraid space available than by worrying about pre-clear status. So my point is there seems to be an unnecessary bias or unbalanced viewpoint provided (at least through the parts of this thread that I read). There should be some kind of disclaimer that balances things out for some of these people - might help prevent a few panicked comments on a very long thread too! Point of note - when I did run the preclear plugin I got a small error, which doesn't actually matter. When I added it to the array, I got that same error during its (much faster) preclear anyway. And in both cases it happened within first 10 seconds. Probably the case for most people - if they see anything, otherwise the vendor would include it in the product right? And pre-clear seems quite buggy.

Thanks for this - I've had it running for days now, with no issue. Though it hasn't exactly been idle, nevertheless, I think (hope? pray?!) it's sorted now!

This plugin makes me want to go back to RAID 5. Who knew it would take 3 days to add a drive and it might not even work, or the disk might fail a day after this plugin said it was OK. This feels like taking vitamin tablets and 'knowing' it's making a difference, when in reality there's no proof and it's all in my mind. Sorry to sound so negative (not really my style), but why people would want to do multiple read passes etc on modern disks that are designed to handle these kinds of errors as a near daily occurrence and quite normally correcting them in hardware without issue is beyond me. If you want true confidence of your data, get a self-repairing file system like ZFS coupled with ECC RAM. That peace of mind will need expensive hardware, but ZFS is stunning in that regard. However, in my opinion none of this multi-pass pre-clearing stuff gives you any guarantee over your data. You might pick up a failed drive, but you also might not. If I was this worried about my data, I'd go the ZFS route. For now I just want my drive to be part of the array and not have to wait a year while it figures out which side of the lottery it's going to fall on - correct or not. All said, I'm very new to unRAID, so hey, perhaps I've gotten something wrong (and I'm sure someone is about to tell me)! Again sorry if this sounds overly negative.

Wow, I see your post on reddit and it's getting way more traction than on here - sad. I'm going to try to see what the difference is between onboard and PCI based NIC's I have in case there's something there. My CPU seems good and I'm using all onboard SATA, but still getting weirdness.

Hmmm, such basic functionality, you would think they would add it. Maybe someone thinks unraid is just for home users, but given it's capabilities, it must be quite advanced home users that could actually understand and benefit from groups. I'm just looking into purchasing unraid now and this is a rather large negative of it. Even the base model home nas units like qnap have groups. So does Mac, Windows and so on. My 2c is this should be added and accessible from the GUI, or at least survive reboots. Certainly if I put my IT hat on.

I did find the below link, which suggests if I find the deep sleep setting and enable it I can then turn back on these other settings. Can't say I've noticed a deep sleep setting, but would be interested in your thoughts on this too. Sounds like you've figured out how to make yours nice and stable. I'll see how your suggestion works anyway. Thanks.

Thanks for that, mine was set to Auto, so have now changed it to typical current idle. Is this a known problem in general or specific to the error I posted? I haven't come across it before - googling now.... Thanks.

Wow, just posted and default filter pushes it behind all these other posts that are older. Doesn't give me much visibility does it.

All, while testing out Unraid (haven't paid yet) as a potential replacement for my QNAP's I'm getting the below infrequently, but frequently enough that I won't be able to use this as a NAS / VM or whatever else I need to do if I don't fix it. I have disabled c states and am running latest BIOS 4207 with Agesa 1006. I think it's a soft lockup as the keyboard lights were still on, but actually didn't 100% confirm. I did get a hard lockup the other day, but that was before I disabled c states in the bios. Can anybody help with any ideas / suggestions? If it's a hardware fault, I 'should' be able to return it - I assume the AMD warranties are fairly decent in length. Thanks, tower-diagnostics-20190117-2140.zip