Dragon99

There is a single page about ZFS and I did read it. It nowhere says anything about requirements to create one. There for I had to go off my external knowledge about ZFS and thhe outdated videos I could find. My original request when it came to switching to asking about ZFS was simply for a guide. I was and am more than willing to read a guide and documentation but when none is provided that is impossible. I don't have 30 minutes to watch an outdated video that doesn't actually cover the information anyway since I have now watched the entire space invader one video, and it did not mention stopping the array and creating the "pool" as unraid calls it... That was the original issues, but I stated I resolved that myself and although "Not supported" It was and is fact is still working now. VMDK or Virtual machine disk is a common term just because you don't know it doesn't mean it "doent' mean anything resued" https://en.wikipedia.org/wiki/VMDK When I originally opened it I wasn't able to boot unraid to get most of that information so no it was not provided. Yes, I could have grabbed the USB and gotten logs that way, but I hadn't gotten that far to be frank. When I later shifted the post to be about ZFS was any of that information asked for? I included a partial screenshot of the main tab but was never asked for the full thing. You are expecting me to provide information that is not asked for. Maybe add a line to the one page of ZFS information in the docs saying you create a ZFS pool the same way you create the array or a secondary pool instead of linking to a video that says to do it by command line. This is the video I could find myself and you can see at the time stamp he had just created a "Native ZFS Pool" on unraid via command line not via gui. Trust me I get it you probably deal with people who post stuff with no effort or an attempt to google a solution. I work in IT support. If my responses have come across as passive aggressive then I apologize it wasn't my intent. I was simply frustrated at the lack of a proper guide on unraids website. The problem with videos is they become dated so quickly unless they can constantly be updated. It's one of the major downsides to having most guides be YouTube videos rather than written articles anymore. Space invader one does some good work, but he often has to add details I just don't care about in order for the video to serve more people and there is no good way to search a video for the 5 seconds of information I need. I gladly would have provided any screenshots and logs asked for I just needed to know what would have been helpful for my issue. I tried my best to use terms like export and pool and array in the way unraid does but that is different than other OS and that clearly lead to confusion as well. Again apologies for at times replying in annoyance rather than waiting a few minutes to further explain things. It just often felt like some replies ignored what I had just attempted to explain.

That is not the case as I have said multiple times already... These was new VM disks I added for the sole purpose of testing they did not exist before I added them to unraid and for sure did not have a file system on them. Those videos are over 3 years old and all on older versions of unraid. Not to mention one was what I was originally following and makes 0 mention of making a pool but instead says to use CLI to create the ZFS raid but does not mention anything about actually using that share in unbraid. Anyway, the issue is "resolved" technically. Proper documentation would be very useful but I guess relying on outdated videos is what is expected for unraid now.

So, I managed to figure it out Perhaps I am out of practice with unraid as it's been a long time since unraid was my main NAS OS. (I keep the VM for the pure reason of testing and assisting others as needed. Main reason I was trying ZFS was to see if it was practical for a friend who just got new drives and is upgrading.) For some reason and this is rather unclear from the Unraid dashboard (if the array is started at least which it by default is an on existing server) You have to first stop the array and then to create a pool that is completely separate from the array. You have to make sure to click onto this pool and set it as ZFS before starting the array even though you can create a ZFS pool via CLI while the array is running, and a pool separate from the array should have no direct impact on the array and on other OS at least could be created without having to take down your primary storage. A proper guide or docs regarding ZFS pool creations would be very handy in preventing these issues rather than having to rely on third party often outdated source and videos, but I at least was unable to find official documentation about using ZFS on unraid save the blog post which reads more as a add and information piece than a proper guide and how its implemented. https://unraid.net/blog/zfs-guide

I am unable to select that as a option as shown in a previous screenshot.

Okay but how do I put a share on a ZFS pool? I have no option to do so as far as I can tell. You can see I have no shares for those datasets that were created. and when clicking add share you can see in my previous post I can only select array or cache. So I cant select to put a share on those pools. So the question remains.

Okay so it did work the way I would have expected. I just for some reason have no option to select the ZFS datasets as a storage location. So Unless I am missing a critical step between creating the datasets and ZFS pool and then exporting via the share tab it just seems to not be working at the moment for me. I will look into it more later today as time allows me.

Sorry by export I mean export the share via SMB. Its a native Unraid ZFS share but it does not give me the option to export the datasets or create a share on the shares screen that is set to use the ZFS pool or dataset. Basically I want to make these accessible on my network for testing purposes.

I am currently failing at figuring out how to export a ZFS pool and also failing to find a good written guide for ZFS setup on unraid if anyone has any suggestions.

I was able to boot the VM and then "hotplug" the VM disks into it. I have yet to reboot it but will be curious to see if it works upon reboot. But I suspect this was mostly a result of running in a VM. But as I said this is my test unraid server that is designed to be broken by playing with things. I want to play around with ZFS pools and decided now was a good time but clearly I ran into other issues.

I have a Pro License so it's not related to license, and it was not booting at all. I know that without a pro license it won't start the array.

So after some further playing with it. I did confirm its not a flash drive problem. As mentioned, I can boot into unraid in another VM and my desktop fine. It seems to be an issue with that I added a few drives to play around with ZFS expansion and such. Turns out there is a limit to the number it will boot with as I removed the other added drives and unraid boots fine. But I then added the new drives back again and got a different issue. I am in the process of adding drives 2 at a time to see what that limit is. I assume its related to the VM and not unraid. Although I assume you are right with the lexar USB so I will start looking into replacing it as well before it fails.

Hello, I tried to update from The latest stable version to the RC 7 release channel. I had just rebooted the server multiple times to get it ready to update but upon upgrading it said it was waiting 30 seconds for device labeled unraid to come online. I decided to make a new drive to test boot it. But in the process removed the current one and plugged it into my desktop just to check it, and now I see it says this in the unraid USB creator tool. anyone have any idea what could cause this and ways to fix/work around it. Let me know if you need anything else Screenshot of the error of unraid booting. I should probably mention this is a VM running on proxmox but again was working completely fine before. Edit to add more details. Decided to try and boot my desktop off the flash drive to see if it works would, and turned out it did. So, seems to be an issue related to the Proxmox VM. Does V 7 of Unraid have different hardware requirements? I also spun up a new VM and tried booting the flash drive and that worked despite using the same options as the original minus I didn't add the drives to it. So It seems it should work but for some reason it won't boot in the original VM.

Hello, Every so often my server will start acting up and causing a bunch of different issues. Basically, when trying to interact with a docker it will freeze or just not work properly and run very slow. When it's doing this if I try to open the Webui to restart the docker half the time it won't load the docker tab at all either. Usually, main load fine and some other tabs but not all of them VM and Docker are the ones I have noticed it the most since those are usually what I am having issues with that I am trying to troubleshoot and fix. I am not sitting at crazy CPU usage or anything like that or anything else I can see that might be causing the issues. I can usually restart my whole server and sometimes that fixes it sometimes I can't even start the array afterwards or it restarts fine but is still doing it. I finally thought about posting here and waited for it to do it so I could grab a log. I attached a picture of the docker tab basically it just sits on that forever. It might eventually load but usually not for at least 10 minutes or more. Let me know if you guys have seen this before and have any ideas or see something in the logs that might explain it. diagnostics-20211206-0942.zip

Ever able to resolve this? I am having the same issue.