Joss_G

Members
  • Posts

    7
  • Joined

  • Last visited

Joss_G's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Quick update on the issue. It's been 2 days and the log is at 1% so all seems to be OK now. Thanks so much again for the help and advice!
  2. Thanks so much, I've changed that and will let you know how it goes overt the next few days! I've also swapped the appdata to prefer as well, thank you for the tip/insight! Amazing.
  3. Hi all, The server log file fills to 100% in just a few days after a restart. I've hunted through the forums for a way to solve this issue but I cant seem to find a solution. I did have nerdpack installed and have uninstalled it, didn't help at all. I've got rid of quite a few idle bits and pieces, rested the server several times and nothing seems to stop the log filling to 100% in a matter of days. Any help at all would be most welcome and thanks so much in advance for any help you can offer! Attached the diagnostics file. dobbie-diagnostics-20210607-1357.zip
  4. Thanks, I will try swapping all the SATA cables today and see what happens (With crossed figures). As of this morning there are also a couple of errors that popped up as well, might be unrelated? Not sure? Jun 16 15:00:32 Dobbie emhttpd: shcmd (91676): echo 128 > /sys/block/sdd/queue/nr_requests Jun 16 22:16:36 Dobbie emhttpd: shcmd (92552): echo 128 > /sys/block/sdd/queue/nr_requests The above was from the Parity drive but there was also 2 similar log issues for each of the other drives?
  5. Thanks for the reply. I've run an extended SMART test as you suggested and it completed without error. I've attached the SMART report as well. dobbie-smart-20200616-1500.zip
  6. Sorry, thanks. I've attached the Diagnostics dobbie-diagnostics-20200616-0851.zip
  7. Hi All, I recently had to replace my Parity drive and I've been getting a lot of errors from it. I've done a bit of digging and a lot of people that have had similar errors think it might be the SATA cable? I'm really hoping it's not a dead drive, any help would be amazing! Jun 14 23:36:11 Dobbie kernel: ata5.00: exception Emask 0x0 SAct 0xff8000 SErr 0x0 action 0x0 Jun 14 23:36:11 Dobbie kernel: ata5.00: irq_stat 0x40000008 Jun 14 23:36:11 Dobbie kernel: ata5.00: failed command: READ FPDMA QUEUED Jun 14 23:36:11 Dobbie kernel: ata5.00: cmd 60/40:78:e8:af:66/05:00:06:00:00/40 tag 15 ncq dma 688128 in Jun 14 23:36:11 Dobbie kernel: ata5.00: status: { DRDY ERR } Jun 14 23:36:11 Dobbie kernel: ata5.00: error: { UNC } Jun 14 23:36:11 Dobbie kernel: ata5.00: configured for UDMA/133 Jun 14 23:36:11 Dobbie kernel: sd 5:0:0:0: [sdd] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jun 14 23:36:11 Dobbie kernel: sd 5:0:0:0: [sdd] tag#15 Sense Key : 0x3 [current] Jun 14 23:36:11 Dobbie kernel: sd 5:0:0:0: [sdd] tag#15 ASC=0x11 ASCQ=0x4 Jun 14 23:36:11 Dobbie kernel: sd 5:0:0:0: [sdd] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 06 66 af e8 00 00 05 40 00 00 Jun 14 23:36:11 Dobbie kernel: print_req_error: I/O error, dev sdd, sector 107393680 Jun 14 23:36:11 Dobbie kernel: ata5: EH complete