nametaken_thisonetoo

Members
  • Posts

    34
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

nametaken_thisonetoo's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Thanks for the reply. Can I ask how you are able to work this out? Would be great if I could fix this sort of thing myself in the future.
  2. Hi there, This error has popped up in my syslog and although I found an old thread covering it, there was no resolution contained within. So I thought I'd see if anyone else out there has had this recently, and if so, what they did to resolve the problem. Thanks in advance. Diagnostics attached and syslog excerpt is immediately below: Sep 19 16:44:23 TheMagicEye kernel: ata11.00: exception Emask 0x10 SAct 0x1f8 SErr 0xba0100 action 0x6 Sep 19 16:44:23 TheMagicEye kernel: ata11.00: irq_stat 0x08000000 Sep 19 16:44:23 TheMagicEye kernel: ata11: SError: { UnrecovData PHYInt 10B8B Dispar BadCRC LinkSeq } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/40:18:50:72:56/05:00:4d:04:00/40 tag 3 ncq dma 688128 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/40:20:90:77:56/05:00:4d:04:00/40 tag 4 ncq dma 688128 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/40:28:d0:7c:56/05:00:4d:04:00/40 tag 5 ncq dma 688128 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/40:30:10:82:56/05:00:4d:04:00/40 tag 6 ncq dma 688128 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/40:38:50:87:56/05:00:4d:04:00/40 tag 7 ncq dma 688128 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11.00: failed command: READ FPDMA QUEUED Sep 19 16:44:23 TheMagicEye kernel: ata11.00: cmd 60/90:40:90:8c:56/00:00:4d:04:00/40 tag 8 ncq dma 73728 in Sep 19 16:44:23 TheMagicEye kernel: res 40/00:00:90:8c:56/00:00:4d:04:00/40 Emask 0x10 (ATA bus error) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: status: { DRDY } Sep 19 16:44:23 TheMagicEye kernel: ata11: hard resetting link Sep 19 16:44:23 TheMagicEye kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 19 16:44:23 TheMagicEye kernel: ata11.00: supports DRM functions and may not be fully accessible Sep 19 16:44:23 TheMagicEye kernel: ata11.00: supports DRM functions and may not be fully accessible Sep 19 16:44:23 TheMagicEye kernel: ata11.00: configured for UDMA/133 Sep 19 16:44:23 TheMagicEye kernel: ata11: EH complete themagiceye-diagnostics-20210919-2034.zip
  3. @ChatNoir you are a lifesaver thanks so much. I think I'll go with your option 1 and learn more about MC another day. I assume the two step mover will work for all of the system based shares - Appdata, System, Domains, isos? I'm a bit surprised that there are no instructions in the creating additional cache pools documentation on moving these critical shares safely. I guess they assume most folks have broad knowledge which is a shame if correct.
  4. Hi there, For too long I have had both my downloads folder and appdata etc all on the same single cache drive. I have now setup a second cache pool/drive and feel like I am stuck in a circular reference trying to work out how best to move the files from one drive to the other. - All relevant shares have been adjusted to Cache:Prefer with the new cache drive also selected. Mover did not move any of the data when invoked (something that seems to be a constant problem with Mover in many situations) - In order to use Krusader I would need to turn on Dockers which then creates new Appdata in the new cache drive while all the old data also remains where it was. This feels like bad practice destined to end in disaster. - Using CA backup restore requires me to change the Appdata Share path on the backup tab in order for the Restore tab to deposit the files on the new cache drive. But the new path won't save unless I click 'apply' on the backup tab - which will then initiate another backup of the new empty share on the new cache drive and overwrite the original share I want to restore. Please help me with this madness! I assume as a relative noob I a missing something obvious here, but I have been unable to find instructions either in the forum, via SpaceInvader, or elsewhere. Thanks!
  5. Apologies @Vr2Iobut I'm a bit of a noob and not entirely sure what you are referring to in this post. What I have done is double check the logs for activity related to drive spin up and down, and 99% of the time it is for the purposes of reading the drive SMART info. Perhaps I'm not looking at the correct log or missing something entirely? I also haven't noticed anything in the logs about anything else on the network that might be waking up the drives, but admittedly I'm very vague on what that would look like in logs or elsewhere. I have attached recent diagnostics - hoping you or someone else might be able to take a look and see what I might be missing. themagiceye-diagnostics-20210627-1126.zip
  6. Good to know, thanks @JorgeB. Murphy's law seem to be in effect at the moment as drive activity seems to be back to normal the last 3-4 hours. But will definitely consider a rollback if it continues again. I'm fairly new to UnRaid - is it reasonable to expect this issue to be fixed in the next release?
  7. Thanks @Vr2Io, although I'm really pretty lost as to what would be causing so much activity. At the time that screenshot was taken there was one user watching Plex remotely, Deluge downloading to the Cache drive, and that's it. My setup is pretty straightforward - just Plex and a few *arr related Dockers. No VM's and not much else at all. I've attached my diagnostics if you or anyone else can offer some insight it would be much appreciated. themagiceye-diagnostics-20210623-0923.zip
  8. I have noticed that the disks in my array are almost always all spun up, and looking at the logs I can see that this seems to be because of the default interval set by UnRaid for polling each drive for SMART data. This is every 1800 seconds (or 30 minutes). Separate to this, I have also previously set the default spin down delay to 30 mins to avoid too much stopping and starting. With these two settings combined there really isn't much time where individual drives are actually spun down. What is typical best practice for these settings (and any others that are similarly relevant) in terms of power efficiency and long term disk health?
  9. I would just go with option 3 and place it safely on your desk or on an old mousepad or similar if you are worried about vibrations. Well worth doing a preclear even though its not technically needed - much better to find faults with a new drive prior to it being added to your array and loaded up with all that lovely data.
  10. Thanks for the response @Gragorg. It would be great to have this running for the future, so I have found and enabled the syslog server for the local machine, but not for any remote server as I only have the one. I have also set the log files to be created on the cache drive in Appdata. My only question now is when will I see a log file there? It has been a few hours and no luck. Screen capture is attached of my syslog settings
  11. There was a huge storm here last night and I lost power for around 10 hours. I would really like to check the UnRaid logs to see if my UPS did was it was supposed to with a graceful shutdown etc. When I check the logs they are only available from when the Server was turned back on this morning. Is there somewhere I can access a log history? I have checked the wiki and done a few searches and haven't come up with an answer. Cheers, R
  12. Apologies if this is not in the right place - it's not really specific to one container so didn't seem to fit elsewhere. I have tried a few methods to route traffic for a few of my containers (Radarr, Sonarr) through the Binhex DelugeVPN container. First attempt was by changing the network type in Radarr to None and then adding --net=container:binhex-delugevpn to the extra parameters field; then adding Radarr's port to the Deluge container settings, all as per SpaceInvader's video. I could see via the console that the IP address for Radarr had changed to that of Deluge, but am still unable to get the GUI to show its face. The second attempt was via Privoxy in the DelugeVPN container, again following SpaceInvaders video on this. Both Radarr and Sonarr lose connection with Deluge as soon as I add the Proxy into their respective settings. I am far from an expert on this, and only a few months into my UnRaid journey, so not quite sure what to try next. I have attached diagnostics themagiceye-diagnostics-20210331-2246.zip
  13. Sigh...I think I have FINALLY worked out what has been causing the problem. @itimpi if you could confirm I'm on the right track I would be eternally grateful. 1. When I first set up UnRaid a few months ago some of my Shares were set to only reside on 2 of the 4 drives in my array. Not sure why I did this but it seemed like a plan at the time. 2. The largest Share amongst these is TV Shows, and was setup with a Split Level of only the Top 2 Levels. 3. These drives are now at or near capacity, meaning that Mover can't always shift new TV Show files to the array because the two drives that contain the top two levels of the TV Show Share are too full. I'm reluctant to set TV Shows to Top Level or Any Level Splits as I'd rather keep each show on the same drive if possible. But if this is the only fix then I'm ok with it. Alternatively, is there any way to cut and paste some of the shows from one array drive to another array drive but still within the TV Show share? An unfortunate consequence of my early array config is that my files are now not evenly spread across the 4 array drives.
  14. Thanks for the reply - I have previously had cache set to Yes on the relevant Shares. It seemed to work fine until it just didn't anymore, which is odd as I have not been playing with any settings, new dockers, VM's etc. I am not sure how to check the top level of the cache drive other than by clicking on the folder icon in Main>Cache. Doing so only shows one set of folder names. Is there a better way to check this, such as Krusader? I have noticed this mentioned a few times but haven't used it yet
  15. Hi all, I'm extremely frustrated to find myself unable to solve this problem on my own, but am now very much hoping someone can help. I feel like there must be software Gremlins in the corner of the room pissing themselves laughing at me as I type this. So...I frequently run DelugeVPN, setup as per SpaceInvaders awesome tutorial. This places the fresh download files temporoarily in a Downloads\Incomplete and then Downloads\Complete folder once finished. This downloads folder is an UnRaid share set to Cache:Yes. I believe the mistake I have made is that the final destination folder (aka Unraid shares) for these files, for example 'Software', also has had a setting of Cache:Yes. This has meant whether I manually cut/paste downloads or Sonarr etc is moving them, they are only being effectively moved as far as another folder on the cache drive. So then eventually the cache drive fills as more downloads come in behind the existing ones. I have changed these final destination folders to Cache:No, and now also the Downloads folder to the same, but mover still doesn't want to clear out these files from the Cache. I have tried switching off Dockers before invoking the mover, with no luck, and today for some reason now the mover will not even start working when I click the button. At this point I am at a loss as to what to do next - thanks in advance for any help. Diagnostics are attached. themagiceye-diagnostics-20210319-1401.zip