dlandon

Use http://ip address of server:9000

Yes. It's only configuration info for UD.

Use all the default values. Don't change anything. Once you get access to the GUI working, you can make changes.

Did you use the Docker Container menu to access LMS? Click on WebGUI.

Post diagnostics.

Click on the disk icon next to each disk and you'll see the log for that disk:

You don't have network problems, you have two disks having problems: Jan 21 09:55:03 Tower kernel: ata2: softreset failed (1st FIS failed) Jan 21 09:55:03 Tower kernel: ata2: hard resetting link Jan 21 09:55:09 Tower kernel: ata2: found unknown device (class 0) Jan 21 09:55:09 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 21 09:55:09 Tower kernel: ata2.00: configured for UDMA/33 Jan 21 09:55:09 Tower kernel: ata2: EH complete Jan 21 09:55:09 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x10 SErr 0x90200 action 0xe frozen Jan 21 09:55:09 Tower kernel: ata2.00: irq_stat 0x00400000, PHY RDY changed Jan 21 09:55:09 Tower kernel: ata2: SError: { Persist PHYRdyChg 10B8B } Jan 21 09:55:09 Tower kernel: ata2.00: failed command: WRITE FPDMA QUEUED Jan 21 09:55:09 Tower kernel: ata2.00: cmd 61/08:20:28:22:01/00:00:80:02:00/40 tag 4 ncq dma 4096 out Jan 21 09:55:09 Tower kernel: res 40/00:20:28:22:01/00:00:80:02:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:09 Tower kernel: ata2.00: status: { DRDY } Jan 21 09:55:09 Tower kernel: ata2: hard resetting link Jan 21 09:55:10 Tower kernel: ata2: SATA link down (SStatus 0 SControl 310) Jan 21 09:55:10 Tower kernel: ata2: hard resetting link Jan 21 09:55:16 Tower kernel: ata2: found unknown device (class 0) Jan 21 09:55:20 Tower kernel: ata2: softreset failed (1st FIS failed) Jan 21 09:55:20 Tower kernel: ata2: hard resetting link Jan 21 09:55:26 Tower kernel: ata2: found unknown device (class 0) Jan 21 09:55:30 Tower kernel: ata2: softreset failed (1st FIS failed) Jan 21 09:55:30 Tower kernel: ata2: hard resetting link Jan 21 09:55:36 Tower kernel: ata2: found unknown device (class 0) Jan 21 09:55:36 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 21 09:55:36 Tower kernel: ata2.00: configured for UDMA/33 Jan 21 09:55:36 Tower kernel: ata2: EH complete Jan 21 09:55:36 Tower kernel: ata4.00: exception Emask 0x10 SAct 0x7f800 SErr 0x90200 action 0xe frozen Jan 21 09:55:36 Tower kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed Jan 21 09:55:36 Tower kernel: ata4: SError: { Persist PHYRdyChg 10B8B } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/08:58:50:aa:79/04:00:00:00:00/40 tag 11 ncq dma 528384 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:60:58:ae:79/04:00:00:00:00/40 tag 12 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:68:58:b2:79/04:00:00:00:00/40 tag 13 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:70:58:b6:79/04:00:00:00:00/40 tag 14 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:78:58:ba:79/04:00:00:00:00/40 tag 15 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:80:58:be:79/04:00:00:00:00/40 tag 16 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/f8:88:58:c2:79/03:00:00:00:00/40 tag 17 ncq dma 520192 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4.00: failed command: READ FPDMA QUEUED Jan 21 09:55:36 Tower kernel: ata4.00: cmd 60/00:90:68:22:7e/04:00:00:00:00/40 tag 18 ncq dma 524288 in Jan 21 09:55:36 Tower kernel: res 40/00:88:58:c2:79/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jan 21 09:55:36 Tower kernel: ata4.00: status: { DRDY } Jan 21 09:55:36 Tower kernel: ata4: hard resetting link

Yes, it is safe to do that. All that is removed is the configuration for that specific device.

That would do it. Glad you sorted it out.

Disk problem.

Did it work and create the file system?

Go to a command line and type this command and see if an error shows up: /sbin/mkfs.xfs -f '/dev/nvme0n1p1'

There's a partition but no file system. Click on the 'Dev 1' and see if the SMART shows any issues with the disk.

It did mount once: Jan 19 14:40:02 optimus unassigned.devices: Adding partition 'sdp1'... Jan 19 14:40:02 optimus unassigned.devices: Mounting partition 'sdp1' at mountpoint '/mnt/disks/MK0371YVGN7WUA'... Jan 19 14:40:02 optimus unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdp1' '/mnt/disks/MK0371YVGN7WUA' Jan 19 14:40:02 optimus kernel: XFS (sdp1): Mounting V5 Filesystem Jan 19 14:40:02 optimus kernel: XFS (sdp1): Ending clean mount Jan 19 14:40:02 optimus unassigned.devices: Successfully mounted 'sdp1' on '/mnt/disks/MK0371YVGN7WUA'. Post a screen shot of the UD page showing the disk.

I'm looking into this, but others have reported seeing this problem when booted in safe mode, which implies it's not a plugin issue. Very strange problem.

Yes, it only affects the UD device. Honestly, I think you have some issues on the flash device. Before you do anything, uninstall and re-install UD, then click on the double arrows on the UD page. The setting 'share.1' is set for no at the moment and is what you want. The '.1' specifies the partition for that setting. It is all correct.

Uninstalling and re-installing UD won't change anything because the configuration files are not removed and re-installed, or changed. A couple options: If this is your only UD disk device, delete the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file and then click the double arrow icon on the UD page. You'll need to re-apply any device settings. Don't do this if you have any encrypted devices. You'll lose the password seed. You could use an editor and take a look at the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file for any obvious issues. The device might be duplicated in the UD config file. If you make any changes there, be sure to click the double arrow icon on the UD page to update the copy of the cfg file in ram that UD uses for updating the UD page. Edit the /flash/config/plugins/unassigned.devices/unassigned.devices.cfg and remove the entries for the trouoblesome device. Again, you'll need to click the double arrow icon to refresh the UD page.

You don't need to click 'Save' for the share switch to be saved. Just changing the switch will save the switch status. That's why there is a 'Done' button right below the switches. Change a switch, then click 'Done' does the trick. It is working for me. I suspect you might have a corrupted UD config file on your flash drive. I would take the flash drive to a PC and run a file system check on it.

The links haven't been updated in the plugin for a long time. They will be addressed in the next release.

I just found that bug and it will be fixed in the next release.

Seems to be working for me. The only change was with excluding directoies. Post a screen shot of your recycle bin settings.

You have multuple problems. You have array disk problems: Jan 12 17:40:08 UberTower kernel: XFS (md2): Unmount and run xfs_repair Jan 12 17:40:08 UberTower kernel: XFS (md2): First 128 bytes of corrupted metadata buffer: Jan 12 17:40:08 UberTower kernel: 00000000: 49 4e 81 b6 03 02 00 00 00 00 03 e8 00 00 00 64 IN.............d Jan 12 17:40:08 UberTower kernel: 00000010: 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jan 12 17:40:08 UberTower kernel: 00000020: 5f 30 66 5e 00 00 00 00 5f 28 d6 4a 00 00 00 00 _0f^...._(.J.... Jan 12 17:40:08 UberTower kernel: 00000030: 60 36 cc 16 2c 70 4e 9e 00 00 00 00 00 00 00 00 `6..,pN......... Jan 12 17:40:08 UberTower kernel: 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Jan 12 17:40:08 UberTower kernel: 00000050: 00 00 24 01 00 00 00 00 00 00 00 00 4f 03 ec 5b ..$.........O..[ Jan 12 17:40:08 UberTower kernel: 00000060: ff ff ff ff 8c d4 fa ab 00 00 00 00 00 00 00 08 ................ Jan 12 17:40:08 UberTower kernel: 00000070: 00 00 00 0d 00 34 c4 25 00 00 00 00 00 00 00 00 .....4.%........ Put the array in maintenance mode and check all your disks. Your Trip Lite UPS keeps dropping offline. Try a different USB cable and/or USB port. Jan 12 17:40:18 UberTower kernel: usb 2-1.2: USB disconnect, device number 19 Jan 12 17:40:19 UberTower kernel: usb 2-1.2: new low-speed USB device number 20 using ehci-pci Jan 12 17:40:19 UberTower kernel: hid-generic 0003:09AE:3015.0012: hiddev96,hidraw0: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART1500RM2U ] on usb-0000:00:1d.0-1.2/input0

Don't try this. It is imperative that parity always be correct. On the next parity check, you'll have parity errors on the new drive if it is not zeroed before being installed. Just let Unraid do its thing or preclear the drive before installing it.

Click on the "Plugins" tab and upgrade there.

It was an issue with the latest release that I have fixed now.