publicENEMY

Members
  • Content count

    247
  • Joined

  • Last visited

Community Reputation

0 Neutral

About publicENEMY

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. I have this error when i want to install koel docker Error: failed to register layer: ApplyLayer exit status 1 stdout: stderr: write /opt/koel/node_modules/express/node_modules/debug/node.js: no space left on device What should I do? Thanks.
  2. Can somebody tells me what this means? What should I do? Its an external drive mount with unassigned device
  3. This are the smart error log. However, the last smart result are Completed without error. Should I be worried? smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD30EZRX-00DC0B0 Serial Number: WD-WMC1T3153031 LU WWN Device Id: 5 0014ee 6589b20e4 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Dec 27 17:06:14 2016 SGT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: (38940) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 391) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x70b5) SCT Status 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 7726 3 Spin_Up_Time 0x0027 181 178 021 Pre-fail Always - 5950 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2243 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 1 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 061 061 000 Old_age Always - 28945 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 145 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 45 193 Load_Cycle_Count 0x0032 032 032 000 Old_age Always - 506970 194 Temperature_Celsius 0x0022 108 089 000 Old_age Always - 42 196 Reallocated_Event_Count 0x0032 199 199 000 Old_age Always - 1 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 6 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 194 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 58 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] 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 58 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 d0 f9 c2 e6 Error: UNC 8 sectors at LBA = 0x06c2f9d0 = 113441232 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 d0 f9 c2 e6 08 3d+23:34:29.854 READ DMA c8 00 08 28 7c c2 e6 08 3d+23:34:29.852 READ DMA c8 00 08 e0 fd c1 e6 08 3d+23:34:29.844 READ DMA c8 00 08 10 a0 c1 e6 08 3d+23:34:29.841 READ DMA c8 00 08 50 02 c1 e6 08 3d+23:34:29.829 READ DMA Error 57 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 70 d0 9d e6 Error: UNC 8 sectors at LBA = 0x069dd070 = 111005808 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 70 d0 9d e6 08 3d+23:34:25.177 READ DMA ca 00 08 58 52 9d e6 08 3d+23:34:24.500 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:23.762 SET FEATURES [Enable SATA feature] Error 56 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 58 52 9d e6 Error: UNC 8 sectors at LBA = 0x069d5258 = 110973528 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 58 52 9d e6 08 3d+23:34:21.069 READ DMA ca 00 08 e8 b4 9c e6 08 3d+23:34:20.941 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:20.905 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 3d+23:34:20.905 IDENTIFY DEVICE Error 55 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 e8 b4 9c e6 Error: UNC 8 sectors at LBA = 0x069cb4e8 = 110933224 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 e8 b4 9c e6 08 3d+23:34:18.195 READ DMA ca 00 08 68 56 9c e6 08 3d+23:34:17.485 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:16.779 SET FEATURES [Enable SATA feature] Error 54 occurred at disk power-on lifetime: 14215 hours (592 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 56 9c e6 Error: UNC 8 sectors at LBA = 0x069c5668 = 110909032 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 56 9c e6 08 3d+23:34:14.076 READ DMA ca 00 08 88 93 9b e6 08 3d+23:34:13.940 WRITE DMA ef 10 02 00 00 00 a0 08 3d+23:34:13.914 SET FEATURES [Enable SATA feature] ec 00 00 00 00 00 a0 08 3d+23:34:13.914 IDENTIFY DEVICE SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 28943 - 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.
  4. I got yellow icon on disk 2. Here are the drive attributes. What does this means?
  5. Before I try this, I have few questions. How is the gaming performance? Are the vhd auto expand? If you have enough space on local disk, would you still do this? (I have enough space for my steam game, but I can live with my steam game on mapped network drive) Thanks. By the way, Star Wars Battlefront DLCs are unlocked this Christmas.(or so I heard)
  6. I reboot unraid and it seems fine now. Been hours with no errors. Thanks.
  7. The error keep increasing. Should I turn off unraid?
  8. I am replacing a failed hdd(disk 1). New disk 1 has completed preclear with no errors. Now unraid is building disk 1. I noticed my unraid is unaccessible from network smb although i can access unraid web site and ssh fine. This is the status of unraid website. This are the diagnostics file. https://drive.google.com/file/d/0Bx9K1xNApMr1RzBkeFhaOWZOcU0/view?usp=sharing What has happened and what should I do?
  9. This is the preclear results of my old hdd which i suspect is having problems. What should I do with the disk? Its out of warranty.
  10. Whats the difference between 1. I add a bad disk to unraid array without preclear. 2. I add a good disk to unraid with preclear. Later, the disk turn bad. Whats the difference between those 2 situation? I mean, if later I found out that a disk is bad in unraid(with or without preclear), i just replace with a new disk and everything will be fine. No data loss, even if im not preclearing. What happen if i add a bad disk to unraid? Will it results to data loss? Disk will eventually be bad. Its just a matter of time. Im trying to find justification for preclearing. Thanks.
  11. Managed to preclear the disk after starting the array without the disk.
  12. After starting the array without the disk that i want to preclear, i can preclear the disk. Thanks.
  13. disk 1 is failing. i bought new drive, disk x. i forgot to preclear disk x before adding to array. i then cancel rebuilding disk x, and want to preclear disk x before adding disk x to array. make sense?
  14. One of my disk is failing. Bought new one to replace. Mistakenly rebuild on new disk without preclear. Stopped the rebuild. Try preclear. Unable to preclear. It says "The disk '/dev/sdf' is part of unRAID's array, or is assigned as a cache device." The array has already been stopped and the disk is set to no device. How do I force preclear? Im using preclear plugin for unraid 6.
  15. This is the response I did assign the drive before and start the array(it rebuilds), but cancel minutes later because it doesnt preclear(i have the impression that it will auto preclear, but it doesnt) Before running the script, i have stop the array and set the disk to no device. What should i do?
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.