Jump to content

gleech

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

 Content Type 

Posts posted by gleech

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted · Edited by gleech

    2 hours ago, dlandon said:

    That means that the code to check for duplicate mount points is working, but there seems to be an issue when mounting the devices.

     

    I can't figure this one out.  The only thing I can suggest for the moment is to reboot to see if that will straighten things out.

     

    I'm still looking into the code, but reading code is not the optimum way to find bugs.  I'd really like to reproduce your issue.

     

    I found the culprit. For some reason after my update to 6.10.3. Unraid added those disk label that I have on UD as Shares. That must be the duplicate entry on the log. The cctv label auto-mounted because Unraid did not created a Share with the same label, not sure why Unraid left this one. So I removed all the Shares with the same disk label as my UD, rebooted any everything is back to normal.

     

    Thank you for your help.

     

     

    unraid.jpg

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    57 minutes ago, dlandon said: 
    cat /var/state/unassigned.devices/disk_names.json

      

    root@Tower:~# cat /var/state/unassigned.devices/disk_names.json
{
    "sdj": "dev1",
    "sdk": "dev2",
    "sdh": "dev3",
    "sdg": "dev4",
    "sdb": "dev5",
    "sdf": "dev6",
    "sdi": "dev7"
}root@Tower:~#

     

     

     

     

    51 minutes ago, dlandon said:

      

    cat /var/state/unassigned.devices/share_names.json

     

      

    root@Tower:~# cat /var/state/unassigned.devices/share_names.json
{
    "sdj1": "nftd",
    "sdk1": "nftg",
    "sdh1": "nftf",
    "sdg1": "nftc",
    "sdb1": "nftb",
    "sdf1": "cctv",
    "sdi1": "nfte"
}root@Tower:~#

     

     

    Thank you for the help @dlandon.

    Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array

    in Plugin Support

    Posted

    11 hours ago, gleech said:

    I need help. I updated Unraid to 6.10.3 from 6.9.2. I have 7 disks in UD and I set it to auto-mount. Right after the update, only one disk was mounted, I tried to click the MOUNT button, it just spins and goes back to MOUNT. I tried to reboot and disable auto-mount, and still the same. Any idea how to resolve my issues. Thank you.

     

    3 hours ago, dlandon said:

    Post your diagnostics zip file.

     

    Thank you. Here is my diagnostics zip file.

    tower-diagnostics-20220618-0818.zip

    [support] digiblur's Docker Template Repository

    in Docker Containers

    Posted

    On 3/6/2022 at 5:43 AM, thostr said:

    Hello

    I am trying to set up zigbee2mqtt but having issues connecting to Web frondend. Both mosquitto broker and zigbee2mqtt has verified the connection.

    Frontend have started on 0.0.0.0:8080 and I have forwarded port in docker configuration. I just can't figure out what I am missing....

     

    What to do?

     

    EDIT: uploaded screenshots

     

     

    Try adding this one your yaml.

      

    frontend:
port: 9442

     

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted

    21 hours ago, limetech said:

    Correct.  Patch referenced earlier by @aw_ earlier in the topic has been applied to kernel used in 6.7.0-rc1.  Please confirm if this solves the issue.

    Confirmed. NVMe's with SM2262 controller passing through without problems.

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted

    2 hours ago, Initial.F said:

    The problem also seems to occur with NVMe's using the Silicon Motion SM2263 controller. In my case the Crucial P1 (CT500P1SSD8).

    I'm running version 6.7.0-rc1 and get the same error:

    internal error: qemu unexpectedly closed the monitor: 2019-01-23T17:55:09.769688Z qemu-system-x86_64: -device vfio-pci,host=82:00.0,id=hostdev0,bus=pci.4,addr=0x0: vfio 0000:82:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

    Device: [c0a9:2263] 82:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03)

    My Corsair MP510 NVMe with Phison PS5012-E12 controller passes through without any problems.
     

    I think the patch that was applied was only for the SM2262 controller. Maybe @aw_ can make another patch for the SM2263 controller.

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted

    3 hours ago, limetech said:

    Correct.  Patch referenced earlier by @aw_ earlier in the topic has been applied to kernel used in 6.7.0-rc1.  Please confirm if this solves the issue.

    I will report back once I solve my no video issues on my vm. But I think it's fine now since I'm not getting any error anymore on my Adata SX8200 using SM 2262 controller.

    NVME M.2 Passthrough

    in VM Engine (KVM)

    Posted

    Can some confirm with a working vm. I think this is already fix on the new 6.7 RC1 version.

     

    I have a vm setup but its not showing any video yet, I have to play with the video setting. But I'm not getting any error anymore if I passthrough my Adata SX8200.

×
×
  • Create New...