Jump to content

sdesbure

Community Developer
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

0 Neutral

About sdesbure

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  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!