Jump to content

graywolf

Members
  • Content Count

    654
  • Joined

  • Last visited

Community Reputation

5 Neutral

About graywolf

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    NC

Recent Profile Visitors

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

  1. I'm having the same thing happen to me. Downloads but fails in post-processing. I have touch the config settings for sabnzb or sickrage in ages.
  2. Just got back home. Red Ball - Drive 14 - Advice? The SMART looks fine (I think) What actions should I take? Diagnostics file attached tower-diagnostics-20180617-0909.zip Looks like it occurred around Jun 13 04:37:37
  3. Thanks John_M. Shut down Checked cables Start up Running extended SMART test We'll see how it goes (fingers crossed)
  4. Diagnostic file tower-diagnostics-20180520-0957.zip
  5. Been so long and many versions ago since had an issue. First time since been on xfs Trying to find the troubleshooting link to determine what to do next. Please help point me in the right direction May 20 04:40:01 Tower root: Fix Common Problems Version 2018.04.25 May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 Sense Key : 0x3 [current] May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 ASC=0x11 ASCQ=0x0 May 20 04:43:06 Tower kernel: sd 7:0:3:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 02 35 2f 28 00 00 04 00 00 00 May 20 04:43:06 Tower kernel: print_req_error: critical medium error, dev sde, sector 37039912 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039848 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039856 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039864 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039872 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039880 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039888 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039896 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039904 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039912 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039920 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039928 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039936 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039944 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039952 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039960 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039968 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039976 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039984 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37039992 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040000 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040008 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040016 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040024 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040032 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040040 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040048 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040056 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040064 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040072 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040080 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040088 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040096 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040104 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040112 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040120 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040128 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040136 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040144 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040152 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040160 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040168 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040176 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040184 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040192 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040200 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040208 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040216 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040224 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040232 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040240 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040248 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040256 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040264 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040272 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040280 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040288 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040296 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040304 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040312 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040320 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040328 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040336 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040344 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040352 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040360 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040368 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040376 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040384 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040392 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040400 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040408 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040416 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040424 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040432 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040440 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040448 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040456 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040464 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040472 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040480 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040488 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040496 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040504 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040512 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040520 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040528 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040536 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040544 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040552 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040560 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040568 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040576 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040584 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040592 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040600 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040608 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040616 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040624 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040632 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040640 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040648 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040656 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040664 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040672 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040680 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040688 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040696 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040704 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040712 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040720 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040728 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040736 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040744 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040752 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040760 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040768 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040776 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040784 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040792 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040800 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040808 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040816 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040824 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040832 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040840 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040848 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040856 May 20 04:43:06 Tower kernel: md: disk14 read error, sector=37040864
  6. Thanks @Tybio for providing the logs. @jbrodriguez I assume you don't need logs from me since @Tybio already provided. I was getting same type of info in my log
  7. Question regarding Gather. I see when done it copied all that I wanted to the desired drive but I had to go back and delete from the old drives manually what was copied. Used the default options.
  8. BTW. Looking forward to the Gather function. Been meaning to consolidate some shares to specific drives but have not done it yet due to time constraints. How close are you for it?
  9. Going from memory since not near machine. Tools tab. Docker safe permission (think part of fix common problem plugin)
  10. You do know that a Parity Drvie does not have a files system per se. it is just a collection of bits based upon the bits on the sectors on the other drives. As I (and others) have mentioned, collect the diagnostic files and post them to get help. Otherwise maybe unRaid is not for you and you should find some other solution. unRaid is not perfect, nor is it for everyong, but it works great for me and many others. Best of luck in finding a solution that makes you happy and satisfied
  11. As far as adding drives to a parity protected array that you read up on the preclear script. Will be handy
  12. Another tip. If you have problems, collect the diagnostics file and post it. Type diagnostics at cmd line or thru the GUI. Doing that folks could have identified USB or other issues and provide recommendations. As as others have said, 24/7 power consumption can be greatly minimized by using spin down functionality. Several of your general statements were very negative and off putting. Initial reaction was "screw him" but I will take it as initial frustration and hope your experience (and attitude) get better now past the USB drive issue.
  13. Shutdown the box then the preclear ends. Not restartable in place. But each cycle is separate. So if you do 3 cycles and shutdown in middle of cycle 2 then you can rerun preclear with 2 cycles to get your full 3 cycles I have a spare tower with hot swap bays I use for preclear using a trial key (no drives assigned to it)
  14. I was thinking along the lines of a configurable setting for the location. Exactly. Have it automatically backed up to a configurable location whenever the array is started with a changed configuration (based on file date/timestamp?)