3 hours ago, Pri said:

Sorry this took so long, I had to wait for the problem to occur again. Which it just did:

Please post a link to your original post of the issue.

11 minutes ago, dlandon said:

Please post a link to your original post of the issue.

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/399/#comment-1312939

4 hours ago, Pri said:

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/399/#comment-1312939

I don't see anything that could be caused by UD, but why are you logging into SSH every minute?

Oct 18 09:52:02 HYEPYC sshd[5915]: Connection from 192.168.0.3 port 49458 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:52:02 HYEPYC sshd[5915]: Accepted password for root from 192.168.0.3 port 49458 ssh2
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:52:02 HYEPYC sshd[5915]: Starting session: command for root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Close session: user root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Received disconnect from 192.168.0.3 port 49458:11: 
Oct 18 09:52:02 HYEPYC sshd[5915]: Disconnected from user root 192.168.0.3 port 49458
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session closed for user root
Oct 18 09:53:02 HYEPYC sshd[10772]: Connection from 192.168.0.3 port 49839 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:53:02 HYEPYC sshd[10772]: Accepted password for root from 192.168.0.3 port 49839 ssh2
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:53:02 HYEPYC sshd[10772]: Starting session: command for root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Close session: user root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Received disconnect from 192.168.0.3 port 49839:11: 
Oct 18 09:53:02 HYEPYC sshd[10772]: Disconnected from user root 192.168.0.3 port 49839
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session closed for user root
Oct 18 09:54:02 HYEPYC sshd[14662]: Connection from 192.168.0.3 port 50286 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:54:02 HYEPYC sshd[14662]: Accepted password for root from 192.168.0.3 port 50286 ssh2
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:54:02 HYEPYC sshd[14662]: Starting session: command for root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Close session: user root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Received disconnect from 192.168.0.3 port 50286:11: 
Oct 18 09:54:02 HYEPYC sshd[14662]: Disconnected from user root 192.168.0.3 port 50286
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session closed for user root

 

Is that really necessary?

 

I also see three array disks (disk 1, disk 2, and disk 4) at 100% and very little on other disks.  You need to spread that out to keep disks below maybe 80 or 90%.  Full disks are not a good idea.

3 hours ago, dlandon said:

I don't see anything that could be caused by UD, but why are you logging into SSH every minute?

Oct 18 09:52:02 HYEPYC sshd[5915]: Connection from 192.168.0.3 port 49458 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:52:02 HYEPYC sshd[5915]: Accepted password for root from 192.168.0.3 port 49458 ssh2
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:52:02 HYEPYC sshd[5915]: Starting session: command for root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Close session: user root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Received disconnect from 192.168.0.3 port 49458:11: 
Oct 18 09:52:02 HYEPYC sshd[5915]: Disconnected from user root 192.168.0.3 port 49458
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session closed for user root
Oct 18 09:53:02 HYEPYC sshd[10772]: Connection from 192.168.0.3 port 49839 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:53:02 HYEPYC sshd[10772]: Accepted password for root from 192.168.0.3 port 49839 ssh2
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:53:02 HYEPYC sshd[10772]: Starting session: command for root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Close session: user root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Received disconnect from 192.168.0.3 port 49839:11: 
Oct 18 09:53:02 HYEPYC sshd[10772]: Disconnected from user root 192.168.0.3 port 49839
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session closed for user root
Oct 18 09:54:02 HYEPYC sshd[14662]: Connection from 192.168.0.3 port 50286 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:54:02 HYEPYC sshd[14662]: Accepted password for root from 192.168.0.3 port 50286 ssh2
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:54:02 HYEPYC sshd[14662]: Starting session: command for root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Close session: user root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Received disconnect from 192.168.0.3 port 50286:11: 
Oct 18 09:54:02 HYEPYC sshd[14662]: Disconnected from user root 192.168.0.3 port 50286
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session closed for user root

 

Is that really necessary?

 

I also see three array disks (disk 1, disk 2, and disk 4) at 100% and very little on other disks.  You need to spread that out to keep disks below maybe 80 or 90%.  Full disks are not a good idea.

 

There is software which logs in to run commands for docker. When the server is working properly it only needs to login very seldom. So that isn't me, it's automated software doing that.

 

All the disks have 100GB or more free, they're not at 100%, they're high capacity disks.

 

I've uninstalled the UD plugin for the time being to see if the crash still occurs because I too have no indication that it is UD, I'm just going by what the guy said on reddit and trying it. When he said, reinstall UD and it would fix it, for me I was getting these lockups daily until I reinstalled UD. At that point I had 16 days of uptime without issues until today.

 

So now I've uninstalled UD entirely and I'll leave it like that for at least 2 months or until I get a crash again which would rule out UD as the culprit entirely if that happens.

Having issue with making a remote smb mount of windows 11. Wanting to rsync some stuff to unraid originally.

 

tower-diagnostics-20231018-1542.zip

8 minutes ago, jcgeh2 said:

Having issue with making a remote smb mount of windows 11. Wanting to rsync some stuff to unraid originally.

The error code -13 typically indicates a permission issue or some form of authentication problem.  Try to not use special characters.  You are sharing the complete Windows disk and you need to be sure you have the disk set to share properly and with valid permissions for the user.

 

Let UD search for the server and shares.  If your permissions are set correctly, the shares will be listed.  If not, the shares won't show.

9 minutes ago, dlandon said:

The error code -13 typically indicates a permission issue or some form of authentication problem.  Try to not use special characters.  You are sharing the complete Windows disk and you need to be sure you have the disk set to share properly and with valid permissions for the user.

 

Let UD search for the server and shares.  If your permissions are set correctly, the shares will be listed.  If not, the shares won't show.

This time I let UD do its thing and selected server and shares for me. Is this normal, and how do I specify directory in a drive? Still failed to mount with code = -13. I think I should create a seperate local account and test from there.

Edited October 18, 20232 yr by jcgeh2

I just bought a Crucual P3 2TB NVME.

This will later replace my SSD cache disk but I through I would add it to unassigned devices first and so some writes to it to check it is all working ok.

It is shown on array start, so I clicked format.  BTRFS.

All said the usual things but it is not mountabel, and no mount button.

It has the circle/line thing, and UDEV next to it.

 

Logs :

 

Oct 19 09:41:03 Tower unassigned.devices: Formatting disk '/dev/nvme0n1' with 'btrfs' filesystem.
Oct 19 09:41:03 Tower unassigned.devices: Format drive command: /sbin/mkfs.btrfs -f '/dev/nvme0n1p1' 2>&1
Oct 19 09:41:06 Tower kernel: BTRFS: device fsid 1b423e96-8024-4ff6-84f7-afab8c5cac56 devid 1 transid 6 /dev/nvme0n1p1 scanned by mkfs.btrfs (16493)
Oct 19 09:41:07 Tower unassigned.devices: Format disk '/dev/nvme0n1' with 'btrfs' filesystem: btrfs-progs v6.3.3 See https://btrfs.readthedocs.io for more information.  Performing full device TRIM /dev/nvme0n1p1 (1.82TiB) ... NOTE: several default settings have changed in version 5.15, please make sure       this does not affect your deployments:       - DUP for metadata (-m dup)       - enabled no-holes (-O no-holes)       - enabled free-space-tree (-R free-space-tree)  Label:              (null) UUID:               1b423e96-8024-4ff6-84f7-afab8c5cac56 Node size:          16384 Sector size:        4096 Filesystem size:    1.82TiB Block group profiles:   Data:             single            8.00MiB   Metadata:         DUP               1.00GiB   System:           DUP               8.00MiB SSD detected:       yes Zoned device:       no Incompat features:  extref, skinny-metadata, no-holes, free-space-tree Runtime features:   free-space-tree Checksum:           crc32c Number of devices:  1 Devices:    ID        SIZE  PATH     1     1.82TiB  /dev/nvme0n1
Oct 19 09:41:10 Tower unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Oct 19 09:41:10 Tower kernel: nvme0n1: p1
Oct 19 09:41:10 Tower unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table

 

Image attached :

 

 

2 hours ago, jcgeh2 said:

This time I let UD do its thing and selected server and shares for me. Is this normal, and how do I specify directory in a drive? Still failed to mount with code = -13. I think I should create a seperate local account and test from there.

You have to specify permissions on the share in Windows for the user you want to have access.

2 hours ago, vw-kombi said:

I just bought a Crucual P3 2TB NVME.

This will later replace my SSD cache disk but I through I would add it to unassigned devices first and so some writes to it to check it is all working ok.

It is shown on array start, so I clicked format.  BTRFS.

All said the usual things but it is not mountabel, and no mount button.

It has the circle/line thing, and UDEV next to it.

Udev shows a different file system from the actual file system on the disk.  What file system shows on the UD page?  It's not in your screen shot.

 

Try the following:

• Click on the double arrows on the upper right of the UD page.  This refreshes udev and might straighten out the file system detection.
• Power down and reseat the nvme drive and reformat.

4 minutes ago, dlandon said:

Udev shows a different file system from the actual file system on the disk.  What file system shows on the UD page?  It's not in your screen shot.

 

Try the following:

• Click on the double arrows on the upper right of the UD page.  This refreshes udev and might straighten out the file system detection.
• Power down and reseat the nvme drive and reformat.

 

Jeez!  I just had to click refresh!!!!!

On 10/19/2023 at 1:14 AM, jcgeh2 said:

I think I should create a seperate local account and test from there.

Yes, you never want to use the default shares. Create a user and sepecifically create a share for the folders you want to access and give it RW permissions to that user.

On 10/18/2023 at 6:41 PM, dlandon said:

I don't see anything that could be caused by UD, but why are you logging into SSH every minute?

Oct 18 09:52:02 HYEPYC sshd[5915]: Connection from 192.168.0.3 port 49458 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:52:02 HYEPYC sshd[5915]: Accepted password for root from 192.168.0.3 port 49458 ssh2
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:52:02 HYEPYC sshd[5915]: Starting session: command for root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Close session: user root from 192.168.0.3 port 49458 id 0
Oct 18 09:52:02 HYEPYC sshd[5915]: Received disconnect from 192.168.0.3 port 49458:11: 
Oct 18 09:52:02 HYEPYC sshd[5915]: Disconnected from user root 192.168.0.3 port 49458
Oct 18 09:52:02 HYEPYC sshd[5915]: pam_unix(sshd:session): session closed for user root
Oct 18 09:53:02 HYEPYC sshd[10772]: Connection from 192.168.0.3 port 49839 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:53:02 HYEPYC sshd[10772]: Accepted password for root from 192.168.0.3 port 49839 ssh2
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:53:02 HYEPYC sshd[10772]: Starting session: command for root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Close session: user root from 192.168.0.3 port 49839 id 0
Oct 18 09:53:02 HYEPYC sshd[10772]: Received disconnect from 192.168.0.3 port 49839:11: 
Oct 18 09:53:02 HYEPYC sshd[10772]: Disconnected from user root 192.168.0.3 port 49839
Oct 18 09:53:02 HYEPYC sshd[10772]: pam_unix(sshd:session): session closed for user root
Oct 18 09:54:02 HYEPYC sshd[14662]: Connection from 192.168.0.3 port 50286 on 192.168.0.6 port 22 rdomain ""
Oct 18 09:54:02 HYEPYC sshd[14662]: Accepted password for root from 192.168.0.3 port 50286 ssh2
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Oct 18 09:54:02 HYEPYC sshd[14662]: Starting session: command for root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Close session: user root from 192.168.0.3 port 50286 id 0
Oct 18 09:54:02 HYEPYC sshd[14662]: Received disconnect from 192.168.0.3 port 50286:11: 
Oct 18 09:54:02 HYEPYC sshd[14662]: Disconnected from user root 192.168.0.3 port 50286
Oct 18 09:54:02 HYEPYC sshd[14662]: pam_unix(sshd:session): session closed for user root

 

Is that really necessary?

 

I also see three array disks (disk 1, disk 2, and disk 4) at 100% and very little on other disks.  You need to spread that out to keep disks below maybe 80 or 90%.  Full disks are not a good idea.

The problem happened again today even while Unassigned Devices and Unassigned Devices Plus were completely uninstalled. So the mystery continues and I shall make a thread for my issue with the latest diagnostics I took for todays lockup.

 

Thank you for your help

Hi

 

I added a 1 TB NVMe in a PCIe to M.2 adapter to my Unraid Server.

 

I managed to do "clear" and then "format".

 

However, the result is this and I cannot access the device:

 

Any recommendation what may be wrong here?

THX!

 

daNick

38 minutes ago, daNick73 said:

However, the result is this and I cannot access the device:

The 'Udev' marker on the mount button means udev is not reporting the same file system type as is on the device.  That's why 'FS' is blank.  Click on the double arrows icon an see if it sorts itself out.  That will refresh udev and it should clear up the situation.

 

What is the format you used on the device?

1 hour ago, dlandon said:

The 'Udev' marker on the mount button means udev is not reporting the same file system type as is on the device.  That's why 'FS' is blank.  Click on the double arrows icon an see if it sorts itself out.  That will refresh udev and it should clear up the situation.

 

What is the format you used on the device?

 

Amazing, that solved it, thx a lot!

 

And, in case anyone stumbles over this and doesnt know what the "double arrows icon" was (like stupid me  )

 

 

 

Hey all, 

 

I'm planning on installing a large SATA SSD as an unassigned device for gaming on the Headless-Steam container.

 

I'm looking for advice on what the current best way is of backing up the entirety of an unassigned device to a share on the array?

 

Cheers.

Im on latest Unraid 6.12.4 and i have an external HDD mounted and passed to a plex library, only one plex library is mounted, no other docker etc is mounted, it has been like this for months and never did my HDD spin up randomly only when someone was playing soemthing from library, from few weeks, my hdd seems to be contstantly running, nothing seems to pop up in both open files or file activity plugin

even unmounting the drive doesnt help as it still spins up

2 hours ago, Vyktrii said:

Im on latest Unraid 6.12.4 and i have an external HDD mounted and passed to a plex library, only one plex library is mounted, no other docker etc is mounted, it has been like this for months and never did my HDD spin up randomly only when someone was playing soemthing from library, from few weeks, my hdd seems to be contstantly running, nothing seems to pop up in both open files or file activity plugin

even unmounting the drive doesnt help as it still spins up

Post diagnostics.

Hey!

 

I was wondering if the detach option was removed recently, I used to have my disk detached but i no longer see an option to detach when I click on a disk. Thank you!

On 10/29/2023 at 12:06 AM, Johann said:

Hey!

 

I was wondering if the detach option was removed recently, I used to have my disk detached but i no longer see an option to detach when I click on a disk. Thank you!

No, but is is only available on the disk, and not on the partition.  Click on the disk line (line with the mount button) and it should be available.

I am trying to mount a NFS share from my TrueNAS computer, but it shows the mount point directory empty. How do I put in the credentials for the mount point?

12 hours ago, Hellomynameisleo said:

I am trying to mount a NFS share from my TrueNAS computer, but it shows the mount point directory empty. How do I put in the credentials for the mount point?

You set NFS rules in Settings->Unassigned Devices for access.

I've got a bit of an odd scenario. I've somehow got two separate USB drives that I plug in to do backups with that both have the same disk identification numbers. How is that even possible and how can I change the ID of one of the drives?

1 hour ago, Phredwerd said:

I've got a bit of an odd scenario. I've somehow got two separate USB drives that I plug in to do backups with that both have the same disk identification numbers. How is that even possible and how can I change the ID of one of the drives?

The ID that UD uses is the serial number of the device and that is expected to be unique for each drive.  Two drives should not have the same serial number.  There is no way to change the serial number as they are assigned by the manufacturer.

 

If you are using an external drive bay, the serial number might be the same for both drives.  If that is the case, you'll need to find a different drive bay that will present the drives with their actual serial numbers.

 

If none of this helps, post a screen shot of UD with both drives installed.