9 minutes ago, SimonF said:

Have you enabled sharing in UD of the device via the cog and then slider in options?

 

Yes, sharing is enabled...

18 minutes ago, Erich said:

Is there anyone who can help me with this?

Have you also set the drive to share?

2 hours ago, dlandon said:

Have you also set the drive to share?

Not sure what you mean. The drive is being shared in Unraid as you can see in the images I attached earlier. If you are talking about setting the share permissions in the Windows machine, I cannot, as the drive doesn't show in the Windows PC.

I just noticed that even though the Share setting is turned on, when I click on the Cog wheel, the share reads "No". 

Edited March 19, 20233 yr by Erich

12 hours ago, dlandon said:

The device is not set to share as you have said from the tooltip:

Mar 17 20:13:49 Wyse unassigned.devices: Device '/dev/sdb1' is not set to be shared.

 

Show a screen shot of the device settings.

2 hours ago, Erich said:

I just noticed that even though the Share setting is turned on, when I click on the Cog wheel, the share reads "No". 

Click on the three gears icon and set the "Share" switch on.  That will share the device with the permissions you set in UD Settings,

57 minutes ago, dlandon said:

Click on the three gears icon and set the "Share" switch on.  That will share the device with the permissions you set in UD Settings,

It is on, even though the menu that appears when I hover over the Gears says it is off...

 

Edited March 19, 20233 yr by Erich

2 hours ago, Erich said:

It is on, even though the menu that appears when I hover over the Gears says it is off...

 

I'm having this same issue - can see my above screenshot confirming the switch is turned on, but the tooltip still says "Share: No".

 

Edit: maybe relevant - mine is also an external drive.

Edited March 20, 20233 yr by mattalat

6 minutes ago, mattalat said:

I'm having this same issue - can see my above screenshot confirming the switch is turned on, but the tooltip still says "Share: No".

 

Edit: maybe relevant - mine is also an external drive.

How are the drives connected?  Post diagnostics and a screen shot of the UD page.

6 minutes ago, dlandon said:

How are the drives connected?  Post diagnostics and a screen shot of the UD page.

USB 3.0.

Attached screenshot of UD settings page and diagnostics.

 

wyse-diagnostics-20230318-2050.zip

34 minutes ago, mattalat said:

USB 3.0.

Attached screenshot of UD settings page and diagnostics.

 

wyse-diagnostics-20230318-2050.zip 95.33 kB · 1 download

Fixed in the next release of UD.

Just now, dlandon said:

Fixed in the next release of UD.

You rock. Thanks!

4 hours ago, dlandon said:

How are the drives connected?  Post diagnostics and a screen shot of the UD page.

Drive is attached via USB. Diagnostics and screenshot of UD page is attached...

phoenix-diagnostics-20230319-2307.zip

Edited March 20, 20233 yr by Erich

4 hours ago, dlandon said:

Fixed in the next release of UD.

Is this what is causing me to not be able to connect to the drive on my windows PC? (The drive is physically connected to my Unraid server via USB, but I need to be able to connect to it remotely via my windows PC).

Just updated the UD plugin. The problem is now fixed. I can access my external drive from my windows 10 PC. Thank you.

I just tried to erase and format an nvme drive and I selected btrfs and got vfat and now I cant mount it...

 

Is this normal?

 

 

Mar 20 20:45:50 Datasaurusrex unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'.
Mar 20 20:47:32 Datasaurusrex unassigned.devices: Format device '/dev/nvme0n1'.
Mar 20 20:47:32 Datasaurusrex unassigned.devices: Device '/dev/nvme0n1' block size: 976773168.
Mar 20 20:47:32 Datasaurusrex unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'.
Mar 20 20:47:32 Datasaurusrex unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.0107248 s, 196 MB/s
Mar 20 20:47:34 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Mar 20 20:47:34 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Mar 20 20:47:34 Datasaurusrex unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'.
Mar 20 20:47:34 Datasaurusrex kernel: nvme0n1: p1
Mar 20 20:47:34 Datasaurusrex unassigned.devices: Create mbr partition table result: write mbr signature done 
Mar 20 20:47:36 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Mar 20 20:47:36 Datasaurusrex kernel: nvme0n1: p1
Mar 20 20:47:36 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Mar 20 20:47:36 Datasaurusrex unassigned.devices: Formatting disk '/dev/nvme0n1' with 'btrfs' filesystem.
Mar 20 20:47:36 Datasaurusrex unassigned.devices: Format drive command: /sbin/mkfs.btrfs -f '/dev/nvme0n1p1' 2>&1
Mar 20 20:47:38 Datasaurusrex kernel: BTRFS: device fsid 3eaa032f-8941-45fb-8d24-37c5ba01353f devid 1 transid 6 /dev/nvme0n1p1 scanned by mkfs.btrfs (16143)
Mar 20 20:47:39 Datasaurusrex unassigned.devices: Format disk '/dev/nvme0n1' with 'zfs' filesystem: btrfs-progs v6.0.1 See http://btrfs.wiki.kernel.org for more information.  Performing full device TRIM /dev/nvme0n1p1 (465.76GiB) ... NOTE: several default settings have changed in version 5.15, please make sure       this does not affect your deployments:       - DUP for metadata (-m dup)       - enabled no-holes (-O no-holes)       - enabled free-space-tree (-R free-space-tree)  Label:              (null) UUID:               3eaa032f-8941-45fb-8d24-37c5ba01353f Node size:          16384 Sector size:        4096 Filesystem size:    465.76GiB Block group profiles:   Data:             single            8.00MiB   Metadata:         DUP               1.00GiB   System:           DUP               8.00MiB SSD detected:       yes Zoned device:       no Incompat features:  extref, skinny-metadata, no-holes Runtime features:   free-space-tree Checksum:           crc32c Number of devices:  1 Devices:    ID        SIZE  PATH     1   465.76GiB  /dev/nvme0n1p1 
Mar 20 20:47:42 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Mar 20 20:47:42 Datasaurusrex kernel: nvme0n1: p1
Mar 20 20:47:42 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Mar 20 20:47:57 Datasaurusrex unassigned.devices: Mounting partition 'nvme0n1p1' at mountpoint '/mnt/disks/S3X4NB0K428321V'...
Mar 20 20:47:57 Datasaurusrex unassigned.devices: Mount cmd: /sbin/mount -t 'vfat' -o rw,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/nvme0n1p1' '/mnt/disks/S3X4NB0K428321V'
Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): bogus number of reserved sectors
Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): Can't find a valid FAT filesystem
Mar 20 20:48:00 Datasaurusrex unassigned.devices: Mount of 'nvme0n1p1' failed: 'mount: /mnt/disks/S3X4NB0K428321V: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '
Mar 20 20:48:00 Datasaurusrex unassigned.devices: Partition 'S3X4NB0K428321V' cannot be mounted.

 

Edited March 21, 20233 yr by WexfordStyle
add syslog exerpt

39 minutes ago, WexfordStyle said:

I just tried to erase and format an nvme drive and I selected btrfs and got vfat and now I cant mount it...

 

Is this normal?

It's not very clear what's going on.  I see a format btrfs, followed by a format zfs, and then a mount of a vfat.  Clear the drive and try again.

 

After you do that, post your diagnostics.

Hi Team!

 

Sadly I can no longer successfully complete my rsync script within UD,  it runs but ends with so many I/O errors. I have tried everything I can think of, multiple drives, changing sata cables and even using a Sata to usb adaptor but to no avail.

 

I've come to the conclusion that something has changed within UD

 

My error is as follows:

 

Quote

Executing: 05_-_Videos_-__Pictures_-_Music_-_SYNC.sh 2>&1

Source Path is /mnt/user/Multimedia/Music Destination Path is /mnt/disks/05 - Videos - Pictures - Music - SYNC
Source Path is /mnt/user/Multimedia/Pictures Destination Path is /mnt/disks/05 - Videos - Pictures - Music - SYNC
rsync: [generator] readlink_stat("/mnt/disks/05 - Videos - Pictures - Music - SYNC/Pictures/Tommy/ROV - Offshore/Offshore - Sunsets & Moon") failed: Input/output error (5)
rsync: [generator] readlink_stat("/mnt/disks/05 - Videos - Pictures - Music - SYNC/Pictures/Tommy/ROV - Offshore/Random - Sea Life, Bioluminescent algae, etc") failed: Input/output error (5)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1336) [sender=3.2.7]
Source Path is /mnt/user/Multimedia/Videos Destination Path is /mnt/disks/05 - Videos - Pictures - Music - SYNC
rsync: [generator] readlink_stat("/mnt/disks/05 - Videos - Pictures - Music - SYNC/Videos/Tommy's Videos/ROV - Offshore/Lightning @ Sea") failed: Input/output error (5)
rsync: [generator] readlink_stat("/mnt/disks/05 - Videos - Pictures - Music - SYNC/Videos/Tommy's Videos/ROV - Offshore/Man Basket @ Sea") failed: Input/output error (5)
rsync: [generator] readlink_stat("/mnt/disks/05 - Videos - Pictures - Music - SYNC/Videos/Tommy's Videos/ROV - Offshore/Random - Sea Life, Bioluminescent algae, etc") failed: Input/output error (5)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1336) [sender=3.2.7] 

 

 

 

Also i have attached my script also. 

05_-_Videos_-__Pictures_-_Music_-_SYNC.sh

 

OK.... nothing to do with UD..... I think?

 

That's 2 x drives that got corrupted somehow, they were working fine when i last used them (used 2 months ago for same backups, then they sat on a shelf) . I plug them into a spare bay on 3.5" enclosure - mount - run script, but today the 1st drive seized up with the above errors, then I tried the 2nd drive with a different script and got the same result. 

 

1st ntfs drive failed to repair in Windows 10, but I could access all the files and copy to and from them in both windows and unraid. But after a format they worked fine and completed the UD rsync script. 

 

2nd - I was able to repair in Windows 10 - I also made an edit to the script to "delete-before" in rsync script as the drive was running out of space before deleting the other files.

 

Sorry for posting in wrong forum, so clueless as to what happened today, I did reboot the server a few times during troubleshooting, not sure if that helped.

 

Also attached a log file.

 

Anyhow all good, would appreciate a reply if have missed something so this doesn't happen again.

 

Thanks

wacko-unraid-syslog-20230323-0919.zip

Edited March 23, 20233 yr by wacko37
Further troubleshooting

Can the spin-up/down indicator of the unassigned disks be disabled when a SMART test is running? Accidentally clicked on them because I was managing on my tiny phone screen and thought I'd have to restart the 14+ hour long SMART test. Thankfully the drive didn't abort the test but I'd like to prevent something like this happening in the future.

11 hours ago, ericswpark said:

Can the spin-up/down indicator of the unassigned disks be disabled when a SMART test is running? Accidentally clicked on them because I was managing on my tiny phone screen and thought I'd have to restart the 14+ hour long SMART test. Thankfully the drive didn't abort the test but I'd like to prevent something like this happening in the future.

Implemented in the next release of UD.

On 3/1/2023 at 9:59 PM, dlandon said:

That doesn't mean your router/dhcp server has finished handing out IP addresses.

 

Create a User Script that starts on the first array start only with the followiing contents:

sleep 10
/usr/local/sbin/rc.unassigned mount autoshares

What this will do is wait 10 seconds (feel free to adjust this), and then re-auto mount remote shares.  If the share is already mounted, nothing will change.  If an auto mount share is not mounted, it will then be mounted.

 

Hello!

 

Sorry for responding so late, your script works fine, but I hav to put 25 sec instead of 10.

Don't know why, but it works!

 

Big thanks !

I'm trying to use unassigned devices to share an exFat-formatted flash drive over SMB.

 

It looks like it should work, the share is visible and I can read files fine but write errors out – on Windows eventually and on Mac immediately (all copied files are 0 bytes.)

 

I thought it might be the flash drive but with the CLI I can copy multi-gig files to its mount point under /mnt/disks/ consistently.

 

I've tried with SMB security set to Public and Private, force user 'nobody' yes and no, same result.

 

I'm on 6.12.0-rc2 - could that be the issue?

I haven't tried with earlier versions.

nas-diagnostics-20230327-0814.zip

4 hours ago, CS01-HS said:

I'm trying to use unassigned devices to share an exFat-formatted flash drive over SMB.

 

It looks like it should work, the share is visible and I can read files fine but write errors out – on Windows eventually and on Mac immediately (all copied files are 0 bytes.)

 

I thought it might be the flash drive but with the CLI I can copy multi-gig files to its mount point under /mnt/disks/ consistently.

 

I've tried with SMB security set to Public and Private, force user 'nobody' yes and no, same result.

 

I'm on 6.12.0-rc2 - could that be the issue?

I haven't tried with earlier versions.

nas-diagnostics-20230327-0814.zip 206.07 kB · 0 downloads

Turn off the 'macOS Interroperability' in the SMB Settings and see if you still have the issue with the Windows PC.

I did and it seems to be working now both on Windows and Mac, thanks.

In windows event log I see entries like below referencing the share but maybe they're expected:

 

Are there specific tests you'd like me to run before I restore 'macOS Interoperability' ?

 

EDIT: Darn, I spoke too soon. The copy operation in windows just failed with another entry like the above in the event log.

Edited March 27, 20233 yr by CS01-HS

35 minutes ago, CS01-HS said:

EDIT: Darn, I spoke too soon. The copy operation in windows just failed with another entry like the above in the event log.

Post another diagnostics.