thank you. just mounting does allow me to see it in krusader along with the partitions. i don't know why i was passing through before. 

17 minutes ago, dlandon said:

You have a partition 3 that is causing UD to choke.  There is no file system on partition 3.  Can I get you to upgrade to 6.11.5?  There are better diagnostics that will help me understand why UD is choking on partition 3.  If you are willing to upgrade, give me new diagnostics.

Sure, here's after upgrading to 6.11.5.

 

tower-diagnostics-20230205-2217.zip

1 hour ago, Gepard said:

Sure, here's after upgrading to 6.11.5.

 

tower-diagnostics-20230205-2217.zip 134.26 kB · 0 downloads

Show the output of this command:

/sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p3)

 

Great, thanks

Just a heads up the latest update is still not working for my nvme drive. I saw in the patch notes there was an update to improve the clear disk however my drive still only works when formatted as ntfs.

gringotts-diagnostics-20230205-2139.zip

9 hours ago, dlandon said:

Show the output of this command:

/sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p3)

 

root@Tower:~# /sbin/udevadm info -q path -n /dev/nvme1n1p3
/devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p3
root@Tower:~# /sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p3)
DEVLINKS=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S4J4NZFNC00208H-part3 /dev/disk/by-id/nvme-eui.0025385c019e3454-part3 /dev/disk/by-partlabel/No\x20name /dev/disk/by-partuuid/b7e646c6-3301-4944-ad2f-478eb04a93e9
DEVNAME=/dev/nvme1n1p3
DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p3
DEVTYPE=partition
DISKSEQ=23
ID_MODEL=Samsung SSD 970 EVO Plus 2TB
ID_PART_ENTRY_DISK=259:2
ID_PART_ENTRY_FLAGS=0x8000000000000000
ID_PART_ENTRY_NAME=No\x20name
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=1228800
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_SIZE=32768
ID_PART_ENTRY_TYPE=e3c9e316-0b5c-4db8-817d-f92df00215ae
ID_PART_ENTRY_UUID=b7e646c6-3301-4944-ad2f-478eb04a93e9
ID_PART_TABLE_TYPE=gpt
ID_PART_TABLE_UUID=9eb11b06-e3b4-4979-8efb-9c3e9e87e993
ID_SERIAL=Samsung SSD 970 EVO Plus 2TB_S4J4NZFNC00208H
ID_SERIAL_SHORT=S4J4NZFNC00208H
ID_WWN=eui.0025385c019e3454
MAJOR=259
MINOR=5
PARTN=3
PARTNAME=No name
SUBSYSTEM=block
USEC_INITIALIZED=30030581

 

The name look sus to me

On 2/2/2023 at 1:45 PM, dlandon said:

That's what I was talking about.  You need to unmount the device, then set a different volume, then remount.  I don't see anywhere in the logs where you attempted to mount an apfs drive.

 

I'm having trouble understanding what is going on from your logs.  Do this:

• Set all devices to not auto mount.
• Reboot the server leaving everything connected.  It looks like some of the devices are USB devices.
• After the server has rebooted, click on the mount button on one of the drives that didn't mount and post diagnostics.

Just to provide an update from my side. For some reason the Western Digital Element drives weren't able to mount simultaneously. After rebooting the server I was able to read them out fine, just not at the same time. Thanks again for taking the time to think along!  

7 hours ago, Andrew Dens said:

Just a heads up the latest update is still not working for my nvme drive. I saw in the patch notes there was an update to improve the clear disk however my drive still only works when formatted as ntfs.

gringotts-diagnostics-20230205-2139.zip 220.16 kB · 1 download

You have some zfs residue left on the disk that UD can't remove:

Feb  5 21:35:52 Gringotts unassigned.devices: Successfully unmounted 'nvme0n1p1'
Feb  5 21:35:52 Gringotts  zed[4419]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by ntfs)
Feb  5 21:36:04 Gringotts unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'.
Feb  5 21:36:04 Gringotts  zed[4419]: zed_disk_event:
Feb  5 21:36:04 Gringotts  zed[4419]: #011class: EC_dev_status
Feb  5 21:36:04 Gringotts  zed[4419]: #011subclass: dev_dle
Feb  5 21:36:04 Gringotts  zed[4419]: #011dev_name: /dev/nvme0n1p1
Feb  5 21:36:04 Gringotts  zed[4419]: #011path: /devices/pci0000:00/0000:00:01.2/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1
Feb  5 21:36:04 Gringotts  zed[4419]: #011devid: nvme-CT500P2SSD8_2239E66F2DAD-part1
Feb  5 21:36:04 Gringotts  zed[4419]: #011dev_size: 500106788864
Feb  5 21:36:04 Gringotts  zed[4419]: #011dev_parent_size: 500107862016

You'll need to do some manual operations and/or remove the zfs master plugin.  I don't know enough about how it works to help you other than that.

4 hours ago, Gepard said:

root@Tower:~# /sbin/udevadm info -q path -n /dev/nvme1n1p3
/devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p3
root@Tower:~# /sbin/udevadm info --query=property --path $(/sbin/udevadm info -q path -n /dev/nvme1n1p3)
DEVLINKS=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S4J4NZFNC00208H-part3 /dev/disk/by-id/nvme-eui.0025385c019e3454-part3 /dev/disk/by-partlabel/No\x20name /dev/disk/by-partuuid/b7e646c6-3301-4944-ad2f-478eb04a93e9
DEVNAME=/dev/nvme1n1p3
DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:07:00.0/nvme/nvme1/nvme1n1/nvme1n1p3
DEVTYPE=partition
DISKSEQ=23
ID_MODEL=Samsung SSD 970 EVO Plus 2TB
ID_PART_ENTRY_DISK=259:2
ID_PART_ENTRY_FLAGS=0x8000000000000000
ID_PART_ENTRY_NAME=No\x20name
ID_PART_ENTRY_NUMBER=3
ID_PART_ENTRY_OFFSET=1228800
ID_PART_ENTRY_SCHEME=gpt
ID_PART_ENTRY_SIZE=32768
ID_PART_ENTRY_TYPE=e3c9e316-0b5c-4db8-817d-f92df00215ae
ID_PART_ENTRY_UUID=b7e646c6-3301-4944-ad2f-478eb04a93e9
ID_PART_TABLE_TYPE=gpt
ID_PART_TABLE_UUID=9eb11b06-e3b4-4979-8efb-9c3e9e87e993
ID_SERIAL=Samsung SSD 970 EVO Plus 2TB_S4J4NZFNC00208H
ID_SERIAL_SHORT=S4J4NZFNC00208H
ID_WWN=eui.0025385c019e3454
MAJOR=259
MINOR=5
PARTN=3
PARTNAME=No name
SUBSYSTEM=block
USEC_INITIALIZED=30030581

 

The name look sus to me

The only thing I can suggest is to manually remove partition 3.  The partition has no file system anyway.

I am writing to express my extreme overwhelming everengoulfing neverending 24/7/356 forever  rage

 

about how slow the MAIN page is when UD plugin loads the disks stuff.

 

Why is it so and how to fix it ?

 

Thanks.

Edited February 7, 20233 yr by GRRRRRRR

Hi All, Got an issue with one of my Unassigned Drives, I've got 7 drives all showing as shares fine, I've added another and its showing fine in Unraid but I can't see it on my Shares on my Windows PC, I've tried restarting Unraid, leaving it several hours, Unmounting and re-mounting. All the others show up just fine, Any ideas? No idea why this specific drive share isn't showing.  Checking the shares in Krusader I can see the drive, but no files are showing inside.

Edited February 7, 20233 yr by [email protected]
Update and Added Screenshot

4 hours ago, GRRRRRRR said:

I am writing to express my extreme overwhelming everengoulfing neverending 24/7/356 forever  rage

 

about how slow the MAIN page is when UD plugin loads the disks stuff.

 

Why is it so and how to fix it ?

 

Thanks.

Post your diagnpstics.  UD shouldn't take that long to display.

1 hour ago, [email protected] said:

Hi All, Got an issue with one of my Unassigned Drives, I've got 7 drives all showing as shares fine, I've added another and its showing fine in Unraid but I can't see it on my Shares on my Windows PC, I've tried restarting Unraid, leaving it several hours, Unmounting and re-mounting. All the others show up just fine, Any ideas? No idea why this specific drive share isn't showing.  Checking the shares in Krusader I can see the drive, but no files are showing inside.

Have you set that disk to share?  Click the three gears ad turn on "Share".

On 2/5/2023 at 2:46 PM, shpitz461 said:

Here you go. There was an update this morning, but the errors still appear when I'm on MAIN page.

Thanks!

selanas-diagnostics-20230205-1444.zip 351.08 kB · 0 downloads

Hi @dlandon, did you get a chance to look @ the errors posted in syslog when on MAIN page?

Thanks!

58 minutes ago, shpitz461 said:

Hi @dlandon, did you get a chance to look @ the errors posted in syslog when on MAIN page?

Thanks!

One of your devices has some php reserved characters in a field - '~', '!', etc.  Post a screen shot of your UD page so we can find the disk giving the problems and see where the characters are showing up.

Here you go:

1 hour ago, dlandon said:

Have you set that disk to share?  Click the three gears ad turn on "Share".

Hi Dilandon, Yeah, all set to share, in fact it won't let me turn share off, if i do and press save it just turns immediately back on. 

12 minutes ago, shpitz461 said:

Here you go:

Your Dev 3 device has a partition with no file system.  That's why the 'Mount' button is greyed out.  You need to get rid of that partition.  A disk with a partition and no file system is fairly useless anyway.  What do you intend to do with that disk?

14 minutes ago, [email protected] said:

Hi Dilandon, Yeah, all set to share, in fact it won't let me turn share off, if i do and press save it just turns immediately back on. 

The buttons at the top are immediate and you don't need to click 'Save'.  That being said, do you have the 'Auto Mount USB Devices?' set to 'Yes'?

 

It sounds as if the configuration file is corrupt.  You could look at the /flash/plugins/unassigned.devices/unassigned.devices.cfg with an editor and see if you see anything amiss.  The file is fairly easy to read.  PM the file to me if you are unsure of what you are looking at.  Don't post it on the forum it contains a password seed.

10 minutes ago, dlandon said:

Your Dev 3 device has a partition with no file system.  That's why the 'Mount' button is greyed out.  You need to get rid of that partition.  A disk with a partition and no file system is fairly useless anyway.  What do you intend to do with that disk?

The NVMe is actually a pass-through to a VM (which is currently off), and it does have an NTFS GPT partition on it.

I can't config it @ all since there is no cog for it, anything I could do to make it recognize the NTFS partition?

2 hours ago, dlandon said:

The buttons at the top are immediate and you don't need to click 'Save'.  That being said, do you have the 'Auto Mount USB Devices?' set to 'Yes'?

 

It sounds as if the configuration file is corrupt.  You could look at the /flash/plugins/unassigned.devices/unassigned.devices.cfg with an editor and see if you see anything amiss.  The file is fairly easy to read.  PM the file to me if you are unsure of what you are looking at.  Don't post it on the forum it contains a password seed.

Thanks Dlandon, So ive had a look and everything looks ok to me, nothing different to some of the other shares. Share.1 was set to no so i changed to yet, but no change as of yet, still can't access, very strange.

4 minutes ago, [email protected] said:

Thanks Dlandon, So ive had a look and everything looks ok to me, nothing different to some of the other shares. Share.1 was set to no so i changed to yet, but no change as of yet, still can't access, very strange.

If you make a change to the flash config file, you'll have to click the double arrows icon on the UD page to refresh the ram file that holds the config file.  When UD is operating, the configuration file is in ram and copied to the flash drive when a change is made.

3 minutes ago, dlandon said:

If you make a change to the flash config file, you'll have to click the double arrows icon on the UD page to refresh the ram file that holds the config file.  When UD is operating, the configuration file is in ram and copied to the flash drive when a change is made.

Thanks, have just tried that, still no share showing up on the network, it's so strange that this drive isn't showing up, I might try another drive and see if that works. 

5 minutes ago, dlandon said:

If you make a change to the flash config file, you'll have to click the double arrows icon on the UD page to refresh the ram file that holds the config file.  When UD is operating, the configuration file is in ram and copied to the flash drive when a change is made.

Ignore all of that. It's just showed up. Dlandon, thanks, you've saved me many hours of trial and error here. Will scribble all of this down in my notebook for future reference. Thanks Again 👍

32 minutes ago, [email protected] said:

Ignore all of that. It's just showed up. Dlandon, thanks, you've saved me many hours of trial and error here. Will scribble all of this down in my notebook for future reference. Thanks Again 👍

When you turn on the 'Share' switch, it can take up to two minutes to actually share the disk.