LoLig

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

LoLig's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Yes you can: in the WebGui go to Settings and there you'll see Scheduler -> from there you can schedule the Parity Check and the Mover Hope this answers your question.
  2. Thx for the answers and advice! I have rebuilt parity on my new 4TB disk and the former parity disk is preclearing (maybe I can hdparm after that but it's not necessary). I'll make sure to have HPA one at least one connected disk (currently on two data disks and on the flash drive). After that I will try to turn of the HPA, I think I've seen this option in the Bios. Thx again!
  3. Hey everybody, First off: system works normally... ...but: Recently update my setup, I now have: Gigabyte Z97P-D3 Intel i5-4460 CPU 16GB memory Also update the Parity drive to a 4TB WD so I could start updating all 2TB disks to 4TB in nearby future. So yesterday I added the first 4TB disk and precleared it, however when I wanted to start the array it said it was bigger then the Parity drive. So I did some reading and figured it should be the HPA problem with Gigabyte Motherboards. I ran: hdparm -N /dev/sd? /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 0/1, HPA is enabled /dev/sdb: max sectors = 3907027055/3907029168, HPA is enabled /dev/sdc: max sectors = 3907027055/3907029168, HPA is enabled /dev/sdd: max sectors = 488397168/488397168, HPA is disabled /dev/sde: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdf: max sectors = 7814037168/7814037168, HPA is disabled /dev/sdg: READ_NATIVE_MAX_ADDRESS_EXT failed: Input/output error /dev/sdh: max sectors = 3907029168/3907029168, HPA is disabled /dev/sdi: max sectors = 3907029168/3907029168, HPA is disabled sdg is the Parity drive.. and I haven't found out what that error message means. Any ideas how to fix it? is it even broken? Or just swap the parity drive with the new 4TB drive? Thx in advance! syslog.txt WDC_WD40EZRX-00SPEB0_WD-WCC4E7EXTY2N-20160410-1153.txt
  4. Ok fixed it I thought I had everything double checked.. Couch wasn't working cause i had it set to "Only scan new movie folder at remote XBMC servers", which doesn't work somehow. Deselecting that option made it work. And Sonarr didn't work because of some weird reason, fixed it with this: https://forums.sonarr.tv/t/solved-kodi-not-importing-newly-downloaded-episodes/4317/7 So nothing to do with Koma! Thx again, works great now
  5. Hey Sparkly, Got it all setup and functioning, except for the important part of updating the database... When Sonarr downloads and sends its command to update the library and clean, it only cleans. Same goes for couchotato, library doesn't get updated. I know you said "don't use Kodi's WebUI": but from there the update library button does update the library. Updating from Sonarr to the clients (HTPC and tablet) works. It's just the Headless Kodi that doesn't get updated.. Any ideas? Thx, LoLig