R__

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by R__

  1. 51 minutes ago, dlandon said:

    UD tracks a disk by its serial number as that is the only reliable thing to use because other things like the sdX device designation can change.  Because UD tracks devices by serial number, if you have duplicates, UD thinks they are all one disk and any thing done on one disk, is also done the the other as you've seen.

     

    Your external USB bay is presenting several disks with the same serial number.  UD can't handle this situation.

    That makes sense, however, like I mentioned the other two disks (who also share the same serial) can be independently mounted/unmounted successfully. Is there a way to reset the mount point name for the one that now both have "movies-archive" assigned to their defaults, so I can use them independently?

  2. Hi, I'm not quite sure how I got in this situation, but two of my disks have the same mount point, which leads to obvious issues when mounting/unmounting (they both mount/unmount at the same time, but only one of the disk's contents shows up under /mnt/disks/mountpointname.

     

    Is there a way to fix this? These are both disks in an external USB enclosure. The other 2 disks in the same enclosure both have unique mount points.

     

    Thanks!

  3. Hi all,

     

    I'm not quite sure how I got in this situation, but two of my disks have the same mount point, which leads to obvious issues when mounting/unmounting (they both mount/unmount at the same time, but only one of the disk's contents shows up under /mnt/disks/mountpointname.

     

    Is there a way to fix this? These are both disks in an external USB enclosure. The other 2 disks in the same enclosure both have unique mount points.

     

    Thanks!

  4. Hi all,

     

    I've been using Unraid for a little over half a year now, but I have one issue that has plagued me since the start: I have a specific share (called homes) that I'm unable to connect to over SMB. I get error messages on both Windows and macOS (multiple PCs) when trying to open the share, even though it's configured exactly the same as some other shares (all of which work fine over SMB). I can browse the folder in a terminal session just fine and browsing through Unraid's web interface also works. 

     

    The error I'm getting on Windows is:

    Windows cannot access \\***\homes

    Error code: 0x80070043

    The network name cannot be found.

     

    I have checked the share settings multiple times:

    homes

    Export: Yes

    Case-sensitive names:  Auto

    Security:  Private

     

    And the user I'm connecting with has Read/Write access (like my other shares).

     

    I have no clue why this one specific share doesn't want to connect. I've already tried SMB 1.0 support in Windows features and enabling insecure guest logins through Group Policy, but nothing had an effect (sort of expected, since the problem is across Windows and macOS clients).

     

    Hoping you have some sort of clue to help me figure this out. Thanks!