Jump to content

RageInvader

Members
  • Content Count

    26
  • Joined

  • Last visited

Community Reputation

3 Neutral

About RageInvader

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. So I have a request in changing how unRAID distributes files across the array. I currently have my share set to 'most-free' as I'd like files to be split as evenly as possible across all the drives I have, for a long time I had 4 x 1tb drives in my array (slowly replacing these out now) and when set to most free this leaves each of these 1tb drives at around 50% while my 3/4tb drives are 80/85% full, as you can see in the picture attached. I'd prefer the 'most-free' option to have a secondary option to then measure in % rather than actual space free. This could also be useful for the 'high-water' method also.
  2. It appears that I have fixed it somehow, but unfortunately I have no idea how, as I was getting so frustrated at it I ended up changing 2/3 things at once. The last I remember changing is; I updated the bios version even although it was already on latest, which also reset all the bios settings to default. There might have been a funny setting deep somewhere, one of which was I had my board setup so that the two on board USB controllers would show seperately so I could pass one through to VM's. I also performed a check disk on my unRAID USB, although it didn't find any errors, so doubt it done anything. I had my GPU back in my machine at this point, and noticed when booting I had a PCI-e to PCI bridge which wasn't there while I was having issues. The third one might well be linked to the first change I made. I have had the whole server back together for over a week now ran two parity syncs and have had no ATA errors now
  3. I have read through this thread, and will try the fixes at the weekend. Unfortunately I do not have the cash to upgrade the card, the IBM and Dell cards seem quite hard to get a hold of in the uk. Has the Linux kernal patch been included in unRAID 6.2? If so which exact version has the patch been added.
  4. I think I'm getting this same issue with my Marvell controller (Model 88SE9485) with VT-d enabled. I initially thought it was related to my GPU being installed, but have now discovered I only get the errors when VT-d is enabled. What I don't understand is that all my drives show up fine, and I only get DMA errors randomly every couple of hours, or more often when doing a parity check. ness-diagnostics-20160329-1611-nogpu.zip
  5. Okay after some more research with my machine, I have got my GPU and Marvell controller installed after doing a BIOS update VT-d was disabled and no errors have occurred in 48 hours. So I'm almost certain this is related to this bug here. https://lime-technology.com/forum/index.php?topic=40683.0 Although I'm completely baffled as to why i'm only getting these errors now, and never before.
  6. I have had my controller for about a year and a half now, Originally had it in an old dell server, then moved my unRAID into my gaming machine, and had been running for 6 months with no issues, I added a new drive to the system, all went well, parity sync fine, then a week later was seeing these errors.
  7. Im sorry again I have no idea what DMA is, I have googled the error lines, but can't find anything relevant to me. I have been away all weekend and my GPU has been removed from the system, but after 3/4 days with no errors, I got some this morning, so I have attached new logs. Many thanks ness-diagnostics-20160329-1611-nogpu.zip
  8. I'm unsure what you mean, how would I find out if they are? They show up on unRAID in different IOMMU groups, if that has anything to do with what u mean?
  9. Have been loving unRAID for about 3 years now, but recently added a new drive to my array, pre-cleared, then added, then while parity syncing it had corrected errors, after the weekly parity sync, it corrected more errors, which led me to checking the logs to then discover that... I'm having 'ata' errors on drives attached to my Supermicro SAS2LP-MV8, which is causing parity sync errors in the hundreds. After a week long of troubleshooting, checking cables, buying new cables, reseating the PCI cards, I have isolated the issue to only happen when I have my GTX 670 GPU installed in my machine. I have tried with my SAS card in the PCI-e 2.0 slot and the GPU in the 3.0 slot, and have also tried the other way round, if I have both cards installed I get the errors every 10 minutes or so. I have also tried with the GPU installed but the PCI power from PSU not attached, possibly ruling out a bad PSU. I have had my GPU out for 48 hours now with no errors, so i'm almost certain that having it installed is causing the issues. Unfortunately I don't have the full diagnostics but have the full syslog from when the errors are occurring, as I have came to post in the forums and just now read the read-first post, and worried about my data getting corrupted if I put my GPU back in. I have attached my full syslog from when the errors where occurring, and also my full diagnostics. Many thanks in advance for your help. syslog-witherrors.txt.zip ness-diagnostics-20160327-0759-noerrors.zip
  10. I'm getting these messages every few hours, although mine are happening on my Sata Controller (SAS2LP-MV8) followed by at a errors, and its causing parity errors, have reseated every cable and my card to the board, and still getting errors. Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67e000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67e000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:16 Ness kernel: dmar: DRHD: handling fault status reg 3 Mar 24 07:21:16 Ness kernel: dmar: DMAR:[DMA Write] Request device [04:00.0] fault addr ff67f000 Mar 24 07:21:16 Ness kernel: DMAR:[fault reason 05] PTE Write access is not set Mar 24 07:21:46 Ness kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Mar 24 07:21:46 Ness kernel: sas: trying to find task 0xffff8802233da200 Mar 24 07:21:46 Ness kernel: sas: sas_scsi_find_task: aborting task 0xffff8802233da200 Mar 24 07:21:46 Ness kernel: sas: sas_scsi_find_task: task 0xffff8802233da200 is aborted Mar 24 07:21:46 Ness kernel: sas: sas_eh_handle_sas_errors: task 0xffff8802233da200 is aborted Mar 24 07:21:46 Ness kernel: sas: ata10: end_device-1:3: cmd error handler Mar 24 07:21:46 Ness kernel: sas: ata7: end_device-1:0: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata8: end_device-1:1: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata9: end_device-1:2: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata10: end_device-1:3: dev error handler Mar 24 07:21:46 Ness kernel: ata10.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen Mar 24 07:21:46 Ness kernel: ata10.00: failed command: READ FPDMA QUEUED Mar 24 07:21:46 Ness kernel: ata10.00: cmd 60/00:00:10:bb:f6/04:00:fa:00:00/40 tag 2 ncq 524288 in Mar 24 07:21:46 Ness kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Mar 24 07:21:46 Ness kernel: ata10.00: status: { DRDY } Mar 24 07:21:46 Ness kernel: ata10: hard resetting link Mar 24 07:21:46 Ness kernel: sas: ata11: end_device-1:4: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata12: end_device-1:5: dev error handler Mar 24 07:21:46 Ness kernel: sas: ata13: end_device-1:6: dev error handler Mar 24 07:21:46 Ness kernel: sas: sas_form_port: phy0 belongs to port3 already(1)! Mar 24 07:21:48 Ness kernel: drivers/scsi/mvsas/mv_sas.c 1430:mvs_I_T_nexus_reset for device[0]:rc= 0 Mar 24 07:21:49 Ness kernel: ata10.00: configured for UDMA/133 Mar 24 07:21:49 Ness kernel: ata10.00: device reported invalid CHS sector 0 Mar 24 07:21:49 Ness kernel: ata10: EH complete Mar 24 07:21:49 Ness kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1
  11. I've never tried redirecting Plex to my own domain name. Is there a particular reason why you want to do so? I think you may find yourself in somewhat uncharted territory here tbh. I have my own site setup with some stats on the main page, a link to PlexRequests, which is proxy'd and I thought I could do Plex also, I guess i will just have to just make it a link to http://www.plex.tv/web/app
  12. I have my apache server setup on port 90 and my router redirects from 90 to 80, so when accessing my http://mydomain.ddns.net I get my apache server okay, have gotten plexrequests proxy setup, and tried setting up Plex but plex keeps changing the port in the url adding ":90" My default.conf file settings for Plex are... <Location /plex> ProxyPass http://10.0.0.11:32400/web ProxyPassReverse http://10.0.0.11:32400/web </Location> When accessing "http://mydomain.ddns.net/plex" Plex is redirecting from that url to "http://mydomain.ddns.net:90/plex/index.html" Can't figure out why its adding the port, or how to stop it.
  13. Hey, I'm having a problem I just can't figure out how to fix... My uTorrent runs on a MacMini, which I use automator to either extract or copy the .mkv file to my unRAID server into Filebot's /input folder. But Filebot will sometimes start processing the file before the MacMini has finished extracting or copying the file, thus leading to the resulting file, that has been moved to Plex's folder being corrupt. Here is the following settings in filebot.conf SETTLE_DURATION=03:00 MAX_WAIT_TIME=59:00 MIN_PERIOD=00:10
  14. To use plexconnect on your unRAID server you will have to change the port for unRAIDs webGUI. The Apple TV will only use port 80 and 443 for receiving its content.
  15. Ahh yes that explains why after the restart it was cyberghosts fork, as I couldn't get the variable working either. The reason i'd prefer to pick any fork as, I have actually forked CyberGhost's fork and changed a few things and would love to use it.