gurulee

Just installed this to possibly replace Headphones. However, I'm on the Artist import process after pointing it to my large music collection. It is taking forever to allow import and resolve artists... Also if my browser closes or time-out, the import process seems to start from the beginning again. I am seeing this in the Lidarr logs: Error|AddArtistService|The operation has timed out.: 'https://api.lidarr.audio/api/v0.3/artist/fa6521a7-56b5-4e56-b946-fda469becba9?primTypes=Album&secTypes=Studio&releaseStatuses=Official' Any workaround on this? UPDATE: Fixed my issue, which was adjusting my pfsense fw rule to redirect traffic for api.lidarr.audio out wangw instead of pia vpn.

32gb unfortunately, x3200 m3 limit apparently 😞 Itching to invest in a new server, but I'm married lol

Anyone get a supported/working ver. of open vm tools working in unraid 6.5.x ? Can someone confirm if the referenced open_vm_tools-10.2.0-4.14.49-unRAID-x86_64.tgz works and how to install it? I'm currently have installed: 2017.05.28, build for unRaid releases based on Kernel 4.9.30 (6.3.5), but it shows as not running in vcenter/vsphere client.

Thank you for providing this. Is it actively being updated and maintained?

I'm on unraid 6.5.2 and my Community apps plugin will not update and I get this error below. Also when I click on Apps from menu bar, it doesn't display any content, then the Apps menu item just disappears. How do I fix this? plugin: updating: community.applications.plg Cleaning Up Old Versions plugin: downloading: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2018.07.08.txz ... failed (Generic error) plugin: wget: https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2018.07.08.txz download failure (Generic error)

It mounts fine, I perform format and it seems to finish quickly. It then still shows mounted. I reboot and it then shows not able to mount message . UPDATE: After using Preclear, re-mounting and re-formatting again, then rebooting it seems to be mounting properly now. Copying cache contents back over from disk1 to cache drive... UPDATE: Cache contents copied back from disk1 to cache drive and started docker service, PRESTO! I'm fully upgraded and operational with all dockers and appdata intact. Thanks @doron and @uldise

@doron, I was able to complete the upgrade to 6.5.2 and copy my cache contents to disk1 as a backup. BUT I am not able format the cache drive after starting array. The format starts and then seems to finish quickly. However, the drive fs is the same (btrfs) and the old contents are still on the drive. How can I force a format on the cache drive?

Yes! :-) is going to perform those steps today. Thank you for all the guidance! I'll report back with outcome. Sent from my SM-N910V using Tapatalk

@doron, If I downgrade back to 6.3.2, then boot up and copy all my cache contents to disk1 of array, then re-upgrade to 6.5.2 and format cache drive. Will copying the cache contents back from disk1 recovery my cache and installed dockers?

@doron, @uldise I powered down the unraid vm and mounted the vmdk on another vm and copied in all the bz* files. Booted up and it successfully upgraded! BUT my cache drive is offline and unmountable stating: Unmountable: Unsupported partition layout Any ideas?

@doron, Derr! I must be getting rusty! Why didn't I think of that?! LOL

@uldise, I do not see that ESXi setting under VM > Settings anywhere. Is this a ESXi globa advanced setting? Nor do I see my vmdk as an unassigned disk with the unraid Unassigned drives plugin.

It boots back to 6.3.2. But I have not fully replaced all the bz* files within the vmdk yet. Aside from taking unraid vm offline, downloading the vmdk and mounting it with winimage for bz* file injection, is there an easier way to mount over net to esxi? Sent from my SM-N910V using Tapatalk

After above mount, anything I create in /mnt/t auto syncs to /boot. I guess I have the wrong volume still...

root@Tower:/mnt/t# mount /dev/sda1 /mnt/t root@Tower:/mnt/t# cd .. root@Tower:/mnt# ls cache/ disk1/ disk2/ disk3/ disks/ hgfs/ t/ u/ user/ user0/ root@Tower:/mnt# cd t root@Tower:/mnt/t# ls EFI-/ bzroot* custom/ make_bootable.bat* previous/ bzfirmware* bzroot-gui* ldlinux.c32* make_bootable_linux* syslinux/ bzimage* bzroot.bak* ldlinux.sys* make_bootable_mac* bzimage.bak* changes.txt* license.txt* memtest* bzmodules* config/ logs/ packages/ root@Tower:/mnt/t#

@doron, vmdk is 1.11GB Disk /dev/loop0: 40 GiB, 42949672960 bytes, 83886080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sda: 7.5 GiB, 8004304896 bytes, 15633408 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sda1 * 8192 15631244 15623053 7.5G b W95 FAT32 Disk /dev/sdc: 121 GiB, 129922523136 bytes, 253754928 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf6abb9d1 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 253753343 253751296 121G 83 Linux Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 1FD63159-FC88-4F08-A8F9-46A700449731 Device Start End Sectors Size Type /dev/sdd1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: A4DDF22F-729E-4D95-B90E-964BB4DA78D0 Device Start End Sectors Size Type /dev/sde1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdf: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 26AB77C2-FA2F-40FD-A87F-D674D5D23077 Device Start End Sectors Size Type /dev/sdf1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: BDBDE1D4-F973-4C0A-B929-2CD7126ABB56 Device Start End Sectors Size Type /dev/sdb1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/sdg: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: AD0993AD-6CE9-4BB3-938B-5F5E69BABDD7 Device Start End Sectors Size Type /dev/sdg1 64 7814037134 7814037071 3.7T Linux filesystem Disk /dev/md1: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md2: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md3: 3.7 TiB, 4000786976768 bytes, 7814037064 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Tower:/dev#

@doron root@Tower:/dev# umount /mnt/t root@Tower:/dev# mount /dev/sdb1 /mnt/t mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. root@Tower:/dev# ls /mnt/t root@Tower:/dev#

@doron root@Tower:/dev# df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 2500428 398608 2101820 16% / tmpfs 2541924 232 2541692 1% /run devtmpfs 2500444 0 2500444 0% /dev cgroup_root 2541924 0 2541924 0% /sys/fs/cgroup tmpfs 131072 2264 128808 2% /var/log /dev/sda1 7807424 575712 7231712 8% /boot /dev/md1 3905110812 1966093256 1939017556 51% /mnt/disk1 /dev/md2 3905110812 1416179428 2488931384 37% /mnt/disk2 /dev/md3 3905110812 33008 3905077804 1% /mnt/disk3 /dev/sdc1 126875648 77132764 49344436 61% /mnt/t shfs 11715332436 3382305692 8333026744 29% /mnt/user0 shfs 11842208084 3459438456 8382371180 30% /mnt/user /dev/loop0 41943040 6122460 34282068 16% /var/lib/docker shm 65536 0 65536 0% /var/lib/docker/containers/24ea32895c680b5415411e6073fe303c08b3248d7673c86caa363d0aa58fe830/shm shm 65536 0 65536 0% /var/lib/docker/containers/ff3a18f5a78caf6fb4429f654b19314d0ad38be80305ee1dd677788096c20f59/shm shm 65536 0 65536 0% /var/lib/docker/containers/3b6af8925fbf2b210065153bfde3927cab157b69f2909b5e5867059580ae6658/shm shm 65536 0 65536 0% /var/lib/docker/containers/767650da23239e6fc026bc1058319270ae6e578450b5d40de3934c0113ffde7f/shm shm 65536 8 65528 1% /var/lib/docker/containers/f6dde6c677c1185fb6a837046f80bf7aba1cf8fec651274907f91423d43c6b16/shm shm 65536 0 65536 0% /var/lib/docker/containers/a4285f9799d74a16677434208e1c6833d6c3c630fd906a705e2b5cf2101ed056/shm /dev/loop1 1048576 16752 926288 2% /etc/libvirt root@Tower:/dev#

@doron I get this as a result: root@Tower:/dev# mount /dev/sdb1 /mnt/t mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so.

@doron root@Tower:/dev# ls sd* sda sda1 sdb sdb1 sdc sdc1 sdd sdd1 sde sde1 sdf sdf1 sdg sdg1 root@Tower:/dev# ls -la /dev/disk/by-uuid total 0 drwxr-xr-x 2 root root 200 Jun 4 12:09 ./ drwxr-xr-x 7 root root 140 Jun 4 12:07 ../ lrwxrwxrwx 1 root root 10 Jun 4 12:07 25d5cb0f-784e-4871-85c3-e0d31579ab38 -> ../../sdg1 lrwxrwxrwx 1 root root 10 Jun 4 12:07 491e0f08-9110-4f89-9010-c9e9c93c725d -> ../../sdf1 lrwxrwxrwx 1 root root 10 Jun 4 12:07 4C75-46AF -> ../../sda1 lrwxrwxrwx 1 root root 10 Jun 4 12:07 a8f923f6-497d-40be-857e-b8fa7919304d -> ../../sdd1 lrwxrwxrwx 1 root root 10 Jun 4 12:07 c432e7f1-a023-4746-90ad-91c0a55ce928 -> ../../sde1 lrwxrwxrwx 1 root root 11 Jun 4 12:09 c8be74f1-106e-400c-9e5f-8ce2129cf83d -> ../../loop1 lrwxrwxrwx 1 root root 10 Jun 4 12:07 ed70cf8c-dbdb-4166-af58-1d69f6171228 -> ../../sdc1 lrwxrwxrwx 1 root root 11 Jun 4 12:08 f424ef4c-e986-4065-b939-7c510417b911 -> ../../loop0 root@Tower:/dev#

Makes sense now and I recall this from when I originally set this up a few years ago. If I do not see /dev/sdb when I SCP in. How do I identify and mount my vmdk w/o shutting it down and downloading the vmdk files to mount offline with WinIMage?

Thank you for the further clarification and recommendation. I will work on this later.

@uldise, Thanks for responding. I do not recall which method I'm using to boot the usb stick connected to the unraid vmdk. However, I did only attempt replacing the bzimage and bzroot files from/boot and copied it to my usb stick. This was not successful and booted back to 6.3.2. Should I grab all updated files under /boot that start with bz* ?

I performed the upgrade via Plugins > OS Upgrade. Now I see the new bz* files in /boot with timestamp of 5/15/18 and changes.txt show its 6.5.2. However, I am not sure where to copy these files if not to the USB stick. I think I only have one /boot on vm in vmdk...

@doron, So just to confirm the steps: 1. Use unraid plugins upgrade OS function in my 6.2.3 version 2. Do reboot, but replace bz* files in my vmdk, OR on the usb stick which boots the vm? Thanks in advance for the assistance and clarification!