23 minutes ago, shaunvis said:

I don't know either but I had constant OOM caused by Avahi-daemon on my main server. I eventually made it go away by removing unassigned devices. I reinstalled it and was fine after that. The OOM made 6.12 totally unusable on my main server. After fixing the OOM caused by UD, I was able to finally upgrade to 6.12.4 and have been up over a week without issue.

Your flash drive is having issues:

Oct 10 14:37:27 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:37:38 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:37:43 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 05 e5 30 00 00 20 00
Oct 10 14:37:43 Hoth kernel: I/O error, dev sda, sector 386352 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
Oct 10 14:38:07 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:38:23 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:38:35 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 02 53 08 00 00 08 00
Oct 10 14:38:47 Hoth kernel: I/O error, dev sda, sector 152328 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:39:02 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:39:17 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:39:35 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 02 53 80 00 00 08 00
Oct 10 14:39:54 Hoth kernel: I/O error, dev sda, sector 152448 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:40:11 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:40:28 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:40:47 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 05 1e 00 00 00 08 00
Oct 10 14:41:07 Hoth kernel: I/O error, dev sda, sector 335360 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:41:26 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd

It almost looks like the flash USB was removed from the server.

 

Eventually you are getting the OOM and the network goes out?

Oct 10 15:22:47 Hoth kernel: oom_reaper: reaped process 13872 (avahi-daemon), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Oct 10 15:22:47 Hoth avahi-dnsconfd[13881]: read(): EOF
Oct 10 15:22:47 Hoth unassigned.devices: Remote server 'STARKILLER' cannot be found on the LAN.
Oct 10 16:14:16 Hoth webGUI: Successful login user root from 192.168.10.117

 

You need to get your flash working without the errors:

• Try a different USB port.  Preferably a USB 2.0 port.  Some USB devices work better on a USB 2.0 port.
• Do a file system check of the flash on a PC.  I don't think you'll find any issues, bit check jus in case.
• Use another USB flash device.  You're on a trial, so a new USB device will work without having to transfer the license.  Create a new flash, prepare it to boot, and be sure to copy the /config/ folder to the new flash to preserve your configuration.

24 minutes ago, dlandon said:

Your flash drive is having issues:

Oct 10 14:37:27 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:37:38 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:37:43 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 05 e5 30 00 00 20 00
Oct 10 14:37:43 Hoth kernel: I/O error, dev sda, sector 386352 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 2
Oct 10 14:38:07 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:38:23 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:38:35 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 02 53 08 00 00 08 00
Oct 10 14:38:47 Hoth kernel: I/O error, dev sda, sector 152328 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:39:02 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:39:17 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:39:35 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 02 53 80 00 00 08 00
Oct 10 14:39:54 Hoth kernel: I/O error, dev sda, sector 152448 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:40:11 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Oct 10 14:40:28 Hoth kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=0s
Oct 10 14:40:47 Hoth kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 05 1e 00 00 00 08 00
Oct 10 14:41:07 Hoth kernel: I/O error, dev sda, sector 335360 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
Oct 10 14:41:26 Hoth kernel: usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd

It almost looks like the flash USB was removed from the server.

 

Eventually you are getting the OOM and the network goes out?

Oct 10 15:22:47 Hoth kernel: oom_reaper: reaped process 13872 (avahi-daemon), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Oct 10 15:22:47 Hoth avahi-dnsconfd[13881]: read(): EOF
Oct 10 15:22:47 Hoth unassigned.devices: Remote server 'STARKILLER' cannot be found on the LAN.
Oct 10 16:14:16 Hoth webGUI: Successful login user root from 192.168.10.117

 

You need to get your flash working without the errors:

• Try a different USB port.  Preferably a USB 2.0 port.  Some USB devices work better on a USB 2.0 port.
• Do a file system check of the flash on a PC.  I don't think you'll find any issues, bit check jus in case.
• Use another USB flash device.  You're on a trial, so a new USB device will work without having to transfer the license.  Create a new flash, prepare it to boot, and be sure to copy the /config/ folder to the new flash to preserve your configuration.

I'll mess with the flash drive, thanks.

 

But yes, on two different servers in 6.12 when I'de get the OOM, the system is totally unresponsive. Even trying to SSH into it, it would take my username, then just hang on the password until I got a timeout error. Eventually the process is killed and things work fine again

10 hours ago, dlandon said:

The 'Reboot' on the mount button shows up when the drive is mounted and then goes offline before it is unmounted.  As you found out, the soluton is to reboot the server to sort it out - hence the 'Reboot' on the mount button.

 

It appears all the drives with the 'Reboot' issue are in the same drive bay, so it's probably a common issue.  Check the log and see if there is any indication of what is going on.

 

Check the following:

• Power supply for the drive bay.
• USB cable.
• USB port - change ports.

Thanks for your fast reply.

I already tested different drive enclosures with different USB cables and changed the ports on the motherboard. I guess that means that the issue might be the motherboard itself. I will try to find something in the logs.

 

Edit: It happened again. This time I saved all the syslogs:

It seems like the USB enclosure got disconnected at 10:11:49:

 

Oct 11 09:06:00 Tower monitor: Stop running nchan processes
Oct 11 10:11:49 Tower kernel: usb 4-1: Device not responding to setup address.
Oct 11 10:11:49 Tower kernel: usb 4-1: Device not responding to setup address.
Oct 11 10:11:49 Tower kernel: usb 4-1: device not accepting address 3, error -71
Oct 11 10:11:50 Tower kernel: usb 4-1: USB disconnect, device number 3
Oct 11 10:11:50 Tower kernel: sd 13:0:0:3: [sdv] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Oct 11 10:11:50 Tower kernel: sd 13:0:0:3: [sdv] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 d2 fc a0 40 00 00 02 40 00 00
Oct 11 10:11:50 Tower kernel: I/O error, dev sdv, sector 3539771456 op 0x1:(WRITE) flags 0x800 phys_seg 39 prio class 2
Oct 11 10:11:50 Tower kernel: EXT4-fs warning (device sdv1): ext4_end_bio:343: I/O error 10 writing to inode 257988388 starting block 442471432)
Oct 11 10:11:50 Tower kernel: sd 13:0:0:1: [sdt] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Oct 11 10:11:50 Tower kernel: sd 13:0:0:1: [sdt] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 cd 71 0e b0 00 00 00 08 00 00
Oct 11 10:11:50 Tower kernel: I/O error, dev sdt, sector 3446738608 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
Oct 11 10:11:50 Tower kernel: EXT4-fs warning (device sdt1): ext4_end_bio:343: I/O error 10 writing to inode 45192797 starting block 430842326)
Oct 11 10:11:50 Tower kernel: sd 13:0:0:3: [sdv] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Oct 11 10:11:50 Tower kernel: sd 13:0:0:3: [sdv] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 cf 04 ef b0 00 00 00 08 00 00
Oct 11 10:11:50 Tower kernel: I/O error, dev sdv, sector 3473207216 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
Oct 11 10:11:50 Tower kernel: EXT4-fs warning (device sdv1): ext4_end_bio:343: I/O error 10 writing to inode 257988391 starting block 434150902)

 

and then got reconnected 20 seconds later at 10:12:09:

 

Oct 11 10:12:09 Tower kernel: EXT4-fs warning (device sds1): dx_probe:820: inode #18153800: lblock 0: comm storagenode: error -5 reading directory block
Oct 11 10:12:09 Tower kernel: usb 4-1: new SuperSpeed USB device number 4 using xhci_hcd
Oct 11 10:12:09 Tower kernel: usb-storage 4-1:1.0: USB Mass Storage device detected
Oct 11 10:12:09 Tower kernel: scsi host14: usb-storage 4-1:1.0
Oct 11 10:12:09 Tower kernel: EXT4-fs warning (device sds1): dx_probe:820: inode #18153800: lblock 0: comm storagenode: error -5 reading directory block

 

This never happened before and is now happening to both enclosures with different USB cables and different motherboard ports. Is there a way to find out more about the root cause than in the syslog?

Edited October 11, 20232 yr by median-symposium6528

6 hours ago, median-symposium6528 said:

This never happened before and is now happening to both enclosures with different USB cables and different motherboard ports. Is there a way to find out more about the root cause than in the syslog?

It might be a power supply problem.  Remove a few drives from the bay and see if the remaining drives stay online.

Just to add a bit, it seems DNS related. I have issues when I add a server by name, but by IP it doesn't seem to have any trouble.

 

Is there something special in Unraid with setting up DNS? I'm just using my OpnSense firewall for dns and haven't noticed issues with other things

1 hour ago, shaunvis said:

Just to add a bit, it seems DNS related. I have issues when I add a server by name, but by IP it doesn't seem to have any trouble

DNS issues relate to remote shares and do not affect locally attached disk drives.

 

Are you passing local DNS lookups to OpenSense and if so is it setup to resolve local lookups or pass local lookups to a DNS resolver?

 

You can check by trying these two commands and see if local names are being resolved:

arp -a remote_server

and

arp -a remote_server.local

 

If neither of those commands return an IP address, you have an issue with DNS.  If one or the other command resolves, post diagnostics so I can take a look.  There have been some recent changes in UD with resolving local names.  There might still be issues I need to work on.

I also have this issue with DNS names. I can ping my server.local address but I can't seem to add it with unassigned.devices so not sure it is a DNS issue on my side? I can browse the SMB share with DNS record to from my computer and unraid.

1 minute ago, Michel Amberg said:

I also have this issue with DNS names. I can ping my server.local address but I can't seem to add it with unassigned.devices so not sure it is a DNS issue on my side? I can browse the SMB share with DNS record to from my computer and unraid.

Post diagnostics.

On 10/4/2023 at 8:27 PM, unr41dus3r said:

Short question, i have an encrypted ZFS Partition on which i have a dataset.

The partition is mounted correctly but the dataset is not mounted and i need to run "zfs mount -a" to mount it after every reboot.

 

What would be the recommended way to automate this?

 

On 10/5/2023 at 4:12 AM, dlandon said:

I'm working on a potential solution.

"zfs mount -a" wow this has answered so much confusion as to why I cant view any of my UD mounted zfs drive contents! Thankyou

I look forward to the official solution.

11 minutes ago, wacko37 said:

 

"zfs mount -a" wow this has answered so much confusion as to why I cant view any of my UD mounted zfs drive contents! Thankyou

I look forward to the official solution.

Fix is in the latest release of UD.

25 minutes ago, dlandon said:

Fix is in the latest release of UD.

Ok, maybe its my use case is the issue here.

 

I have an offline ZFS drive I use for replication of my ZFS cache pool, up until now (zfs mount -a) I have not been able to view my contents on the offline drive after being mounted via UD. I can see it space used and the snapshots but not the contents, I get "Invalid Path" error, which makes total sense now that I know the ZFS pools are mounted during Unraid boot sequence.

Should this not be the case? 

Edited October 12, 20232 yr by wacko37
grammer

46 minutes ago, wacko37 said:

Ok, maybe its my use case is the issue here.

 

I have an offline ZFS drive I use for replication of my ZFS cache pool, up until now (zfs mount -a) I have not been able to view my contents on the offline drive after being mounted via UD. I can see it space used and the snapshots but not the contents, I get "Invalid Path" error, which makes total sense now that I know the ZFS pools are mounted during Unraid boot sequence.

Should this not be the case? 

I don't understand your issue.  Give some more information about the zfs drive you are mounting in UD and post diagnostics.

400 pages on this - crazy.

I have a user script that wakes a backup server, then rsyncs my media to it.

I find I have to manually un mount the nfs connection to it of there are errors/warnings in the logs as the server has gone to sleep.

I would like to automate the mounting and unmounting as part of the script with suitable delays.

I looked at the logs on unraid after a mount, but it does not help me with the actual commands.

Can anyone help me with the moount and unmount commands.

From the interface - 

The source is 192.168.1.6:/mnt/user/Media

The mount point is 192.168.1.6_Media

 

 

I think I have it :

 

/sbin/mount -t 'nfs' -o rw,soft,relatime,retrans=4,timeo=300 '192.168.1.6:/mnt/user/Media' '/mnt/remotes/192.168.1.6_Media'

 /sbin/umount -t nfs '/mnt/remotes/192.168.1.6_Media'
 

Edited October 12, 20232 yr by vw-kombi
found it

1 hour ago, vw-kombi said:

400 pages on this - crazy.

I have a user script that wakes a backup server, then rsyncs my media to it.

I find I have to manually un mount the nfs connection to it of there are errors/warnings in the logs as the server has gone to sleep.

I would like to automate the mounting and unmounting as part of the script with suitable delays.

I looked at the logs on unraid after a mount, but it does not help me with the actual commands.

Can anyone help me with the moount and unmount commands.

From the interface - 

The source is 192.168.1.6:/mnt/user/Media

The mount point is 192.168.1.6_Media

 

Click on the 'Help' icon in the upper right of the UD webpage and read the help text.  You'll see how to mount and unmount remote shares from a script.

11 hours ago, dlandon said:

I don't understand your issue.  Give some more information about the zfs drive you are mounting in UD and post diagnostics.

I guess the easiest way to explain is via screenshots.

 

The mounted device below in UD is the offline ZFS backup ssd for my cache pool, which I mount periodical for ZFS replication.

 

Once I attempt to view the contents of ZFS--BACKUP--SSD as per the screen grab below OR via UD "browse disk share"

 

I get "invalid path" as per screenshot below

 

If i run the "zfs mount -a" command, I can view all the contents in the datasets as per normal.

 

Below is a screengrab of the syslog when ZFS--BACKUP--SSD is unmounted and then mounted.

 

Edited October 13, 20232 yr by wacko37
bloody spelling

20 minutes ago, wacko37 said:

If i run the "zfs mount -a" command, I can view all the contents in the datasets as per normal.

Do the following:

• Unmount the disk
• Mount the disk
• Show the oupout of this command:

  zfs list -H -o name,mountpoint

   

• And this command:

  zfs mount

   

5 hours ago, dlandon said:

Do the following:

• Unmount the disk
• Mount the disk
• Show the oupout of this command:

  zfs list -H -o name,mountpoint

   

• And this command:

  zfs mount

   

As requested

 

 

On 10/4/2023 at 7:12 PM, dlandon said:

I'm working on a potential solution.

 

I updated to the latest plugin version and today i stopped the array and started it again (without reboot)

It was again necessary to run zfs mount -a

6 hours ago, wacko37 said:

As requested

Fixed in the next release of UD.

56 minutes ago, unr41dus3r said:

 

I updated to the latest plugin version and today i stopped the array and started it again (without reboot)

It was again necessary to run zfs mount -a

 

Do the following:

• Unmount the ZFS disk.
• Mount the ZFS disk.
• Show the output of the following commands:

zfs list -H -o name,mountpoint

and

zfs mount

 

2 hours ago, dlandon said:

 

Do the following:

• Unmount the ZFS disk.
• Mount the ZFS disk.
• Show the output of the following commands:

zfs list -H -o name,mountpoint

and

zfs mount

 

 

Thanks for checking

 

Output:

zfs list -H -o name,mountpoint

 

backup-ssd                             /mnt/disks/backup-ssd
backup-ssd/backup                 /mnt/disks/backup-ssd/backup
 

zfs mount

 

backup-ssd                      /mnt/disks/backup-ssd

36 minutes ago, unr41dus3r said:

Thanks for checking

The issue is the '-' in the pool name the same as the previous poster.  Fixed in the next release of UD.

On 10/13/2023 at 7:26 AM, vw-kombi said:

400 pages on this - crazy.

I have a user script that wakes a backup server, then rsyncs my media to it.

I find I have to manually un mount the nfs connection to it of there are errors/warnings in the logs as the server has gone to sleep.

I would like to automate the mounting and unmounting as part of the script with suitable delays.

I looked at the logs on unraid after a mount, but it does not help me with the actual commands.

Can anyone help me with the moount and unmount commands.

From the interface - 

The source is 192.168.1.6:/mnt/user/Media

The mount point is 192.168.1.6_Media

 

 

I think I have it :

 

/sbin/mount -t 'nfs' -o rw,soft,relatime,retrans=4,timeo=300 '192.168.1.6:/mnt/user/Media' '/mnt/remotes/192.168.1.6_Media'

 /sbin/umount -t nfs '/mnt/remotes/192.168.1.6_Media'
 

 

So those commans I got from the log for when UD does the mount do not work.

The mount command throws this - mount point /mnt/remotes/192.168.1.6_Media does not exist

I checked the help page but that is all do do with /dev devices - not the UD NFS mounts

I am not a linux guy and am way out of my depth here.

6 minutes ago, vw-kombi said:

 

So those commans I got from the log for when UD does the mount do not work.

The mount command throws this - mount point /mnt/remotes/192.168.1.6_Media does not exist

I checked the help page but that is all do do with /dev devices - not the UD NFS mounts

I am not a linux guy and am way out of my depth here.

From UD help:

 

Check out this post:

 

10 hours ago, dlandon said:

Fixed in the next release of UD.

Thanks as always for your time and hard work.....legend!