jbartlett

Community Developer
  • Posts

    1714
  • Joined

  • Last visited

  • Days Won

    7

jbartlett last won the day on August 6 2019

jbartlett had the most liked content!

2 Followers

About jbartlett

  • Birthday 07/20/1970

Retained

  • Member Title
    John Bartlett

Converted

  • Gender
    Male
  • URL
    https://www.youtube.com/c/TheCritterRoom/
  • Location
    Seattle, WA
  • Personal Text
    Foster parent for cats & kittens

Recent Profile Visitors

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

jbartlett's Achievements

Community Regular

Community Regular (8/14)

216

Reputation

  1. Gotcha - I thought this was the built in functionality, I'll report it on the Mover Tuning plugin thread.
  2. The way it reads to me is to collapse multiple underscores such as "drive______id" to "drive_id". Just stating this because that's not what is actually happening - it's converting multiple underscores into spaces but leaving the last underscore.
  3. [rc6] Changing root user password will log out all webGUI browser sessions. I changed the password of user "jess" and I was logged out of the webGUI. Based on the change log, I should remain logged in. nas-diagnostics-20220512-1951.zip
  4. I think I figured out what happened. In the Historical section, it lists: Samsung_SSD_960_EVO_500GB_S3X4NB0K309824V (Samsung_960EVO) In the UD list, it has: Samsung SSD 960 EVO 500GB_S3X4NB0K309824V + 1: Samsung_960EVO It looks like rc8 removed the underscores from the drive ID so it didn't find a match and created it as if it was new.
  5. I updated all plugins and then upgraded from 6.9.2 to 6.10.0-rc8. The partition names identified by UD changed back to the default serial number and not the value I had set previously and the 6.9.2 version was listed in the "Historical Devices" section. Reverting back to 6.9.2 restored the partition name. Under 6.9.2: Samsung_SSD_960_EVO_500GB_S3X4NB0K309824V (Samsung_960EVO) Once I renamed the partition back to "Samsung_960EVO", it fixed the mounting location so my VM's could be located again. nas-diagnostics-20220511-2047 (rc8).zip nas-diagnostics-20220511-2052 (6.9.2).zip
  6. Make sure your antivirus, Acronis Home, etc are disabled and ensure you have the prompt to run as Admin show up.
  7. I kept getting data corruption and missing files and a parity sync kept reporting errors if I wait a few days after the last parity check. I managed to isolate it to one drive I swapped it out and did a parity rebuild but the issue persisted so I assumed a corrupted XFS. I was using this utility to help track corruptions and it was a clear benefit there. It seemed that removing all files fixed whatever corruption was happening, had no issues even after filling up the drive with large NULL files in the event I needed to 7zip the drive up to give someone to check but it never failed in the next month. Since I needed to reformat, I decided to switch to btrfs to use it's own built in scrub for bitrot, and I was thinking of taking advantage of btrfs features.
  8. One thing to note is that the memtest86 that comes with UNRAID is an old version* - if you want the most recent, you have to download it from https://www.memtest86.com/ and create your own boot flash. Note that this version restriction placed by memtest86. * At least this was the case the last time I used the tool, YMMV
  9. I've been pondering software KVM's off & on and looked into Barrier. It strikes me that if you create a VM running Windows or Unix, you can use that as your Barrier host.
  10. Sometime last week, I set my Validation scheduled to weekly on Sunday. Disk 1 kicked off and completed but none of the others did. I'm also wondering how does the Task function work. You can set up One drive per Task which seems the logical choice but you can also assign multiple drives to a single Task. What exactly *is* as "Task" in this case? It seems like a single thread that will do stuff. There's no built-in help around it.
  11. When ever I tried to schedule one to kick off daily in 15 minutes, it's only ever kicked off the check for Drive 3. It finished and nothing else started. *shrug*
  12. A workaround is to export the drive and then check the export on that drive.