DjShugaA

Members
  • Posts

    23
  • Joined

  • Last visited

DjShugaA's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Does anyone have any idea what causes this? tower-diagnostics-20191120-2029.zip
  2. Hi Sorry for asking if this has already been answered but is there any issues by using 2FA with PIA and this docker? (and deluge)
  3. I managed to fix it. Had to download a new openvpn.zip from pia and use different servers
  4. Hi I am also getting errors suddenly error log shows this 2018-09-13 09:25:11,249 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2018-09-13 09:25:20,648 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 11 retries left [info] Retrying in 10 secs... 2018-09-13 09:25:30,690 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 2018-09-13 09:25:30,691 DEBG 'start-script' stdout output: [info] 10 retries left [info] Retrying in 10 secs... 2018-09-13 09:25:40,732 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 9 retries left [info] Retrying in 10 secs... 2018-09-13 09:25:50,773 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 2018-09-13 09:25:50,773 DEBG 'start-script' stdout output: [info] 8 retries left [info] Retrying in 10 secs... in addition i also get the timeouts from the usenet servers. Using Newshosting/usenet.farm and PIA
  5. This is what i got after i ran a check on disk 9 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "" in shortform directory 8594108554 references invalid inode 64739253237559434 entry contains offset out of order in shortform dir 8594108554 junking entry "" in directory inode 8594108554 entry "-." in shortform directory 8594108554 references invalid inode 4503606069821564 junking entry "-." in directory inode 8594108554 entry "" in shortform directory 8594108554 references invalid inode 20548016897261568 entry #0 is zero length in shortform dir 8594108554, junking 4 entries corrected entry count in directory 8594108554, was 4, now 0 corrected i8 count in directory 8594108554, was 6, now 0 corrected directory 8594108554 size, was 299, now 6 corrected entry offsets in directory 8594108554 bogus .. inode number (0) in directory inode 8594108554, clearing inode number - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 2 - agno = 4 - agno = 0 - agno = 5 - agno = 3 - agno = 1 bogus .. inode number (0) in directory inode 8594108554, clearing inode number - agno = 6 - agno = 7 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... entry "Season 04" in dir ino 6442451068 doesn't have a .. entry, will set it in ino 8594108554. Invalid inode number 0x0 xfs_dir_ino_validate: XFS_ERROR_REPORT fatal error -- couldn't map inode 8594108554, err = 117 If i remove the -n tag and run the check again nothing happens.....
  6. Hi getting some wierd and disturbing errors in the log May 25 10:08:17 Tower kernel: XFS (md9): Internal error xfs_dir_ino_validate at line 224 of file fs/xfs/libxfs/xfs_dir2.c. Caller xfs_dir2_sf_verify+0x6a/0x1c5 [xfs] May 25 10:08:17 Tower kernel: CPU: 7 PID: 8943 Comm: shfs Not tainted 4.14.40-unRAID #1 May 25 10:08:17 Tower kernel: Hardware name: MSI MS-7885/X99A SLI PLUS(MS-7885), BIOS 1.D0 07/15/2016 May 25 10:08:17 Tower kernel: Call Trace: May 25 10:08:17 Tower kernel: dump_stack+0x5d/0x79 Anyone got any idea? tower-diagnostics-20180525-1011.zip
  7. Changed the breakout cable and tried to plug it into different sas port. No disks from that cable found at all. Plugged it back into the previous sas port and presto, all disks detected. Guess i have to rma the 9201-16i card.....
  8. The disk in question is Powered straight from the psu With no adapters. my data disks are on the Lian li hot swap backplanes (bp3sata), more incoming so all the disks are connected by them
  9. Hi I had some problems a while back with disks going disabled and couldnt figure out why. Some suggestions was changing the SATA cable, changing the psu etc So what i did was Changed PSU Installed a 9201-16i HBA card Bought new sff 8087 cables (some from ebay and some from a webshop) Ebay Webshop All disks are connected to the HBA except the cache drive. Now im getting these errors on two of the disks, one disk is unassigned and one is one of the parity drives Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 0 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 86 51 67 a8 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 2253481896 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 ad 1d 9c 20 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 2904398880 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 a4 db ea 10 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 2765875728 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 03 57 0c 94 d0 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 14345344208 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 03 57 0c 95 c0 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 14345344448 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 03 57 0c 95 e0 00 00 00 08 00 00 Mar 8 10:38:14 Tower kernel: print_req_error: I/O error, dev sdf, sector 14345344480 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 Sense Key : 0x2 [current] Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 ASC=0x4 ASCQ=0x0 Mar 8 10:38:14 Tower kernel: sd 13:0:3:0: [sdf] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 03 57 0c 96 00 00 00 00 08 00 00 Mar 8 10:38:52 Tower kernel: sd 13:0:3:0: [sdf] Synchronizing SCSI cache Mar 8 10:38:52 Tower kernel: sd 13:0:3:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Bought 2 more SFF 8087 cables from the local webshop today since these are perhaps higher quality than the ebay ones, will be here in couple of days Anyone got any idea what could be wrong this time ? tower-diagnostics-20180308-2051.zip
  10. Update 2 Changed PSU and got a 9201-16i Got the same errors right after i installed the 9201 but only on 1 drive connected to the mainboard connected all drives except cache to the 9201 and no errors as of yet. and bonus...hotswap now works yay cache is still on mainboard *fingers crossed harder*
  11. Update Changed sata cable and plugged it into a cheap 2 port sata controller i had. No issues yet....*fingers crossed*
  12. i orderer these...they should be okey https://i.ebayimg.com/images/g/PFMAAOSwiLdWApX7/s-l1600.jpg
  13. havent changed it no but used molex to sata the last time i changed the parity drive hoping that was the cause. the psu is EVGA SuperNOVA G2 650W PSU
  14. Parity drives last between couple of days to 1 week now. Tried different drives, change power cables, changed sata cables. I suspect its the motherboard but never encountered this type of error before. System was stable when i had less disks (5-6 compared to 10, increased slowly over time) If i test the disk on a windows computer with seagate tools it reports no errors. Anyone have any idea? tower-diagnostics-20180102-1923.zip