Jump to content

dnLL

Members
  • Content Count

    92
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dnLL

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Has anyone updated to 6.7.1 or 6.7.2 and can confirm that this still works properly for the new zombieland vulnerability? I assume everything is fine looking at cybrnook's post.
  2. Honestly, getting 2 or 3% on average is already a lot in my book and enough to bother. People overclock and sometimes stress their components a lot for barely more than that. Getting more than that in some specific scenarios is just a nice bonus.
  3. So what advantage does the plugin provide over a simple parity check overall other than performance-related issues? Does bitrot still happen in modern system or is it something that should be disregarded altogether? The reason I started worrying about it is my friend lost some JPG files recently due to this, had to recover from a backup and he's been using unRAID for a while. He does have a lot of old hard drives however and old hardware in general so that may be an issue that I'm not really facing as much.
  4. I'm no expert (so no, I'm not sure about this) but from my understanding, since you have at least 1 parity disk which has each bit set to the sum of the corresponding bits on all the other disks, if one disk is corrupted, some bits won't add up anymore, thus creating parity check issues. I thought it would be easy to repair then. But I'm probably wrong, I just need someone with better knowledge about this to explain it. With RAID5 it's different, the parity is stripped across all disks. So if you lose a disk, you definitely lose some data and some parity, but you can recover with your stripped parity and data from the other disks.
  5. Good to know. I do have ECC memory installed. What is the purpose of the file integrity plugin then if it just shouldn't happen anymore?
  6. Yes and that's fine but SSDs are not slower when they're part of the cache instead of unassigned I would assume, unless BTRFS makes them slower than xfs somehow.
  7. This might be off topic a little bit but are you suggesting Plex is faster on an unassigned SSD than on a SSD cache? I just want to make sure that I'm not missing out on something crazy, I have a RAID1 cache SSD and did notice an improvement over HDDs but if it's faster completely outside the array/cache...
  8. Hi, First of all, I want to thank everyone in this community working on making unRAID such an awesome product. I just had a disk fail on me 2 days ago and I swapped it for a brand new one with almost no downtime at all, the GUI made me feel safe during the whole process of rebuilding the disk from parity and I really appreciate knowing my data is very safe in the future (with backups too just in case ;-)). My question is regarding silent data corruption, also known as bit-rot. I've read a little bit about it on the unRAID forums and over r/unraid on Reddit and did notice the existence of the Dynamix File Integrity plugin below. However, while this plugin, well configured, will help me detecting any potential issue, it doesn't fix the issues. Two years ago, someone was asking a similar question (https://www.reddit.com/r/DataHoarder/comments/537ys9/unraid_users_how_do_you_handle_disk_encryption/), and I see comments saying the devs at LT were considering adding some sort of protection against bit-rot, because if well integrated it could be fixed on-the-fly thanks to the parity disks. Years later I don't see many discussions regarding this and I'm sure it's an important subject to a lot of us data hoarders. Am I missing something or do we still have in 2019 to address this issue completely manually (ie. by restoring backups when it happens and hope the backup isn't corrupted and is up-to-date enough)? If there is anything about this coming soon in unRAID that I'm unaware of, I'd definitely like to hear about it!
  9. I'm also interested in this question since most motherboard manufacturers have provided updated version of their BIOS following Spectre. If it's at the motherboard level then how can the OS interact with this? There is definitely a detail we're missing here.
  10. well somehow sr0, sda, sdb and sdc weren't counted in this specific case.
  11. Really, floppy and optical drives count? I'm lucky I don't have old hardware, that would be a huge issue lol. I mean if you add the BMC virtual medias you can have 5 or 6 completely empty media drives...
  12. I've never seen a keyboard be counted as a device when it comes down to unRAID licensing. I have the basic license with 6 HDD and it wasn't an issue despite the 3 "Unknown USB devices" identified as sda, sdb and sdc.
  13. They're not part of the array, so no.
  14. It's probably just relevant to my OCD ;-). And obviously because I'm monitoring my VMs with check_mk, it doesn't really like the letter change.
  15. You are actually 100% right. Seems like the floppy was indeed created by the BMC setting but the 2 other USB peripherals were me on the IPMI console. Heh... well, the problem is now solved, thank you. It's basically a mixed of the 2. I wasn't connected to the console when I did a reboot earlier... then the issue was there so I went into the BIOS through the console and just made it worst by staying on the console while rebooting couple more times. Then I found the virtual media settings on the BMC which made one of the 3 drives disappear permanently but the 2 other ones would stay. After I closed the console they both disappeared. I wonder if unRAID could handle this differently a little bit, like prioritize hard drives over USB devices when it comes to device assignment (except maybe for the boot drive which is sda). It would solve most possible issues.