1 hour ago, pallalino said:

unmount

umount not unmount

48 minutes ago, Squid said:

umount not unmount

👓oh my god... thank you, already read uNmount

30 minutes ago, pallalino said:

👓oh my god... thank you, already read uNmount

Don't feel bad.   While I'm not going to go on record saying that I will usually type the "n", I'm also not going to say that I never type the "n".  

On 3/7/2025 at 12:42 AM, 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.

me too - it seems to show the opposite on my system too!

Why would I be able to use a particular NTFS-formatted disk without problem via an external USB enclosure, but then, because I wanted to try to transfer files faster using the same drive on an internal SATA connection, end up unable to mount that drive, getting FORMAT as my only option for what I can do with the drive?

Please note that nothing spontaneously went wrong with the drive. I removed it as an internal drive, put it back in the external USB enclosure, and it was once again perfectly usable as an Unassigned Device.

2 hours ago, RasterEyes said:

via an external USB enclosure

Some USB enclosures are not transparent, I.e., they should the disk or partition in a custom way.

4 minutes ago, JorgeB said:

Some USB enclosures are not transparent, I.e., they should the disk or partition in a custom way.

I'm not sure what you're saying here. Are you saying that the USB enclosure might have changed the way the drive got formatted? SO the disk only works properly as an NTFS volume when used inside the enclosure?

Some enclosures encrypt the drive, some reserve some of the first sectors so the disk shows smaller in the enclosure than it would when attached directly so when you do so there's "no partition table" cause it's shifted etc

 

Note that as long as the enclosure is USB3 or better you won't see a difference in performance.

Edited March 18, 20251 yr by Kilrah

1 hour ago, Kilrah said:

Note that as long as the enclosure is USB3 or better you won't see a difference in performance.

True. What's now making the file transfer run a lot faster, however, is reconstruct write. That's 2-3 times faster.

Hey guys, im not a power user but have been running Unraid for 4-5 years now. I'm having an issue after I upgraded to 7.0.1. I had a failed drive and I was using unassigned devices to keep it going until I can afford to replace the failed drive. After the upgrade the disk has moved to "Historical" as seen in the picture attached. Now im unable to start my array. It just says "cache - too many wrong or missing devices" when I try. Is there a way I can fix this until I can get a new drive in the server? Any help is appreciated thank you. EDIT: I've tried to search the forums and didn't find a solutions.  If there's been a similar issue please link!

3 minutes ago, SeanFromYYC said:

"cache - too many wrong or missing devices"

This has nothing to do with Unassigned Devices plugin. Plus you already have a thread going about your problems so let's keep it there.

17 minutes ago, trurl said:

This has nothing to do with Unassigned Devices plugin. Plus you already have a thread going about your problems so let's keep it there.

 

Ok sorry I didn't realize the support people were the same in both places.  Cheers

Can you make share from unassigned drive hidden?

Hello all, since some weeks my mounted external SSD went from "unmount" to "array". Any idea why?

 

3 minutes ago, CptRetro said:

external SSD went from "unmount" to "array"

UD thinks it is a disk that was in the array and it doesn't want you to accidentally use it another way.

 

Also, I notice all of your array are SSDs. SSDs in the array cannot be trimmed. Usually these would be assigned to pools and not to the array. Various raid modes with btrfs and zfs are supported for multidisk pools. And, Unraid V7 doesn't require an array at all.

19 hours ago, trurl said:

UD thinks it is a disk that was in the array and it doesn't want you to accidentally use it another way.

 

Also, I notice all of your array are SSDs. SSDs in the array cannot be trimmed. Usually these would be assigned to pools and not to the array. Various raid modes with btrfs and zfs are supported for multidisk pools. And, Unraid V7 doesn't require an array at all.

Thanks a lot for your advice. What can I do to prevent UD to see it as a array drive to get a backup the the SSD?

 

As soon as I got the backup I will inform myself how to setup the disks for my need

1 hour ago, CptRetro said:

What can I do to prevent UD to see it as a array drive

 

Unfortunately it happening all the time. Even stopping the array and starting it is not working. The only way to solve it (at least for the first 10 minutes) is to reboot the whole server.

30 minutes ago, CptRetro said:

Unfortunately it happening all the time. Even stopping the array and starting it is not working. The only way to solve it (at least for the first 10 minutes) is to reboot the whole server.

Next time that happens, post the diags before rebooting.

18 minutes ago, JorgeB said:

Next time that happens, post the diags before rebooting.

Sure

 

ms01-diagnostics-20250331-1725.zip

Log is filled with messages like this:

 

Mar 31 15:54:54 MS01 ntfs-3g[14070]: Incomplete multi-sector transfer: magic: 0x58444e49  size: 4096  usa_ofs: 40  usa_count: 6  data: 63375  usn: 63373: Input/output error

 

Try running chkdsk on that disk.

thanks for your help. It turns out that the drive is faulty. I will try it with the new one

This has been a very useful tool and have it loaded on Unraid 7 as well (it works right? -- hope so).  Anyways while it doesn't seem to necessarily break anything I noticed that its portion on the Main page causes a couple of 404 errors to show in the log.  Figured I'd let you know in case you didn't already know.

 

Apr  7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483992 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main"
Apr  7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483987 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main"

 

I have tried searching for an answer but have not found anything. I am pretty new to unraid but I did purchase a lifetime subscription so I am going to learn to use to the best of my ability. My questions is this...Can I force SMB shares to mount at startup. If so how do i go about that and  please give me specific instructions as I am also new to the Linux system. I am using unraid 7.0.1. 

1 hour ago, Mugly said:

Can I force SMB shares to mount at startup.

Click the settings icon for that remote share, then enable "auto-mount"