• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

OmniOS and storage spaces update

N

N Bates

Limp Gawd
Joined
Jul 15, 2017
Messages
205
It's about time I have updated my ZFS and windows media file system, I store my media files on Window 11 25H2 and created the first pool in windows 10 on windows 10 pro for workstations using ReFS, I have updated and installed Windows 11 25H2 and updated the storage spaces pool and is working fine.

I access my media via the windows 11 PC via SMB and backup the media on a server with OmniOS installed, can't remember the version as I haven't updated or upgraded for a while.

I have run out of space on my windows 11 PC currently using 5 drives on parity (WD 14TB drives), I have purchased 5 x 28tb Seagate recertified enterprise drives to replace the current WD 14tb drives, I have only got enough space for 5 drives in the windows 11 PC, that's why I am replacing the drives and not adding to them.

I will purchase another identical WD 14tb drive to add to ZFS OmniOS pool currently running Raidz2, 6 x 14tb drives currently and will add another 6, 5 that have been used in the Windows 11 PC.

writing this will get me some help in hopefully prioritising what I need to do to achieve the above.

1) Ensure the backup on the ZFS pool is up to date.
2) format the 5 WD drives used in the Windows ReFS storage spaces system to (FAT, FAT2, NTFS or not bother?).
3) Remove the 5 WD drives from the Windows PC and set aside.
4) Install the five Seagate 28tb drives to replace the WD 14tb drives.
5) Create ReFS storage pool and tweak for performance (I may create another post to get some help when I get to this stage).
6) Re-install the media files from the backup OmniOS server.
7) Test the Windows re-installed media files.
8) Export the ZFS pool on the server.
9) Update OmniOS and Napp_it to the latest, not sure yet how to do this, or maybe I need a full re-install, hopefully not as I will have to start from scratch?
10) Import the ZFS pool.
11) Install the 5 + 1 new x 14tb WD drives in the server.
12) Format the 6 WD drives and add to the storage ZFS pool.
13) Test the ZFS pool working OK and tweak Napp_it for 10gbe performance, although I can't remember how to do that? currently the Windows PC and server are connected via two intel's 540 T2 10gbe network adaptors.

Thank you for all your help, guidance and comments!
 
First hurdle, I can't access my NAS from Windows 11 25h2 yet, my NAS is connected to the Windows PC via a couple of Inte's X540 T2 network cards, both my PC and NAS are setup via static IP, 192.168.0.XX, the adaptors are connected to a 10gb switch Netgear xs708t, the Windows PC static address is not connected to the internet.

I have tried so far:

Set-SmbClientConfiguration -RequireSecuritySignature $false
and
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

The above has not worked, so, I will revert these back for more security.

I have tried enabeling IPV4 tc/ip WINS setting to "enable NetBIOS over TCP /IP.

I possibly need to try and enable password access in my OmniOS NAS via Napp_it?
 
some remarks

OmniOS update
- switch repository to newer release + pkg update + reboot
- for older OmniOS, update in stages over lts

napp-it update
- use meni About > Update
- for older napp-it, update in stages

Storage Spaces Pool
This is just a basket of disks
Redundancy, location, tiering and filesystem is set per Space (virtual disk)

OmniOS 10G tuning
- increase ip buffers
- use Jumbo Frames

Windows 10G tuning
- compare Windows nic driver vs newest Intel driver
- use Jumbo frames
- optimise buffers and int handling in driver setings
(ask ai for details)

Windows 11
- anonymous SMB connect is disabled, can be enabled via registry (ask ai)
- pw access is via OmniOS user+pw

btw
The Windows filesystem driver for a regular OpenZFS is still beta /release candidate but nearly ready and worth to look at. You can import a pool from OmniOS. You can use napp-it cs to manage Storage Spaces and ZFS on Windows.

Sync
For ZFS-ZFS use replication, otherwise robocopy on Windows. On Unix, use rsync (no support for Windows ACL)
 
Thank you for the great info _Gea, it looks like I have a load of research to do.

The beta Windows drivers for openZFS filesystem you mention is pretty interesting, does this mean Windows will support ZFS pool in Windows directly?

Forgot, needed to add, for Napp-it update, will updating directly via the GUI (menu, about, update) will update in stages, or will I have to do this manually? I am pretty sure I have an old version of Napp-it.
 
Yes, the OpenZFS driver gives you full ZFS support on Windows
You can update an old napp-it se in menu About > Update.

btw
Napp-it cs (Client/Server edition for any OpenZFS, Free-BSD, Illumos, Linux, OSX, Windows) is included in newest napp-it se 25.06 (Solaris Edition)

For napp-it cs on Windows, download napp-it cs with Xampp and start web-gui
https://napp-it.org/doc/downloads/windows-aio.pdf
 
_Gea said:
Windows 11
- anonymous SMB connect is disabled, can be enabled via registry (ask ai)
- pw access is via OmniOS user+pw
Click to expand...
Darn it, I still can't seem to be able to access the OmniOS NAS in Windows 11 25H2, I have tried the registry DWORD value on "ALLowInsecureGuestAuth" change from "0" to "1", rebooted te windows PC before trying, still getting the same windows access restriction as per below:

Windows cannot access 192.168.0.XX check the spelling of the name, otherwise, there might be a problem with your network, to try to identify and resolve network problems, click diagnose.

I have tried multiple googled solutions without success, I have also tried adding a new SMB user with password via Napp-it, but still the same, maybe I need to edit this new SMB user to add similar when setting the OmniOS up with guest OK, with added settings for CHMOD or 777 or something like that.

I think my only solution to get Windows 11 to recognise my NAS is to add a new SMB user with password, any thoughts?
 
OmniOS guest access requires

- a OmniOS user guest
cli command: "smbadm enable-user guest"
- share a filesystem with guest allowd
 
The guest user is already enabeled and a share allowed but I think this is the reason why Windows 11 will not connect, how do I add a SMB user using a password and how do I refresh sharing the shared folders via Napp-it?

Many thanks
 
when you enable a share, your options are:
- guest allowed enabled: no user or pw required
- guest allowed not enabled: only OmniOS (or AD) users can connect with their pw
 
How do you set "guestok=false" in Napp-it to trigger a password request by the OmniOS server?
 
"guestok=false" => guest allowed not enabled
There is no false option, you can enable guest or not
 
So the option will be to disable guest? if so, will the Window PC's accessing the server be prompted for a password and will the password be the default setup by the administrator?

Or, once the guest is disabeled, do I need to create another SMB account to login with a password?

Many thanks
 
Illumos/Solaris SMB works different to SAMBA SMB. When you disable guest access, Windows prompts for name+pw.
You can then login as any OmniOS user with the OmniOS pw, including root if you want full permissions.

If you want to allow only SMB access, disable user shell when you create a user.
 
Thank you _Gea, this looks like Windows 11 25H2 share problem, I have tried all Windows sugestion and tweeks to unable access to my NAS guest account without success, I have even disabled the guest account in OmniOS and Window 11 doesn't even prompt for User or pw, I have even created a new SMB user on OmniOS without success, I have also uninstalled two recent updates, it looks like Windows have done it again, breaking shares, not sure where to go from here.
 
Windows remembers login credentials per host ip or hostname
Start "Credential Manager" in Windows 11 to check and optionally delete login data

or change ip of OmniOS and SMB connect to new ip to try new credidentials
 
_Gea said:
Windows remembers login credentials per host ip or hostname
Start "Credential Manager" in Windows 11 to check and optionally delete login data

or change ip of OmniOS and SMB connect to new ip to try new credidentials
Click to expand...
Nothing under credentials manager, the OmniOS NAS is connected via 2 separate adaptors, I have tried the other IP address without success. thank you for the suggestion.
 
I think I am going to update OmniOS and see if that will make a difference, should I update Napp-it first or OmniOS?

Is there anything that could break my pool while upgrading?

The Napp-it version that I am running is 18.1 and OmniOS version r151038 I think, I have also version 5000 of the zfz pool I believe.
 
ohh such an old OmniOS

First update napp-it as a newer OmniOS may require a newer napp-it. But this is not critical as only some menus like User can be affected, not a later update. But an old OmniOS can be the problem as Microsoft requires now SMB signing for security reasons, https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-signing?tabs=group-policy and this is only in newer OmniOS SMB.

OS and ZFS update is far less critical in OmniOS compared to Linux. Just switch repository to next lts 151046 then do a pkg update + reboot. Then switch repository to current lts 151054 and call pkg update + reboot, then optionally update to newest stable 151056. A zpool update can update the ZFS pool.

https://omnios.org/releasenotes.html
http://www.napp-it.org/doc/downloads/setup_napp-it_os.pdf
 
Oh...Napp-it will not update from about, update, I am currently running version v.18.12w7.
 
1. Pool Export not needed
2. What message did you get in About > Update?
 
Apologies _Gea, the error is due to static address being set on both of my network adaptors and recently I had a new ISP which I think dont allow static :(
 
I have updated OmniOS to r151054lts, I have seen the below comments about updating beyond r151054lts, what's needed before updating to stable r151056?

Upgrade notes:​


 
napp-it 22.03 is the current default/free release.
You can use an evalkey from napp-it.org to update to newest 25.06 (that includes the multi-os/multi-server napp-it cs)

Grub was item for a very old OmniOS 151022
 
Thank you for all your help _Gea, Windows can see now OmniOS NAS.

I'll be replacing the 5x 14tb with the 5x 28tb storage spaces hdd's very soon, hope it all goes well!
 
N Bates said:
Thank you for all your help _Gea, Windows can see now OmniOS NAS.

I'll be replacing the 5x 14tb with the 5x 28tb storage spaces hdd's very soon, hope it all goes well!
Click to expand...
If not, try OpenZFS on Windows and napp-it cs that supports also Storage Spaces
 
Hummm... not happy with windows 11 for workstations storage spaces pool limitation of 63tb and the network write performance, only getting 100mb trasfering large files.

OpenZFS for windows is still beta, so I'll hold off on that one.

Will running windows server 2025 on hyper-v or vmware give me better performance and no large pool limitation, will this be suitable for a large media home server shared via SMB?
 
The 63tb on Win 11 is per virtual disk, not per pool but a Server 2022/25 (cheap Essentials is ok) has many advantages.
 
Did you follow this windows support article?
https://learn.microsoft.com/en-us/w...-guest-logons-smb2-and-smb3?tabs=group-policy

Since windows 10, guest access to remote smb shares has been disabled by default, and you need to manually enable it. I just skimmed the article, but looks like there is no graphical configuration for it, you need to enable with group policy/power shell.

As for user/password protected access, windows is pretty particular about matching the user name, and maybe workgroup name as well (don't remember, been too long). If it doesn't match, then it won't allow access.

SMB is just a pita in general. It's nice when it works, but when it doesn't... 😡😡😡
 
SMB is just be best sharing protokol. No other is as common and fast with SMB Direct/rdma up to 10 GB/s with lowest latency or superiour ACL and auditing options. Microsoft hesitated for a long time to enforce SMB signing that was the problem here as all older SMB servers stop working.

In the end Microsoft chooses security over compatibility and I welcome that.
 
You must log in or register to reply here.
Back
Top