w5lee

Looks like the modification is no longer needed. Here is my current go file and all is working: root@Tower:/boot/config# cat go #!/bin/bash # Copy and apply udev rules for white label drives #cp /boot/config/rules.d/60-persistent-storage.rules /etc/udev/rules.d/ #chmod 644 /etc/udev/rules.d/60-persistent-storage.rules #udevadm control --reload-rules #udevadm trigger --attr-match=subsystem=block # Start the Management Utility /usr/local/sbin/emhttp & here is what my rules.d dir looks like: root@Tower:/etc/udev/rules.d# ls 70-persistent-net.rules 99_persistent_unassigned.rules I only have one white label drive left in the system and it is a 14GB one so newer than the other ones I had. So not sure if the new persistent storage rules discover them properly on their own now or the drive is exposing the serial number. Anyway thanks for remembering the thread and helping me out

Here is my go file: root@Tower:/boot/config# cat go #!/bin/bash # Copy and apply udev rules for white label drives cp /boot/config/rules.d/60-persistent-storage.rules /etc/udev/rules.d/ chmod 644 /etc/udev/rules.d/60-persistent-storage.rules udevadm control --reload-rules udevadm trigger --attr-match=subsystem=block # Start the Management Utility /usr/local/sbin/emhttp &

May I ask for a bit more guidance. I have a file cat 60-whitelabel.rules ACTION=="remove", GOTO="whitelabel_end" ENV{UDEV_DISABLE_whitelabel_RULES_FLAG}=="1", GOTO="whitelabel_end" SUBSYSTEM!="block", GOTO="whitelabel_end" KERNEL!="sd*|sr*|cciss*", GOTO="whitelabel_end" # for partitions import parent information ENV{DEVTYPE}=="partition", IMPORT{parent}="ID_*" # SCSI devices KERNEL=="sd*|sr*|cciss*", ENV{DEVTYPE}=="disk", ENV{ID_SERIAL_SHORT}=="00000000", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_MODEL}-$env{ID_WWN}" KERNEL=="sd*|cciss*", ENV{DEVTYPE}=="partition", ENV{ID_SERIAL_SHORT}=="00000000", SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_MODEL}-$env{ID_WWN}-part%n" LABEL="whitelabel_end" root@Tower:/boot/config/rules.d# ls 60-persistent-storage.rules 60-whitelabel.rules Can I make things work with these files or do I need to downgrade again to retrieve some info?

Think this is a bingo. I had some white label drives I had to do something to get going if I remember correctly.

Post the output of udevadm info -q property -n /dev/nvme0n1 and udevadm info -q property -n /dev/nvme1n1 From both v6.9 and ... 6.9.2: root@Tower:~# udevadm info -q property -n /dev/nvme0n1 DEVLINKS=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S59CNM0R402382P DEVNAME=/dev/nvme0n1 DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:01:00.0/nvme/nvme0/nvme0n1 DEVTYPE=disk ID_MODEL=Samsung_SSD_970_EVO_Plus_2TB ID_MODEL_ENC=Samsung\x20SSD\x20970\x20EVO\x20Plus\x202TB\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 ID_PART_TABLE_TYPE=dos ID_REVISION=2B2QEXM7 ID_SERIAL=Samsung_SSD_970_EVO_Plus_2TB_S59CNM0R402382P ID_SERIAL_SHORT=S59CNM0R402382P ID_TYPE=nvme MAJOR=259 MINOR=0 SUBSYSTEM=block USEC_INITIALIZED=21286137 root@Tower:~# udevadm info -q property -n /dev/nvme1n1 DEVLINKS=/dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_2TB_S59CNM0R410089P DEVNAME=/dev/nvme1n1 DEVPATH=/devices/pci0000:00/0000:00:03.0/0000:02:00.0/nvme/nvme1/nvme1n1 DEVTYPE=disk ID_MODEL=Samsung_SSD_970_EVO_Plus_2TB ID_MODEL_ENC=Samsung\x20SSD\x20970\x20EVO\x20Plus\x202TB\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20 ID_PART_TABLE_TYPE=dos ID_REVISION=2B2QEXM7 ID_SERIAL=Samsung_SSD_970_EVO_Plus_2TB_S59CNM0R410089P ID_SERIAL_SHORT=S59CNM0R410089P ID_TYPE=nvme MAJOR=259 MINOR=1 SUBSYSTEM=block USEC_INITIALIZED=20525164 6.11.5: root@Tower:~# udevadm info -q property -n /dev/nvme0n1 DEVNAME=/dev/nvme0n1 DEVPATH=/devices/pci0000:00/0000:00:02.0/0000:01:00.0/nvme/nvme0/nvme0n1 DEVTYPE=disk DISKSEQ=19 ID_PART_TABLE_TYPE=dos MAJOR=259 MINOR=1 SUBSYSTEM=block USEC_INITIALIZED=54420603 root@Tower:~# udevadm info -q property -n /dev/nvme1n1 DEVNAME=/dev/nvme1n1 DEVPATH=/devices/pci0000:00/0000:00:03.0/0000:02:00.0/nvme/nvme1/nvme1n1 DEVTYPE=disk DISKSEQ=18 ID_PART_TABLE_TYPE=dos MAJOR=259 MINOR=0 SUBSYSTEM=block USEC_INITIALIZED=54420424

Hi I have tried up upgrade to 6.11.5 from 6.9.2. When I do my array will not start and I am missing 2 of my 5 cache drives. They are both 2TB nvme ssd drives in pcie slots via adapters. When I downgrade they show back up. Tried a couple of times same result. tower-diagnostics-20221211-1541.zip

Wow has been a long time. Thanks so much for the reply. Glad you got it going. I may give it a go in a couple of weeks. I have some travel coming up and can't get to it right away but still would like to have it working.

Anyone get this working yet? I think I am close. I have my SSL certificate created but don't know how/where to put it the docker container.

Here is an example of copying from two array shares. I am showing the resource monitor to demonstrate data isn't going through my windows box:

I am not sure about the SSD's being trimmed Pool appears healthy no alerts anywhere Side note if I move a large file to the array I see the same sawtooth behavior, just at a much slower throughput. PWM: The data isn't moving to the windows machine. I have verified this by using task manager and looking at my network bandwidth and can confirm the data isn't going through my windows box.

Thanks for the responses. I need to check my forum settings as I didn't get an email my post was replied to so sorry for the delay. My system has 32GB of memory. I am writing to a cache pool of 3 SSD's using btrfs. The data is not using the network the copy is being done on the server. I found a nice youtube video on configuring a root share to move data from one place to another without having to move data over the network. This works great! He has many other well done and informational videos as well. Check them out! So bottom line this is moving data from one share on the cache pool to another one. I would expect a fast transfer. Looks to me it first copies to ram. Once the ram is exhausted then it flushes to disk. Maybe that is what is causing the sawtooth. I would like to figure it out and try to fix as the transfer rate goes to zero sometimes and just seems to hang there a bit. Then things take back off again. Think it is a config issue but not sure.

Hello, I am seeing write speed vary when moving large files. Any ideas why I am seeing this behavior? It happens both to cache and array writes.

The network is bridged but the firewall will not allow access to the unraid server on local network. pushbullet is also blocked from firewall. Any other ideas?

Hello, I have seen that the VNC server in UNRAID doesn't allow cut and paste. The VM's I am running are windows 7 and I really need cut and paste or at least a shared folder with the host. The problem is I connect to a VPN with the VM's that does not allow local LAN access. So that means I can't run a vnc server on the vm or use RDP. Any ideas are welcome.

Hi, When ever I do the initial log in for the management gui it takes a very long time to challenge me for password (20 seconds or so). After logging in though when I return to website everything is responsive as it should be. Seems to be an issue with the authentication mechanism. tower-diagnostics-20170316-1947.zip