16 minutes ago, ToTo said:

Log:

 

Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] 4096-byte physical blocks
Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] Write Protect is off
Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] Mode Sense: 7f 00 10 08
Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] Write cache: enabled, read cache: enabled, supports DPO and FUA
Oct 19 00:04:47 Tower kernel: sdas: sdas1
Oct 19 00:04:47 Tower kernel: sd 45:0:18:0: [sdas] Attached SCSI disk
Oct 19 00:04:47 Tower emhttpd: HGST_HTS545050A7E380_131108TM85A3PY16J8HM (sdas) 512 976773168
Oct 19 00:04:47 Tower emhttpd: read SMART /dev/sdas
Oct 19 00:05:26 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdas'.
Oct 19 00:05:32 Tower kernel: sdas:
Oct 19 00:05:45 Tower unassigned.devices: Device '/dev/sdas' block size: 976773168.
Oct 19 00:05:45 Tower unassigned.devices: Clearing partition table of disk '/dev/sdas'.
Oct 19 00:05:46 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 00:05:46 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 00:05:46 Tower unassigned.devices: Creating a 'gpt' partition table on disk '/dev/sdas'.
Oct 19 00:05:46 Tower unassigned.devices: Formatting disk '/dev/sdas' with 'ntfs' filesystem.
Oct 19 00:05:47 Tower unassigned.devices: Format disk '/dev/sdas' with 'ntfs' filesystem: Cluster size has been automatically set to 4096 bytes. Creating NTFS volume structures. mkntfs completed successfully. Have a nice day.
Oct 19 00:05:50 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 00:05:51 Tower kernel: sdas: sdas1
Oct 19 00:05:51 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 00:40:35 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdas'.
Oct 19 00:40:41 Tower kernel: sdas:
Oct 19 00:40:49 Tower unassigned.devices: Device '/dev/sdas' block size: 976773168.
Oct 19 00:40:49 Tower unassigned.devices: Clearing partition table of disk '/dev/sdas'.
Oct 19 00:40:49 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 00:40:49 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 00:40:49 Tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/sdas'.
Oct 19 00:40:50 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 00:40:50 Tower kernel: sdas: sdas1
Oct 19 00:40:50 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 00:40:50 Tower unassigned.devices: Formatting disk '/dev/sdas' with 'xfs' filesystem.
Oct 19 00:40:53 Tower unassigned.devices: Format disk '/dev/sdas' with 'xfs' filesystem: meta-data=/dev/sdas1 isize=512 agcount=4, agsize=30524160 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=122096638, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=59617, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0
Oct 19 00:40:56 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 00:40:56 Tower kernel: sdas: sdas1
Oct 19 00:40:56 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 15:09:25 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdas'.
Oct 19 15:09:30 Tower kernel: sdas:
Oct 19 15:09:45 Tower unassigned.devices: Device '/dev/sdas' block size: 976773168.
Oct 19 15:09:45 Tower unassigned.devices: Clearing partition table of disk '/dev/sdas'.
Oct 19 15:09:45 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 15:09:45 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 15:09:45 Tower unassigned.devices: Creating a 'gpt' partition table on disk '/dev/sdas'.
Oct 19 15:09:46 Tower unassigned.devices: Formatting disk '/dev/sdas' with 'ntfs' filesystem.
Oct 19 15:09:47 Tower unassigned.devices: Format disk '/dev/sdas' with 'ntfs' filesystem: Cluster size has been automatically set to 4096 bytes. Creating NTFS volume structures. mkntfs completed successfully. Have a nice day.
Oct 19 15:09:50 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 15:09:51 Tower kernel: sdas: sdas1
Oct 19 15:09:51 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 15:14:58 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdas'.
Oct 19 15:14:59 Tower kernel: sdas:
Oct 19 15:15:04 Tower kernel: sdas:
Oct 19 15:15:19 Tower unassigned.devices: Device '/dev/sdas' block size: 976773168.
Oct 19 15:15:19 Tower unassigned.devices: Clearing partition table of disk '/dev/sdas'.
Oct 19 15:15:19 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 15:15:19 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 15:15:19 Tower unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/sdas'.
Oct 19 15:15:20 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 15:15:20 Tower kernel: sdas: sdas1
Oct 19 15:15:20 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table
Oct 19 15:15:20 Tower unassigned.devices: Formatting disk '/dev/sdas' with 'xfs' filesystem.
Oct 19 15:15:23 Tower unassigned.devices: Format disk '/dev/sdas' with 'xfs' filesystem: meta-data=/dev/sdas1 isize=512 agcount=4, agsize=30524160 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 data = bsize=4096 blocks=122096638, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=59617, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0
Oct 19 15:15:26 Tower unassigned.devices: Reloading disk '/dev/sdas' partition table.
Oct 19 15:15:26 Tower kernel: sdas: sdas1
Oct 19 15:15:26 Tower unassigned.devices: Reload partition table result: /dev/sdas: re-reading partition table

 

What does it show under 'FS'?

11 minutes ago, ToTo said:

Unraid does not recognize the file system.  Put the disk in a computer with a partition manager and be sure there are no partitions other than the main XFS partition.  There is probably a hidden partition getting in the way.

So I re-formatted it on my laptop with NTFS. Then it appeared as mountable, but got this:

 

Mounting volume... $MFTMirr does not match $MFT (record 24).

 

Then I ran ntfsfix couple of times and VOALA! It mounted! Thanks for your support and great plugin!!

Hi, I plugged a USB device and backed up. Now I connected another device and I have this error

8 minutes ago, Braulio said:

Hi, I plugged a USB device and backed up. Now I connected another device and I have this error

I'm not seeing an error.  That is the result of you executing the device script.

24 minutes ago, dlandon said:

I'm not seeing an error.  That is the result of you executing the device script.

It isn't run the script, because the script name is "1TB-ROTEADOR" and the device label is "1TB-BRANCO".

Just now, Braulio said:

It isn't run the script, because the script name is "1TB-ROTEADOR" and the device label is "1TB-BRANCO".

You can change that in the settings.  Click on the three gears icon.

40 minutes ago, dlandon said:

You can change that in the settings.  Click on the three gears icon.

Let me explain again.

I have two backup device. The script runs automatically when connecting.
Label device 1 = 1TB-ROTEADOR
Label device 2 = 1TB-BRANCO

 

I connected the device 1 and the label name is "1TB-ROTEADOR".
The backup fineshed perfectly. So I removed and connected the second device. It doesn't run the script because it's linking with the old device (1TB-ROTEADOR).

 

When script runs does it create something in the temp folder?
I think there's some error and it doesn't load the script's temp file from the second device.

This has happened before, and I need to restart the server every time it happens.

1 minute ago, Braulio said:

Let me explain again.

I have two backup device. The script runs automatically when connecting.
Label device 1 = 1TB-ROTEADOR
Label device 2 = 1TB-BRANCO

 

I connected the device 1 and the label name is "1TB-ROTEADOR".
The backup fineshed perfectly. So I removed and connected the second device. It doesn't run the script because it's linking with the old device (1TB-ROTEADOR).

 

When script runs does it create something in the temp folder?
I think there's some error and it doesn't load the script's temp file from the second device.

This has happened before, and I need to restart the server every time it happens.

When you click on the settings, what script name shows there?

11 minutes ago, dlandon said:

When you click on the settings, what script name shows there?

 

1 hour ago, Braulio said:

 

Post your diagnostics.

59 minutes ago, dlandon said:

Post your diagnostics.

The complete file .zip?

34 minutes ago, Braulio said:

The complete file .zip?

That would be best.

1 hour ago, dlandon said:

That would be best.

 

server-diagnostics-20211019-1808.rar

On 1/21/2016 at 5:55 PM, dlandon said:

 

• Don't share devices and SMB/NFS Shares unless necessary and enable SMB Security for user access when you do.

Hi,

How do i exactly can limit to specific users access to the share under UD (a share created on a phisical device mounted with UD)?
(i'm asking because of course being outside of the array i can't manage the share with the "Shares" tab).

Thanks.

Edited October 20, 20214 yr by dhstsw

1 hour ago, dhstsw said:

Hi,

How do i exactly can limit to specific users access to the share under UD (a share created on a phisical device mounted with UD)?
(i'm asking because of course being outside of the array i can't manage the share with the "Shares" tab).

Thanks.

Not sure you can do this without manual editing of the Samba configuration file  

 

Is there a reason it is not set up as a pool (as pools can pools can participate in User Shares).  With the 6.9.x releases supporting multiple pools you only need to continue to use UD mounted devices if they are removable ones.

2 hours ago, dhstsw said:

Hi,

How do i exactly can limit to specific users access to the share under UD (a share created on a phisical device mounted with UD)?
(i'm asking because of course being outside of the array i can't manage the share with the "Shares" tab).

Thanks.

You can set user access to all UD devices in UD settings.  You can't set user access to a particular device share.

Thanks.

On 10/19/2021 at 5:49 PM, Braulio said:

 

server-diagnostics-20211019-1808.rar 84.81 kB · 1 download

Please post the zip file.

4 hours ago, dlandon said:

Please post the zip file.

 

server-diagnostics-20211019-1808.zip

Wondering if there is a way, and if not, perhaps this would be a request, but a way to organize or group the drives in UD? Currently running some zpools and would love to group the drives used for a pool together to clean it up a bit and be able to visualize better what goes with what.

There are some interest founding about UD disk spindown issue after I rearrange most disk. My setup was 10 data + 2 parity and 16 UD.

 

When 10 array data disk have activity, then UD dev 1-10 won't spindown, but dev 11-16 will spindown.

After only array disk 3,4 have activity, then UD also only dev 3,4 in spinup.

 

I notice UD state spin down not control by UD after 6.9+, so does it is Unraid OS issue ?

 

FYR, parity sync in progress and no other disk activity, OS 6.10.0-RC1.

 

 

 

 

 

 

 

Edited October 21, 20214 yr by Vr2Io

45 minutes ago, muddro said:

Wondering if there is a way, and if not, perhaps this would be a request, but a way to organize or group the drives in UD? Currently running some zpools and would love to group the drives used for a pool together to clean it up a bit and be able to visualize better what goes with what.

 

I am not sure the outlook of zpools in UD, I have two RAID0 pool in UD, I will mask member disk by set to passthrough, then got a clear look.

 

6 minutes ago, Vr2Io said:

 

I am not sure the outlook of zpools in UD, I have two RAID0 pool in UD, I will mask member disk by set to passthrough, then got a clear look.

 

Yes I've done the same with mine, but would be nice to be able to arrange the drives and maybe insert spacers between rows to be able to segregate groups of drives. Don't know if thats possible, but would make it much more visually appealing.