karlpox

Members
  • Posts

    120
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

karlpox's Achievements

Apprentice

Apprentice (3/14)

1

Reputation

  1. parity check failed in a few minutes. server froze. so i just replaced all rams with new ones now. hopefully that fixes the problem.
  2. 2 of my rams are having errors and already removed. checking parity again now.
  3. So I have redid this 3 times. Once I start the array it runs ok for a few hours (2-3) then ultimately freezes. Sometimes the docker apps are still accessible but the unraid gui is not. Then later on everything just dies. With some random stuff on the screen. I used to have a mellanox 10g sfp+ card but already removed it. sobnology-diagnostics-20220625-1208.zip
  4. this is actually a 4tb cache drive (not ssd). and the 2 shares that are missing are supposed to use the said drive for cache.
  5. just noticed 2 of my shares went missing. thats actually where this all started. shares missing.
  6. yeah just the parity-check freezes everything is fine. also the docker apps doesnt work. even made a new docker image. sobnology-diagnostics-20220607-0950.zip
  7. The spam stopped lol thanks! sobnology-diagnostics-20220607-0038.zip
  8. Hey guys, I was wondering why my parity-check is freezing at 50+%? Ive already dont this 3 times already and it just freezes there. The ETA just doesnt update anymore as well. So im stuck. sobnology-diagnostics-20220606-1942.zip
  9. Things I did which has contributed to solving whatever problems i was encountering -changed usb -upgraded to a beta version of unraid (because i had a feeling that my existing unraid was corrupt) -upgraded firmware for both my LSI cards (9211 & 9207) -switched one of my drives with a new one -check for errors on all drives -scrub my cache
  10. Due to lots of crashes, my drives started dying i dont even have a good parity now because i did a new config.
  11. darn thats gonna takke a long time. did a last resort kinda thing. I updated my unraid to beta version. then i just found out that one of my lsi cards didnt update. need to update it if my server crashes again.
  12. updated the LSI cards. unraid still crashing. guess its time to change the board. I also keep getting this error before everything freezes Aug 26 13:44:23 sobnology kernel: kernel BUG at drivers/md/unraid.c:356! Aug 26 13:44:23 sobnology kernel: invalid opcode: 0000 [#1] SMP PTI Aug 26 13:44:23 sobnology kernel: CPU: 5 PID: 26228 Comm: mdrecoveryd Not tainted 5.10.28-Unraid #1
  13. Aug 26 03:02:21 sobnology root: /mnt/cache: 1.3 TiB (1453279731712 bytes) trimmed on /dev/sdg1 Aug 26 04:57:47 sobnology kernel: ata6.00: READ LOG DMA EXT failed, trying PIO Aug 26 04:57:47 sobnology kernel: ata6.00: exception Emask 0x0 SAct 0x20000 SErr 0x0 action 0x0 Aug 26 04:57:47 sobnology kernel: ata6.00: irq_stat 0x40000008 Aug 26 04:57:47 sobnology kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 26 04:57:47 sobnology kernel: ata6.00: cmd 60/78:88:20:b7:3f/03:00:04:00:00/40 tag 17 ncq dma 454656 in Aug 26 04:57:47 sobnology kernel: res 41/40:00:9c:b8:3f/00:00:04:00:00/00 Emask 0x409 (media error) <F> Aug 26 04:57:47 sobnology kernel: ata6.00: status: { DRDY ERR } Aug 26 04:57:47 sobnology kernel: ata6.00: error: { UNC } Aug 26 04:57:47 sobnology kernel: ata6.00: configured for UDMA/133 Aug 26 04:57:47 sobnology kernel: sd 6:0:0:0: [sdi] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 26 04:57:47 sobnology kernel: sd 6:0:0:0: [sdi] tag#17 Sense Key : 0x3 [current] Aug 26 04:57:47 sobnology kernel: sd 6:0:0:0: [sdi] tag#17 ASC=0x11 ASCQ=0x4 Aug 26 04:57:47 sobnology kernel: sd 6:0:0:0: [sdi] tag#17 CDB: opcode=0x28 28 00 04 3f b7 20 00 03 78 00 Aug 26 04:57:47 sobnology kernel: blk_update_request: I/O error, dev sdi, sector 71284892 op 0x0:(READ) flags 0x80000 phys_seg 64 prio class 0 Aug 26 04:57:47 sobnology kernel: ata6: EH complete Aug 26 05:40:03 sobnology kernel: ata6.00: exception Emask 0x0 SAct 0x100000 SErr 0x0 action 0x0 Aug 26 05:40:03 sobnology kernel: ata6.00: irq_stat 0x40000008 Aug 26 05:40:03 sobnology kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 26 05:40:03 sobnology kernel: ata6.00: cmd 60/00:a0:50:b2:3f/02:00:04:00:00/40 tag 20 ncq dma 262144 in Aug 26 05:40:03 sobnology kernel: res 41/40:00:84:b2:3f/00:00:04:00:00/00 Emask 0x409 (media error) <F> Aug 26 05:40:03 sobnology kernel: ata6.00: status: { DRDY ERR } Aug 26 05:40:03 sobnology kernel: ata6.00: error: { UNC } Aug 26 05:40:03 sobnology kernel: ata6.00: configured for UDMA/133 Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#20 Sense Key : 0x3 [current] Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#20 ASC=0x11 ASCQ=0x4 Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#20 CDB: opcode=0x28 28 00 04 3f b2 50 00 02 00 00 Aug 26 05:40:03 sobnology kernel: blk_update_request: I/O error, dev sdi, sector 71283332 op 0x0:(READ) flags 0x80700 phys_seg 58 prio class 0 Aug 26 05:40:03 sobnology kernel: ata6: EH complete Aug 26 05:40:03 sobnology kernel: ata6.00: exception Emask 0x0 SAct 0x1805128 SErr 0x0 action 0x0 Aug 26 05:40:03 sobnology kernel: ata6.00: irq_stat 0x40000008 Aug 26 05:40:03 sobnology kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 26 05:40:03 sobnology kernel: ata6.00: cmd 60/08:b8:88:b2:3f/00:00:04:00:00/40 tag 23 ncq dma 4096 in Aug 26 05:40:03 sobnology kernel: res 41/40:00:88:b2:3f/00:00:04:00:00/00 Emask 0x409 (media error) <F> Aug 26 05:40:03 sobnology kernel: ata6.00: status: { DRDY ERR } Aug 26 05:40:03 sobnology kernel: ata6.00: error: { UNC } Aug 26 05:40:03 sobnology kernel: ata6.00: configured for UDMA/133 Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#23 Sense Key : 0x3 [current] Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#23 ASC=0x11 ASCQ=0x4 Aug 26 05:40:03 sobnology kernel: sd 6:0:0:0: [sdi] tag#23 CDB: opcode=0x28 28 00 04 3f b2 88 00 00 08 00 Aug 26 05:40:03 sobnology kernel: blk_update_request: I/O error, dev sdi, sector 71283336 op 0x0:(READ) flags 0x100 phys_seg 1 prio class 0 Aug 26 05:40:03 sobnology kernel: BTRFS error (device sdg1): bdev /dev/sdi1 errs: wr 0, rd 79, flush 0, corrupt 0, gen 0 Aug 26 05:40:03 sobnology kernel: ata6: EH complete Aug 26 05:40:03 sobnology kernel: BTRFS info (device sdg1): read error corrected: ino 2254065 off 94208 (dev /dev/sdi1 sector 71283272) Aug 26 05:58:22 sobnology kernel: ata6.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x0 Aug 26 05:58:22 sobnology kernel: ata6.00: irq_stat 0x40000008 Aug 26 05:58:22 sobnology kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 26 05:58:22 sobnology kernel: ata6.00: cmd 60/60:d8:d0:04:72/02:00:16:00:00/40 tag 27 ncq dma 311296 in Aug 26 05:58:22 sobnology kernel: res 41/40:00:80:06:72/00:00:16:00:00/00 Emask 0x409 (media error) <F> Aug 26 05:58:22 sobnology kernel: ata6.00: status: { DRDY ERR } Aug 26 05:58:22 sobnology kernel: ata6.00: error: { UNC } Aug 26 05:58:22 sobnology kernel: ata6.00: configured for UDMA/133 Aug 26 05:58:22 sobnology kernel: sd 6:0:0:0: [sdi] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Aug 26 05:58:22 sobnology kernel: sd 6:0:0:0: [sdi] tag#27 Sense Key : 0x3 [current] Aug 26 05:58:22 sobnology kernel: sd 6:0:0:0: [sdi] tag#27 ASC=0x11 ASCQ=0x4 Aug 26 05:58:22 sobnology kernel: sd 6:0:0:0: [sdi] tag#27 CDB: opcode=0x28 28 00 16 72 04 d0 00 02 60 00 Aug 26 05:58:22 sobnology kernel: blk_update_request: I/O error, dev sdi, sector 376571520 op 0x0:(READ) flags 0x80000 phys_seg 22 prio class 0 Aug 26 05:58:22 sobnology kernel: ata6: EH complete Aug 26 05:58:22 sobnology kernel: ata6.00: exception Emask 0x0 SAct 0x8d000342 SErr 0x0 action 0x0 Does this error means both my cache drives have problems? sdg & sdi are both my 1tb ssd cache drives.
  14. already did the bios earlier this year actually and theres no update after that. its an old motherboard too. Any suggestion what else should I try?