Jump to content

sdesbure

Community Developer
  • Content Count

    39
  • Joined

  • Last visited

Everything posted by sdesbure

  1. Hello, seems to be an user permission. Look if permissions of your folder is OK
  2. Well, I think that's because there's no answer from the trackers (I have the same with t411.io...). They tried to only answers with results from the category but it screws sonar...
  3. The update is there and you have to check because I never had the issue...
  4. Hello, update for Jackett is ongoing and should be there within an hour!
  5. Hello, I was on holidays without laptop sorry. I did update jackett to 0.6.3 2 days ago and 0.6.4 today.
  6. Hello this is the continuation of the questions I've asked in preclear topic. Since it's a 6.0 Unraid that I have, it seems to be more efficient to put it there : I tried a new preclear but I stopped at the "start" of the pre read (running et less than 1MB/S...). Attached smart status (which seems clear...) and the syslog (where we see the errors shown before, but no other ones...). I tried with another HDD on the same SATA Card (but not port) and It worked smoothly. To be honest, I think that I'll return the HDD to amazon. What do you think? smart.txt syslog-pre-clear-2015-08-02.txt
  7. Hello Robj. First, Thank you for answering. Second, I didn't saw the "Read Me first" and I apologize for that. In order to check if the issue was from the disk or for any other stuff, I've started a preclear on a spare drive (1Tb this one). So I had to reboot... I'll wait for the preclear to be finished and I'll start back the preclear on the 3Tb (because it's so far so good on the 1Tb disk). And I'll create a topic accordingly. Thanks again, Sylvain
  8. Hello Guys, I bought a new hard drive on friday and installed it on my NAS (unraid 6.0.1). it's a WD 3T (WDC_WD30EZRX-00D8PB0_WD-WMC4N0JAPE9L) So I used preclear script in order to clear it using the web plugin (from gfjardim). After a long pre read part (starting from 4.4Mb/s, ending à ~75MB/s), my disk went to preclear but a lot more faster (~220 MB/s). At the end of the process, the system was weird (no possibility to see the exit of the command) so I decided to reboot and redo (withour pre / post read) And I have this error: ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 3:34:17 ========================================================================1.15 == == SORRY: Disk /dev/sde MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000240382 s, 0.0 kB/s 0000000 I took a look into /var/log/messages and there's huge amount of this comments: Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: 139 callbacks suppressed Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 0 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 00 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860532992 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 00 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860532992 Aug 1 13:54:19 nas kernel: buffer_io_error: 134 callbacks suppressed Aug 1 13:54:19 nas kernel: Buffer I/O error on dev sde, logical block 732566624, async page read Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 a0 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860533152 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 a0 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860533152 Aug 1 13:54:19 nas kernel: Buffer I/O error on dev sde, logical block 732566644, async page read Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 0 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 0 Aug 1 13:54:19 nas kernel: Buffer I/O error on dev sde, logical block 0, async page read Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 08 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 8 Aug 1 13:54:19 nas kernel: Buffer I/O error on dev sde, logical block 1, async page read Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 a8 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860533160 Aug 1 13:54:19 nas kernel: Buffer I/O error on dev sde, logical block 732566645, async page read Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 13:54:19 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5d 50 a3 a8 00 00 00 08 00 00 Aug 1 13:54:19 nas kernel: blk_update_request: I/O error, dev sde, sector 5860533160 and also some of these errors: Aug 1 10:21:14 nas kernel: ata2.00: exception Emask 0x0 SAct 0x1fffffff SErr 0x0 action 0x6 frozen Aug 1 10:21:14 nas kernel: ata2.00: failed command: WRITE FPDMA QUEUED Aug 1 10:21:14 nas kernel: ata2.00: cmd 61/e8:00:b8:b8:09/07:00:00:00:00/40 tag 0 ncq 1036288 out Aug 1 10:21:14 nas kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 1 10:21:14 nas kernel: ata2.00: status: { DRDY } ... Aug 1 10:21:14 nas kernel: ata2.00: status: { DRDY } Aug 1 10:21:14 nas kernel: ata2: hard resetting link Aug 1 10:21:24 nas kernel: ata2: softreset failed (timeout) Aug 1 10:21:24 nas kernel: ata2: hard resetting link Aug 1 10:21:34 nas kernel: ata2: softreset failed (timeout) Aug 1 10:21:34 nas kernel: ata2: hard resetting link Aug 1 10:22:09 nas kernel: ata2: softreset failed (timeout) Aug 1 10:22:09 nas kernel: ata2: limiting SATA link speed to 1.5 Gbps Aug 1 10:22:09 nas kernel: ata2: hard resetting link Aug 1 10:22:14 nas kernel: ata2: softreset failed (timeout) Aug 1 10:22:14 nas kernel: ata2: reset failed, giving up Aug 1 10:22:14 nas kernel: ata2.00: disabled Aug 1 10:22:14 nas kernel: ata2.00: device reported invalid CHS sector 0 ... Aug 1 10:22:14 nas kernel: ata2: EH complete Aug 1 10:22:14 nas kernel: sd 3:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Aug 1 10:22:14 nas kernel: sd 3:0:0:0: [sde] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 09 b0 d0 00 00 07 e8 00 00 Aug 1 10:22:14 nas kernel: blk_update_request: I/O error, dev sde, sector 635088 Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79386, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79387, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79388, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79389, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79390, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79391, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79392, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79393, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79394, lost async page write Aug 1 10:22:14 nas kernel: Buffer I/O error on dev sde, logical block 79395, lost async page write Any clue of what happened? Do I have to RMA the disk?
  9. Still having the same problem on my 2 trackers.... yep some trackers sometimes stops to work can you retest (version 0.5.1) ?
  10. thanks for the topic! I'm currently running plex directly on unraid ans was considering moving to a container (especially for auto update...). I'm waiting the answers of the owners now
  11. I built a new image with one more volume (/opt/Jackett/.config/Jackett) with should allow to make it work correctly. I have tested it and it work with my two trackers (and config is "saved").
  12. it's directly a build from git (my fork to add frenchtorrentdb). I'll check tonight sorry!
  13. Just woke up. Gimme an hour or two. Added. You should add the <Date> entry to the template so that it shows up in the new / updated list. If you're running CA using Kode's feed, then the app should be available within two hours. If you're not using Kode's feed with CA, the App is available immediately. (Working on an update to alleviate this to a certain extent) Hi and thanks! I'll test in the next 2 hours!
  14. Hi, I tested only with t411.io and frenchtorrentdb (that I have coded) where I have accounts. On which tracker do you have tested?
  15. Hello, not sure it's the right place but can you add my repository to the list? (this one https://github.com/sdesbure/docker-containers) thanks!
  16. Hello, I've created a Jackett Container for Unraid (with the xml description) --> https://lime-technology.com/forum/index.php?topic=41543.0
  17. Description Docker Images built on top of archlinux thanks to binhex (see it's awesome support page) Installation (stolen from binhex support page) OK, sounds good to me, so how do i install your Docker apps using unRAID?. Firstly you need to be running unRAID ver 6 beta 9 or later, once installed follow the instructions below:- Navigate to "Extensions" and then "Docker" in the unRAID webui Enter in a URL of https://github.com/sdesbure/docker-containers in the "Template repositories" field Click on the "Save" button Click back to "Extensions" menu and then click on the "Add" button Click on the "Template" dropdown menu and select the desired Docker image Click the "Advanced View" toggle on the top right and fill in required fields e.g. volume data, environment variables etc Click on the "Add" button at the bottom of the window to begin pulling down the Docker image Once the image is downloaded you should see it appear in the "Extensions" section under the heading "Docker Apps" Docker Apps I have colour coded each application as follows (again as binhex):- green - confirmed working, no known issues orange - needs enhancements/under testing red - currently broken/wip. Jackett: https://github.com/zone117x/Jackett Netatmo_Librato Domoticz: https://www.domoticz.com/ Links GitHub https://github.com/sdesbure Docker https://hub.docker.com/u/sdesbure/ Changelog https://raw.githubusercontent.com/sdesbure/docker-containers/master/CHANGELOG.md News First release of Jackett!! First release of Netatmo_Librato Moved Jackett to 0.6.4 Added Domoticz server
  18. Upgraded from rc6a with a realtek NIC (RTL8168C/8111C). It seems that I use r8168. Everything seems to work as fine as before
  19. I'll put here http://lime-technology.com/forum/index.php?topic=13257.0 the packages I have upgraded for 5.0 unRaid. There's now just OpenSSL and OpenSSH
  20. Hi, I have moved some packages (their conf files actually) to make them aligned with slackware 13.x Here are the two firsts: Openssl-solibs Openssh openssl-unmenu-package.conf openssh-unmenu-package.conf
  21. The solution for the web-gui is simple: see here: http://lime-technology.com/forum/index.php?topic=10840.msg103297#msg103297 Hi JoeL and Defected07. I saw that afterward that I needed to erase php. In order to make work Plex Media Server, I also needed to not install gcc and al from unmenu. Actually, what would be awesome is an "5.0" version of unMenu whith 13.1 slackware packages You are more than welcome to create a new .conf file for the newer version of gcc. Just name it after the "gcc" version, put a new set of 13.1 URLS and MD5 checksums in it, and it should just work. You can copy the existing compile .conf file and most of it will be exactly the same. I advise AGAINST using anything from slackware/current, since the files there (in "current") change quickly and the file names will not be the same in a few months when they get replaced with newer versions. If you can find/use a slackware/13.1/ hierarchy, it would be perfect. I will actually do that first for Python I think (I'm using FlexGet so I need that) and I will give you the links. For GCC, as soon as I need it I'll do it to if nobody has done it before
  22. The solution for the web-gui is simple: see here: http://lime-technology.com/forum/index.php?topic=10840.msg103297#msg103297 Hi JoeL and Defected07. I saw that afterward that I needed to erase php. In order to make work Plex Media Server, I also needed to not install gcc and al from unmenu. Actually, what would be awesome is an "5.0" version of unMenu whith 13.1 slackware packages