Krzaku

Members
  • Content count

    36
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Krzaku

  • Rank
    Advanced Member
  1. This is primarily useful for Seagate drives which sometimes use the lower 32 bits of the SMART value to indicate the total number of events that could lead to an error (eg. total number of reads etc.), and the upper 16 bits to store the actual error value. This is already supported by smartctl, but needs to be configured using the "-v" option. The way you use this option is by setting which octets of a value are actually read, and so, setting it to "-v 1,raw48:543210" would read the whole 48 bits, but setting it to "-v 1,raw48:54" would only read the upper 16 bits, which is the error value we want. My request is to implement support for this "-v" option on the SMART display screen, so we can get actually useful SMART error notifications for these drives.
  2. I just bought a couple of those to add to my array. They seem to be working fine however I just noticed that the Load Cycle Count is pretty high, over 400 in 1 week of usage. This is almost 8x higher than my Ironwolf 3 TB drives did in almost a year of usage. They supposedly are rated for LCC values of 600000 but it still is disconcerting. I have disabled drive spin-down however I also noticed that the 8 TB drive does not support APM (nothing comes up in hdparm) while the 3 TB does so I'm not entirely sure if it respects this setting (the indicator light on the WebUI is always green though). I also have very high G-Sense Error Rates (2000-3000) however this seem to be a very common issue and does not SEEM to affect anything. All this makes me wonder if this isn't just another flop like the old ST3000DM001 were. Does anyone use these drive and can share what their smart values are?
  3. Dynamix File Integrity plugin

    @bonienl First of all, thanks for this plugin. I'm using it on my array and it's working fine with one exception: it has trouble checking hashes of my EncFS directory. When the verify task finishes I always get some hash mismatches on the encrypted files and I'm sure the decrypted files are fine. This might not even have anything to do with this plugin, but have you encountered something like this?
  4. As in the title. Though I wish my disks would read at an average rate of 275 MB/s, this is only a visual error. The average speed is probably calculated at the time it is shown using current parity drive size and not saved after parity check finishes.
  5. Parity swap procedure clarification

    Thanks. I hope all goes well when I'll be replacing my drives.
  6. Parity swap procedure clarification

    Is there a speed difference when copying the parity data as opposed to calculating it from scratch?
  7. I've read this parity swap procedure on the wiki: https://lime-technology.com/wiki/The_parity_swap_procedure Correct me if I'm wrong, but doesn't this mean that during the procedure the array is entirely without protection? Meaning if any of the drive fails, I lose all the contents of parity, the failed drive and the drive I was replacing. Wouldn't it be safer to first fully replace the parity (having the old parity as backup to put back in, in case something goes wrong), and only after it was replaced successfully I would replace the smaller data drive with the old parity drive?
  8. Yes, they haven't released an update. I even contacted them and they said an update was in the works, but that was 3 months ago so I'm not holding my breath. The board is Asrock C236M WS.
  9. In my opinion there should be something like this included by default in unRAID. Crashes sometimes are unpredictable, and if a system crashes for a user, enabling the logging after that might not do that much good because the crash may not even happen for another few months. I had a system crash on me twice (luckily no data was lost), after that I enabled logging, and what do you know, it never crashed after that... To this day I don't know for sure what caused the crashes.
  10. Can we please get this included? It's been 4 months.
  11. Preclear plugin

    Not sure if this was reported already, but when updating this plugin I get no button to close the update dialog as with all the other plugins I update.
  12. [Support] Gitea

    /usr/bin/docker: Error response from daemon: manifest for fanningert/gitea:latest not found. Your docker hub doesn't seem to have any releases present.
  13. How to adjust theme width?

    Like I said, it's more important for users of UW monitors. 16:9 monitors (which WQHD is) usually don't have 35 inch screen sizes, while for UW monitors it's something normal.
  14. How to adjust theme width?

    I can, but honestly, who resizes their browser window. We all just maximize it, am I right? I added a patch to /boot/config/go that changes the max-width in the css file to 1200px and that works for me. But I think anyone who uses an ultra wide monitor will agree with me that 1200px (or thereabouts) should be the default. We may have super wide monitors, but it's no fun to move your head around so much.
  15. How to adjust theme width?

    @limetech Ok, in the latest update it's better, but I think 1920px width is still too high. I found 1200px to be the sweet spot.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.