neebski

Members
  • Posts

    21
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

neebski's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I have had continuing problems with drives disconnecting. First it was one of my cache drives now it is an array drive. When I had this issue in the past I moved all my sata connections from the motherboard to new sata controller cards (except two). I just moved my other cache drive from the moterboard sata controller to a pci card. I've tried so many combinations of connections. Also I have replaced the sata cables. Does anyone have any suggestions? I am so frustrated I don't know what else to do at this point. It has made the server nearly useless. Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 1968417, flush 117859, corrupt 198, gen 59 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 438458, flush 2784, corrupt 99, gen 154 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 438459, flush 2784, corrupt 99, gen 154 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 1968418, flush 117859, corrupt 198, gen 59 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 438460, flush 2784, corrupt 99, gen 154 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 1968419, flush 117859, corrupt 198, gen 59 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 438461, flush 2784, corrupt 99, gen 154 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 1968420, flush 117859, corrupt 198, gen 59 Oct 19 21:37:47 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 438462, flush 2784, corrupt 99, gen 154 Oct 19 21:37:49 NeberServ1 kernel: ata24: SATA link down (SStatus 0 SControl 300) Oct 19 21:37:49 NeberServ1 kernel: ata23: SATA link down (SStatus 0 SControl 300) Oct 19 21:37:50 NeberServ1 kernel: ata23: SATA link down (SStatus 0 SControl 300) Oct 19 21:37:52 NeberServ1 kernel: ata24: SATA link down (SStatus 0 SControl 300) Oct 19 21:38:55 NeberServ1 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdf Oct 19 21:40:06 NeberServ1 kernel: btrfs_dev_stat_print_on_error: 52808 callbacks suppressed Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 2001655, flush 117859, corrupt 198, gen 59 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 458037, flush 2784, corrupt 99, gen 154 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 458038, flush 2784, corrupt 99, gen 154 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 2001656, flush 117859, corrupt 198, gen 59 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 458039, flush 2784, corrupt 99, gen 154 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdh1 errs: wr 4918395, rd 2001657, flush 117859, corrupt 198, gen 59 Oct 19 21:40:06 NeberServ1 kernel: BTRFS error (device sdh1): bdev /dev/sdi1 errs: wr 681555, rd 458040, flush 2784, corrupt 99, gen 154 Oct 19 21:40:48 NeberServ1 kernel: veth9c3bf80: renamed from eth0 Oct 19 21:40:48 NeberServ1 kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings. Oct 19 21:40:52 NeberServ1 kernel: veth5cabe79: renamed from eth0 Oct 19 21:40:52 NeberServ1 kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings. Oct 19 21:40:55 NeberServ1 kernel: vethf15100b: renamed from eth0 Oct 19 21:40:55 NeberServ1 kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings. Oct 19 21:40:59 NeberServ1 kernel: vethdf43bf3: renamed from eth0 Oct 19 21:40:59 NeberServ1 kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings. Oct 19 21:40:59 NeberServ1 kernel: vethf9f266e: renamed from eth0 Oct 19 21:40:59 NeberServ1 kernel: igb 0000:04:00.0 eth0: mixed HW and IP checksum settings. Oct 19 21:41:10 NeberServ1 emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/disk_log sdf Oct 19 21:43:38 NeberServ1 emhttpd: error: mdcmd, 2723: No such file or directory (2): write Oct 19 21:43:38 NeberServ1 kernel: mdcmd (46): spindown 3 Oct 19 21:43:38 NeberServ1 kernel: md: do_drive_cmd: lock_bdev error: -2 Oct 19 21:43:43 NeberServ1 emhttpd: error: mdcmd, 2723: No such file or directory (2): write Oct 19 21:43:43 NeberServ1 kernel: mdcmd (47): spindown 3 Oct 19 21:43:43 NeberServ1 kernel: md: do_drive_cmd: lock_bdev error: -2 neberserv1-diagnostics-20201019-2149.zip
  2. I'm not sure why I am unable to access anything. Only way I've been able to connect is by using Safari and that only gets me to the WEBUI. I've attached my diagnostics if that is any help. Any suggestions would be greatly appreciated. neberserv1-diagnostics-20200214-1822.zip
  3. Thank you. Seems like I'm having an issue with one of my sata controllers so I have two new ones on order. Once they are replaced I'll be able to work on this.
  4. I attached the entire page unraid cache.txt
  5. Besides the age of Unraid what can I do to resolve this?
  6. No strange issues to report. All my dockers and shares went offline and my cache drive says Unmountable: No file system. Any suggestions? neberserv1-diagnostics-20191219-1255.zip
  7. I have several containers that I need to have their own IPs in order to route them through my routers VPN, all other traffic is fine to go over standard network. Unfortunately I've noticed that the dockers that are using br0 are unable to communicate with each other thus I'm not able to use nginx to route to these containers. What is the best way of doing this? I'm sure further information will be needed but please let me know where to start. Thank you!
  8. Thanks @trurl I did as instructed and it worked great until this morning. I must have some sort of hardware issue with the cables or controller. Will have to troubleshoot further.
  9. I've read through several other topics as to why this might be happening. I can run smart tests on the drive so I know its still connected. It just passed a quick smart test and is currently running a long but I wanted to jump on here with the current smart data and see if anyone could tell me what I might be missing. A little bit of background - I just yesterday had to run an xfs_repair -L on my cache disk since it wasn't mounting. It fixed the problem for about 24 hours. I again today had to run it and after I restarted the server this disk is disabled and emulated. PS is there an in depth guide to what all these values mean? If so it would really help my troubleshooting. 1 Raw read error rate 0x000f 113 100 006 Pre-fail Always Never 52351040 3 Spin up time 0x0003 092 091 000 Pre-fail Always Never 0 4 Start stop count 0x0032 098 098 020 Old age Always Never 2555 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 085 060 030 Pre-fail Always Never 14170308924 9 Power on hours 0x0032 076 076 000 Old age Always Never 21026 (2y, 4m, 22d, 2h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 276 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command timeout 0x0032 100 087 000 Old age Always Never 28 28 32 189 High fly writes 0x003a 097 097 000 Old age Always Never 3 190 Airflow temperature cel 0x0022 071 051 045 Old age Always Never 29 (min/max 20/29) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 5 193 Load cycle count 0x0032 042 042 000 Old age Always Never 116710 194 Temperature celsius 0x0022 029 049 000 Old age Always Never 29 (0 17 0 0 0) 195 Hardware ECC recovered 0x001a 113 100 000 Old age Always Never 52351040 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 4 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 15740h+33m+42.387s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 69635711756 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 743699718438 neberserv1-diagnostics-20180308-2025.zip
  10. @aptalca Most of your suggestions worked as intended, although I have a few issues when attempting to login to the WP install. Do you mind if I PM you about this?
  11. Also interested. I'm stuck right now trying to get a site to work that is running through cloudflare > nginx > apache-php (docker) > wordpress install. If I could just axe having to run apache docker that would be great. Does nginx have builtin php support?
  12. It was a pool but I removed the second a few days ago. The array is doing a rebuild so Ill post in a few hours with your suggestion results.
  13. @johnnie.black diagnostics attached neberserv1-diagnostics-20180126-1350.zip
  14. I'm having a bit of trouble mounting my cache drives, which poses an obvious problem. Could anyone point out anything I'm doing wrong here? Edit, I tried adding my logs and cli output here but it flagged it as spam. Here it is on dropbox.