Jump to content

P_K

Members
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

0 Neutral

About P_K

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. hi all, I'm using unraid for long time but last 2-3 months I got a very annoying issue. I have dockers with couchpotato and sickrage which use deluge to download Movies/TV Series to a disk that is not in the array (managed by unassigned devices plugin). After either couchpotato or sickrage detects the download is complete it then copies the downloaded file to the cache disk (2 x 500 Gb SSD's (btrfs)). Overnight, the mover then moves those files to a disk in the array. This all worked fine for years but since 2-3 months some of the files are not copied completely. As an example, the movie Lady Bird was just downloaded on the disk out of the array. It's size is 7,04GB : Couchpotato copied it : But after the copy size is much smaller, only 1,61 GB : Couchpotato logs don't show any issue. Also, same happens with some copies from SickRage so I don't think it's an application issue. Unraid logs also don't show anything at the time of the copy (12:45) (at 12:18 I restarted deluge docker. 12:47 I opened a console session from GUI). Full unraid log : tower-syslog-20180317-1337.zip I'm quite honestly lost with this. First I expected the Mover but as can be seen above the issue happens already before moving. Is there any way I can check further what can cause this?
  2. I'm moving my disks from ReiserFS to XFS after upgrading to 6.4. I follow the procedure from here : http://lime-technology.com/wiki/index.php/File_System_Conversion when copying disk3 to disk9, the rsync stopped after 10 hours more or less (earlier then I expected) : sent 1,270,465,325,294 bytes received 705,847 bytes 33,832,630.68 bytes/sec total size is 1,270,152,418,034 speedup is 1.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] I don't have all the output rsync produced before that so cannot 'see previous errors'. My syslog shows this : Jan 22 08:10:22 Tower kernel: REISERFS warning (device md3): jdm-20001 reiserfs_xattr_get: Invalid magic for xattr (user.org.netatalk.supports-eas.bCcdQh) associated with [2 2112 0x0 SD] The strange thing however is that disk3 has 1.95Tb on it while disk9 now only has 1.27Tb. Seems that big part is not copied... Should I start over and maybe use the --log-file=/path/to/log option on the rsync this time to see if I get errors during the copy? Any other advise ?
  3. In this post, it was said that 6.4 Mover would be generalized to move contents of any device to any other device or device set. Is that indeed the case in 6.4 ? Can the mover now be used to migrate disks from ReisterFS to XFS ?
  4. Yes, I do indeed. See attachment.
  5. I restarted the server as the load in top went up to 50. The diagnostics files are taken after the reload (before reload I couldn't access the gui to take them). Hopefully they are still useful. tower-diagnostics-20170121-2053.zip
  6. cachedirs is installed but I turned it off long time ago as I had some issues with it. This is an i5 processor with 16Gb of memory.
  7. This morning I got a notification (from PlexPy) that my Plex server is down. I tried to open the unraid webpage to check but it doesn't open. I can ssh into the server and can see in top that shfs uses 100% cpu. Any ideas to bring my server back to normal? unraid 6.2.4 with several dockers.
  8. A while ago I tried to preclear 2 disks. One worked and something went wrong for the other so I had to start preclear again (don't remember the exact details though). I noticed now (several weeks later) in the logs the following after a startup : Dec 9 10:04:46 Tower preclear.disk: Resuming preclear of disk 'sdm' sdm was the disk that had issues with the preclear before but 'sdm' doesn't exist anymore now (there is no disk labeled sdm anymore). That disk is now sdk and is part of the cache pool. Seems preclear still thinks it has to do something. Is it possible/needed to stop this?
  9. That worked, thanks a lot. Got indeed rid of the errors now that my UD disk is not mounted on /mnt/user anymore.
  10. Yes, that's what I thought indeed (that it must get out of /mnt/user). I'm not sure however how to 'remove it, delete it from the list'... I had the drive unmounted but the only thing I can do then is to click the red X next to the partition. If I hover over that it says 'delete partition'. I'm afraid I'm going to lose the data on that disk if I do so. I don't see another option to remove that disk from UD.
  11. I was already on 2016.12.04 for Unassigned Devices. I stopped my array which unmounted that disk and started it again : same issue.
  12. Picking this back up as I still have the errors. Didn't look into them much as all seems to be working. I didn't remove the Unassigned Devices. I think however I know what the issue is. The mount point for a disk I added in Unassigned Devices is /mnt/user/Torrents_3Tb. I read that this is wrong and it should be /mnt/disks/... Correct ? My 'Torrents_3Tb' is showing up as a user share under the Share tab of unraid. I guess that's where the errors come from. (see attached screenshots). Question : is there an easy way to change that mount point without deleting all the data on that partition ?
  13. Thanks! Adding iommu=pt to the append line of my syslinux.cnf file fixed it.
  14. Hi all, unRAID : 6.1.9 MB : ASUSTeK COMPUTER INC. - P8B75-M LE Controller : startech.com 4 port PCIe SATA III 6Gbps Raid controller card with heatsink Added that 4 port Sata card to my unRAID and connected 2 Samsung EVO 850 500Gb SSD's to it. During boot there are errors and the 2 SSD's don't show up (cannot add them). I see following in the logs : Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata18: limiting SATA link speed to 1.5 Gbps Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13: limiting SATA link speed to 3.0 Gbps Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: link is slow to respond, please be patient (ready=0) Oct 18 21:24:37 Tower kernel: ata18.00: qc timeout (cmd 0xa1) Oct 18 21:24:37 Tower kernel: ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata13.00: qc timeout (cmd 0xec) Oct 18 21:24:37 Tower kernel: ata13.00: failed to IDENTIFY (I/O error, err_mask=0x4) Oct 18 21:24:37 Tower kernel: ata18: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 18 21:24:37 Tower kernel: ata13: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: limiting SATA link speed to 3.0 Gbps Oct 18 21:24:37 Tower kernel: ata11: COMRESET failed (errno=-16) Oct 18 21:24:37 Tower kernel: ata11: reset failed, giving up When I move one of the SSD's to another controller then it shows up. If I move a drive that was on another controller before to the new one, that drive doesn't show up anymore. So it seem the controller has an issue. Anybody can assist on this? Logs attached. tower-syslog-20161018-2127.zip
  15. anybody an idea about this? Would be appreciated. I upgraded to 6.1.7 in the meantime but errors keep coming.