9 minutes ago, dlandon said:

Now post diagnostics zip file.  Tools->Diagnostics.

unraid01-diagnostics-20200422-0232.zip

15 minutes ago, TrondHjertager said:

unraid01-diagnostics-20200422-0232.zip 155.21 kB · 1 download

UD thinks the disk is 'zfs_member' (obviously).  I have no idea why that is happening.

Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1'
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted.
Apr 22 02:19:16 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'...
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2'
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted.
Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc1'...
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1'
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted.
Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'...
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2'
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted.

The only suggestion I have is to format the disk with UD, then write the files to the drive on the other computer.

2 hours ago, dlandon said:

UD thinks the disk is 'zfs_member' (obviously).  I have no idea why that is happening.

Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1'
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted.
Apr 22 02:19:16 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'...
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2'
Apr 22 02:19:16 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:16 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted.
Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc1'...
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc1' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part1'
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc1' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part1: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part1' could not be mounted.
Apr 22 02:19:55 UNRAID01 unassigned.devices: Adding disk '/dev/sdc2'...
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount drive command: /sbin/mount -t zfs_member -o rw,auto,async,noatime,nodiratime '/dev/sdc2' '/mnt/disks/ST2000NM0011_Z1P2VKMV-part2'
Apr 22 02:19:55 UNRAID01 unassigned.devices: Mount of '/dev/sdc2' failed. Error message: mount: /mnt/disks/ST2000NM0011_Z1P2VKMV-part2: unknown filesystem type 'zfs_member'. 
Apr 22 02:19:55 UNRAID01 unassigned.devices: Partition 'ST2000NM0011_Z1P2VKMV-part2' could not be mounted.

The only suggestion I have is to format the disk with UD, then write the files to the drive on the other computer.

Okey. Thanks a lot for your time and help  

I have three hard drives. One brand new WD Red.

One xfs formatted shucked drive with data on.

One NTFS formatted shucked drive with data on.

 

When I put them in the server, there's no option under UD to either format them or mount them.

 

What am I doing wrong?

Edited April 22, 20206 yr by cinereus

1 hour ago, cinereus said:

I have three hard drives. One brand new WD Red.

One xfs formatted shucked drive with data on.

One NTFS formatted shucked drive with data on.

 

When I put them in the server, there's no option under UD to either format them or mount them.

 

What am I doing wrong?

In UD settings be sure destructive mode is on.

4 hours ago, dlandon said:

In UD settings be sure destructive mode is on.

That doesn't explain why I can't mount that. I'm not 100% sure but it out that it doesn't recognise the disk filesystem(?) even when formatted as JBOD in a WD My Book Duo.

9 hours ago, cinereus said:

That doesn't explain why I can't mount that. I'm not 100% sure but it out that it doesn't recognise the disk filesystem(?) even when formatted as JBOD in a WD My Book Duo.

If Linux doesn't recognize the file system, UD can't mount it.

1 hour ago, dlandon said:

If Linux doesn't recognize the file system, UD can't mount it.

I realise that now. I thought they were both just standard NTFS and exFAT but 🤷‍♀️

Mounting unassigned devices as SMB shares?

 

Normally I don't have any problems with UAD shares

And I can mount any internal Unraid shared folder to NextCloud

But for some reason I can get UAD shares working with Nextcloud?

 

Could this be related to the Smb v1 or v2 thing? or because its a shared drive and not a folder share?

If I write \\192.168.0.6\ I get listed all shares (except UAD drive shares) but writing the share drive names works

\\192.168.0.6\domains_ssd\ or is this just not possible because its not a folder share but a whole drive share?

 

Example:

 

 

 

 

 

 

New to Unraid. All was well until yesterday. I'm getting this error:

 

Warning: syntax error, unexpected '=' in Unknown on line 1 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1468

16 minutes ago, dariusz65 said:

New to Unraid. All was well until yesterday. I'm getting this error:

 

Warning: syntax error, unexpected '=' in Unknown on line 1 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1468

Post diagnostics.  You have not provided enough information to allow me to help you.

9 minutes ago, dlandon said:

Post diagnostics.  You have not provided enough information to allow me to help you.

Attached

diagnostics-20200423-1417.zip

1 hour ago, dariusz65 said:

Attached

diagnostics-20200423-1417.zip 117.51 kB · 1 download

Disk sdk does not have a serial number.  This is a Linux issue and is probably the reason for the php error.  Remove it from the system?

 

Your sdd disk does not have a format that UD can mount.  Why do you have it set to auto mount?

Apr 23 13:41:12 Borgcube unassigned.devices: Mounting 'Auto Mount' Devices...
Apr 23 13:41:12 Borgcube emhttpd: Warning: syntax error, unexpected '=' in Unknown on line 1
Apr 23 13:41:12 Borgcube emhttpd:  in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1468
Apr 23 13:41:12 Borgcube unassigned.devices: Disk '/dev/sdk' does not have a serial number and cannot be mounted.
Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd1'...
Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd1' '/mnt/disks/SEAGATE_ST2000NM0043-part1'
Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd1' failed. Error message: mount: /mnt/disks/SEAGATE_ST2000NM0043-part1: unknown filesystem type 'linux_raid_member'. 
Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'SEAGATE ST2000NM0043-part1' could not be mounted.
Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd2'...
Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd2' '/mnt/disks/SEAGATE_ST2000NM0043-part2'
Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd2' failed. Error message: mount: /mnt/disks/SEAGATE_ST2000NM0043-part2: unknown filesystem type 'linux_raid_member'. 
Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'SEAGATE ST2000NM0043-part2' could not be mounted.
Apr 23 13:41:12 Borgcube unassigned.devices: Adding disk '/dev/sdd3'...
Apr 23 13:41:12 Borgcube unassigned.devices: Mount drive command: /sbin/mount -t linux_raid_member -o rw,auto,async,noatime,nodiratime '/dev/sdd3' '/mnt/disks/Subcube2'
Apr 23 13:41:12 Borgcube unassigned.devices: Mount of '/dev/sdd3' failed. Error message: mount: /mnt/disks/Subcube2: unknown filesystem type 'linux_raid_member'. 
Apr 23 13:41:12 Borgcube unassigned.devices: Partition 'Subcube2' could not be mounted.
Apr 23 13:41:12 Borgcube unassigned.devices: Disk with serial 'Cruzer_Blade_4C530000121123118320', mountpoint 'PA_WINPE' is not set to auto mount and will not be mounted.

 

1 hour ago, dlandon said:

Disk sdk does not have a serial number.  This is a Linux issue and is probably the reason for the php error.  Remove it from the system?

 

Your sdd disk does not have a format that UD can mount.  Why do you have it set to auto mount?

 

Thank you for looking into this. I removed that disk couple days ago as parity drive to copy substantial amount of data to the unraid.  I put it back as parity and all is well.

Edited April 23, 20206 yr by dariusz65

There's an issue using WD My Book devices since they com up under the same serial ID.

 

 

If you try to rename the readable partition, it renames them both! Meaning you then can't mount them both. It should check to rename by device ID not Identification ID maybe?

2 hours ago, cinereus said:

There's an issue using WD My Book devices since they com up under the same serial ID.

 

 

If you try to rename the readable partition, it renames them both! Meaning you then can't mount them both. It should check to rename by device ID not Identification ID maybe?

If by device ID you mean sdg sdh that is not guaranteed to stay the same after reboot. In fact, with removable drives it is very likely to change when you plug them in again.

2 hours ago, trurl said:

If by device ID you mean sdg sdh that is not guaranteed to stay the same after reboot. In fact, with removable drives it is very likely to change when you plug them in again.

I know. I wasn't saying persistent device ID. I just meant for avoiding this renaming bug once connected.

7 hours ago, cinereus said:

I know. I wasn't saying persistent device ID. I just meant for avoiding this renaming bug once connected.

It's not a bug.  The disk serial number must be unique.  That's how UD identifies a disk.  It applies to all UD operations like mounting, renaming, etc.  You'll have to remove one of the duplicate disks.

7 hours ago, cinereus said:

I wasn't saying persistent device ID. I just meant for avoiding this renaming bug once connected.

If you did indeed mean sdg sdh, then what would your proposed solution do with Automount devices? How could it know which should automount and which script to run if there was an associated script? Of course it has to be something that persists or it will just be more problems.

Hi Guys.

 

I'm mounting SMB shares from another server on my unraid server with unassigned devices. But these shares becomes re shared as an SMB share of my unraid server. I don't want this behaviour. How do I turn it off? It happens with every SMB mount I create.

6 hours ago, dlandon said:

It's not a bug.  The disk serial number must be unique.  That's how UD identifies a disk.  It applies to all UD operations like mounting, renaming, etc.  You'll have to remove one of the duplicate disks.

The issue is I now can't even add the disks independently as they have become entangled and changes to one reflect in the other. Sometimes it even mounts the EFI partition instead but there's no consistency.

 

I want aware of auto mount issues but that is a fair point. Perhaps the best way to avoid such issues is to prevent renaming when two connected disks share the same serial number? I'm not sure if the best way to approach this or if there's a unique data point that could be used. 

Edited April 25, 20206 yr by cinereus

8 minutes ago, cinereus said:

share the same serial number?

Duplicate serial numbers is clearly a bug at the manufacurer's side (WD).

A serial number is used to uniquely identify a product and is used in the RMA process of the vendor.

2 hours ago, Jezper said:

Hi Guys.

 

I'm mounting SMB shares from another server on my unraid server with unassigned devices. But these shares becomes re shared as an SMB share of my unraid server. I don't want this behaviour. How do I turn it off? It happens with every SMB mount I create.

That's the way UD works.  You can make the shares hidden in UD settings.

2 hours ago, cinereus said:

The issue is I now can't even add the disks independently as they have become entangled and changes to one reflect in the other. Sometimes it even mounts the EFI partition instead but there's no consistency.

Remove both disks and then delete all references to their serial numbers in the "Historical Devices" section.

2 hours ago, cinereus said:

I want aware of auto mount issues but that is a fair point. Perhaps the best way to avoid such issues is to prevent renaming when two connected disks share the same serial number? I'm not sure if the best way to approach this or if there's a unique data point that could be used. 

The unique data point is the serial number.  The best way to handle this is to install disks with unique serial numbers.

4 hours ago, cinereus said:

best way to avoid such issues is to prevent renaming when two connected disks share the same serial number?

What exactly do you mean by "renaming"?