On 3/1/2025 at 8:33 PM, Cyclical Jester said:

How? This is driving me nuts. I've installed a new drive, I have this message showing, and I cannot work out a way to fix it. I have no ability to do anything on this drive whether it is plugged in or not plugged in (yes, destructive mode is available). I was able to pre-clear with no issues (but that is literally the only thing I can do with it).

 

Edited to provide a little more context:

• I have a brand new IronWolf drive, sitting an external HDD enclosure
• The slot in the enclosure was previously used for a drive that was in the array (it's not the same physical HDD)
• The new drive can be seen, but I'm seeing the "not" and "array" (first screenshot)
• I want to add the drive to the array. The array has a spare slot available, and all I'm trying to do is to assign this drive to that slot and rebuild the parity.
• I have tried uninstalling and reinstalling all the UD apps. I have tried moving the drive around, shutting down, removing, booting up etc. in many combinations to no avail.

 

The only thing I have not yet tried is simply adding a new config to the array. I've never done that and I'm slightly nervous, but if this is what I need to do then I will.

 

zeus-diagnostics-20250303-0842.zip 156.4 kB · 0 downloads

Go to a command line and type 'ud_diagnostics'.  Then post the /flash/logs/ud_diagnostics.zip.

On 3/1/2025 at 8:33 PM, Cyclical Jester said:

How? This is driving me nuts. I've installed a new drive, I have this message showing, and I cannot work out a way to fix it. I have no ability to do anything on this drive whether it is plugged in or not plugged in (yes, destructive mode is available). I was able to pre-clear with no issues (but that is literally the only thing I can do with it).

 

Edited to provide a little more context:

• I have a brand new IronWolf drive, sitting an external HDD enclosure
• The slot in the enclosure was previously used for a drive that was in the array (it's not the same physical HDD)
• The new drive can be seen, but I'm seeing the "not" and "array" (first screenshot)
• I want to add the drive to the array. The array has a spare slot available, and all I'm trying to do is to assign this drive to that slot and rebuild the parity.
• I have tried uninstalling and reinstalling all the UD apps. I have tried moving the drive around, shutting down, removing, booting up etc. in many combinations to no avail.

 

The only thing I have not yet tried is simply adding a new config to the array. I've never done that and I'm slightly nervous, but if this is what I need to do then I will.

 

zeus-diagnostics-20250303-0842.zip 156.4 kB · 1 download

Unraid does not recognize the 'sda' device as an unassigned disk.  On the UD page, click on the double arrows icon in the upper right of the page and see if Unraid will determine if the disk is unassigned.  It will assign the disk device to 'Dev 1',  If it doesn't work, go to the UD Settings page and set the logging to 'Udev and Hotplug', then click on the double arrow again.  Once you do that, then post the diagnostics again.

I plugged in a USB drive to my Unraid 7. 0.1 with Unassigned Devices installed and set to automount but Unraid doesn't recognise the USB is connected? What can I do? The USB is  seen okay in windows. I've tried various USB ports on the server. Still learning Unraid so not familiar with the workings of it.

Dioagnostics attached.

tower-diagnostics-20250305-1131.zip

I don't know if this was reported but clicking on Toggle Read/Write Display is not consistent with other panels. When unassigned devices displays read write speed, the other panels display read/write count. Clicking on toggle again reverses the display.

1 hour ago, dariusz65 said:

I don't know if this was reported but clicking on Toggle Read/Write Display is not consistent with other panels. When unassigned devices displays read write speed, the other panels display read/write count. Clicking on toggle again reverses the display.

 

I've noticed this too. If Array shows speeds, UD shows counts and vice versa. Doesn't matter which panel you make the changes. Seeing it in 6.12.15 and 7.0.0.

 

On 3/5/2025 at 6:33 AM, dOM152 said:

I plugged in a USB drive to my Unraid 7. 0.1 with Unassigned Devices installed and set to automount but Unraid doesn't recognise the USB is connected? What can I do? The USB is  seen okay in windows. I've tried various USB ports on the server. Still learning Unraid so not familiar with the workings of it.

Dioagnostics attached.

tower-diagnostics-20250305-1131.zip 153.88 kB · 2 downloads

Is it seen when you go into the BIOS of the system?

2 hours ago, dariusz65 said:

I don't know if this was reported but clicking on Toggle Read/Write Display is not consistent with other panels. When unassigned devices displays read write speed, the other panels display read/write count. Clicking on toggle again reverses the display.

Thanks.  I'll look into it

The reversed counter vs RW throughput should be fixed on next release.  

Is there a new bug that once pre-cleared you cannot format or use the drive?

 

On 3/3/2025 at 6:58 AM, dlandon said:

Go to a command line and type 'ud_diagnostics'.  Then post the /flash/logs/ud_diagnostics.zip.

Is /flash/logs a new dir structure?

9 hours ago, DiscoverIt said:

Is there a new bug that once pre-cleared you cannot format or use the drive?

You should only format the drive if it's not going to be added to the array, or the preclear signature will be lost, to format with UD you need to enable destructive mode.

Hi,

 

I had to setup a new MacMini and need therefore to create a SMB connection again. But I'm not able to get it running. I tried the following where I think in the meantime it's not related to the unassigned devices plugin, but maybe someone has a hint for me:

 

1. In Unraid:

 Add remote SMB share (enabled in Unraid). Enter IP address, user name (small and capital letters tried), password, domain empty. Press button „Load shares“: nothing found. I enter name of a shared forder manually (confirmed on MacMini with „sharing -l“ that the folder is shared and name is correct).  Success message is shown.

Pressing on button „Mount“. Fail.

Log:

Mar 12 13:18:19 nas kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE

Mar 12 13:18:19 nas kernel: CIFS: VFS: \\192.168.178.61 Send error in SessSetup = -13

 

I found some hints, that it could be related to wrong user/password. Therefore, I wrote user name with capital letters, but result is he same. PW is correct.

 

2.

When I try to mount the folder manually in a Uraid terminal window:

mount.smb3 //192.168.178.61/Dokumente /mnt/user/MacMini/ -o user=xxxx

(folder MacMini created before in Unraid, SMB enabled), password is requested. After entering PW I get the message „mount error(13): Permission denied“.

On MacMini I listen to the log via „sudo log stream --predicate 'process == "smbd"' –info“ in parallel, I get two error messages:

smbd: [com.apple.smb:default] transact: gss_accept_sec_context: major_status: 0xd0000, minor_status: 0xa2e9a74a

smbd: [com.apple.smb:default] smb2_dispatch_session_setup: session_setup_transact status: 0xc000006d

 

Here I found somewhere that the date/time between Uraid and MacMini could be off. But this isn’t the case.

 

I don't know what to do now...

 

Thank you

1 hour ago, pallalino said:

I don't know what to do now...

 

Try this.  Under the sharing options, check off the user for the Mac to store windows creds in a less secure manner but which gives greater compatibility

 

23 minutes ago, Squid said:

Try this.  Under the sharing options, check off the user for the Mac to store windows creds in a less secure manner but which gives greater compatibility

 

Thank you, it's working now! There must have been some changes as I hadn't this setting before.

10 minutes ago, pallalino said:

Thank you, it's working now! There must have been some changes as I hadn't this setting before.

Actually, thank you.   About two years ago I raised an issue with UD where I couldn't connect to a Mac Share, but it wasn't important to me.  With your post I had to try it again and found the solution

6 hours ago, JorgeB said:

You should only format the drive if it's not going to be added to the array, or the preclear signature will be lost, to format with UD you need to enable destructive mode.

 

Preclear is often done as a test before a drive is used either in a parity protected array, pool, or elsewhere. Destructive mode is enabled with the Plus addon installed. There appears to no longer be a mechanism to format a drive with a pre-clear signature.

Edited March 12, 20251 yr by DiscoverIt

12 minutes ago, DiscoverIt said:

 

Preclear is often done as a test before a drive is used either in a parity protected array, pool, or elsewhere. Destructive mode is enabled with the Plus addon installed. There is no longer a mechanism to format a drive with a pre-clear signature.

Trying this now.  Thanks for reporting

28 minutes ago, Squid said:

Actually, thank you.   About two years ago I raised an issue with UD where I couldn't connect to a Mac Share, but it wasn't important to me.  With your post I had to try it again and found the solution

I see many error messages in Unraid log (every seocnd the same...)

Mar 12 15:37:14 nas emhttpd: error: malloc_share_locations, 7936: Operation not supported (95): getxattr: /mnt/user/MacMini

 

this is the share I mounted manually. I can't find the unmount command in Unraid... any idea?

Edited March 12, 20251 yr by pallalino

29 minutes ago, DiscoverIt said:

Preclear is often done as a test before a drive is used either in a parity protected array, pool, or elsewhere.

Of course, but not clear how you intend to use it. If you add a formatted drive to the array, Unraid will have to clear it so parity remains valid. That is really the point of the preclear signature. The format needs to happen after the drive is added to the array.

3 minutes ago, trurl said:

Of course, but not clear how you intend to use it. If you add a formatted drive to the array, Unraid will have to clear it so parity remains valid. That is really the point of the preclear signature. The format needs to happen after the drive is added to the array.

Where do you see that I want to add a formatted drive to a parity protected array? That string of text was never typed by me. 

 

The intention is that if a drive is acquired the most common way to test the drive is to leverage a pre-clear operation. I found a way to format the drive but it has become incredibly convoluted. Since all status went to the footer (which by the way why did that change occur?), you first hover over the symbol, click the red x to need to remove the pre-clear report, click the red X on the main page, enter in Yes, and only then does the UI element change to allow Format.

Just now, DiscoverIt said:

Where do you see that I want to add a formatted drive to a parity protected array? That string of text was never typed by me. 

Neither was there any explanation of how you intended to use the drive. Just wanted to save you the trouble of having to let Unraid clear the disk again if you did intend to add it to the array.

Is the removal of the pre-clear report a new(er) addition to the workflow before the signature can be removed via the subsequent red x click?

Edited March 12, 20251 yr by DiscoverIt

1 hour ago, pallalino said:

I see many error messages in Unraid log (every seocnd the same...)

Mar 12 15:37:14 nas emhttpd: error: malloc_share_locations, 7936: Operation not supported (95): getxattr: /mnt/user/MacMini

 

this is the share I mounted manually. I can't find the unmount command in Unraid... any idea?

Yeah, you shouldn't ever mount anything into /mnt/user by yourself.  unmount command is 

umount

 

1 hour ago, DiscoverIt said:

click the red X on the main page, enter in Yes, and only then does the UI element change to allow Format.

Looks like that's by design.   Admittedly not super obvious though...

38 minutes ago, Squid said:

Yeah, you shouldn't ever mount anything into /mnt/user by yourself.  unmount command is 

umount

 

unmount command is not available, I rebooted Unraid. It was only for testing, I don't do this typically...