jonathansayeb

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by jonathansayeb

  1. Hi all, I just bought a retired Dell r730xd 12 bays with the following specs for 1300usd: Xeon 12 core e5-2680 v3 32GB ECC Ram 4x 4TB WD gold Broadcom nic 1gbe 4 ports Raid controller perc h730 2x 750w power supply question 1: is that a good deal [emoji28]? Question 2: Our main unraid server has 50 TB of footages and images for our media company and the tiny 512GB of cache only help during ingest of new content which makes our 10gbe network kind of pointless apart from filling those 512GB of cache. Here comes the question then, do you think I should use the new server as a freenas raid 5 speed beast to feed our editing team the content they need via 10gbe and do nightly backups to the unraid server or would you have another option? Cheers [emoji1635] Sent from my LYA-L29 using Tapatalk
  2. Restarted the server and reinstalled krusader docker and everything looks great now! 1PB ouch [emoji23]Thank you all. Sent from my LYA-L29 using Tapatalk
  3. Sorry, it must have been the frustration to get it to work [emoji28]. I've created all my Google drive mounts and team drives. I can mount them via script properly. Once mounted I can see each mounts in both krusader and windows 10 but they are all empty. I can copy files in the mount but when I check in Google drive the copied files don't appear. On unraid terminal I can see all the content of the remotes I've setup by using rclone ls remotename: My question is how can I see the content of my remotes in krusader and/or smb shares? Thank you. Sent from my LYA-L29 using Tapatalk
  4. Hi all, been going through the tuto many times but couldn't get it to work after 2 nights trying to figure it out. Followed space invader tuto as well and for some reasons my Google drive content doesn't show in neither windows 10 via smb nor krusader. I try to keep things as simple as possible and just have an easy way to upload our massive library of footages and pictures to Google drive directly from our Unraid server. And thanks for your help. Sent from my LYA-L29 using Tapatalk
  5. Same thing here. Docker doesn't work anymore :( Following for some updates...
  6. Thanks Johnny for your quick reply! What do you think the read write speed would be with standard ssd? I'd love to be able to create a huge final cut pro library accessing the media from the unraid server. Sent from my SM-G950F using Tapatalk
  7. Hi All. First of all I'd like to say that a very happy unsaid user for the last year. I'm a photographer, videographer and within that last year I maxed out my 26To array and it's now time to upgrade. Check the file attached for my current unraid setup: My daily workstation at the moment is an Imac 5k 2015. Here is what I plan to upgrade: Workstation: Change the imac to a maxed out hackintosh I8700K with an SPF+ Ethernet card. Unraid server: Install an additional Sata controller to add more HD. Add a 1to SSD as cache drive. Add 2to ssd drive for all the work in progress Add a SPF+ Ethernet card. So my question is with that upgrade plan what do you reckon would be the benefits appart from having additional HD space. Do you think I'll be able to easily achieve read/write speed around 1000mb/s and if not what would you suggest? Thank you and looking forward to hearing your input. Cheers, Sent from my SM-G950F using Tapatalk
  8. Just wanted to let you all know especially XEOMA TEAM that i've been running 8 cameras for 5 months already and everything is working great except for the terrible log problem that keeps filling up my docker.img. Please Xeoma do something asap. Cheers.
  9. Thanks for your reply! I guess I'll stick with nextcloud then even if it's super slow
  10. @thebored can you please tell me if you were able to figure your login problem out. I've just installed the docker and get exactly the same problem. Here is what i've tried: - Basic installation by just changing the info where required (ip, admin email, passord etc...), launch webui, input exactly the same info as in the docker installation, cannot connect. - Installed separate Maria-db database only for seafile, install docker container with maria-db parameter, launch webui, still login problem. Thank you
  11. Ok so does it mean that i should completely reinstall maria-db and nextcloud and start from scratch because of the update?
  12. Hello @CHBMB, Just updated all my docker containers including nextcloud and maria-db but now I get the exact same log as above (CHBMB previous post). I've tried your 2nd method to get it working but it didn't fix anything and I still have the same problem. I never did any backups of my nextcloud database, do you know how I could use your first method? Cheers
  13. Hi Coppit and thank you for your reply. I've checked for dot files (apple dstores) but there are none in the folders affected. What I don't understand is why Xeoma docker is trying to delete these folders in the first place since they contain the records from the cameras??? I understand that it might need to remove some footages based on the archive settings "Storage time for this archive" which btw I have set to 1 week, but at the moment it's trying to delete all the records since Xeoma has been setup: Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-24 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-25 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-26 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-27 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-28 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-29 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Window/2017-07-30 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-24 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-25 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-26 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-27 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-28 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-29 (39) Directory not empty Jul 31 08:42:44 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-30 (39) Directory not empty Please tell me what I might be doing wrong.
  14. You are awesome! Can't wait and my 120.000 Pictures gallery is thanking you big time!
  15. Hello Aptalca and thank you very much for your work. Just wondering if you had any plans to update the Digikam Docker? I've been using your 4.9 version but the latest 5.6 version seems really good and would love to run it on my server. Thank you again
  16. Hello, First of all thank you very much for this docker. it works great and made my life super easy. The only thing that is a bit weird is that those lines keeps showing in my unraid sys log: Jul 28 08:53:28 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-22 (39) Directory not empty Jul 28 08:53:28 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-23 (39) Directory not empty Jul 28 08:53:28 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-24 (39) Directory not empty Jul 28 08:53:28 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-25 (39) Directory not empty Jul 28 08:53:28 ECSERVER shfs/user: err: shfs_rmdir: rmdir: /mnt/disk1/CAMERAS/Records/Enzo-Creation-Entrance/2017-07-26 (39) Directory not empty I have dozens of those and i'm not too sure if that is a big issue or not since everything else seems to be working properly. Cheers
  17. Oh sorry about that. I thought defect was like "Something is wrong". Please admin move to the right category if possible. Sent from my SM-G950F using Tapatalk
  18. It seems to be rebuilding fine and I still have access to all the files! Awesome. Thank you again all!
  19. Awesome Johnie, thank you so much! I'll do that now and let you know.
  20. Thank you Johnie. Here is the diagnostic file. I have just realized reading the report that the failing disk has almost no data in it and that most files have been written to the other 3 data disks. Just used krusader to see what are the files in that "disk4" and they are not that important since i have backups on an external drive. Just to make sure of the process to not do anything foolish. 1- cancel the parity rebuild 2- stop the array 3- power off 4- replace disk4 with my old partity drive WD RED 6TB (the one before the 8tb hgst i've just installed) 5- power on (6- should i preclear the wd red 6tb that comes in place of the failing disk) 7- rebuild the parity sync. Thank you in advance for your help ecserver-diagnostics-20170704-1930.zip
  21. Thank you for your replies. It makes me worry less. Here is the smart report downloaded. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Purple Device Model: WDC WD10PURX-64E5EY0 Serial Number: WD-WCC4J3SVAHE9 LU WWN Device Id: 5 0014ee 20c35fcc1 Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm 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: 6.0 Gb/s) Local Time is: Tue Jul 4 19:20:37 2017 ICT 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: (0x00) Offline data collection activity was never started. 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: (13500) 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: (0x303d) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 177 177 051 Pre-fail Always - 39801 3 Spin_Up_Time 0x0027 133 132 021 Pre-fail Always - 4333 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 752 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 10601 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 68 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 36 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 715 194 Temperature_Celsius 0x0022 113 094 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 189 182 000 Old_age Always - 1916 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 56 (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 56 occurred at disk power-on lifetime: 10591 hours (441 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 00 28 72 11 e4 Error: UNC at LBA = 0x04117228 = 68252200 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 78 5f 06 e4 08 4d+11:03:13.274 READ DMA c8 00 18 60 5f 06 e4 08 4d+11:03:13.229 READ DMA c8 00 08 58 5f 06 e4 08 4d+11:03:13.229 READ DMA c8 00 08 50 5f 06 e4 08 4d+11:03:13.228 READ DMA c8 00 08 48 5f 06 e4 08 4d+11:03:13.228 READ DMA Error 55 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 f0 4b 3a e9 Error: UNC at LBA = 0x093a4bf0 = 154815472 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 88 98 49 3a e9 08 03:38:57.548 READ DMA c8 00 58 40 49 3a e9 08 03:38:57.548 READ DMA c8 00 58 e8 48 3a e9 08 03:38:57.548 READ DMA c8 00 20 c8 48 3a e9 08 03:38:57.548 READ DMA c8 00 20 a8 48 3a e9 08 03:38:57.548 READ DMA Error 54 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 90 61 2d e9 Error: UNC at LBA = 0x092d6190 = 153969040 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 c0 68 4b 2d e9 08 03:38:26.231 READ DMA c8 00 90 d8 4a 2d e9 08 03:38:26.230 READ DMA c8 00 58 80 4a 2d e9 08 03:38:26.230 READ DMA c8 00 70 10 4a 2d e9 08 03:38:26.230 READ DMA c8 00 38 d8 49 2d e9 08 03:38:26.230 READ DMA Error 53 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 20 a8 07 e9 Error: UNC at LBA = 0x0907a820 = 151496736 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 28 60 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 40 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 20 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 00 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 e0 91 07 e9 08 03:37:05.098 READ DMA Error 52 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 b0 83 03 e9 Error: UNC at LBA = 0x090383b0 = 151225264 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 10 38 78 03 e9 08 03:36:48.641 READ DMA c8 00 18 20 78 03 e9 08 03:36:48.641 READ DMA c8 00 08 18 78 03 e9 08 03:36:48.641 READ DMA c8 00 20 f8 77 03 e9 08 03:36:48.641 READ DMA c8 00 10 e8 77 03 e9 08 03:36:48.641 READ DMA SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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.
  22. would it be doable to stop the parity rebuild, leave the newly installed Hgst 8tb as parity drive, unassigned the disk 4 which seems to be faulty, power off, remove the faulty drive, replace with the previous parity drive ihad in the machine before (wd red 6tb), power on, rebuild the parity?
  23. Hello Is it what you are talking about? ATA Error Count: 56 (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 56 occurred at disk power-on lifetime: 10591 hours (441 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 00 28 72 11 e4 Error: UNC at LBA = 0x04117228 = 68252200 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 78 5f 06 e4 08 4d+11:03:13.274 READ DMA c8 00 18 60 5f 06 e4 08 4d+11:03:13.229 READ DMA c8 00 08 58 5f 06 e4 08 4d+11:03:13.229 READ DMA c8 00 08 50 5f 06 e4 08 4d+11:03:13.228 READ DMA c8 00 08 48 5f 06 e4 08 4d+11:03:13.228 READ DMA Error 55 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 f0 4b 3a e9 Error: UNC at LBA = 0x093a4bf0 = 154815472 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 88 98 49 3a e9 08 03:38:57.548 READ DMA c8 00 58 40 49 3a e9 08 03:38:57.548 READ DMA c8 00 58 e8 48 3a e9 08 03:38:57.548 READ DMA c8 00 20 c8 48 3a e9 08 03:38:57.548 READ DMA c8 00 20 a8 48 3a e9 08 03:38:57.548 READ DMA Error 54 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 90 61 2d e9 Error: UNC at LBA = 0x092d6190 = 153969040 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 c0 68 4b 2d e9 08 03:38:26.231 READ DMA c8 00 90 d8 4a 2d e9 08 03:38:26.230 READ DMA c8 00 58 80 4a 2d e9 08 03:38:26.230 READ DMA c8 00 70 10 4a 2d e9 08 03:38:26.230 READ DMA c8 00 38 d8 49 2d e9 08 03:38:26.230 READ DMA Error 53 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 20 a8 07 e9 Error: UNC at LBA = 0x0907a820 = 151496736 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 28 60 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 40 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 20 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 00 92 07 e9 08 03:37:05.098 READ DMA c8 00 20 e0 91 07 e9 08 03:37:05.098 READ DMA Error 52 occurred at disk power-on lifetime: 10488 hours (437 days + 0 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 00 b0 83 03 e9 Error: UNC at LBA = 0x090383b0 = 151225264 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 10 38 78 03 e9 08 03:36:48.641 READ DMA c8 00 18 20 78 03 e9 08 03:36:48.641 READ DMA c8 00 08 18 78 03 e9 08 03:36:48.641 READ DMA c8 00 20 f8 77 03 e9 08 03:36:48.641 READ DMA c8 00 10 e8 77 03 e9 08 03:36:48.641 READ DMA
  24. Hello all, Here is my issue: Just followed this guide to replace my WD RED 6tb parity drive to a bigger one HGST NAS 8tb. I started the parity sync and everything was rebuilding nicely at average 140 mb/s until few hours ago where it just went to 84.4 kb/s, yes that's not a typo i mean KB. The estimated finish sayd 935 days, 20 hours, 2 minutes!!!!!! (See attached screenshot) Something definitely went wrong so i checked the log and it seems that my data drive number 4 has read errors which i think might be the cause of the problem. Please tell me there is a solution without losing my datas.
  25. Thank you all guys for your comments! @wgstarks i'll test soon after I finish a 4tb file transfer which will probably be tomorrow morning LOL. @tdallen sorry for the confusion about the network cable, i meant cat5e. @1812 when you use final cut, do you move your files from the finder or do you actually import them via the final cut import box?