skyfox77

Members
  • Posts

    32
  • Joined

  • Last visited

Everything posted by skyfox77

  1. I would really like to have a plugin to defrag the XFS drives, anyone willing to make one?
  2. I was referring to the Bug formatting bigger disks then 2 Tb in old version. Sorry for being unclear, i havent updated to this one yet.
  3. This was a CRITICAL bug and I almost lost 10Tb of data because of it, do not haste to add newer versions unless they are checked. This should really only happen on a BETA version. Edit: Well, we will see in 5 hours if I have lost anything or not, I am not out of the woods yet. I am reffering to the over 2 tb disk format in the old version not this one.
  4. Yikes, me too, almost lost 10Tb of data because of this bug!
  5. Parity sync is as fast as the slowest disk. My guess is that your USB disk is making the parity sync extremely slow.
  6. Any news on this as a plugin? I would really love one
  7. Wen it comes out as a plugin, i will surely use it
  8. Sure its not a huge problem anymore, but there is so many plugins for almost everything already so it would be nice to have one for defragging too
  9. Why isnt there a plugin to make a defrag on the disks?
  10. Well, that is not what I want to do with my server. Thanks for the tip. but that actually made it worse than before Trying on version 6.6.6
  11. I am downloading to my User Shares, but they are all set to use my Cache drive which is an SSD. I actually bought an SSD because i thought that was the issue. Still, no issues with 6.4.1. Or VERY rarely and for a shorter period of time, newer versions I have to paus the downloads to get it to catch up. Glad It works for you, I still think It's a bit overkill to have to create a VM to download things to a fileserver. I really just wish I knew what the issue could be with all the newer versions of Unraid that says the disk overload when the older version don´t.
  12. I am still stuck with Unraid 6.4.1, I have newer hardware now and still has the same problem when I update to a newer version of Unraid. Is there someone that has any idea how to solve my problem or will I be stuck with 6.4.1 forever?
  13. Zero replies to this? Does no one have any idea what causes issues with Unraid 6.5+ on my rig?
  14. So my problem is, whenever I am using any newer version of Unraid than 6.4.1 I cant utilize my internet bandwith for downloading directly to my Unraid server. My usual speed with 6.4.1 is about 50Megabytes per second (I have 500/500Mbit). And it rarely gets disk overload in Utorrent. But as soon as i have upgraded to version 6.5 and newer I have always had this problem that my speed drops and disk overload. Nothing else is changed than the never version of Unraid. I have tried all 6.5+ updates to date and I have always reverted back to 6.4.1 because of this issue. I wonder if this has something to do with the Meltdown/Spectre update and my server cant handle it? diagnostics-20180527-1459.zip
  15. I have the exact same problem, alot of stuff has been put in the recycle bin folder, it seems like all files goes to the recycle bin folder even on the cache drive. And then is moved to the wrong place on my shares.
  16. Same. I had hoped to see a solution soon.
  17. I was about to ask the same question, I would really love to have a script/plugin to automatically even out space on the disks if you accidentally overfilled them. Right now I manually have to move files from one disk to another.
  18. It would be great if you could make unRAID packages of, PluginDataDir, Plugin_GetDir and PluginChoose. Really great work you've done with this UnTorrent package. Second that, those would be very nice to have.
  19. I would recommend Supercopier2 over teracopy, but thats me
  20. Ooops! Sorry. Looks my web-hosting subscription ran out. I'll renew it on monday. Oh, bummer, well, could you please upload it elsewhere until then?
  21. When i try to download the package, it says: Page Not Found Anyone have a working link for it?
  22. Thanks for the reply. Sounds good, then I might try to use this drive in my Unraid server atleaste until i buy a new bigger drive. what about the errors in the log when running smart tests? Is that just an indication of the pending failing sectors? SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 12286 - # 2 Short offline Completed without error 00% 12262 - # 3 Extended offline Completed: read failure 40% 12259 641949242 # 4 Extended offline Completed without error 00% 12253 - # 5 Extended offline Completed: read failure 40% 12244 641949245 # 6 Extended offline Completed: read failure 90% 12241 641949242 # 7 Extended offline Completed without error 00% 12118 - # 8 Short offline Completed without error 00% 12069 - # 9 Extended offline Completed without error 00% 12055 - #10 Extended offline Completed without error 00% 12046 - #11 Short offline Completed without error 00% 12043 - #12 Short offline Completed without error 00% 12043 - #13 Short offline Completed without error 00% 2820 - #14 Short offline Completed: read failure 90% 2818 14225960 And what bout the other errors? This and the other 4 errors that is logged? Anything to be concerned about? Error 455 occurred at disk power-on lifetime: 2816 hours (117 days + 8 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 01 52 c0 90 f0 Error: UNC at LBA = 0x0090c052 = 9486418 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 d8 01 52 c0 90 07 00 07:48:11.991 READ VERIFY SECTOR(S) EXT b0 d8 01 01 4f c2 00 00 07:48:11.925 SMART ENABLE OPERATIONS 42 00 02 52 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT 25 00 01 c1 3e 00 00 00 07:48:08.682 READ DMA EXT 42 00 02 50 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT
  23. I have a drive that I wonder if it's safer to use for my unraid box. If I check the smart staus log I have some big concerns. I have still 6 month warranty left. but westen digitals diagnostics software cant find any errors. I still would like to RMA it. here is the COMPLETE log: SMART status Info for /dev/hdc smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Western Digital Caviar SE family Device Model: WDC WD5000AAKB-00YSA0 Serial Number: WD-WCAS82496563 Firmware Version: 12.01C02 User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jan 16 12:32:29 2010 GMT-1 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: (13200) 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: ( 154) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x203f) 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 0x000f 200 200 051 Pre-fail Always - 2669 3 Spin_Up_Time 0x0003 174 173 021 Pre-fail Always - 6300 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 404 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 084 084 000 Old_age Always - 12286 10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 337 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 343 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 463 194 Temperature_Celsius 0x0022 116 095 000 Old_age Always - 34 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 7 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 13 200 Multi_Zone_Error_Rate 0x0008 199 194 051 Old_age Offline - 118 SMART Error Log Version: 1 ATA Error Count: 458 (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 458 occurred at disk power-on lifetime: 12105 hours (504 days + 9 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 -- -- -- -- -- -- -- 01 51 00 7f 37 50 f0 Error: AMNF at LBA = 0x0050377f = 5257087 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 7f 37 50 26 08 06:19:43.690 READ DMA EXT 25 00 00 7f 33 50 26 08 06:19:43.680 READ DMA EXT 25 00 00 7f 2f 50 26 08 06:19:43.670 READ DMA EXT 25 00 00 7f 2b 50 26 08 06:19:43.660 READ DMA EXT 25 00 00 7f 27 50 26 08 06:19:43.640 READ DMA EXT Error 457 occurred at disk power-on lifetime: 11980 hours (499 days + 4 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 -- -- -- -- -- -- -- 01 51 00 ff 9f 5e f0 Error: AMNF at LBA = 0x005e9fff = 6201343 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff 9f 5e 26 08 1d+07:06:05.454 READ DMA EXT 25 00 00 ff 9b 5e 26 08 1d+07:06:05.444 READ DMA EXT 25 00 00 ff 97 5e 26 08 1d+07:06:05.434 READ DMA EXT 25 00 00 ff 93 5e 26 08 1d+07:06:05.404 READ DMA EXT 25 00 00 ff 8f 5e 26 08 1d+07:06:05.394 READ DMA EXT Error 456 occurred at disk power-on lifetime: 11614 hours (483 days + 22 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 -- -- -- -- -- -- -- 01 51 00 c7 fe cb e0 Error: AMNF at LBA = 0x00cbfec7 = 13369031 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 c7 fe cb 34 08 04:17:11.860 READ DMA EXT 25 00 00 c7 fa cb 34 08 04:17:11.850 READ DMA EXT 25 00 00 c7 f6 cb 34 08 04:17:11.840 READ DMA EXT 25 00 00 c7 f2 cb 34 08 04:17:11.822 READ DMA EXT 25 00 00 c7 ee cb 34 08 04:17:11.810 READ DMA EXT Error 455 occurred at disk power-on lifetime: 2816 hours (117 days + 8 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 01 52 c0 90 f0 Error: UNC at LBA = 0x0090c052 = 9486418 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 d8 01 52 c0 90 07 00 07:48:11.991 READ VERIFY SECTOR(S) EXT b0 d8 01 01 4f c2 00 00 07:48:11.925 SMART ENABLE OPERATIONS 42 00 02 52 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT 25 00 01 c1 3e 00 00 00 07:48:08.682 READ DMA EXT 42 00 02 50 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT Error 454 occurred at disk power-on lifetime: 2816 hours (117 days + 8 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 02 52 c0 90 f0 Error: UNC at LBA = 0x0090c052 = 9486418 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 42 00 02 52 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT 25 00 01 c1 3e 00 00 00 07:48:08.682 READ DMA EXT 42 00 02 50 c0 90 07 00 07:48:08.682 READ VERIFY SECTOR(S) EXT 25 00 01 00 00 00 00 00 07:48:08.682 READ DMA EXT 42 00 04 54 c0 90 07 00 07:48:08.667 READ VERIFY SECTOR(S) EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 12286 - # 2 Short offline Completed without error 00% 12262 - # 3 Extended offline Completed: read failure 40% 12259 641949242 # 4 Extended offline Completed without error 00% 12253 - # 5 Extended offline Completed: read failure 40% 12244 641949245 # 6 Extended offline Completed: read failure 90% 12241 641949242 # 7 Extended offline Completed without error 00% 12118 - # 8 Short offline Completed without error 00% 12069 - # 9 Extended offline Completed without error 00% 12055 - #10 Extended offline Completed without error 00% 12046 - #11 Short offline Completed without error 00% 12043 - #12 Short offline Completed without error 00% 12043 - #13 Short offline Completed without error 00% 2820 - #14 Short offline Completed: read failure 90% 2818 14225960 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.
  24. Update: Well, i bought 2 new drives instead and I am using only 1 of my old drives at the moment and that seems to work, I am not using my old PCI IDE controller anymore. Now i will try just adding one new drive at a time and see if any parity errors occurs again or not.