JorgeB

Moderators
  • Posts

    60408
  • Joined

  • Last visited

  • Days Won

    630

Community Answers

  1. JorgeB's post in "Unmountable: Unsupported or no file system" Cache problem after update 6.12 - Docker containers do not start anymore was marked as the answer   
    If the only issue is the log tree this may help, don't stop the array and type:
    btrfs rescue zero-log /dev/mapper/sdb1 Then re-start array and post new dags
  2. JorgeB's post in Cache drive swap attempt leads to old drive as "Unmountable" was marked as the answer   
    Type N + return to keep the signature, then type
    write and hit return once more, then re-start array and post new diags.
  3. JorgeB's post in Issue with Docker/User Shares was marked as the answer   
    Jun 25 13:15:04 Tower kernel: XFS (sdd1): Please unmount the filesystem and rectify the problem(s) Cache filesystem is corrupt, check filesystem.
  4. JorgeB's post in CPU Cores Pegged! was marked as the answer   
    Filesystem Size Used Avail Use% Mounted on tmpfs 32M 32M 0 100% /run  
    tmpfs is full, I seem to recall other users running Plex or some other app excessively logging to /run, do a search for that.
  5. JorgeB's post in Parity drive listed errors was marked as the answer   
    Run an extended SMART test on party, but should be OK for now.
  6. JorgeB's post in 6.11.5 upgrade to 6.12 docker and key fault was marked as the answer   
    You likely have crack related stuff left on your go file, replace it with a stock go file from the download zip.
  7. JorgeB's post in SMART - Is my HDD faulty was marked as the answer   
    SMART looks OK and it passed the extended test, so everything points to a good disk.
  8. JorgeB's post in UNMOUNTABLE: UNSUPPORTED OR NO FILE SYSTEM was marked as the answer   
    You are running into a known issue, but it's not fixed yet, stop the array, click on each new disk and change filesystem form auto to xfs-encrypted, start array and they should now format.
  9. JorgeB's post in Problem creating new configuration with a new drive already containing data... was marked as the answer   
    Unraid requires a specific partition layout and MBR signature, a disk formatted with UD will also adhere to those.
     
    You can re-format with UD, copy the data, then add to array (if there's no parity installed yet).
  10. JorgeB's post in [Solved] Missing br0 network with UNRAID 6.12.0 was marked as the answer   
    br0 is up:
     
    br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet 10.22.33.100  netmask 255.255.255.0  broadcast 10.22.33.255  
    Start by updating to v6.12.1 stable.
  11. JorgeB's post in unraid goes unresponsive at least once per day was marked as the answer   
    Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  12. JorgeB's post in Server defaults to 169.xxx address was marked as the answer   
    You can try leasing a specific IP from the router, if that doesn't work assign a manual IP on the server (Settings -> Network Settings), make sure you assign an IP that is reserved in the DHCP server, i.e., one that cannot be assigned to a different device later.
  13. JorgeB's post in Starting array after upgrading to 6.12.1 stuck at Mounting ZFS Cache Pool (VERIFY3 failed) was marked as the answer   
    That's expected, since it's importing the pool the same way Unraid was trying to, pool corruption can be the result of a RAM issue, it would be a good idea to run a couple of memtest passes before proceding, then you can try importing the pool in read-only mode:
    zpool import -o readonly=on cache If it works backup and re-create the pool
  14. JorgeB's post in How can I build parity with additional space? was marked as the answer   
    First add the two data drives, start array, stop array, now you can add parity.
  15. JorgeB's post in My server crashed and now my cache is unmountable. was marked as the answer   
    If the log tree is the only issue this may help:
    btrfs rescue zero-log /dev/nvme2n1p1  
  16. JorgeB's post in Docker service failed to start was marked as the answer   
    Jun 24 10:24:09 ryan kernel: __vm_enough_memory: pid: 22222, comm: php-fpm, no enough memory for the allocation Jun 24 10:24:09 ryan kernel: php-fpm[22222]: segfault at 1568a92870a0 ip 00000000008dcd1b sp 00007fff6de4cf10 error 6 in php-fpm[600000+3c0000] likely on CPU 6 (core 2, socket 0) Jun 24 10:24:09 ryan kernel: Code: 85 ff 74 10 f6 47 04 40 75 0a 83 2f 01 75 05 e8 2b 75 fc ff 48 83 c3 20 49 39 dc 0f 84 8e fe ff ff 80 7b 09 00 74 d4 48 8b 3b <83> 2f 01 75 b0 e8 6b d7 fe ff eb c5 66 0f 1f 84 00 00 00 00 00 48 Jun 24 10:24:09 ryan nginx: 2023/06/24 10:24:09 [error] 2296#2296: *9916 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.178.90, server: , request: "POST /plugins/community.applications/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.178.103", referrer: "http://192.168.178.103/Apps" Jun 24 10:24:09 ryan php-fpm[2158]: [WARNING] [pool www] child 22222 exited on signal 11 (SIGSEGV) after 0.519772 seconds from start Jun 24 10:26:27 ryan kernel: __vm_enough_memory: pid: 24942, comm: php-fpm, no enough memory for the allocation  
    Were starting something at this time?
     
    Also see some other segfaults in the newer diags, so should really run memtest.
  17. JorgeB's post in parity check triggered on reboot was marked as the answer   
    The issues with tsdb2 disk start write from boot, and are constantly spamming the log, looks more like a connection issue, replace cables for that disk or swap it to a different controller.
  18. JorgeB's post in 6.11.5 Pool Name Does Not Match Share Config was marked as the answer   
    Change use cache= yes, choose new pool, apply, then change back to cache= no, apply
  19. JorgeB's post in Upgrade 6.11.5 to 6.12.1 and now no Web GUI was marked as the answer   
    DESCRIPTION[0,3]="vlanGigaTech" VLANID[0,3]="77" PROTOCOL[0,3]="ipv4" USE_DHCP[0,3]="no" IPADDR[0,3]="192.168.77.11"  
    This VLAN has the same IP as your main bond, I know you cannot have that with two NICs/bonds, not sure about VLANs, try changing that.
  20. JorgeB's post in User shares gone, Disk 1 Unmountable: Unsupported or no file system, data loss? was marked as the answer   
    Check filesystem on disk1.
  21. JorgeB's post in 6.12 to 6.12.1 (ZFS cache drive) not mounting was marked as the answer   
    Pool corruption can be the result of a RAM issue, it would be a good idea to run a couple of memtest passes before proceeding, then you can try importing the pool in read-only mode:
    zpool import -o readonly=on cache-medium If it works backup and re-create the pool
  22. JorgeB's post in keep crashing on 6.11.5 was marked as the answer   
    Nope, but start with RAM since it's a possibility and easy to test.
  23. JorgeB's post in What does the ZFS row mean when it's at 100 on the dashboard for system stats? was marked as the answer   
    Yes, that's the ARC stats, by default it's set to 1/8 installed RAM, and in normal use it should be at or near 100%, though should not be over 100%, possibly a display error, post output of:
    cat /proc/spl/kstat/zfs/arcstats | grep "^c"  
  24. JorgeB's post in 6.12.1 Docker Service failed to start | Cache pool Unmountable: Unsupported or no file system was marked as the answer   
    First copy the appdata back then recreate the docker image.
  25. JorgeB's post in No Network Connection after first Boot was marked as the answer   
    Realtek drivers with Linux are kind of hit and miss, the model you're using usually works, but try with a different NIC if possible, ideally from Intel.