Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,042

  • Joined

  • Last visited

  • Days Won

    702

Community Answers

  1. JorgeB
    JorgeB's post in [Solved] Docker, plugins and My Server access problem was marked as the answer   
    Try simplifying you LAN as much as possible, also make sure date and time are correctly set, you can also delete/rename network.cfg and reboot in case there's some misconfiguration there, it will go back to using the defaults, if that doesn't help likely there's a LAN config problem,
  2. JorgeB
    JorgeB's post in [SOLVED] Docker service died. Cause: directory and shares issue. was marked as the answer   
    You need to remove "root" from Settings -> NFS -> Tunable (fuse_remember): leave it blank to use default value.
  3. JorgeB
    JorgeB's post in Excluding a disk was marked as the answer   
    Check the split level setting, it overrides that, if the folder exists there it will be copied there.
  4. JorgeB
    JorgeB's post in Files not appearing in /mnt/user/{share} was marked as the answer   
    Check filesystem on disk10.
  5. JorgeB
    JorgeB's post in Millions of Read Errors during Parity was marked as the answer   
    Formatted with type 1 protection  
    You need to remove this protection from the disks, more info below:
     
    https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078

    https://forums.unraid.net/topic/110835-help-with-a-sas-drive/
  6. JorgeB
    JorgeB's post in Discs suddenly switched to disabled was marked as the answer   
    Disk dropped offline, looks more like a power/connection problem.
  7. JorgeB
    JorgeB's post in 6.10.3 Unraid unstable and crashes! was marked as the answer   
    Switching to ipvlan should fix the problem (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
  8. JorgeB
    JorgeB's post in 6.11.0 final - EDID block 0 is all zeroes error was marked as the answer   
    Do you have a monitor plugged in? If not using a VGA or HDMI dummy plug *might* help.
  9. JorgeB
    JorgeB's post in Unbraid Community Help was marked as the answer   
    IPADDR="192.168.68.111" NETMASK="255.255.224.0" GATEWAY="192.168.681.1"  
    Note that the gateway is wrong (x.x.681.x)
  10. JorgeB
    JorgeB's post in (SOLVED) Server becomes unresponsive was marked as the answer   
    Start here:
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
     
  11. JorgeB
    JorgeB's post in I had to restart my server today as it wasn't responding and now the drives aren't showing up. was marked as the answer   
    Try clearing the browser cache and/or using a different browser, if that fails boot in safe mode.
  12. JorgeB
    JorgeB's post in Issues every couple days was marked as the answer   
    Start here:
    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
     
  13. JorgeB
    JorgeB's post in [Solved] Looking to migrate to Unraid question was marked as the answer   
    This.
  14. JorgeB
    JorgeB's post in Is my server about to crash? was marked as the answer   
    Once there's corruption updating won't fix anything, but it should prevent more, run a scrub, if corrupt files are found they will be listed in the syslog, delete/replace them from backups.
  15. JorgeB
    JorgeB's post in CLI shows disk offline but GUI shows disk fine was marked as the answer   
    Sep 19 23:36:23 Coruscant kernel: XFS (md7): Internal error rec.ir_free != frec->ir_free || rec.ir_freecount != frec->ir_freecount at line 1558 of file fs/xfs/libxfs/xfs_ialloc.c. Caller xfs_dialloc_ag_update_inobt+0xd0/0x121 [xfs]  
    Check filesystem on disk7.
  16. JorgeB
    JorgeB's post in IPv4 address: not set IPv6 address: not set was marked as the answer   
    NIC problems:
     
    Sep 22 02:16:58 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:16:58 Tower kernel: Tx Queue <0> Sep 22 02:16:58 Tower kernel: TDH <1000001> Sep 22 02:16:58 Tower kernel: TDT <1000001> Sep 22 02:16:58 Tower kernel: next_to_use <1> Sep 22 02:16:58 Tower kernel: next_to_clean <0> Sep 22 02:16:58 Tower kernel: buffer_info[next_to_clean] Sep 22 02:16:58 Tower kernel: time_stamp <fffbd99a> Sep 22 02:16:58 Tower kernel: next_to_watch <0> Sep 22 02:16:58 Tower kernel: jiffies <fffbe940> Sep 22 02:16:58 Tower kernel: next_to_watch.status <0> Sep 22 02:17:00 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:17:00 Tower kernel: Tx Queue <0> Sep 22 02:17:00 Tower kernel: TDH <1000001> Sep 22 02:17:00 Tower kernel: TDT <1000001> Sep 22 02:17:00 Tower kernel: next_to_use <1> Sep 22 02:17:00 Tower kernel: next_to_clean <0> Sep 22 02:17:00 Tower kernel: buffer_info[next_to_clean] Sep 22 02:17:00 Tower kernel: time_stamp <fffbd99a> Sep 22 02:17:00 Tower kernel: next_to_watch <0> Sep 22 02:17:00 Tower kernel: jiffies <fffbf140> Sep 22 02:17:00 Tower kernel: next_to_watch.status <0> Sep 22 02:17:01 Tower dhcpcd[1478]: br0: probing for an IPv4LL address Sep 22 02:17:02 Tower kernel: e1000 0000:03:01.0 eth0: Detected Tx Unit Hang Sep 22 02:17:02 Tower kernel: Tx Queue <0> Sep 22 02:17:02 Tower kernel: TDH <1000001> Sep 22 02:17:02 Tower kernel: TDT <1000001> Sep 22 02:17:02 Tower kernel: next_to_use <1> Sep 22 02:17:02 Tower kernel: next_to_clean <0> Sep 22 02:17:02 Tower kernel: buffer_info[next_to_clean] Sep 22 02:17:02 Tower kernel: time_stamp <fffbd99a> Sep 22 02:17:02 Tower kernel: next_to_watch <0> Sep 22 02:17:02 Tower kernel: jiffies <fffbf940> Sep 22 02:17:02 Tower kernel: next_to_watch.status <0> Sep 22 02:17:04 Tower kernel: ------------[ cut here ]------------ Sep 22 02:17:04 Tower kernel: NETDEV WATCHDOG: eth0 (e1000): transmit queue 0 timed out  
    Do you have a different one you could try with?
  17. JorgeB
    JorgeB's post in VMs not reachable via VNC was marked as the answer   
    Clear the browser cookies and try again.
  18. JorgeB
    JorgeB's post in BTRFS issues was marked as the answer   
    Cache2 dropped offline:
     
    Sep 14 04:40:02 Tower kernel: sd 2:0:0:0: [sdk] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Sep 14 04:40:02 Tower kernel: sd 2:0:0:0: [sdk] tag#22 CDB: opcode=0x2a 2a 00 00 00 08 80 00 00 08 00 Sep 14 04:40:02 Tower kernel: blk_update_request: I/O error, dev sdk, sector 2176 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 14 04:40:02 Tower kernel: BTRFS warning (device sdj1): lost page write due to IO error on /dev/sdk1 (-5)  
    Check/replace cables and also see here for better pool monitoring.
  19. JorgeB
    JorgeB's post in Array disk usage wrong, showing less used than actual value. was marked as the answer   
    Forgot to mention, you must run without -n or nothing will be done.
  20. JorgeB
    JorgeB's post in 6.9.2 --> 6.10.3; "You do not have permissions to access this server" was marked as the answer   
    /mnt/user permissions are wrong, don't ask me why they work with v6.9, but they are still wrong, type
    chmod 777 /mnt/user reboot and try again.
  21. JorgeB
    JorgeB's post in Is this drive toast? current pending sector is 672 was marked as the answer   
    Yes.
  22. JorgeB
    JorgeB's post in blk_update_request: I/O error was marked as the answer   
    It's logged as a disk problem but SMART looks mostly OK and the extended test passed, I would keep if for now, but any more errors on the next parity checks would recommend replacing.
  23. JorgeB
    JorgeB's post in Server Randomly Shutting Down was marked as the answer   
    Check fans and CPU temp, if the server shuts down vs crashing it's usually a hardware problem and not something easy to diag remotely, one thing you might want to confirm is that no shutdown command is being sent to Unraid, by for example a faulty power button, you can do that by enabling the syslog server and checking it or posting after the next shutdown.
     
    P.S. next time please post the diagnostics.zip, not all the files inside it.
  24. JorgeB
    JorgeB's post in Slow writes to Array was marked as the answer   
    2TB 2.5" drives will be SMR, what brand/model? Some SMR models, particularity by Seagate performe decently, SMR drives by Toshiba or WD can have several minutes writing below 5MB/s, even when doing sequential writes.
  25. JorgeB
    JorgeB's post in Unable to write to cache was marked as the answer   
    Sep 19 12:25:53 Tower kernel: BTRFS error (device sdf1): block=2395218591744 write time tree block corruption detected This usually means bad RAM or other kernel memory corruption, Ryzen with overclocked RAM like you have is known to corrupt data, so you should fix that, then run memtest.
     
     
    Sep 17 16:59:52 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Sep 17 16:59:52 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Unrelated, macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), or see below for more info.
×
×
  • Create New...