18 minutes ago, dlandon said:

Can UD see them each with a unique identification?  Some drive bays present the disks all with the same ID.  UD can only mount them when they have unique ID's.

no that’s all fine and not the issue 

2 minutes ago, theunraidhomeuser said:

no that’s all fine and not the issue 

What is the issue?

8 hours ago, dlandon said:

What is the issue?

 

hi everyone, I've recently upgraded my Unraid server and added a NVME via PCI adapter.

 

I've formated the NVME in UD and taken out all the partitions multiple times, but whenever it comes out of format, it gives me UDEV button? I've renamed it to nvr1 as it's going to be my drive for my cameras to leave recordings on. I have sharing turned on via SMB and NFS but cannot see it anywhere.

 

Any help would be greatly appreciated:

 

 

 

 

4 minutes ago, UR-jay said:

hi everyone, I've recently upgraded my Unraid server and added a NVME via PCI adapter.

 

I've formated the NVME in UD and taken out all the partitions multiple times, but whenever it comes out of format, it gives me UDEV button? I've renamed it to nvr1 as it's going to be my drive for my cameras to leave recordings on. I have sharing turned on via SMB and NFS but cannot see it anywhere.

 

Any help would be greatly appreciated:

 

 

 

 

This sommetimes happens with nvme drives.  I have yet to figure it out, but the fix is to click on the double arrows icon in the upper right corner and udev should report the correct file format.

3 minutes ago, dlandon said:

This sommetimes happens with nvme drives.  I have yet to figure it out, but the fix is to click on the double arrows icon in the upper right corner and udev should report the correct file format.

 

Oh thank you!! this worked, I was confused by the double arrows icon, which to me is the "refresh" icon I found it and it worked, thank you so much. I've been scratching my head for hours last night trying to figure out why I couldnt see my drive.

1 minute ago, UR-jay said:

 

Oh thank you!! this worked, I was confused by the double arrows icon, which to me is the "refresh" icon I found it and it worked, thank you so much. I've been scratching my head for hours last night trying to figure out why I couldnt see my drive.

The "refresh" causes udev to update UD and what Unraid is reporting as unassigned drives.  Harmless even when it isn't neessarily needed.

9 minutes ago, UR-jay said:

 

Oh thank you!! this worked, I was confused by the double arrows icon, which to me is the "refresh" icon I found it and it worked, thank you so much. I've been scratching my head for hours last night trying to figure out why I couldnt see my drive.

Did you format the disk zfs?

10 minutes ago, dlandon said:

Did you format the disk zfs?

 

yes the disk is formated to ZFS. I've mounted it and I can see it via my Windows machine. 

I'm now trying to get the NFS working to have it mounted on my Frigate server to use exclusively as the NVR drive.

On 11/24/2023 at 3:06 AM, JonathanM said:

 

Thanks, I think I figured it out. PCI-E USB 3.0 cards were simply maxed out... Somebody else explained the endpoint logic to me which seems to work out!

Hi, all,
I'm trying to mount a usb disk to a w10 vm, somehow I sill haven't been able to figure out why I cant get it to work with the disk I need to. (as temporary solution I have it mounted as a network share)

 

I have the latest version of Unassigned Devices and Libvirt Hotplug USB plugins installed. So, what I do is; plug in the usb drive, it appears in the Unassigned Devices section on the main page and I go to the vms tab. Under Hotplug USB, I select the running w10 vm and usb device, and click attach.

Doing this, with a usb drive (fat, exfat) or another 1TB usb hdd (ntfs), will make it pop up in the vm. Exelent, however the drive I need to connect is won't do this.

 

Here the system log of me plugging in a usb, attaching, detaching and removing the drive;

Nov 25 19:01:50 tower kernel: usb 1-5: new high-speed USB device number 4 using xhci_hcd
Nov 25 19:01:50 tower kernel: usb-storage 1-5:1.0: USB Mass Storage device detected
Nov 25 19:01:50 tower kernel: scsi host8: usb-storage 1-5:1.0
Nov 25 19:01:51 tower kernel: scsi 8:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 4
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: Attached scsi generic sg11 type 0
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: [sdl] 60437492 512-byte logical blocks: (30.9 GB/28.8 GiB)
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: [sdl] Write Protect is off
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: [sdl] Mode Sense: 45 00 00 00
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: [sdl] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov 25 19:01:51 tower kernel: sdl: sdl1
Nov 25 19:01:51 tower kernel: sd 8:0:0:0: [sdl] Attached SCSI removable disk
Nov 25 19:01:52 tower unassigned.devices: Disk with ID 'Kingston_DataTraveler_2.0_-0:0 ()' is not set to auto mount.
Nov 25 19:02:28 tower kernel: br0: port 3(vnet1) entered blocking state
Nov 25 19:02:28 tower kernel: br0: port 3(vnet1) entered disabled state
Nov 25 19:02:28 tower kernel: device vnet1 entered promiscuous mode
Nov 25 19:02:28 tower kernel: br0: port 3(vnet1) entered blocking state
Nov 25 19:02:28 tower kernel: br0: port 3(vnet1) entered forwarding state
Nov 25 19:05:09 tower kernel: usb 1-5: reset high-speed USB device number 4 using xhci_hcd
Nov 25 19:05:10 tower kernel: usb-storage 1-5:1.0: USB Mass Storage device detected
Nov 25 19:05:10 tower kernel: scsi host8: usb-storage 1-5:1.0
Nov 25 19:05:11 tower kernel: scsi 8:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 4
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: Attached scsi generic sg11 type 0
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: [sdl] 60437492 512-byte logical blocks: (30.9 GB/28.8 GiB)
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: [sdl] Write Protect is off
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: [sdl] Mode Sense: 45 00 00 00
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: [sdl] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Nov 25 19:05:11 tower kernel: sdl: sdl1
Nov 25 19:05:11 tower kernel: sd 8:0:0:0: [sdl] Attached SCSI removable disk
Nov 25 19:05:12 tower unassigned.devices: Disk with ID 'Kingston_DataTraveler_2.0_-0:0 ()' is not set to auto mount.
Nov 25 19:06:50 tower kernel: br0: port 3(vnet1) entered disabled state
Nov 25 19:06:50 tower kernel: device vnet1 left promiscuous mode
Nov 25 19:06:50 tower kernel: br0: port 3(vnet1) entered disabled state
Nov 25 19:07:51 tower kernel: usb 1-5: USB disconnect, device number 4

 

However I have a 8TB Seagate desktop drive which wont connect, here the system log;

Nov 25 20:30:03 tower kernel: usb 2-5: new SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:30:03 tower kernel: usb-storage 2-5:1.0: USB Mass Storage device detected
Nov 25 20:30:03 tower kernel: scsi host8: usb-storage 2-5:1.0
Nov 25 20:30:04 tower kernel: scsi 8:0:0:0: Direct-Access     Seagate  Desktop          040B PQ: 0 ANSI: 6
Nov 25 20:30:04 tower kernel: sd 8:0:0:0: Attached scsi generic sg11 type 0
Nov 25 20:30:04 tower kernel: sd 8:0:0:0: [sdl] Spinning up disk...
Nov 25 20:30:17 tower kernel: ............ready
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] Very big device. Trying to use READ CAPACITY(16).
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] 15628053167 512-byte logical blocks: (8.00 TB/7.28 TiB)
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] 2048-byte physical blocks
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] Write Protect is off
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] Mode Sense: 4f 00 00 00
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 25 20:30:17 tower kernel: sdl: sdl1
Nov 25 20:30:17 tower kernel: sd 8:0:0:0: [sdl] Attached SCSI disk
Nov 25 20:30:18 tower unassigned.devices: Disk with ID 'ST8000DM004- ()' is not set to auto mount.
Nov 25 20:31:22 tower kernel: sd 8:0:0:0: [sdl] Synchronizing SCSI cache
Nov 25 20:32:03 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:32:33 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:33:17 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:33:47 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:34:31 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 25 20:35:01 tower kernel: usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd

It got stuck here, till i detach; "kernel: hrtimer: interrupt took - ns"

 

Did I miss something, this should work right?

 

Edited November 25, 20232 yr by ZekerPixels

If you want to pass the USB drive through to the VM have you made sure the Passed Through flag is set for that drive in its UD Settings?

1 hour ago, ZekerPixels said:

Did I miss something, this should work right?

 

1 hour ago, ZekerPixels said:

Nov 25 20:30:18 tower unassigned.devices: Disk with ID 'ST8000DM004- ()' is not set to auto mount.

The serial number of that disk is woefully incomplete.  The only thing there is the model number.  There is no seril number.  I'd say that Linux can't handle that.

 

Post diagnostics so I can see what udev reports as the serial number on that disk.  Sometimes some strange characters in the serial number can cause issues.

2 hours ago, itimpi said:

If you want to pass the USB drive through to the VM have you made sure the Passed Through flag is set for that drive in its UD Settings?

A individual drive setting, just to confirm where can I find the passed through flag.

If you refer to the vm settings, then no not checked, but also not needed because of the Libvirt Hotplug USB plugin. Which works perfectly to mount usb drives like a usb stick and other hdds.

 

1 hour ago, dlandon said:

The serial number of that disk is woefully incomplete.  The only thing there is the model number.  There is no seril number.  I'd say that Linux can't handle that.

Post diagnostics so I can see what udev reports as the serial number on that disk.  Sometimes some strange characters in the serial number can cause issues.

Sorry, that was my part in anonymizing information, serial number, my server also isnt called tower, etc.

13 hours ago, ZekerPixels said:

A individual drive setting, just to confirm where can I find the passed through flag.

If you click on the Settings icon for a particular drive under UD then it is a toggle there.   It needs to be set as otherwise UD will take control of the drive stopping the Libvirt Hotplug USB handling it.

1 hour ago, itimpi said:

If you click on the Settings icon for a particular drive under UD then it is a toggle there.   It needs to be set as otherwise UD will take control of the drive stopping the Libvirt Hotplug USB handling it.

I'm currently using that drive with the UD share mounted. Anyways, I didn't see the passed trough toggle initially, because that option disappears when it is mounted.

 

Trying to pass trough my 8TB seagate desktop smr nfts hdd, while doing exactly thesame, same settings, gets stuck every time on that reset line after synchronizing in the log.

sd 8:0:0:0: [sdl] Synchronizing SCSI cache
usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd
usb 2-5: reset SuperSpeed USB device number 2 using xhci_hcd

 

I posted a part of the system log before, with a usb that I did manage to mount in the vm and one that doesnt. I tried it again, paying attention to the toggles in the UD settings, but they are set thesame.

Meanwhile I also tried various usb sticks (FAT, exFAT), a 1TB portable ntfs hdd and they mount to the vm directly every time. However I when trying my hdd dock (which i havent used on unraid before) with other big hdds, it doesnt work either.

Edited November 26, 20232 yr by ZekerPixels
removed an unrelated error, fixed

12 minutes ago, ZekerPixels said:

Meanwhile I also tried various usb sticks (FAT, exFAT), a 1TB portable ntfs hdd and they mount to the vm directly every time.

What is the file system on the disk that won't mount in the Windows VM?

2 minutes ago, dlandon said:

What is the file system on the disk that won't mount in the Windows VM?

also ntfs, 8TB as a single partition.

Edited November 26, 20232 yr by ZekerPixels

1 minute ago, ZekerPixels said:

also ntfs, 8TB as a single partition.

Take it to a Windows PC and check the file system.

19 minutes ago, dlandon said:

Take it to a Windows PC and check the file system.

In disk management under properties of the drive, tools and check now.

Result; Your drive was successfully scanned. Windows successfully scanned the drive. No errors where found.

1 minute ago, ZekerPixels said:

In disk management under properties of the drive, tools and check now.

Result; Your drive was successfully scanned. Windows successfully scanned the drive. No errors where found.

Can UD mount the disk?

1 hour ago, dlandon said:

Can UD mount the disk?

Yes, I can mount the disk, share the partition over the network, read and write data to it. Everything works, except mounting this drive to the vm.

 

I have now tried multiple usb storage devices to pass trough, and they all work as expected;

- usb sticks of various sizes formatted FAT and exFAT

- usb portable 1TB ntfs hdd

- usb portable 256GB ntfs ssd

- usb exclosure and a usb hdd dock with various 500GB, 1TB, 1,5TB, 2TB, 3TB hdds ntfs or zerod in which case they show up in the w10 disk management.

 

However, using the usb enclosure, which is old, with a 4TB ntfs hdd does mount but is not correctly recognized (it reports 16TB). Using the usb dock, this leads to thesame "reset SuperSpeed USB device number 2 using xhci_hcd" as before, with the 8TB external.

I tried both the external enclosure and hdd dock, with his 4TB drive on a windows machine to verify. and the 4TB also doesn't work in the external enclosure and reports 16TB idk. (as i mentioned, it quite old so it could be a limitation) The 4TB disk with the hdd dock is fine on a windows machine.

 

I only have one 4TB available and the 8TB is an external, so I cant test more. But it appears I only have this vm mounting issue only with big >4TB drives. Everything else works in unRAID and they also work under windows.

 

I also tried passing the usb at boot of the vm (so, not using the Libvirt Hotplug USB plugin), but this leads to thesame "usb 2-5: reset SuperSpeed USB device number 13 using xhci_hcd"

Edited November 26, 20232 yr by ZekerPixels

Is there any way I can add additional mount options? For example compress and autodefrag options for btrfs devices.

I didn't find any relevant discussions in this topic, if so please point me to them, thanks!

The new update isn't processing periods in a host?

 

and all existing configurations are invalid?

2 minutes ago, DiscoverIt said:

The new update isn't processing periods in a host?

 

and all existing configurations are invalid?

There have been some changes in UD to detect configurations that will cause UD to have problems.  Remove the shares and re-add them as the messge shows.