Please update to the latest UD.

5 hours ago, dlandon said:

Please update to the latest UD.

Hi @dlandon Just installed the update for UD devices and its been up and running with no issues now for about 20min. Looks like the fix you did is working 🙂 Unless the workaround you did earlier for me is still holding.

 

Would updating the UD plugin remove your workaround you did earlier?

44 minutes ago, Titan84 said:

Hi @dlandon Just installed the update for UD devices and its been up and running with no issues now for about 20min. Looks like the fix you did is working 🙂 Unless the workaround you did earlier for me is still holding.

 

Would updating the UD plugin remove your workaround you did earlier?

It will fix itself.  You can ignore it.  What I did was what UD should have done.

Ahh gotcha. In that case then the fix you pushed has worked like a charm.

I also have another friend with a similar setup to me and he just went though the same upgrade process that i did and after upgrading UD to this new version (12a) and then upgrade unraid to 6.11.3 he had no issues at all.

 

So 2 seperate test cases all saying its fixed 🙂 thanks very much for debugging and fixing this for us so quickly. Its very much appreciated!

16 hours ago, Kilrah said:

Why have an Unmount button on the partition then if you're not supposed to use it?

 

OP's post is likely the result of clicking the wrong unmount button by mistake, not intentionally wanting to unmount the single partition. Then you can't remount it without unmounting the whole disk first.

The original design of UD included the partition buttons to unmount a partition.  Not sure why that was implemented.  You can use them to unmount a partition you don't need mounted.

 

If clicking the wrong 'Unmount' button is an issue, you can set the 'Disable Mount Button' for the device and the 'Unmount' button will be disabled.  The other thing to do is to not expand the partitions on a device.  The partition 'Unmount' buttons would then be hidden.

13 hours ago, dlandon said:

The original design of UD included the partition buttons to unmount a partition.  Not sure why that was implemented.  You can use them to unmount a partition you don't need mounted.

 

If clicking the wrong 'Unmount' button is an issue, you can set the 'Disable Mount Button' for the device and the 'Unmount' button will be disabled.  The other thing to do is to not expand the partitions on a device.  The partition 'Unmount' buttons would then be hidden.

There initially IS a mount button for the partition. But if you unmount it (expecting to be able to mount it again at some point in the future), you can't because the button is no longer there. The expected behaviour is inconsistent.

I take it back. I'm guessing you just removed the individual mount buttons?

Hello all,
 

I have set up UNRAID half a year ago and at the same time also installed "Unassigned Devices" and created backups on two external hard drives (NTFS).

Now I wanted to connect a external hard disk and create a new backup, however, both hard disks can no longer be mounted.
Also no exact error message appears. On the PC the disks work without problems. 
For test purposes I connected a USB stick (FAT) to the server. This works.

I don't know what to do and I don't want to format the hard disks again.
 

Does anyone have any ideas?

 

Nov 14 18:59:03 AMHOST kernel: sdc: sdc1 sdc2
Nov 14 18:59:03 AMHOST kernel: sd 10:0:0:0: [sdc] Attached SCSI disk
Nov 14 18:59:04 AMHOST unassigned.devices: Disk with ID 'TOSHIBA_EXTERNAL_USB_20211214006742F-0:0 (sdc)' is not set to auto mount.
Nov 14 18:59:12 AMHOST unassigned.devices: Partition 'sdc1' does not have a file system and cannot be mounted.
Nov 14 18:59:12 AMHOST unassigned.devices: Adding partition 'sdc2'...
Nov 14 18:59:12 AMHOST unassigned.devices: Mounting partition 'sdc2' at mountpoint '/mnt/disks/Backup_2'...
Nov 14 18:59:12 AMHOST unassigned.devices: Mount drive command: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdc2' '/mnt/disks/Backup_2'
Nov 14 18:59:12 AMHOST unassigned.devices: Mount of 'sdc2' failed: ''
Nov 14 18:59:12 AMHOST unassigned.devices: Partition 'Backup_2' cannot be mounted.

 

Hi there,

I have an external HDD (4TB).

It was formatted as NTFS on Windows, but on Unraid, I couldn't mount it because it didn't appear to have any partitions.

So I formatted it as NTFS using unassigned devices, but now when I go to disk management in Windows, it says the disk is not initialized.

Is there any way to format a disk so that it is mountable in both Windows and Unassigned Devices?

I'm sure I had this working with another drive.

1 hour ago, gamerkonks said:

Hi there,

I have an external HDD (4TB).

It was formatted as NTFS on Windows, but on Unraid, I couldn't mount it because it didn't appear to have any partitions.

So I formatted it as NTFS using unassigned devices, but now when I go to disk management in Windows, it says the disk is not initialized.

Is there any way to format a disk so that it is mountable in both Windows and Unassigned Devices?

I'm sure I had this working with another drive.

If you are on Unraid 6.11.2, there is a bug when formatting drives larger than 2TB with UD.  Upgrade Unraid and try again.

On 11/14/2022 at 7:09 PM, Uncreep said:

Hello all,
 

I have set up UNRAID half a year ago and at the same time also installed "Unassigned Devices" and created backups on two external hard drives (NTFS).

Now I wanted to connect a external hard disk and create a new backup, however, both hard disks can no longer be mounted.
Also no exact error message appears. On the PC the disks work without problems. 
For test purposes I connected a USB stick (FAT) to the server. This works.

I don't know what to do and I don't want to format the hard disks again.
 

Does anyone have any ideas?

 

Nov 14 18:59:03 AMHOST kernel: sdc: sdc1 sdc2
Nov 14 18:59:03 AMHOST kernel: sd 10:0:0:0: [sdc] Attached SCSI disk
Nov 14 18:59:04 AMHOST unassigned.devices: Disk with ID 'TOSHIBA_EXTERNAL_USB_20211214006742F-0:0 (sdc)' is not set to auto mount.
Nov 14 18:59:12 AMHOST unassigned.devices: Partition 'sdc1' does not have a file system and cannot be mounted.
Nov 14 18:59:12 AMHOST unassigned.devices: Adding partition 'sdc2'...
Nov 14 18:59:12 AMHOST unassigned.devices: Mounting partition 'sdc2' at mountpoint '/mnt/disks/Backup_2'...
Nov 14 18:59:12 AMHOST unassigned.devices: Mount drive command: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdc2' '/mnt/disks/Backup_2'
Nov 14 18:59:12 AMHOST unassigned.devices: Mount of 'sdc2' failed: ''
Nov 14 18:59:12 AMHOST unassigned.devices: Partition 'Backup_2' cannot be mounted.

 

Is there also no error message if you try to mount it from the console? Just a thought.

6 hours ago, shakeshuck said:

Is there also no error message if you try to mount it from the console? Just a thought.

I believe it just said there wasn't a partition. 

When I checked the dev directory, there was the device sdX, but no partition sdX1.

On 11/16/2022 at 3:25 PM, gamerkonks said:

I believe it just said there wasn't a partition. 

When I checked the dev directory, there was the device sdX, but no partition sdX1.

If Linux doesn't find a partition on the disk, UD can't mount it.  Try scanning the disk for errors.

7 hours ago, gvtci said:

Can anyone offer me a suggestion?

 

Thank You

tower-diagnostics-20221118-0129.zip 122.67 kB · 2 downloads

Why are you using a routable IP address for your server?  It is generally a non routable IP address - 192.x.x.x or 10.x.x.x.

 

I also see some disk messages:

Nov 18 01:28:03 Tower  emhttpd: Device inventory:
Nov 18 01:28:03 Tower  emhttpd: ST10000NM0096_ZA28AN6X0000C84990VP_35000c500a6887b8f (sdj) 512 19532873728
Nov 18 01:28:03 Tower  emhttpd: CT4000P3PSSD8_2240E671E196 (nvme1n1) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: ST18000NM000J-2TV103_ZR5AATG8 (sdk) 512 35156656128
Nov 18 01:28:03 Tower  emhttpd: ST10000NM0096_ZA289X5X0000C84970L4_35000c500a688f673 (sdh) 512 19532873728
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdg problem getting id
Nov 18 01:28:03 Tower  emhttpd: CT2000P3PSSD8_2236E6620BCF (nvme2n1) 512 3907029168
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdw problem getting id
Nov 18 01:28:03 Tower  emhttpd: WD4001FYYG-79SL3_WMC1F0678389_350000c0f011a8fc8 (sdd) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: ST18000NM000J-2TV103_ZR5AASEN (sdt) 512 35156656128
Nov 18 01:28:03 Tower  emhttpd: ST10000NM0096_ZA25B1XW0000C83025ZP_35000c5009538c473 (sde) 512 19532873728
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdu problem getting id
Nov 18 01:28:03 Tower  emhttpd: WD4001FYYG-79SL3_WMC1F0582250_350000c0f01bfcf08 (sdb) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: ST10000NM0096_ZA25B2360000C82959F1_35000c5009538bcd7 (sdr) 512 19532873728
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdf problem getting id
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdv problem getting id
Nov 18 01:28:03 Tower  emhttpd: WD4001FYYG-79SL3_WMC1F0677098_350000c0f01c01870 (sdc) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: CT4000P3PSSD8_2240E671E178 (nvme0n1) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: ST18000NM000J-2TV103_ZR51J2MF (sds) 512 35156656128
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdn problem getting id
Nov 18 01:28:03 Tower  emhttpd: WD4001FYYG-79SL3_WMC1F0611178_350000c0f01bfcf2c (sdq) 512 7814037168
Nov 18 01:28:03 Tower  emhttpd: CT2000P3PSSD8_2236E66208FE (nvme3n1) 512 3907029168
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdo problem getting id
Nov 18 01:28:03 Tower  emhttpd: ST18000NM000J-2TV103_ZR53BJBY (sdl) 512 35156656128
Nov 18 01:28:03 Tower  emhttpd: ST10000NM0096_ZA27GE950000C845LGLY_35000c500a65a6ab7 (sdi) 512 19532873728
Nov 18 01:28:03 Tower  emhttpd: device /dev/sdp problem getting id

I'm not a disk expert, so maybe @JorgeB can offer some insight to whether or not these messages are an issue.

 

As for UD, I do not understand how it could cause these problems.

1 hour ago, dlandon said:

device /dev/sdo problem getting id

This usually means the same devices are being detected twice, make sure there's only one cable from the HBA to the NetApp enclosure, Unraid doesn't support SAS multipath.

I will be at the colo today and I will unplug one of the Sas cables. I sure hope that addresses the issue. I will report back. Thank You guys..

Yep, that was the problem. I removed the 2nd HBA cable to the netapp and it fixed my problem. Array stops and starts now with the UD plugin install. Thank You again for your help.

I inserted a usb drive I've been using with unassigned devices for months and got a "reboot" button instead of a mount button.  What caused this and is there a way to avoid rebooting?

12 minutes ago, quattro said:

I inserted a usb drive I've been using with unassigned devices for months and got a "reboot" button instead of a mount button.  What caused this and is there a way to avoid rebooting?

That happens when the disk was not properly unmounted before being re-inserted.  You need to reboot to clear it up.

14 minutes ago, dlandon said:

That happens when the disk was not properly unmounted before being re-inserted.  You need to reboot to clear it up.

Strange as I've always unmounted before removing it, but thanks for the quick reply. 

 

 Was just hoping to avoid a reboot.

2 minutes ago, quattro said:

Strange as I've always unmounted before removing it, but thanks for the quick reply. 

 

 Was just hoping to avoid a reboot.

When you unmount a disk, confirm it actually is unmounted.  If the disk is busy, it will not unmount.  Just clicking the "Unmount" button doesn't guarantee the disk will unmount.

can anybody help with this error when i am trying to mount an unassigned device 

Nov 19 09:31:52 Interocitor unassigned.devices: Error: Device '/dev/sdj1' mount point 'Plex' - name is reserved, used in the array or by an unassigned device.

 

thanks in advance

 

sorted it i was having a brain fart 🤣

Edited November 19, 20223 yr by andy harris
fixed issue

20 hours ago, dlandon said:

When you unmount a disk, confirm it actually is unmounted.  If the disk is busy, it will not unmount.  Just clicking the "Unmount" button doesn't guarantee the disk will unmount.

Thanks, will do.  Also, thanks for such a great tool

On 11/17/2022 at 8:32 AM, dlandon said:

If Linux doesn't find a partition on the disk, UD can't mount it.  Try scanning the disk for errors.

 

So after formatting to NTFS using the unassigned devices plugin, I ran ntfsfix /dev/sdp
 

I got the following output

Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
Unrecoverable error
Volume is corrupt. You should run chkdsk

 

The disk is working fine in unraid though.

5 hours ago, gamerkonks said:

The disk is working fine in unraid though.

Use UD to check the disk.  Click on the check mark next to the partition.