Jump to content

jeffreywhunter

Members
  • Content Count

    1059
  • 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

1903 profile views
  1. I guess I'll just watch it. I have 2 parity disks, so if I lose one, no big deal...
  2. Duh, now that you put it that way... I ran an extended test last night. HE is at 100? How is that possible? 22 Helium level 0x0023 100 100 025 Pre-fail Always Never 100
  3. Would it help to run the disk through Preclear a couple times?
  4. Apologies, attached! I've not rebooted since the error was displayed. hunternas-diagnostics-20201021-1023.zip
  5. I've had FCP identify a problem with my primary parity drive. Upon investigation, I don't see any errors in the SMART report (see attached). Any ideas what FCP has identified? ERRORS FOUND SUGGESTED FIX parity (HGST_HUS726060ALA640_AR11021EHJAHKB) has read errors If the disk has not been disabled, then unRaid has successfully rewritten the contents of the offending sectors back to the hard drive. It would be a good idea to look at the S.M.A.R.T. Attributes for the drive in question Begin Investigation Here: Parity Settings According to the disk information in Parity Settings there are no problems (Failed = Never). Attributes # ATTRIBUTE NAME FLAG VALUE WORST THRESHOLD TYPE UPDATED FAILED RAW VALUE 1 Raw read error rate 0x000b 100 100 016 Pre-fail Always Never 0 2 Throughput performance 0x0005 131 131 054 Pre-fail Offline Never 87 3 Spin up time 0x0007 200 200 024 Pre-fail Always Never 493 (average 507) 4 Start stop count 0x0012 100 100 000 Old age Always Never 75 5 Reallocated sector count 0x0033 100 100 005 Pre-fail Always Never 0 7 Seek error rate 0x000b 100 100 067 Pre-fail Always Never 0 8 Seek time performance 0x0005 130 130 020 Pre-fail Offline Never 12 9 Power on hours 0x0012 094 094 000 Old age Always Never 42086 (4y, 9m, 18d, 14h) 10 Spin retry count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 35 22 Helium level 0x0023 083 083 025 Pre-fail Always Never 83 192 Power-off retract count 0x0032 080 080 000 Old age Always Never 25085 193 Load cycle count 0x0012 080 080 000 Old age Always Never 25085 194 Temperature celsius 0x0002 176 176 000 Old age Always Never 34 (min/max 17/47) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 0 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 200 200 000 Old age Always Never 0 I've run SMART long version with nothing reported. Thoughts? hunternas-smart-20201020-1422.zip
  6. I've been adding more and more drives to my system. Today I received the below status message and it stated [FAIL], but I had to search the list three or four times to find NOK. I'd like to make a suggestion for improvement of this email. Where would be the appropriate place for that? Did a search for suggestions, but didn't find anything. I'd like to suggest a simple carriage return be placed after each disk report. Also, putting the [OK] or [NOK] or [WHATEVER OTHER STATUS] at the beginning would make it easy to scan and find the offending drive. Something like this... Event: Unraid Status Subject: Notice [HUNTERNAS] - array health report [FAIL] Description: Array has 14 disks (including parity & cache) Importance: warning [OK] - Parity - HGST_HUS726060ALA640_AR11021EHJAHKB (sdc) - active 39 C [OK] - Parity2 - HGST_HUS726060ALA640_AR31021EHUX5HC (sdd) - active 42 C [OK] - Disk 1 - ST4000DM000-1F2168_W30086L5 (sdm) - active 42 C [OK] - Disk 2 - Hitachi_HDS5C3020ALA632_ML0220F31HKTDN (sde) - standby [OK] - Disk 3 - HGST_HUS726060ALA640_AR11001EV14M3B (sdf) - active 40 C [OK] - Disk 4 - Hitachi_HDS5C3020ALA632_ML0220F30MWAYD (sdg) - active 40 C [OK] - Disk 5 - HGST_HUS726060ALA640_AR31051EJSYX2J (sdh) - active 42 C [OK] - Disk 6 - Hitachi_HUA723030ALA640_MK0371YVG9PYUA (sdk) - active 46 C [OK] - Disk 7 - Hitachi_HDS5C3020ALA632_ML0220F30YS4XD (sdl) - standby [OK] - Disk 8 - Hitachi_HUA723030ALA640_MK0373YVHH0A4C (sdi) - active 46 C [NOK] - Disk 9 - Hitachi_HUA723030ALA640_MK0361YHJ0N8JD (sdj) - active 48 C (disk is hot) [OK] - Disk 10 - Hitachi_HDS5C3020ALA632_ML0220F311GHND (sdo) - standby [OK] - Disk 11 - HGST_HUS726060ALA640_AR31051EJU87UJ (sdn) - active 42 C [OK] - Cache - Samsung_SSD_850_EVO_500GB_S2RANX0H811137T (sdb) - active 34 C Parity check in progress. Total size: 6 TB Elapsed time: 7 hours, 5 minutes Current position: 2.48 TB (41.4 %) Estimated speed: 100.0 MB/sec Estimated finish: 9 hours, 46 minutes Sync errors detected: 0 Much easier to read than this... Event: Unraid Status Subject: Notice [HUNTERNAS] - array health report [FAIL] Description: Array has 14 disks (including parity & cache) Importance: warning Parity - HGST_HUS726060ALA640_AR11021EHJAHKB (sdc) - active 39 C [OK] Parity2 - HGST_HUS726060ALA640_AR31021EHUX5HC (sdd) - active 42 C [OK] Disk 1 - ST4000DM000-1F2168_W30086L5 (sdm) - active 42 C [OK] Disk 2 - Hitachi_HDS5C3020ALA632_ML0220F31HKTDN (sde) - standby [OK] Disk 3 - HGST_HUS726060ALA640_AR11001EV14M3B (sdf) - active 40 C [OK] Disk 4 - Hitachi_HDS5C3020ALA632_ML0220F30MWAYD (sdg) - active 40 C [OK] Disk 5 - HGST_HUS726060ALA640_AR31051EJSYX2J (sdh) - active 42 C [OK] Disk 6 - Hitachi_HUA723030ALA640_MK0371YVG9PYUA (sdk) - active 46 C [OK] Disk 7 - Hitachi_HDS5C3020ALA632_ML0220F30YS4XD (sdl) - standby [OK] Disk 8 - Hitachi_HUA723030ALA640_MK0373YVHH0A4C (sdi) - active 46 C [OK] Disk 9 - Hitachi_HUA723030ALA640_MK0361YHJ0N8JD (sdj) - active 48 C (disk is hot) [NOK] Disk 10 - Hitachi_HDS5C3020ALA632_ML0220F311GHND (sdo) - standby [OK] Disk 11 - HGST_HUS726060ALA640_AR31051EJU87UJ (sdn) - active 42 C [OK] Cache - Samsung_SSD_850_EVO_500GB_S2RANX0H811137T (sdb) - active 34 C [OK] Parity check in progress. Total size: 6 TB Elapsed time: 7 hours, 5 minutes Current position: 2.48 TB (41.4 %) Estimated speed: 100.0 MB/sec Estimated finish: 9 hours, 46 minutes Sync errors detected: 0 Thanks!
  7. Thanks ChatNoir, but the problem I have is that none of the disks or devices on the system appear to be available. There's nothing in /MNT and then there's the errors I saw regarding enumerating the boot USB. When the computer boots, it sees all the devices (i.e. I see the BIOS messages that the drives load, and I can see them in the BIOS if I boot to BIOS, BUT...when unRaid boots, it can't find the USB drive (BOOT) and thus nothing loads. I have no idea where the unRaid OS is actually loading from. Quite puzzling...
  8. Any thoughts on how to get the diagnostics off this 'netherworld' boot drive?
  9. Ok, so had the machine turned off since Friday waiting for response to my query. Turned it on and when it came up it said TOWER vs the name I've given it - HunterNAS. No drives available and nothing but basic OS. Rebooted again and watched it boot. LOTS of errors. I tried to capture the info as it booted (see attached screenshots). In the second screenshot, there's an error which said "unable to enumerate USB device", then it booted to Tower and not my server name "HunterNAS". For some reason, unRaid isn't finding the USB or any of the drives on the controller. Could not access the flash at /BOOT. CD /BOOT displays only a /CONFIG directory (The OS must be residing in memory?). Ran diagnostics and it ran said it created the file on /boot/logs, but the file isn't there since it could not enumerate the USB device. The motherboard sees the hard drives, perhaps there's a problem with the USB stick? I've put the stick in my Win10 computer, and can see the files with no issues. I have a backup of the flash, should I reinstall unRaid?
  10. Bump. Any ideas? I'm stuck with a boat anchor...
  11. Latest version of Unraid. Server has worked fine for years. Tried to access server and it was locked (non response via console). Hard Reboot. Now have console access, but unable to load WebGUI. Can ping server, but no shares are visible from Windows File Manager I shutdown from console, syslog attached. I see sever errors about unable to communicate with github, openvpn server not started (installed but not yet configured), but don't see anything else. I also have a problem with GS-Server and the 4 bytes leftover issue, I have been working with the developer to get the new version which solves that issue, but this problem came up, so I'm stuck at the moment. In the \logs directory, I see the hunternas-diagnostics-20200911-1752.zip and syslog.zip files, but they are 0 bytes. I didn't see any errors with WebGUI loading. Confused. What could be the issue? Syslog attached. Your wisdom is appreciated... Jeff... syslog-20200911-175203.txt
  12. So you've successfully updated by manually uninstalling the Docker and Reinstalling from scratch (plus adding the new container path)?