BVD

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About BVD

  • Rank
    Member

Converted

  • URL
    vandyke.tech
  1. I don't think this is under active development - I send at least 20 crash reports to them, and never got a single update the entire time. Seems like it's a dead product at this point.
  2. Interesting... My drives weren't acknowledging the spindown requests, and I figured maybe it was their OEM firmware requiring specific/unique fields. I'd prefer to stick with the plugin so I have a single source of control for drives spindown across the array of course - I'll do some further tinkering to validate whether this is drive or config specific (I've hacked up the crap out of this thing lol), and if it's drive related, update the plugin thread with details. Thanks!
  3. As a heads up, it looks like the plugin doesn't first enable spindown on the drive (in order to allow the feature to be made active and place into standby, then bring them back out, some [well, all 27 of mine at least] drives simply won't acknowledge the spindown request until set to enabled). The command used to enable is mentioned earlier in the thread, but I guess it didn't make it in, or maybe isn't applying equally to all drives? sdparm --flexible -6 -l --set SCT=54000 --set STANDBY=1 /dev/sdWhatever Drives now spin down properly - confirmed both via command, and thankfully
  4. While it'd be great to have built in support, I'm guessing that in efforts to maintain as streamlined a kernel as possible, it's inclusion is unlikely. There are a couple options I'd guess - 1. Request support for RDMA via plugin creation here: https://forums.unraid.net/forum/60-plugin-system/ 2. Simply manually install the driver from the slackware repo / compile a custom kernel with the drivers baked in. I messed around a bit with slackware+IB a while back, and while it's really very interesting, the only people who I believe really 'need' it would likely also b
  5. BVD

    Hotio v CA

    The docker image is under pretty heavy (and needed) development at this point. I've been working with the dev a bit via his github page, trying to get him the information he needs to make the tool a bit more reliable. He's working hard at it, but it still needs some polish before it's ready for primetime IMO.
  6. I really liked the fundamental idea behind Scrutiny, but I don't think it's really ready for primetime yet - the UI kept reporting duplicates for SAS devices (I'm guessing it doesn't understand dual port connections, scanning the scsi bus or something?), and that's only when I could actually get the web UI to do anything other than show the spectacles with the loading dots. Could we perhaps get this marked as a beta or something? I really like the basic idea, it just needs some polish before I think it could be considered fully fledged.
  7. ____ I've just had the same issue on my first time running it - I reran it to see what went wrong, but mine only took something like 45 minutes or so across. Seems to happen when a significant amount of dupes are found and you close out the findings without taking any action initially (at least in my case).
  8. They won’t be able to help you recover the lost data - but with the license, just rerun the installer on the same thumb drive and you should be able to boot. As long as the WWN of the thumb drive hasn’t changed, your license should be fine. Then just follow the information the rest have provided here regarding getting back up and operational.
  9. Oh man... well, in theory the usb WWN should be consistent, so remaking the bootable drive will keep your license. In reality though, some USB drives (the cheap crap I’ve played with at least) don’t provide consistent WWNs - as crazy as that sounds to me coming from enterprise storage land, I saw it with my own eyes or I wouldn’t have believed it. Other than the license (which doesn’t matter if you’re just trialing), yeah, you’re starting from scratch. The drive gets very little in the way of writes, but when writes to the drive do occur, they’re important - configuration files, any
  10. That’s what I’m saying - even if it was automated through the app, you’d have to expose the server to the internet in some way to do so. VPN is the way to go.
  11. While I wouldn’t try it myself, I’d imagine you could do this by forwarding 443 out to your ddns, then accessing it from the app by putting in the domain you’ve set up for it (just as you would with your others, server.domain.com) instead of your local IP. My own .02 though, feels like a bad idea, exposing your entire server, the full kernel I mean, to the outside world without a VPN, API key or no.
  12. You’re right - I completely neglected that! Apologies for the false alarm!
  13. It looks like the most recent update broke the ability to change the sort method used to list out apps for a given category (sort by name, popularity, etc) - Running Chrome (latest), tested in incognito mode as well to mitigate potential for issues with chrome plugins/cache/etc. Anyone else experiencing this as well? Wondering if it's something localized to my system/config, or just an issue with the plugin itself.
  14. I actually still plan to use the unraid array down the line, I’m just not quite there yet - I’ve got about 30 drives laying around, from some old savvios up to a stack of 2TB nearline sas that I never put into full use... the idea was that I’d eventually throw them in this old supermicro chassis I’ve been had gathering dust in the basement for some time now. Ideally I’d like to handle everything under one OS. I guess if Ubuntu is the way to go, I may as well get moving on it. I was just hoping to find out a little more detail on where Unraid was thinking zfs support was headed for
  15. Another option instead of (though that works as well) - go over to nerd pack, and manually re-enable/re-install pigz (or just manually pull it from the slackware repo). I'm not super familiar with the plugin architecture, but if it allows you to do some checking/recording of packages it that it needed which were already available pre-install, that'd be cool... But then the nightmare of dependencies (i.e. what if they uninstall in a different order than install and leave behind components unintentionally) could be a freakin nightmare...