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


dlandon

5995 posts in this topic Last Reply

Recommended Posts

4 hours ago, dlandon said:

UD checks the remote share by pinging it.  When the remote share is not responding, it is usually from a network issue.

 

You are running Unaid 6.7.2.

Yeah, 6.8 on the server with the files, 6.7.2 on the one mounting and trying to access the files. Is there anything I can check in regards to this being a network issue? Both are physically next to each other and I never got this issue until I upgraded the main server to 6.8. I was having very slow array performance with 6.7.2, but appears that 6.8 fixed it. I had the client server, that is doing the mounting, on 6.8 as well. I thought it may have been causing issues, so downgraded it to 6.7.2.

 

I use pfSense for my firewall if that means anything.

Link to post
  • Replies 6k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

While I appreciate your interest in esthetics, there is more to consider than just 'aligning' disk drive mounts: This disk is mounted without a UD script, it is probably better to put it in th

Major new release of UD: "Where are the switches?"  The "Pass Through", "Read Only", "Automount", and "Share" switches have been moved to a new Edit Settings dialog.  This is also where the sc

Posted Images

6 hours ago, drawmonster said:

Yeah, 6.8 on the server with the files, 6.7.2 on the one mounting and trying to access the files. Is there anything I can check in regards to this being a network issue? Both are physically next to each other and I never got this issue until I upgraded the main server to 6.8. I was having very slow array performance with 6.7.2, but appears that 6.8 fixed it. I had the client server, that is doing the mounting, on 6.8 as well. I thought it may have been causing issues, so downgraded it to 6.7.2.

 

I use pfSense for my firewall if that means anything.

I see this in the log:

Oct 21 02:23:33 Unraid2 kernel: traps: lsof[80130] general protection ip:14663e8ac02e sp:33f087d8c00b3409 error:0 in libc-2.29.so[14663e88e000+16b000]
Oct 21 02:25:21 Unraid2 kernel: traps: lsof[81490] general protection ip:147fc496902e sp:4a143e0c8aa6fe81 error:0 in libc-2.29.so[147fc494b000+16b000]
Oct 21 02:25:47 Unraid2 kernel: traps: lsof[81948] general protection ip:14d28e45002e sp:6b022970d9f410c8 error:0 in libc-2.29.so[14d28e432000+16b000]
Oct 21 02:26:13 Unraid2 kernel: traps: lsof[82362] general protection ip:1504300c702e sp:c3716116e0a7fa7d error:0 in libc-2.29.so[1504300a9000+16b000]
Oct 21 02:26:58 Unraid2 kernel: traps: lsof[82679] general protection ip:15304331e02e sp:815217baf54c2d65 error:0 in libc-2.29.so[153043300000+16b000]
Oct 21 02:27:21 Unraid2 kernel: traps: lsof[83187] general protection ip:14f2d120902e sp:8ee8402bdfe127ae error:0 in libc-2.29.so[14f2d11eb000+16b000]
Oct 21 02:27:52 Unraid2 kernel: traps: lsof[83507] general protection ip:14c8d0dd802e sp:1e284918eb881007 error:0 in libc-2.29.so[14c8d0dba000+16b000]
Oct 21 02:28:42 Unraid2 kernel: traps: lsof[84126] general protection ip:151a6c04202e sp:8a17e10c93e17ec3 error:0 in libc-2.29.so[151a6c024000+16b000]
Oct 21 02:28:44 Unraid2 kernel: traps: lsof[84071] general protection ip:14748eb6b02e sp:46945e923f32fa95 error:0 in libc-2.29.so[14748eb4d000+16b000]
Oct 21 02:29:30 Unraid2 kernel: traps: lsof[84573] general protection ip:1528942e902e sp:4302eaad54a53ae4 error:0 in libc-2.29.so[1528942cb000+16b000]
Oct 21 02:30:07 Unraid2 kernel: traps: lsof[85100] general protection ip:14eebce5d02e sp:4f74b89192f9d3d1 error:0 in libc-2.29.so[14eebce3f000+16b000]
Oct 21 02:30:35 Unraid2 unassigned.devices: Error: SMB/NFS server '192.168.1.227' is not responding to a ping and appears to be off-line.
### [PREVIOUS LINE REPEATED 1 TIMES] ###

I don't know anything about the 'traps', but it might be related.  Someone more knowledgeable than I am can possibly help here.

Link to post

I just got a SSD Crucial MX500 and is hotter than my other disks (idles at 45C). If I increase the global temperature threshold my other HDD in UD will not report warnings when they should. Is the individual atributes/warnings in the roadmap for future plugin releases? Thank you!

Link to post
13 minutes ago, Alec.Dalessandro said:

I'm trying to create 2 partitions on a new HDD. 

 

One that is ntfs to virtually mount to a VM then then other is xfs to add to the array.

Is there a way I can create these using unassigned devices because I'm finding I can only do the full amount of the HDD.

No.  You can only create one partition on a UD disk.  Just as a note, you can't use a disk as an array drive and a UD device.  An array device is the whole disk, not a partition on the disk.

Link to post
On 10/27/2019 at 4:16 PM, dlandon said:

No.  You can only create one partition on a UD disk.  Just as a note, you can't use a disk as an array drive and a UD device.  An array device is the whole disk, not a partition on the disk.

Thank you I was unaware of this but found an alternative idea.

 

One question I do have is if you can only create one partition using UD disk, is there an other alternative to creating 2 partitions inside Unraid?

Link to post
57 minutes ago, Alec.Dalessandro said:

Thank you I was unaware of this but found an alternative idea.

 

One question I do have is if you can only create one partition using UD disk, is there an other alternative to creating 2 partitions inside Unraid?

The standard Linux command line tool (gdisk I think) should be able to do this.

Link to post

I am seeing the the following at the bottom on the 'Unassigned Devices' tab:

Quote

Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 448

I have version '2019.10.15'.

Link to post
4 minutes ago, noski said:

I am seeing the the following at the bottom on the 'Unassigned Devices' tab:

I have version '2019.10.15'.

It looks like you might have a corrupt UD config file.  Can you post the /boot/config/plugins/unassigned.devices/unassigned.devices.cfg?

Link to post

[My_Passport_0748_575837314138325031303237]
command.1 = ""
automount = "yes"

The previous warning doesn't seem to be showing now. I assume it corrected itself. Does that contents look OK? On a side note, I am trying to setup a script to run when the drive is plugged in (using the sample provided in the first post), however it is not getting executed. I can't see anything obvious in the syslog.

 

Oct 30 21:44:43 Tower unassigned.devices: Adding disk '/dev/sdu1'...
Oct 30 21:44:43 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdu1' '/mnt/disks/My_Passport'
...
Oct 30 21:44:44 Tower unassigned.devices: Successfully mounted '/dev/sdu1' on '/mnt/disks/My_Passport'.
Oct 30 21:44:44 Tower unassigned.devices: Disk with serial 'My_Passport_0748_575837314138325031303237', mountpoint 'My_Passport' is not set as sharable and will not be shared...

 

Link to post
5 minutes ago, noski said:


[My_Passport_0748_575837314138325031303237]
command.1 = ""
automount = "yes"

The previous warning doesn't seem to be showing now. I assume it corrected itself. Does that contents look OK? On a side note, I am trying to setup a script to run when the drive is plugged in (using the sample provided in the first post), however it is not getting executed. I can't see anything obvious in the syslog.

 


Oct 30 21:44:43 Tower unassigned.devices: Adding disk '/dev/sdu1'...
Oct 30 21:44:43 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdu1' '/mnt/disks/My_Passport'
...
Oct 30 21:44:44 Tower unassigned.devices: Successfully mounted '/dev/sdu1' on '/mnt/disks/My_Passport'.
Oct 30 21:44:44 Tower unassigned.devices: Disk with serial 'My_Passport_0748_575837314138325031303237', mountpoint 'My_Passport' is not set as sharable and will not be shared...

 

Post a screen shot of the drive on UD.

Link to post

Screenshot attached.

I edited the script and hit save (didn't change the contents), and the config file then updated to this:


[My_Passport_0748_575837314138325031303237]
command.1 = "/boot/config/plugins/unassigned.devices/My_Passport.sh"
automount = "yes"
command_bg.1 = "true"

Most recent plugin attempt resulted in this in the syslog, but nothing else after that:

...
Oct 30 21:50:52 Tower unassigned.devices: Running device script: 'My_Passport.sh' with action 'ADD'.

 

screenshot.png

Link to post
6 minutes ago, noski said:

Screenshot attached.

I edited the script and hit save (didn't change the contents), and the config file then updated to this:


[My_Passport_0748_575837314138325031303237]
command.1 = "/boot/config/plugins/unassigned.devices/My_Passport.sh"
automount = "yes"
command_bg.1 = "true"

Most recent plugin attempt resulted in this in the syslog, but nothing else after that:


...
Oct 30 21:50:52 Tower unassigned.devices: Running device script: 'My_Passport.sh' with action 'ADD'.

 

screenshot.png

What do you expect to happen?  Is this your script, or the default?

 

You can test run the script and see the results if you click on the + and then the lightning bolt next to the partition.  Your script will run and you can see the results in the pop up dialog.

Link to post

I have a possible issue (or doing something stupid).

 

One of the unused disks remaining in my unRAID, is my old SBS backup disk.

This is 1TB disk dedicated to backup using Windows Server Backup.

 

When I installed unRAID and unassigned devices, this disk didn't show as mountable for some reason. It showed an unusable partition.
I left it as is for some time (as I didn't need the disk and there was always a possibility to go back to SBS - that won't happen) and today I decided to use this disk (as it occupies a space anyway, pending a bigger disk).

So I deleted the partition using Unassigned Devices own button. When I did that, the disk disappeared fully! Was not shown in any of the tabs.
I rebooted the server and the disk showed up (unmountable again). AGAIN with unusable partition. I tried again to delete it and... again the disk disappeared.

What can I do? What am I doing wrong.

I don't think there is an issue with the disk (it was taking successful daily backups until last month when I took SBS offline).

 

Link to post
1 hour ago, NLS said:

I have a possible issue (or doing something stupid).

 

One of the unused disks remaining in my unRAID, is my old SBS backup disk.

This is 1TB disk dedicated to backup using Windows Server Backup.

 

When I installed unRAID and unassigned devices, this disk didn't show as mountable for some reason. It showed an unusable partition.
I left it as is for some time (as I didn't need the disk and there was always a possibility to go back to SBS - that won't happen) and today I decided to use this disk (as it occupies a space anyway, pending a bigger disk).

So I deleted the partition using Unassigned Devices own button. When I did that, the disk disappeared fully! Was not shown in any of the tabs.
I rebooted the server and the disk showed up (unmountable again). AGAIN with unusable partition. I tried again to delete it and... again the disk disappeared.

What can I do? What am I doing wrong.

I don't think there is an issue with the disk (it was taking successful daily backups until last month when I took SBS offline).

 

Post diagnostics.

Link to post
53 minutes ago, NLS said:

Here are diagnostics AFTER the disk is "lost".

They are possibly different right after reboot (and before trying to delete the partition).

 

quasar-ultima-diagnostics-20191101-2004.zip 132.18 kB · 1 download

The disk is /dev/sdc and appears to be having issues.

Nov  1 15:47:39 quasar-ultima emhttpd: device /dev/sdc has size zero

How do you have the disk connected?  Check cabling?

Link to post

Well that is what I am saying. :D

It appears to be having issues. I also noticed the size zero reported.

 

The disk is connected to one of my SATA ports.

It was working before installing unRAID and used for backups.

Cabling was not touched, but I will try to unplug replug.

 

It is not critical, I just find it weird and hope to resolve it some time.

I might remove the disk and check it on another machine (as it will eventually be removed by unRAID anyway).

 

Thanks.

 

Link to post

Updated to 6.8 RC4, started having a problem with the sharing function of UD. For instance, I have two disks, with share names set as qB1 and qB2. These show up as SMB shares on my network, however, they are now empty as far as SMB/browsing is concerned. I can view the drive's contents in /mnt/disks/ locally on Unraid, but have no meaningful access to them remotely.

Link to post
5 hours ago, WaffleClap said:

Updated to 6.8 RC4, started having a problem with the sharing function of UD. For instance, I have two disks, with share names set as qB1 and qB2. These show up as SMB shares on my network, however, they are now empty as far as SMB/browsing is concerned. I can view the drive's contents in /mnt/disks/ locally on Unraid, but have no meaningful access to them remotely.

I think it's a permissions problem.  Go to an Unraid terminal session and run this command:

ls -l /mnt/disks/qB1

Show the results.

Link to post
  • trurl pinned this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.