jeffreywhunter

Members
  • Posts

    1064
  • Joined

  • Last visited

Converted

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

Recent Profile Visitors

2662 profile views

jeffreywhunter's Achievements

Collaborator

Collaborator (7/14)

1

Reputation

  1. Latest Unraid (6.9.2), all plugins updated. I'm not sure that I have this utility setup properly, or perhaps I just don't fully understand the outputs. After running through the various functions (Build, Export, Check), I saw a bunch of "bunker: error: no export of file: /mnt/..." errors in the syslog (attached). It seems like its flagging these files? What should I do about these errors? Thanks in advance! hunternas-syslog-20210808-1534.zip
  2. Perhaps it just takes a couple minutes to push the share out. In the time it took me to reread the instructions, then to post my query, the share now shows up and I can access it just like any share on the drive. I had opened a new file explorer (from Win 10) to view the share, but when I went back after posting, the share was there. Thanks again, handy tool.
  3. Love the app, thanks for creating it. Just trying to mount and share the drive to get things started. The drive is shown on main. Its an NTFS drive already formatted. It mounted the drive and i can see it in Main, and click on it to access files/directories. I've gone into settings and turned on SHARE. When I go back into settings I see "Mount Point: 2TB_Scratch_Disk". But I'm not seeing an SMB share available. If I go to http://SERVER/2TB_Scratch_Disk, a blank page displays. I've reread through the instructions in the first post, but must be missing something. Thanks in advance!
  4. Sorry, should have said. Version 6.8.3 2020-03-05. If 6.9 has a new kernel, then perhaps that is the resolution. Is there a way to validate plugin compatibility with 6.9?
  5. I continue to see this error every few minutes. I've researched the problem with the developers of GoodSync and they have identified it as an update needed to the kernel. Is there a formal process to get this reviewed with the UnRaid team? This is what the developer posted as a response: William replied (2020/12/20 01:23 pm EST) I googled it and think they say that you need to update kernel. you can do the same search. You wrote (2020/12/20 12:32 pm EST) Are you aware of a solution or way to suppress the message? William replied (2020/12/20 11:32 am EST) this is a known bug in Linux, has nothing to do with GS Mike replied (2020/12/19 11:30 am EST) Hello, The error you are receiving is related to Linux and not GoodSync. Linux - netlink: 4 bytes leftover after parsing attributes in process You will need to address this with your device directly. Thank you. You wrote (2020/12/19 09:55 am EST) Using Goodsync Connect on Linux. I'm seeing entries in my Linux log (see below). Shows up every 4 minutes. Any idea what it is or how to turn this off? Config issue? Bug? Thanks in advance! ================ example line from LOG DEC 19 08:02:30 HunterNAS bunker: exported 277738 files from /mnt/disk1. Duration: 00:01:27 Dec 19 08:02:40 HunterNAS bunker: exported 408250 files from /mnt/disk11. Duration: 00:01:37 Dec 19 08:05:37 HunterNAS kernel: netlink: 4 bytes leftover after parsing attributes in process gs-server'. Dec 19 08:09:37 HunterNAS kernel: netlink: 4 bytes leftover after parsing attributes in process gs-server'. Dec 19 08:13:37 HunterNAS kernel: netlink: 4 bytes leftover after parsing attributes in process gs-server'. Thanks a bunch. This is one of those things that just fills up the log... I'm not sure of a way to suppress the log entry from the APP.
  6. I guess I'll just watch it. I have 2 parity disks, so if I lose one, no big deal...
  7. 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
  8. Would it help to run the disk through Preclear a couple times?
  9. Apologies, attached! I've not rebooted since the error was displayed. hunternas-diagnostics-20201021-1023.zip
  10. 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
  11. 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!
  12. 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...