mnovak

TVDB No longer offers free API access.

The last 2 were added at the same time yes, no error, just changed the drive count to 7 from 5, and added the 2, started the array, and then noticed the 2 new drives had no IO activity. When I investigated the pool properties from there I saw that the first drive hadn't completed resilvering, and the other 2 drives were in a second vdev, didn't think anything of it at the time, but when the first drive finally finished the other 2 remained separate, and I was missing 14-ish TB of usable space because of the mismatch of vdev sizes. (I'm almost done moving the data off the drives, I'll see if I can recreate it once I destroy the pool)

4, then expanded 1 to 5, then the 2 additional drives created a new vdev. mainzpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 /dev/sda1 ONLINE 0 0 0 /dev/sdc1 ONLINE 0 0 0 /dev/sdk1 ONLINE 0 0 0 /dev/sdd1 ONLINE 0 0 0 /dev/sdb1 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 /dev/sdj1 ONLINE 0 0 0 /dev/sdi1 ONLINE 0 0 0

No, I never actively created a second vdev, it was apparently automatic. Because the first expansion wasn't complete, the additional drives created their own separate vdev (as seen above) I'm sure if I deep dive on ZFS it's a default behavior, I just didn't expect it, or expected some kind of error or warning. My assumption is that because the first expansion wasn't complete ZFS couldn't change the first vdev to include the additional disks, so it created a second vdev to add them. That's my pain point because you can't remove the second vdev without destroying the first one as well even though the other 2 disks aren't actually in use until I assume both vdevs match (which would require adding 3 more disks, and in this economy I'm just not willing to spend that much lol)

It would be easy to reproduce, simply stop the array, add a disk, let expansion start. Then 2 days later stop the array, add another disk, start, stop, add... It was on the 3rd drive that I finally clicked into the pool properties to see that the first disk hadn't finished silvering. If the gui had shown a degraded or resilvering etc state I might have hesitated before adding, but the drives didn't appear to be reading or writing when I added disks (I know now I should have checked the properties and not just looked at the IO on the dashboard) Seems silly that the default behavior adding more disks is a second vdev though. Also, definitely not blaming anyone but myself here. Just that the documentation isn't especially clear about how long adding a drive takes, or where to look to see the status. Or that adding another drive before it finishes creates a new vdev. (I also should have known better than to copy data to the drives before I had finished expanding in the first place!)

I didn't do anything from the command line, the gui didn't show any problems, I assumed it was queuing disks as I added, not creating a separate vdev. Honestly I would have expected a warning about stopping the array while it was expanding. Regardless. I should have been slightly more patient and read more before I started. I might be able to recover using some questionable drives I previously pulled and haven't gotten around to destroying yet.

Well f*$@& Really wish the documentation was clearer about expanding. Can't remove the drives once they're added, so I don't have enough spare space to clear off the drives to rebuild them into a single vdev.

I managed to get enough blank disks to migrate my server to ZFS pools (or at least try to) I had 7x8TB drives, created the first pool of 4 drives, off to the races. I added a single drive, expanded the pool. I "thought" it had finished adding the drive (I was mistaken) so I added another, and another. Now I'm left with what I assume is asingle pool with 1 vdev of 5 drives, and 1 vdev of 2 drives. Unraid doesn't seem to acknowledge the second vdev for storage space though. Just wondering how screwed am I, Do I have to add 3 more drives for the other vdev to be acknowledged/used? pool: mainzpool state: ONLINE scan: scrub repaired 1000K in 10:26:38 with 0 errors on Thu Oct 15 20:10:52 2026 expand: expanded raidz1-0 copied 20.5T in 2 days 03:15:39, on Thu Oct 15 09:44:14 2026 config: NAME STATE READ WRITE CKSUM mainzpool ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 /dev/sda1 ONLINE 0 0 0 /dev/sdc1 ONLINE 0 0 0 /dev/sdk1 ONLINE 0 0 0 /dev/sdd1 ONLINE 0 0 0 /dev/sdb1 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 /dev/sdj1 ONLINE 0 0 0 /dev/sdi1 ONLINE 0 0 0 errors: No known data errors

I'm at my wits end. I have one share that I can't access anything other than the root level folder. I have a couple of shares mounted to one machine, all use the same user to access each share, all shares have the same permissions. But if I try to access my Plex share, I can't see past the root of the share, if I try to open any of the folders windows says the folder is unavailable/moved/deleted Even if I set the share to public I still can't get past the root level. I've tried reseting the permissions for all the folders and files, removing and re-adding my user. I'm stuck. (again, the other shares with the same settings all work just fine, it's just THAT share that won't work) Diag's attached Help me Obi wan Kenobi, you're my only hope... <<insert swearing>> case-f`in-sensative-folders. For whatever reason my share was set to lowercase (I didn't change this) and because all of my folders contain uppercase characters when Windows requested the folder from the server the server of course couldn't "find" the shared folder. JFC, I feel like a moron. kwik-e-mart-diagnostics-20250226-2034.zip

The built in VPN using Wireguard can give you direct connection to the server. Easy peasy lemon squeezy. Alternatively I also use Tailscale now that it's free-ish to connect my ROG Ally and Steam Deck to Headless when I'm away from home.

Hilariously I use this to stream to my Deck/Ally more often than I run native titles. Saves battery and gives me a beefier video card to crank up the visuals. Gueniunly appreciate your hard work on this!

JFC that's a lot THANK YOU! You're awesome, just in case you didn't already know lol

You just open the nVidia Driver plugin and select the driver you want, it's all in the same plugin?

Kindly read the last line of drivers for the 4060ti