thegurujim

Members
  • Posts

    14
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

thegurujim's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Taking requests? While I don't want to convert anything in the library I would like an option to normalize volume across all the media. If it requires rencoding the media to another format so be it. Volume normalization is the main thing I'm looking for.
  2. Changing Priority. It's minor for me but may be different priority for others.
  3. I've seen several people reporting slower network speeds (tests and real work performance) are slower after upgrading to 6.7.0 I've seen this with the Speedtest plugin and a Win 10 VM going to speedtest.net. Speed is about 200Mbps slower than in version 6.5.4 (in my case). Others have seen the same issue of speed difference between 6.6.7 (normal expected speeds) and 6.7.0 (slower speeds by 200-300Mbps).
  4. How does one move files from one share to another when the shares in question aren't supposed to exist on the selected disks? Moving the files between shares using the Krusader or Dolphin docker apps results in the files just creating the share in the disk it's already on. Moving it using Windows, actually moves the files from disk to disk. Nothing I choose in the split settings seems to make it move the file from disk to disk while using Krusader/Dolphin.
  5. I've changed it to just setting the drives for inclusion now. I'm moving the data from the other disks to the proper disks and see how that goes. Although I did set both, it should still follow the "rule" I set. Squid's reply that makes me wonder why a split would not follow the include/exclude rule and how I'm supposed to set the split so it won't write to drives I don't want it to write to.
  6. How should I be setting the split then? At the moment it's set to split as required. Do splits override includes? If I set to only include the disks in the share it shouldn't use any drives that are in the exclusion, right?
  7. I have two shares Stuff and Scratch I have the Stuff share assigned to only drives 1-7 and have excluded drives 8-9. Scratch is assigned to drives 8-9 and excluded 1-7. I'm finding items that have been copied into a directory in the Stuff share on drives 8-9. Does this have to do with the split directory setting?
  8. I don't know if you've ever found the answer to this but I found out that the 'autocutse1' process was due to the Krusader docker I was using. I restarted that docker and it went away
  9. https://www.amazon.com/gp/product/B0177GBY0Y/ref=oh_aui_detailpage_o01_s01?ie=UTF8&psc=1 I have two of these and also using the motherboard SATA plugs. Thought I'd split the drive between two PCI interfaces dsa and have room to expand later.
  10. 850W single 12v rail. Same one linked below. https://www.amazon.com/gp/product/B00IKDETOC/ref=oh_aui_detailpage_o01_s02?ie=UTF8&psc=1 xorunraid-diagnostics-20170118-1111.zip
  11. I started looking at my system logs during and after a monthly parity check. These are popping up for some of the drives as it does the check. SMART reports come out clean for all the drives. Parity check come out error free. No performance issues. I've got several dockers that work flawlessly. I've got ten hard drives connected to two SATA cards and the motherboard. Errors happen to any of the SATA ports. I doubt the cards and the motherboard all are defective given checks turn out fine each time. My extensive Google research shows that it's possibly: - the way unRaid handles spinning up the drives from sleep (or that it doesn't spin them up fast enough or in the correct way) - it's a hardware issue with cables (I don't think this is my case. I've swapped cables and all tests and parity check come out clean consistently) - power supply issue (new high quality power supply @ 650W should handle the 8 mechanical drives and the 2 SSDs fine, also spinning up all the drives at boot or for parity checks at the same time doesn't cause any loggable issues. Is this something I can ignore for the time being or do I need to customize something to be a little more forgiving of spin up time of the drives?
  12. Updated to the latest on my unRaid and now the docker isn't starting.
  13. I'm getting a similar error. I tried to complete a parity check and that's when I noticed the error. Not to mention it said the check would take over 100 days. I've tried several different cables. Several different slots. Different cables with different slots. Different power connections (850watt PS feeding 11 drives. New hard drive. It's attempting to rebuild a drive now and it only throws the error up sometimes. When it does throw errors up it slows to 1MB/s then ramp back up to 90+MB/s. I don't know what else to try right now. Feb 5 16:55:44 XORUNRAID kernel: ata16.00: cmd 35/00:08:18:56:68/00:00:14:01:00/e0 tag 14 dma 4096 out Feb 5 16:55:44 XORUNRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 16:55:44 XORUNRAID kernel: ata16.00: status: { DRDY } Feb 5 16:55:44 XORUNRAID kernel: ata16: hard resetting link Feb 5 16:55:44 XORUNRAID kernel: ata16: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 5 16:55:44 XORUNRAID kernel: ata16.00: configured for UDMA/133 Feb 5 16:55:44 XORUNRAID kernel: ata16.00: device reported invalid CHS sector 0 Feb 5 16:55:44 XORUNRAID kernel: ata16: EH complete Feb 5 16:56:19 XORUNRAID kernel: ata16: limiting SATA link speed to 3.0 Gbps Feb 5 16:56:19 XORUNRAID kernel: ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 16:56:19 XORUNRAID kernel: ata16.00: failed command: WRITE DMA Feb 5 16:56:19 XORUNRAID kernel: ata16.00: cmd ca/00:08:98:8b:12/00:00:00:00:00/e0 tag 6 dma 4096 out Feb 5 16:56:19 XORUNRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 16:56:19 XORUNRAID kernel: ata16.00: status: { DRDY } Feb 5 16:56:19 XORUNRAID kernel: ata16: hard resetting link Feb 5 16:56:19 XORUNRAID kernel: ata16: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Feb 5 16:56:19 XORUNRAID kernel: ata16.00: configured for UDMA/133 Feb 5 16:56:19 XORUNRAID kernel: ata16.00: device reported invalid CHS sector 0 Feb 5 16:56:19 XORUNRAID kernel: ata16: EH complete Feb 5 16:56:50 XORUNRAID kernel: ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 16:56:50 XORUNRAID kernel: ata16.00: failed command: WRITE DMA EXT Feb 5 16:56:50 XORUNRAID kernel: ata16.00: cmd 35/00:80:f0:af:21/00:01:00:00:00/e0 tag 11 dma 196608 out Feb 5 16:56:50 XORUNRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 16:56:50 XORUNRAID kernel: ata16.00: status: { DRDY } Feb 5 16:56:50 XORUNRAID kernel: ata16: hard resetting link Feb 5 16:56:50 XORUNRAID kernel: ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 5 16:56:50 XORUNRAID kernel: ata16.00: configured for UDMA/133 Feb 5 16:56:50 XORUNRAID kernel: ata16.00: device reported invalid CHS sector 0 Feb 5 16:56:50 XORUNRAID kernel: ata16: EH complete Feb 5 16:57:26 XORUNRAID kernel: ata16.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 16:57:26 XORUNRAID kernel: ata16.00: failed command: WRITE DMA EXT Feb 5 16:57:26 XORUNRAID kernel: ata16.00: cmd 35/00:80:30:56:26/00:01:00:00:00/e0 tag 28 dma 196608 out Feb 5 16:57:26 XORUNRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 16:57:26 XORUNRAID kernel: ata16.00: status: { DRDY } Feb 5 16:57:26 XORUNRAID kernel: ata16: hard resetting link Feb 5 16:57:26 XORUNRAID kernel: ata16: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 5 16:57:26 XORUNRAID kernel: ata16.00: configured for UDMA/133 Feb 5 16:57:26 XORUNRAID kernel: ata16.00: device reported invalid CHS sector 0 Feb 5 16:57:26 XORUNRAID kernel: ata16: EH complete