ggee

Just noticed today after upgrading to 7.3.0 that some of my containers were not starting. Looks like some zoneinfo file changed? root@ur:~# ls /etc/localtime /etc/localtime@ root@ur:~# ls -l /etc/localtime lrwxrwxrwx 1 root root 35 May 14 20:36 /etc/localtime -> /usr/share/zoneinfo/America/Toronto root@ur:~# ls /usr/share/zoneinfo Africa/ America/ Asia/ Atlantic/ Australia/ Europe/ Indian/ Pacific/ UTC root@ur:~# ls /usr/share/zoneinfo/America/ Anchorage Bogota Campo_Grande Cayenne Chihuahua Godthab Halifax La_Paz Mexico_City New_York Phoenix Santiago St_Johns Asuncion Buenos_Aires Caracas Chicago Denver Guatemala Indiana/ Los_Angeles Montevideo Noronha Regina Sao_Paulo Tijuana I may have missed it, but don't remember seeing that in the release notes. Is this a bug or new behaviour?

OK. Did more looking around. I found that what I look at the drive "Attributes", the tabs open up instantly for all drives but 2 which take a long time. So decided to swap the drive cables for those two drives and all is back stable again. I still find it odd that bad cables on the array can cause issues with the responsiveness of the Dashboard and also even performance of a other pools.

?? Why is there so many cores in wait? Tasks: 536 total, 1 running, 525 sleep, 6 d-sleep, 0 stopped, 4 zombie top - 13:30:15 up 14:02, 0 users, load average: 10.30, 7.10, 6.31 Tasks: 537 total, 2 running, 519 sleep, 11 d-sleep, 0 stopped, 5 zombie %Cpu0 : 0.3 us, 0.0 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu1 : 1.0 us, 0.0 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu2 : 0.0 us, 0.0 sy, 0.0 ni, 0.0 id,100.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu3 : 0.0 us, 0.3 sy, 0.0 ni, 0.0 id, 99.7 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu4 : 0.0 us, 0.0 sy, 0.0 ni, 0.0 id,100.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu5 : 2.0 us, 0.0 sy, 0.0 ni, 98.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu6 : 0.7 us, 0.0 sy, 0.0 ni, 0.0 id, 99.3 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu7 : 0.3 us, 0.3 sy, 0.0 ni, 0.0 id, 99.3 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu8 : 1.0 us, 0.0 sy, 0.0 ni, 99.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu9 : 0.3 us, 0.0 sy, 0.0 ni, 0.0 id, 99.7 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu10 : 0.7 us, 0.0 sy, 0.0 ni, 99.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu11 : 0.0 us, 0.0 sy, 0.0 ni, 0.0 id,100.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 64087.3 total, 23608.2 free, 15193.5 used, 26280.9 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 48893.8 avail Mem

Well, this is getting really concerning. It's been about 12 hours since I started a parity-check and it is only at 1.1% for 4x8TB array. On a ZFS mirror of two 4TB drives, the scrub is only 18% done after 12 hours. I decided to start a SMART test of /dev/sdd (parity drive) right now and the UI is unresponsive while the test was running. WTF is happening? Oh, and I see this in the log occasionally. May 3 00:45:58 ur kernel: sd 8:0:0:0: [sdd] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s May 3 00:45:58 ur kernel: sd 8:0:0:0: [sdd] tag#12 CDB: opcode=0x85 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00

After upgrade to 7.2.5 from 7.2.4, the first boot seemed to be taking forever. I mean after 30 minutes, not everything was running. SMB shares are not reachable. Any interactions with the Array just seems to hang. Even just running the 'reboot' command from the terminal just did nothing and sat there. I think it was stuck in 'mounting disks' for 15 minutes. Shares still have not returned. I am attaching the diagnostic zip which took 10 minutes to complete for some reason. UI also hangs every once and a while. Greg ur-diagnostics-20260502-2339.zip

I may be misunderstanding how shares work. I have a share with the cache as primary. Is it possible for a copy of the share to be mirrored in the array? I've run into a really bad problem today. My cache pool has a zfs mirror of 2 SSDs. In the past few days, both SSD have now failed. Never buying that branch again. I can occasionally get one of the cache drives to come online. So I want to change my config so that I can copy everything that is in the cache into the Array to get back to working until my new SSDs arrive. Is it possible for a share to have the primary and secondary be a copy? This way, if an entire pool goes down, my shares still work. I still don't understand why the "Start Array" needs to have ALL pools and array working. My cache is completely dead and I can't start the Array because the 'cache' pool is not valid. I should be able to start all my working pools and the disk array. Thanks.

Different browser didn't work. I'll try the reboot.

I installed the plugin, but did not do anything to configure. I went to my dashboard and a lot of information is suddenly missing. Like disk list and network information. I uninstalled the plugin and it is still the same. Not sure if the plugin or dependency broke it.

I'm running Unraid 7.0.1. I created a Linux VM (Proxmox Backup) and trying to mount a virtiofs/9p share. I'm having an odd issue that if I add the virtiofs share, the networking in the VM does not start. If I start the VM without the share, networking works. Same with 9p mode.

Decided to try this out. When running the container and choosing Senoma, I got the following error "Image verification failed". The script kept running and I got the notification the VM was ready. Is it?? Choose a product to download (1-8): Downloading 696-08090... Saving http://oscdn.apple.com/content/downloads/11/58/062-53943/of12aseueo2jnehp03qh5g3o17lx4139t1/RecoveryImage/BaseSystem.chunklist to ./BaseSystem.chunklist... 0.0/0.0 MB |==========================| 100.0% downloaded Download complete! Saving http://oscdn.apple.com/content/downloads/11/58/062-53943/of12aseueo2jnehp03qh5g3o17lx4139t1/RecoveryImage/BaseSystem.dmg to ./BaseSystem.dmg... 753.0/753.0 MB |==========================| 100.0% downloaded Download complete! Verifying image with chunklist... Image verification failed. ([Errno 25] Inappropriate ioctl for device) mkdir: created directory '/domains/Sonoma' I have created the Macinabox directories . Formatting '/domains/Sonoma/macos_disk.img', fmt=raw size=107374182400 . Created vdisk BTW, Unraid 7.0.1

I have a few questions. 1. Why can I not do snapshot at the pool level since that is a dataset? I see a snapshot icon at the pool level, but no actions. My 'cache' pool icon shows 183 snapshots but I can't do anything with it. Is this intended? 2. Is there an ability to do a recursive snapshot if there is nested datasets? Thanks, Greg

Thanks for the update.

That doesn't make sense since I've seen other posts that have 8TB disks in array (16TB array) and only 20GB used. Those posts also say that the overhead is not used as part of the USED calculation. This is just one example. At the same time, there are other posts that rubber stamp the "overhead" answer.

Hello all. New user. Created my first array and I'm confused about the space. I found posts about a new empty array using 20GB from the start. That's fine, I see that in the shares list for the system share. But I don't understand why "USED" is 78GB. The posts I have seen for a new system with no data shows the 20GB. But why is my used space so much higher and doesn't equal the amount shown in the shares tab? Thanks, Greg

Thanks. I found out that I could move a dataset to the top level. So not an issue now. zfs rename maintank/usbtank/dataset1 maintank/dataset1 Just need to do some reorganization now.