Hi.
Is possible to change ClusterFaultDomain(in windows 2019) after create cluster. ?
Because i fount information that it's recommend to create that fault domains (chassis, rack, site etc. ) before creation s2d cluster. And create s2d cluster creator ask me if i want user that fault domains. But what if i have already operational cluster and i want to change ClusterFaultDomain from node to rack ?
Hello.
Is any one known where FaultDomainType = StorageNode fits ? Because i cano't faind information about that type ? This type is parent of node or chassis ?
Hello .
I have S2d Cluster on Windows 2019, with 2 nodes. Each node have connected 2 JBOD-s, So in Failover cluster Manager i have 4 enclosures. How i should setup my cluster to be sure that data will be spread between JBODS connected to different nodes. So in situation when 1 node goes down (with them 2 enclosures) all volumes are operational.
Hi There,
Massive shot in the dark here but I am struggling with a pretty major issue atm. We have a production file server that is hosted on the following:
Dell MD 3220i -> iSCSI -> Server 2008 R2 Hyper-v Cluster -> Passthrough Disk -> Server 2012 R2 File Server VM
Essentially 3 times now, roughly a month or so apart. The file server stops accepting connections. During this time, the server is perfectly accessible through rdp or with a simple ping. I can browse the files on the server directly but no-one appears to be able to access the shares over SMB. A reboot of the server fixes the issue.
As per a KB article I removed nod antivirus from the server to rule out a conflicting filter mode driver after the second fault. Sadly yesterday it happened again.
The only relevant errors in the servers log files are:
SMB Server Event ID 551
SMB Session Authentication Failure Client Name: \\192.168.105.79 Client Address: 192.168.105.79:50774 User Name: HHS\H6-08$ Session ID: 0xFFFFFFFFFFFFFFFF Status: Insufficient server resources exist to complete the request. (0xC0000205) Guidance: You should expect this error when attempting to connect to shares using incorrect credentials. This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients. This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled
and
SMB Server event ID 1020 File system operation has taken longer than expected. Client Name: \\192.168.105.97 Client Address: 192.168.105.97:49571 User Name: HHS\12J.Champion Session ID: 0x2C07B40004A5 Share Name: \\*\Subjects File Name: Command: 5 Duration (in milliseconds): 176784 Warning Threshold (in milliseconds): 120000 Guidance: The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.
I have checked the underlying disk/iscsi/network hyper-v cluster for any other errors or issues, but as far as I can tell everything is fine.
Is it possible that something else is left over from the NOD antivirus installation?
Looking for suggestions on how to troubleshoot this further.
Thanks
Hello,
I have a 2 node S2D cluster with 6 CSVs - 3 per node (Windows Server 2019 DC on both nodes) where I would like to swap out the 4TB disks with 8TB disks without blowing it away. Is that something that is supported (I understand there is a risk of data loss at all times), but is there any MS documentation on this and how it should be performed? How can we achieve this?
Thank you!
Hi!
My configuration is like this:
One Windows 10 pro computer (work client)
One physical server running Windows Server 2016 Standard, with two Hyper-V computers,
one running Windows Server 2016 Standard and one running Windows Server 2012.
My problem is, since I rebooted the physical server, I can no longer access the file shares of the physical server.
The work client is able to access both of the Hyper-V servers file shares. The 2012-server is though able to access the physical server's file share.
The physical server is showing up in network discovery, is ping-able from all computers.
I have read through plenty of entires, but have found none of them successful. What could be the problem?
Best regards,
Jonatan
I have two Windows 2016 NAS servers running DFS replication. I need to apply Windows patches to each server. I have experienced corruption of the database journal in the past either due to a previous Windows patching or a reboot of one of the NAS servers for another issue. What is the best practice for patching the servers. Do I stop the DFS service, other services, etc?
Thanks,
Milty
milty60
Hi,
I want to create a storagepool from a bunch af VHD's but I dont' know how to select the disks in the powershell command
What I did:
- New-VHD -Path d:\vhd\disk1.vhdx -SizeBytes 100GB | Mount-VHD (also did this for disk 2 up to 6)
Now I want to create a storagepool with powershell and only use disk 1, 3 and 5
If I use get-physicaldisk it returns me the name of my real physical disk and 6 disks with a friendlyname of "Msft Virtual Disk"
How do I know what is disk1 3 and 5 if all these names are the same ?
Hello all,
Within the past 2 days, we starting experiencing trouble with one of our shared volumes going into a paused state. This error messages constantly occurs every 10 seconds. I tried researching what "c000026e" means but couldn't find an explication for that error code. Can anyone assist?
Environment
1x Failover Cluster used for Scale-Out File Servers
2x Nodes (server 2012 R2)
36x Disk (Cluster Shared Volumes)
6x known "offline" disk
Event ID 5120
Cluster Shared Volume 'Volume27' ('JetStor DIT-JS-E2-B2-01') has entered a paused state because of '(c000026e)'. All I/O will temporarily be queued until a path to the volume is reestablished.
Hi,
I am transferring files from a Windows 2008 R2 servers to a Server 2019 server. It transfers about 6,000 files, then stops with this error: Check if the source device is online - we couldn't access it.
I have rechecked the prerequisites and they are fine.
I am a domain admin, and in the local admin group on both servers.
The 2019 server is build is 10.0.17763.
From the event log:
Couldn't transfer all of the files in the endpoint on the computer.
Job: Jobname
Computer: source computer
Destination Computer: computer
Endpoint: something
State: Failed
Source File Count: 0
Source File Size in KB: 0
Succeeded File Count: 0
Succeeded File Size in KB: 0
New File Count: 0
New File Size in KB: 0
Failed File Count: 0
Error: 40961
Error Message: Transfer failed
Guidance: Check the detailed error and make sure the transfer requirements are met. This could be because the orchestrator computer couldn't reach a source or destination computer, possibly due to a firewall rule, or missing permissions.
Any help would be appreciated!
Thanks
I'm attempting to create a new NFS Mapped identity in Server 2019 but am getting the following exception:
New-NfsMappedIdentity -GroupIdentifier 100 -UserIdentifier 100 -UserName Test--
I've created both passwd and group files:
%SystemRoot%\system32\drivers\etc\passwd
%SystemRoot%\system32\drivers\etc\group
--
And NFS services are running and functioning, I just want to map the UIDs to Windows users. Also tried:
>nfsadmin mappingFailed to connect to NFS WMI provider.
Any ideas?
MCSA: Windows Server 2008
Hi all,
Since the most recent official Windows 10 update (1803 April update) I'm experiencing some issues.
* In explorer, some pictures get thumbnails, some don't (as seen in the figure). Tried deleting the thumbnail cache but that doesn't help.
* The Photos app doesn't sync pictures from the WorkFolders anymore, and doens't show thumbnails anymore for videos.
* In exlporer the icons for 'Download state' aren't correct. Some folders have a 'Failed sync' icon, but all the files inside are downloaded correctly.
A clean install of the client operating system doesn't help. Anyone else experiencing these issues? Is a fix available soon?
Janjaap
Hi,
I am planning a 2-node S2D cluster. I think I'm all set in terms of configuration but one thing I'm not sure about is hot spares.
Obviously these are set at the pool level rather than the tier, so if I wanted hot-spares for both capacity and cache disks, does that just happen; if I assign 2 SSDs as spares, will they only be spares for the fast tier?
I'm thinking 16 capacity disks + 2 spares and 4 cache disks + 2 spares per node. 24 total.
Or am I going mad even thinking about this? Is it totally unneccessary for fast tiers?
Thanks
Dear sir,
Very sorry for disturbing you.
I am running three-way mirror volume on 3-node Storage Spaces Direct cluster. If one drive failed in 2-way mirror, the failed copy will be rebuilt automatically on a different drive on a different server.
However, for my three-way mirror volume, the failed copy is not rebuilt automatically on a different server (since I don't have 4th node).
Only one thing that I can do is to replace a new disk. Then the volume come back to "healthy" again.
In this case, may I ask, is it possible to define a "hot spare" in Storage Spaces Direct? so I don't need to replace the failed disk with a new disk manually (for three-way mirror in 3-node S2D cluster)?
Thank you very much in advance!
Results of the tests:
https://imgur.com/a/NHpIBfM
So, to make my consern clear, I need to understand if it is the known issue or did I do something wrong, or does my configuration needs to be modified in some kind of way. Any help will be greatly appreciated.
After installing KB4503276 on June 12, 2019, our Mac clients can no longer connect to SMB file shares on our Windows 2012 R2 server. Mac clients at our company regularly mount SMB volumes from the server onto their Mac desktops in order to access files stored on the server. Please observe that this problem has been noted as a product alert to its customers (such as our company) by Kodak, Inc. on June 12, 2019, and it also pertains to KB4503292 on Windows 2880 R2 servers; see their knowledgebase Answer ID 74519, quoted below.
Link to the full alert article at Kodak: https://services.kodak.com/app/answers/detail/a_id/74519
As a graphic arts customer using Kodak-supplied software we received the abovementioned product alert and followed Kodak's recommendation to uninstall the update, after which our SMB file shares were again useable by Mac clients.
Hello
I administer a Hyper-v Windows 2016 Server. The data virtual volume (containing the VMs) went offline twice in the last week.
When the error occurs, incidentally the volume is offline (i.e. in Disk Management),
Rebooting the server brings it back up gracefully, with the storage online and perfectly usable.
get-virtualdisk shows healthy and get-physicaldisk shows healthy for every disk in the storage pool.
We got
error 08.09.2017 00:09:37 StorageSpaces-Driver eventID: 312
error on virtual disk "{043afeb2-e102-45f2-937c-df53b68c2289}" on writing in all copies.
and
warning 08.09.2017 00:09:37 Disk 51
An error was detected on device \Device\Harddisk6\DR6.during a paging operation.
This is the virtual volume.
The problem exists on the data volume, containing the VMs. We use 4 disks. 2SSDS and 2 harddisks as tiered storage with storage layout as mirror. This contains 1 Virtual volume (ReFS formatted)
The hardware seems healthy and I thought that the mirror configuration should prevent from going offline if an error occurs in one of the disks.
Do you have any hint what to do? or to further investigate the error?
Thank you very much
Michael
Gurus, I'm really hoping someone can help here. Here's the setup and situation.
Setup:
Situation:
What we need:
We have tried the following:
Regardless of what we try, the client always wipes the CSC cache when the share is re-created. Is there any way around this? Of course we can have the users back up their data and then move it back, but this is very destructive and we would prefer not to take chances that someone forgets or makes a mistake.
What is troubling is that under normal circumstances when a user creates a file while offline and then connects to the network and syncs, the file uploads to the server (expected behavior) rather than deleting itself from the client. So why should this be any different?
Thanks in advance for any help you can provide. We are pulling our hair out!