Jump to content

jeffreywhunter

Members
  • Content Count

    1026
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jeffreywhunter

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Wisconsin
  • Personal Text
    No place like the open road...

Recent Profile Visitors

940 profile views
  1. Has anyone setup audio books in plex? As I understand from the Plex forums, there is a plugin that interfaces with audiobook.com for metadata, etc. https://forums.plex.tv/t/rel-audiobook-metadata-agent-audible/199579 Does the limetech version have the ability to support that? Trying to figure out how to get a good naming structure that works with plex. Thanks!
  2. I'm see the following error in my log, but no reference to any bad files. BLAKE2 hash key mismatch, is corrupted This was the only entry in the log. Is there somewhere else I need to check? Also, if we do see errors, do we need to reformat the file or just recopy the indicated files? I do see errors on a couple of the other disks with file names indicated. Thanks in advance!
  3. UnRaid didn't see the drive at all. No power light on the drive either. I've assumed either...there's not enough power to support the drive or the drive is bad. I don't have a way to test the drive, so I sent it back. I'll try one more and see what happens... Thanks for the tip on the sector size. Would running a preclear against the drive take care of that?
  4. I'm having problems connecting ST6000NM0034 to an LSI 9207-8i. Prior to purchase I checked with all the vendors to see if this would work (great price on 6TB SAS Drives from Backblaze as they are swapping tech). I spoke with a Seagate pre-sales tech who said I could connect this drive into an LSI 9207-8i and it would work. I spoke with the Icy Dock folks ((https://www.amazon.com/gp/product/B013G4EMH8/ref=oh_aui_search_asin_title?ie=UTF8&psc=1)) who said I could use a SAS drive in the Fat Cage, but it would run single channel only (no big deal - I thought...) I spoke with the Broadcom folks who also confirmed that this configuration should work. Today the drive came and I eagerly inserted it into the Icy Dock Fat Cage just fine. Unfortunately the cage does not recognize the drive is actually in the cage (i.e. no green light). I'm assuming something in this chain isn't as anticipated. I heard from someone that Seagate Enterprise SAS drives can't run in single channel? But I verified with Seagate this configuration and they have verified it should work. The configuration in my server is this: 1. Asus P8V77-V LK 2. LSI 9207-8i Controller card in PCIE x8 port. 2. Icy Dock Fat Cage - see Specifications tab (https://www.icydock.com/goods.php?id=155). Icy Dock has confirmed that I can use SAS drives in their cage. 3. 2 SAS to Sata Cables connected to the Fat Cage from the HBA. 3. Seagate Enterprise Capacity 3.5 HDD| ST6000NM0034 | 6TB 7.2K RPM SAS 12Gb/s 128MB Cache 3.5" | 512n 4. The other drives in the system are SATA. Any thoughts? I suspect its just a bad drive and try again...
  5. Having problems with preclear on 6.6.7. It starts up fine, but a few hours later I come back and its stopped. Screenshot is of the preclear screens/log and the system log. I can't tell what is causing it to stop. Could it just be the disk failing? Seems I'd have a error or something that would tell me... Thanks in advance! hunternas-diagnostics-20190312-0656.zip
  6. Does anyone know of any app or plugin for unraid that will list the details of PCI devices. In particular I'd love to have a quick way to identify the model number of a PCI device (i.e. LSI 9702-8i HBA controller) and a plus would be the serial number for the device. Probably a long shot, but worth asking (or maybe inspiring someone!) Thanks in advance! Jeff...
  7. Latest UR 6.6.5 Parity drive (27000 hours) 5TB Seagate ST5000DM000-1FK178 failed at last poweron with Error 22,23,24,25,26. I'm pretty sure the drive is toast, but wanted to ask in case there's a way to recover the drive (data is backed up). Smart report and syslog attached. Could I try a preclear on it? Thanks in advance for your wisdom... hunternas-smart-20190310-1810.zip hunternas-syslog-20190310-1815.zip
  8. UR 6.5.5. I've been using File Integrity for a long time. No real issues. Today, I received an email notice with the following error displayed. Jan 6 14:58:06 HunterNAS bunker: error: BLAKE2 hash key mismatch, /mnt/disk1/My Backups/_gsdata_/a9ebea1d339a02ae40d547cf8068834d.tib is corrupted Jan 6 14:58:08 HunterNAS bunker: error: BLAKE2 hash key mismatch, /mnt/disk1/My Backups/_gsdata_/3bef27d30a51b20186a922805386f65a.tib is corrupted This happened back in Oct with the same files. Oct 21 15:09:53 HunterNAS bunker: error: BLAKE2 hash key mismatch, /mnt/disk1/My Backups/_gsdata_/a9ebea1d339a02ae40d547cf8068834d.tib is corrupted Oct 21 15:09:54 HunterNAS bunker: error: BLAKE2 hash key mismatch, /mnt/disk1/My Backups/_gsdata_/3bef27d30a51b20186a922805386f65a.tib is corrupted These are backups of one of my workstations. Large file size. Anything to worry about? Diagnostics file attached. Thanks in advance! hunternas-diagnostics-20190106-2330.zip
  9. UnRaid 6.6.5. Just replaced batteries in UPS (APC 1500) with no issue. Before replace, pulled power, held power button on UPS for 10 sec to reset. UPS boots fine. Started UR, disabled UPS Daemon, loaded APC Test, changed battery date, ran calibration, it fails. Here's the sequence. 1. Power down UR, power down UPS, pull plug on UPS, replace batteries, reset UPS (power button for 10 sec). 2. Loaded up APCTEST, reset battery date. Success. Select function number: 4 Current battery date: 05/10/2015 Enter new battery date (MM/DD/YYYY), blank to quit: 01/05/2019 Writing new date...SUCCESS Waiting for change to take effect...SUCCESS Current battery date: 01/05/2019 3. So I know I'm talking to the UPS just fine. Then I run a battery calibration - it fails with "NO TEST PERFORMED": Select function number: 10 This test instructs the UPS to perform a battery calibration operation and reports the result when the process completes. The battery level must be at 100% and the load must be at least 10% to begin this test. Battery level is 100% -- OK Load level is 16% -- OK Clearing previous self test result...CLEARED The battery calibration should automatically end when the battery level drops below about 25%. This process can take minutes or hours, depending on the size of your UPS and the load attached. Initiating battery calibration...INITIATED Waiting for calibration to complete... To abort the calibration, press ENTER. CALIBRATION COMPLETED Result of last self test: NO TEST PERFORMED 4. Hmmm...then I ran Self-Test. That fails with "TEST DID NOT COMPLETE": Select function number: 2 This test instructs the UPS to perform a self-test operation and reports the result when the test completes. Clearing previous self test result...CLEARED Initiating self test...INITIATED Waiting for test to complete...TEST DID NOT COMPLETE I've run out of diagnostics. I've looked through APC and UR forums for these errors, but not seen any applicable solution. Thoughts O wise one? Thanks in advance! jeff...
  10. I've upgraded to the latest unRaid 6.6.5. Upon doing so, I've noticed a warning in the Boot Device section of the Main. It says that I have the flash drive setup with a public share. I've looked in the share area but don't see any shares using the flash drive. What am I missing? Screenshot of the error... http://my.jetscreenshot.com/12412/20181208-3ke9-118kb.jpg Thanks! Jeff...
  11. Interesting. If the array is online, its recreates the movies.cfg file immediately. And it creates it blank (i.e. no settings). Turns out the problem was with a share I setup. Not sure how this started failing, as its been this way for over a year, but I had a share setup with /home movies. In the path it looks like \mnt\user\home/ movies. It appears that it was having problems using that path. Changed to /homemovies and \mnet\user\homemovies and its working fine.
  12. I've never actually deleted a share I wanted to keep. This the proper approach? 1. Document the disks connected to the share. 2. Uncheck the disks from the share. 3. Delete the share. 4. Check the appropriate disks. Try to recreate the docker?