jderby6119

Members
  • Posts

    7
  • Joined

  • Last visited

jderby6119's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. About a day or 2 ago one of my disk started showing as disabled in the array and when i look at the disk log no errors are showing. I've restarted array, restarted the host, unplug and replugged the hard drive and still its coming up a disabled. The diagonstic log for the disk is below: smartctl 7.1 2019-12-30 r5022 [x86_64-linux-4.19.107-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Blue Device Model: WDC WD5000AAKX-60U6AA0 Serial Number: WD-WCC2EFD79463 LU WWN Device Id: 5 0014ee 25ddabd84 Firmware Version: 18.01H18 User Capacity: 500,107,862,016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Apr 29 07:58:51 2020 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, NOT FROZEN [SEC1] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x05) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 9060) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 92) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1 3 Spin_Up_Time POS--K 157 136 021 - 3150 4 Start_Stop_Count -O--CK 094 094 000 - 6947 5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0 7 Seek_Error_Rate POSR-K 200 200 051 - 0 9 Power_On_Hours -O--CK 073 073 000 - 20036 10 Spin_Retry_Count PO--CK 100 100 051 - 0 11 Calibration_Retry_Count -O--CK 100 100 000 - 0 12 Power_Cycle_Count -O--CK 099 099 000 - 1989 184 End-to-End_Error PO--CK 100 100 097 - 0 187 Reported_Uncorrect -O--CK 100 096 000 - 4 188 Command_Timeout -O--CK 100 099 000 - 4295032833 190 Airflow_Temperature_Cel -O---K 070 060 040 - 30 (Min/Max 28/33) 192 Power-Off_Retract_Count -O--CK 200 200 000 - 124 193 Load_Cycle_Count -O--CK 198 198 000 - 6822 196 Reallocated_Event_Count -O--CK 200 200 000 - 0 197 Current_Pending_Sector -O--CK 200 200 000 - 0 198 Offline_Uncorrectable ----CK 200 200 000 - 0 199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0 200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 5 Comprehensive SMART error log 0x03 GPL R/O 6 Ext. Comprehensive SMART error log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa0-0xa7 GPL,SL VS 16 Device vendor specific log 0xa8-0xb5 GPL,SL VS 1 Device vendor specific log 0xb6 GPL VS 1 Device vendor specific log 0xb7 GPL,SL VS 1 Device vendor specific log 0xbd GPL,SL VS 1 Device vendor specific log 0xc0 GPL,SL VS 1 Device vendor specific log 0xc1 GPL VS 24 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 4 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 4 [3] occurred at disk power-on lifetime: 19546 hours (814 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 00 00 00 07 8f 34 a8 40 00 Error: IDNF at LBA = 0x078f34a8 = 126825640 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 02 d0 00 48 00 00 07 8f 43 50 40 08 20:54:50.021 WRITE FPDMA QUEUED 61 02 18 00 40 00 00 07 8f 41 38 40 08 20:54:50.016 WRITE FPDMA QUEUED 61 05 40 00 38 00 00 07 8f 3b f8 40 08 20:54:50.016 WRITE FPDMA QUEUED 61 02 10 00 30 00 00 07 8f 39 e8 40 08 20:54:50.011 WRITE FPDMA QUEUED 61 05 40 00 28 00 00 07 8f 34 a8 40 08 20:54:50.006 WRITE FPDMA QUEUED Error 3 [2] occurred at disk power-on lifetime: 19546 hours (814 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 00 00 00 07 8b 7f 28 40 00 Error: IDNF at LBA = 0x078b7f28 = 126582568 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 80 00 30 00 00 07 8b 8d 30 40 08 20:54:18.011 WRITE FPDMA QUEUED 61 05 40 00 28 00 00 07 8b 87 f0 40 08 20:54:18.011 WRITE FPDMA QUEUED 61 03 88 00 20 00 00 07 8b 84 68 40 08 20:54:18.009 WRITE FPDMA QUEUED 61 05 40 00 18 00 00 07 8b 7f 28 40 08 20:54:18.009 WRITE FPDMA QUEUED 61 05 40 00 10 00 00 07 8b 79 e8 40 08 20:54:18.009 WRITE FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 19546 hours (814 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 00 00 00 04 ed ff d0 40 00 Error: IDNF at LBA = 0x04edffd0 = 82706384 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 00 b8 00 d0 00 00 04 ed ff d0 40 08 20:50:22.536 WRITE FPDMA QUEUED 61 00 70 00 c8 00 00 04 ed ff 60 40 08 20:50:22.536 WRITE FPDMA QUEUED 61 05 40 00 c0 00 00 04 ed fa 20 40 08 20:50:22.532 WRITE FPDMA QUEUED 61 05 40 00 b8 00 00 04 ed f4 e0 40 08 20:50:22.527 WRITE FPDMA QUEUED 61 05 08 00 b0 00 00 04 ed ef d8 40 08 20:50:22.521 WRITE FPDMA QUEUED Error 1 [0] occurred at disk power-on lifetime: 19546 hours (814 days + 10 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 10 -- 51 00 00 00 00 01 ff 25 50 40 00 Error: IDNF at LBA = 0x01ff2550 = 33498448 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 61 05 30 00 08 00 00 01 ff 2a e0 40 08 20:46:02.281 WRITE FPDMA QUEUED 61 00 50 00 00 00 00 01 ff 2a 90 40 08 20:46:02.275 WRITE FPDMA QUEUED 61 05 40 00 f0 00 00 01 ff 25 50 40 08 20:46:02.275 WRITE FPDMA QUEUED 61 05 30 00 e8 00 00 01 ff 20 20 40 08 20:46:02.269 WRITE FPDMA QUEUED 61 05 40 00 e0 00 00 01 ff 1a e0 40 08 20:46:02.264 WRITE FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 20019 - # 2 Short offline Completed without error 00% 11099 - # 3 Short offline Completed without error 00% 9976 - # 4 Short offline Aborted by host 90% 9953 - # 5 Short offline Completed without error 00% 9950 - # 6 Extended offline Interrupted (host reset) 90% 1 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) Device State: Active (0) Current Temperature: 30 Celsius Power Cycle Min/Max Temperature: 28/33 Celsius Lifetime Min/Max Temperature: 0/40 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 128 (65) Index Estimated Time Temperature Celsius 66 2020-04-29 05:51 30 *********** ... ..(126 skipped). .. *********** 65 2020-04-29 07:58 30 *********** SCT Error Recovery Control: Read: 85 (8.5 seconds) Write: 85 (8.5 seconds) Device Statistics (GP/SMART Log 0x04) not supported Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x000a 2 3 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x8000 4 68274 Vendor specific
  2. So i tried Plex out on my movie share and it didnt work out the way i wanted so i went with jellyfin. During having plex as a docker in unraid i had one of the moview optimzed for plex and it created a folder with a file in it. Well i got rid of the plex docker but now when i go into the windows share i cant delete the file because it says the user "nobody" is the only one with permissions to do so. you require permission from my server\nobody to make any changes. HOW DO I DELETE THIS FOLDER/FILE?
  3. Ok after hamster did a few laps around its wheel in my head i realize the issue unraid is showing TB and Microsoft is showing TiB even though its has the correct bytes amount. for me though it doesnt explain why on my drive 1 it shows 124GB used but when i look at the actual data stored on the drive its only less than 60gb. Where is the 124GB total amount used from if not from the data i have stored on the network share drive?
  4. so i Microsoft displaying in TB and not TiB hence the smaller drive size display? Then even furthur why does not unraid display it as TiB instead as to not cause confusion.
  5. Im having a issue with the size of my array and the size showing up on my SMB network sharing being reported. When i run compute size in unraid its showing less space available than actually whats being used.