Error -50 on a shared volume (SOLUTION)

Today my antique Xserve (G5, 2 Gigs RAM, 10.4.11) started throwing error -50s on any changes on the main shared volume. Couldn't create a folder, save a file, rename a file or any other change.
After running Disk Utility repairs on the shared volumes and fixing the errors, the volume returned to normal service. YMMV on 10.5 and 10.6 server,but check the disk anyway,

How have you set up sharing.
Can you confirm the exact wording of the error message.

Similar Messages

Error when adding a disk to Cluster Shared Volumes

When adding a disk to Cluster Shared Volumes via Failover Cluster Manager, I get a couple of errors.
Event ID 5145 in System Log:
While adding the disk ('Cluster Disk 1') to Cluster Shared Volumes, setting explicit snapshot diff area association for volume ('\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\') failed with error 'HrError(0x8004230d)'. The only supported software snapshot
diff area association for Cluster Shared Volumes is to self.
Cluster disk resource 'Cluster Disk 1' failed to delete a software snapshot. The diff area on volume '\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\' could not be dissociated from volume '\\?\Volume{420e2cc4-4fb4-41be-afb1-65f2ee62457a}\'. This
may be caused by active snapshots. Cluster Shared Volumes requires that the software snapshot be located on the same disk.
Any ideas why I'm getting this error? This disk was previously added as a CSV to different Windows failover cluster, if that matters. Thanks.

Hi,
As the disk was previously used as a CSV, I assume there is still data on it.
Please check if any VSS snapshot created on that disk. If so, delete them and re-add it as a CSV to see the result - a quick way is to backup important files and perform a re-format if you cannot confirm.
If you have any feedback on our support, please send to [email protected]

File Sharing Service keeps crashing Error Reading Settings, File Sharing Service keeps crashing Error Reading Settings

File sharing service keeps popping up with the error message An error occurred on the server while processing a command. This error occurred while processing a command of type 'getConnectedUsers' in plug-in 'servermgr_afp'.
I have tried multiple solutions on this site, unloading afp and restarting it, restarting postgres. The file sharing tab will show up for a few seconds on the server.app config page then once someone tries to access any of the shared volumes on there, the event log shows it crashing instantly. Error in console:
The server '127.0.0.1' reported an error while processing a command of type 'getConnectedUsers' in plug-in: 'servermgr_afp'. Error: Error Domain=XSActionErrorDomain Code=0 "SETTING_NOT_FOUND_ERR" UserInfo=0x7ffe6a835060 {NSLocalizedDescription=SETTING_NOT_FOUND_ERR}
Also I get the error com.apple.launchd: (com.apple.collabd.notifications[7520]) Exited with code 1 then always followed by Throttling respawn: Will start in 10 seconds and this happens every 10 seconds without fail.

I have started getting this error this morning:
This error occurred while processing a command of type 'getConnectedUsers' in plug-in 'servermgr_afp'.
Using Server 2.2.2; MacMini running OS X 10.8.5, 2 GHz Core i7 with 8 GB RAM attached to a 12TB Pegasus RAID.
When the error appears, my users cease to be able to access file shares.
Often, just before the error occurs, my users experience substantial slow down in the Finder's responsiveness when manipulating files on those shares.
Restarting the Server App will produce one of several results
1. fix the problem (rarely)
2. fail to connect to server
3. connect to server but not get all services running.
The system itself resists a full shutdown, hanging at the grayish-white screen (not spinning wheel or cog or apple logo).
I wish there was some known fix for this.

Hyper-V cluster Backup causes virtual machine reboots for common Cluster Shared Volumes members.

I am having a problem where my VMs are rebooting while other VMs that share the same CSV are being backed up. I have provided all the information that I have gather to this point below. If I have missed anything, please let me know.
My HyperV Cluster configuration:
5 Node Cluster running 2008R2 Core DataCenter w/SP1. All updates as released by WSUS that will install on a Core installation
Each Node has 8 NICs configured as follows:
NIC1 - Management/Campus access (26.x VLAN)
NIC2 - iSCSI dedicated (22.x VLAN)
NIC3 - Live Migration (28.x VLAN)
NIC4 - Heartbeat (20.x VLAN)
NIC5 - VSwitch (26.x VLAN)
NIC6 - VSwitch (18.x VLAN)
NIC7 - VSwitch (27.x VLAN)
NIC8 - VSwitch (22.x VLAN)
Following hotfixes additional installed by MS guidance (either while build or when troubleshooting stability issue in Jan 2013)
KB2531907 - Was installed during original building of cluster
KB2705759 - Installed during troubleshooting in early Jan2013
KB2684681 - Installed during troubleshooting in early Jan2013
KB2685891 - Installed during troubleshooting in early Jan2013
KB2639032 - Installed during troubleshooting in early Jan2013
Original cluster build was two hosts with quorum drive. Initial two hosts were HST1 and HST5
Next host added was HST3, then HST6 and finally HST2.
NOTE: HST4 hardware was used in different project and HST6 will eventually become HST4
Validation of cluster comes with warning for following things:
Updates inconsistent across hosts
  I have tried to manually install "missing" updates and they were not applicable
  Most likely cause is different build times for each machine in cluster
   HST1 and HST5 are both the same level because they were built at same time
   HST3 was not rebuilt from scratch due to time constraints and it actually goes back to Pre-SP1 and has a larger list of updates that others are lacking and hence the inconsistency
   HST6 was built from scratch but has more updates missing than 1 or 5 (10 missing instead of 7)
   HST2 was most recently built and it has the most missing updates (15)
Storage - List Potential Cluster Disks
  It says there are Persistent Reservations on all 14 of my CSV volumes and thinks they are from another cluster.
  They are removed from the validation set for this reason. These iSCSI volumes/disks were all created new for
  this cluster and have never been a part of any other cluster.
When I run the Cluster Validation wizard, I get a slew of Event ID 5120 from FailoverClustering. Wording of error:
  Cluster Shared Volume 'Volume12' ('Cluster Disk 13') is no longer available on this node because of
  'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the
  volume is reestablished.
Under Storage and Cluster Shared VOlumes in Failover Cluster Manager, all disks show online and there is no negative effect of the errors.
Cluster Shared Volumes
We have 14 CSVs that are all iSCSI attached to all 5 hosts. They are housed on an HP P4500G2 (LeftHand) SAN.
I have limited the number of VMs to no more than 7 per CSV as per best practices documentation from HP/Lefthand
VMs in each CSV are spread out amonst all 5 hosts (as you would expect)
Backup software we use is BackupChain from BackupChain.com.
Problem we are having:
When backup kicks off for a VM, all VMs on same CSV reboot without warning. This normally happens within seconds of the backup starting
What have to done to troubleshoot this:
We have tried rebalancing our backups
  Originally, I had backup jobs scheduled to kick off on Friday or Saturday evening after 9pm
  2 or 3 hosts would be backing up VMs (Serially; one VM per host at a time) each night.
  I changed my backup scheduled so that of my 90 VMs, only one per CSV is backing up at the same time
   I mapped out my Hosts and CSVs and scheduled my backups to run on week nights where each night, there
   is only one VM backed up per CSV. All VMs can be backed up over 5 nights (there are some VMs that don't
   get backed up). I also staggered the start times for each Host so that only one Host would be starting
   in the same timeframe. There was some overlap for Hosts that had backups that ran longer than 1 hour.
  Testing this new schedule did not fix my problem. It only made it more clear. As each backup timeframe
  started, whichever CSV the first VM to start was on would have all of their VMs reboot and come back up.
I then thought maybe I was overloading the network still so I decided to disable all of the scheduled backup
and run it manually. Kicking off a backup on a single VM, in most cases, will cause the reboot of common
CSV members.
Ok, maybe there is something wrong with my backup software.
  Downloaded a Demo of Veeam and installed it onto my cluster.
  Did a test backup of one VM and I had not problems.
  Did a test backup of a second VM and I had the same problem. All VMs on same CSV rebooted
Ok, it is not my backup software. Apparently it is VSS. I have looked through various websites. The best troubleshooting
site I have found for VSS in one place it on BackupChain.com (http://backupchain.com/hyper-v-backup/Troubleshooting.html)
I have tested almost every process on there list and I will lay out results below:
  1. I have rebooted HST6 and problems still persist
  2. When I run VSSADMIN delete shadows /all, I have no shadows to delete on any of my 5 nodes
   When I run VSSADMIN list writers, I have no error messages on any writers on any node...
  3. When I check the listed registry key, I only have the build in MS VSS writer listed (I am using software VSS)
  4. When I run VSSADMIN Resize ShadowStorge command, there is no shadow storage on any node
  5. I have completed the registration and service cycling on HST6 as laid out here and most of the stuff "errors"
   Only a few of the DLL's actually register.
  6. HyperV Integration Services were reconciled when I worked with MS in early January and I have no indication of
   further issue here.
  7. I did not complete the step to delete the Subscriptions because, again, I have no error messages when I list writers
  8. I removed the Veeam software that I had installed to test (it hadn't added any VSS Writer anyway though)
  9. I can't realistically uninstall my HyperV and test VSS
  10. Already have latest SPs and Updates
  11. This is part of step 5 so I already did this. This seems to be a rehash of various other stratgies
I have used the VSS Troubleshooter that is part of BackupChain (Ctrl-T) and I get the following error:
  ERROR: Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state!
  - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
  - Writer Failure code: 0x800423f0 (<Unknown error code>)
  - Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  - Instance ID: {d55b6934-1c8d-46ab-a43f-4f997f18dc71}
  VSS snapshot creation failed with result: 8000FFFF
VSS errors in event viewer. Below are representative errors I have received from various Nodes of my cluster:
I have various of the below spread out over all hosts except for HST6
Source: VolSnap, Event ID 10, The shadow copy of volume took too long to install
Source: VolSnap, Event ID 16, The shadow copies of volume x were aborted because volume y, which contains shadow copy storage for this shadow copy, wa force dismounted.
Source: VolSnap, Event ID 27, The shadow copies of volume x were aborted during detection because a critical control file could not be opened.
I only have one instance of each of these and both of the below are from HST3
Source: VSS, Event ID 12293, Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnashot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an
unexpected error.
Source: VSS, Event ID 8193, Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult. hr = 0x80070057, The parameter is incorrect.
So, basically, everything I have tried has resulted in no success towards solving this problem.
I would appreciate anything assistance that can be provided.
Thanks,
Charles J. Palmer
Wright Flood

Tim,
Thanks for the reply. I ran the first two commands and got this:
Name
Role Metric
Cluster Network 1
3  10000
Cluster Network 2 - HeartBeat                              1   1300
Cluster Network 3 - iSCSI                                    0  10100
Cluster Network 4 - LiveMigration                         1   1200
When you look at the properties of each network, this is how I have it configured:
Cluster Network 1 - Allow cluster network communications on this network and Allow clients to connect through this network (26.x subnet)
Cluster Network 2 - Allow cluster network communications on this network. New network added while working with Microsoft support last month. (28.x subnet)
Cluster Network 3 - Do not allow cluster network communications on this network. (22.x subnet)
Cluster Network 4 - Allow cluster network communications on this network. Existing but not configured to be used by VMs for Live Migration until MS corrected. (20.x subnet)
Should I modify my metrics further or are the current values sufficient.
I worked with an MS support rep because my cluster (once I added the 5th host) stopped being able to live migrate VMs and I had VMs host jumping on startup. It was a mess for a couple of days. They had me add the Heartbeat network as part of the solution
to my problem. There doesn't seem to be anywhere to configure a network specifically for CSV so I would assume it would use (based on my metrics above) Cluster Network 4 and then Cluster Network 2 for CSV communications and would fail back to the Cluster Network
1 if both 2 and 4 were down/inaccessible.
As to the iSCSI getting a second NIC, I would love to but management wants separation of our VMs by subnet and role and hence why I need the 4 VSwitch NICs. I would have to look at adding an additional quad port NIC to my servers and I would be having to
use half height cards for 2 of my 5 servers for that to work.
But, on that note, it doesn't appear to actually be a bandwidth issue. I can run a backup for a single VM and get nothing on the network card (It caused the reboots before any real data has even started to pass apparently) and still the problem occurs.
As to Backup Chain, I have been working with the vendor and they are telling my the issue is with VSS. They also say they support CSV as well. If you go to this page (http://backupchain.com/Hyper-V-Backup-Software.html)
they say they support CSVs. Their tech support has been very helpful but unfortunately, nothing has fixed the problem.
What is annoying is that every backup doesn't cause a problem. I have a daily backup of one of our machines that runs fine without initiating any additional reboots. But most every other backup job will trigger the VMs on the common CSV to reboot.
I understood about the updates but I had to "prove" it to the MS tech I was on the phone with and hence I brought it up. I understand on the storage as well. Why give a warning for something that is working though... I think that is just a poor indicator
that it doesn't explain that in the report.
At a loss for what else I can do,
Charles J. Palmer

Permission denied when saving from applications on shared volume

We have an AFP shared volume on Xraid attached to an Xserve running 10.5.8. The OS is kept up to date.
Users started to get a "permission denied" message when trying to save open files on the shared volume, which is using POSIX permissions only. This seems to happen to Snow Leopard clients using Pages and Numbers (iLife 09). No errors appear in the server logs.
At the moment they can circumvent the problem by saving locally and then copying the file onto the server.
Has anyone got any pointer to a solution?
Thanks.

Lucazade wrote:
This seems to happen to Snow Leopard clients using Pages and Numbers (iLife 09).
Of course I meant iWork, not iLife.

Error while starting the shared service server

Hi john,
I am getting the following error while starting the shared service server.
*25 Jul 2009 10:26:39 - org.apache.slide.common.Domain - ERROR - Unable to migrate hub groups to css*
So shared service console is not starting.
Please tell me the solution for it.
Thanks
Edited by: user11358816 on Jul 24, 2009 10:06 PM
Edited by: user11358816 on Jul 24, 2009 10:09 PM

Hi John,
Yes,It was working earlier.
When I have added NTLM authentication for FDM I am getting that error,but instead of that if
I am adding the authentication provider as LDAP(CSS) I am not getting that error.
So finally i have added only one authentication provider and that is LDAP(CSS).
I fallowed ur document for integrating the FDM application with planning application.(http://john-goodwin.blogspot.com/2008/07/planning-v11-drill-back.html )
For the global logon information I have given admin and password , which I have given while adding the LDAP authentication (CSS).
I am getting machine profile missing error when i clicked on the dimension and the target dimension test box contain connection failed.
Can u suggest me where am I wrong?
Thanks
Edited by: user11358816 on Jul 26, 2009 9:42 PM

"Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it." occurs while deploying from Visual studio

HI,
I get this error "Error occurred in deployment step 'Retract Solution': The solution does not have a WSP file associated with it. " when deploying my project from visual studio 2010 to
SharePoint 2010 site. I tried restarting IIS, but it didn't help. This application used to work fine until the server crashed during the deployment process. All the other applications on the same server works fine also. Any ideas how to fix this issue?
Thanks in advance,
AM

Hi
AM ,
Thank you for your posting!
According to your error message, it says your solution does not have a WSP file associated with it. Take a look at the file system. After you Right Click -> Deploy Solution on the VS Solution, there
should be a .wsp file at <Solution Directory>\bin\<debug|release>.
Also the error can be occurring when the developer try to deploy solutions over pre-existing solutions with material changed in the solution. Go to your Central Administration Site and then
Operations and then Solution Management. Make sure that there not already a solution with the same name deployed or installed there. If there is, remove it and try deploying again.
And you could look in logs and find if there is a below error in ULS log (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).
Thank you for your understanding and support.
Best Regards,
Eric
Eric Tao
TechNet Community Support

Error occurred in deployment step 'Add Solution': Failed to extract the cab file in the solution.

I have received the follwoing error when I depoly the custom masterpage with css, images, javascript files:
Error occurred in deployment step 'Add Solution': Failed to extract the cab file in the solution.
Any help will soon is appreciated.

Hi Bagalur,
Thanks for your sharing. It will help others who stuck will the same issue.
Best Regards
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jerry Guo
TechNet Community Support

How do I connect to a Windows Workgroup and mount a shared volume?

I have set up a network at home with my Mac G5 and my PC. I have a workgroup called "HOME". The PC can see my mac drive as a network place and I can access and browse it perfectly fine.
However I have a drive on my PC which I have set up as a shared volume on the PC. I want to mount that shared volume on my Mac. When I set up the share on the PC, I am not prompted to enter a password, and the only password I am aware of is the one I use to log on.
According to the instructions I am supposed to enter the IP address and a "sharename", but I have no idea what the sharename is. If I enter the share name of the volume I want to mount, I get a dialog box which requires a password. It sees the "HOME" workgroup and that is already filled out in the Workgroup window.
It has entered my Mac administrator account name in the Name box. I don't know if this is what name it needs, but what ever combination of names and passwords I use, including my PC logon name and password, I always get the error message "cannot connect because the name or password is not correct".
I have tried using different formats for the smb://Servername/sharename address, but everything I have tried gives the same result.
I have seen many other postings on this subject, all with similar problems, but so far I've yet to see an answer. A disscussion from 2004 said this was a known issue, but surely there must have been a fix by now?
I have read many of the mac documents on this subject but none specifically tells you what the sharename is and how you set a password for it.
Thanks in advance
David

OK - I have answered my own question, so if anyone else has this problem, you may like to know!
I needed to know what sharename to use to log on. On the Windows PC I was under the imprression that the windows log on was my user name. But if you right click on the My Computer and go to manage, you will see Local Users and Groups. Under Users, you will see all the user accounts on the PC. Even though I only ever set up one and it was called "David" that doesn't actually count as the user name.
If you look at the headings at the top, you will see that whatever account you think you are in, the chances are it actually has the name "User". It is what ever is in the Name column that the Mac needs, not what is in the Full Name column which is what you log on as. You can't change this, but when you connect to server, you can enter the SMB script smb://USER@(name of PC or IP address)/share name.
If you wish to mount a volume rather than a shared folder, simply type in the windows drive letter followed by the "$" - ie D$. The password is your log on password on the PC. Otherwise you can set up a folder share on the PC in the usual way, and give it a name. This will be the share name you enter in your smb script.
NONE of this is very clear in any of the Mac Networking Help guides that I have trawled through, so if they were to add it, you might help some more people...
Thanks,
David
G5 Mac OS X (10.4.6)

How to recover deleted files from a shared volume?

Setup - Mac Mini Server (OSX 10.8.4, Server 2.2.1(169)), 256GB Flash drive, System data only. External 8TB G-Raid holds all business data, backed up to a LaCie 6TB Quadra using Intego Backup Manager Pro 1.0.9. The G-Raid has two folders 0_Clients and DATA which are shared through OS X Server.
Situation, told customer backup drive (LaCie) was almost full mid April, purge data. They didn't and backups stopped running at end of April. Yesterday, they accidentally deleted a folder / with files. User was on an iMac, connected to the share DATA when deleted. Called in a panic of course. New folder and files were created after the last back was executed.
Question - Folder and files were deleted but Trash was not "emptied". Researching, I learned about hidden trash folders. So, I was hopeful I'd find the info in the hidden /.Trashes folder on the shared Volume G-Raid. My understanding is that that's where it would go, until an "empty trash" is executed. I've shown all hidden files / folders via "defaults write com.apple.finder AppleShowAllFiles TRUE". Navigated to the volume G-Raid/.Trashes and the folder/ files are not there. Is there another location where they may possibly be??? Or, are they hosed and it's really gone "Deleted"???
Thx

With a locally connected volume e.g. a hard disk or USB flash drive, when you delete a file it does get moved to the 'Trash' folder and until the Trash is emptied can still be retrieved. However with a network volume if a logged in user deletes a file or folder it normally gets deleted immediately. (The user would get a message saying "This item will be deleted immediately. You can’t undo this action.")
So the likelihood is that the items are not in any trash folder even if you found and looked in them.
It used to be the case that even when using a network file server you still had the benefit of files first going to the trash folder but Apple stopped doing this a long time ago. The network trash folder would be at the top level of the network share. (If it exists and works.) Some NAS devices might still support it but as I mentioned I don't believe Apple themselves do.
So you could try using Terminal.app to look for an invisible folder at the top-level folder of the network share, if the network share is a folder called 'Fred' then this invisible folder would be in 'Fred' and would be called "Network Trash Folder". You can try looking for this either on the server or from a logged in client.
Do ls -la in Terminal.app the 'a' flag means show all including invisible files.
As you have probably guessed by now it is almost certainly the case these files are lost and cannot be retrieved. The users unfortunately are guilty of multiple mistakes.
They ignored your warning about the backup drive
They deleted something they should not have
They ignored the warning the Mac would have shown about "This item will be deleted immediately. You can’t undo this action."
I would add an additional error that they and perhaps you as their advisor are guilty of. Never rely on a single level of backup, ideally you should have a rotating set of backups i.e. one for each day - Monday, Tuesday, etc. and even more importantly should store these off-site unless being used so that in the even of a fire, flood or other disaster you still have intact backups.
In theory ACL permissions can be set to allow reading, allow writing but disallow deleting. Unfortunately in the real world trying to use the disallow deleting option is a waste of time. This is because many programs 'save' changes by saving a new temporary file, deleting the original file, and renaming the temporary file to the original name. This will not work if you block deleting.

Snow Leopard Finder's Get Info fails to show Owner and Group for some files or folders which reside on a Shared Volume, hosted by G5 Server w/ OS 10.4 - why?

Frustrations with file permissions abound, as certain co workers are unable to manually determine their level of permission or who to ask to make changes to files and folders belonging to others. Users of Snow Leopard desktop OS get unhelpful feedback via Finder's Get Info, seeing only the permissions listed for "Everyone" and a statement that "You have custom access". The custom message exists, presumably, because ACL's are employed on the shared volume in an attempt to give managerial control over these volumes to specific users, even if all users can create files and folders on those volumes.
Shared volumes are partitions of an external RAID which are set up as sharepoints on a G5 tower running Server 10.4. Other persons in the office, using machines that are running desktop OS 10.5, can correctly see the assigned Owner and Group permissions (although the "custom access" still shows). This at least lets the 10.5 user know who created a given file or folder, so that they can resolve permissions-restricted issues if they come up (i.e. User A wants to delete file X, but as it was created by User B, A must contact B and have them delete it. In 10.6 it appears that A cannot determine who B is).
I know that ACL's are functioning (enabled on the drive) since we have been making use of ACL-granted write privileges for quite a while (and the custom access seems to be evidence too).
An error I encountered, pertaining to this, is that I used a 10.6 machine to create a working folder, then generated and saved several files in this location. Expected permissions thus would be Owner = me (i.e. the user I was logged in as), R/W, Group = staff, R only, Everyone = R only. However, immediately the permissions shown in Finder / Get Info consisted only of Everyone = R only, with no entry for Owner or Group. Moreover, clicking + to add either an Owner or a Group resulted in error message that I had entered an invalid user or group, even though I typed in correct info (such as trying to add "staff" as a group).

Frustrations with file permissions abound, as certain co workers are unable to manually determine their level of permission or who to ask to make changes to files and folders belonging to others. Users of Snow Leopard desktop OS get unhelpful feedback via Finder's Get Info, seeing only the permissions listed for "Everyone" and a statement that "You have custom access". The custom message exists, presumably, because ACL's are employed on the shared volume in an attempt to give managerial control over these volumes to specific users, even if all users can create files and folders on those volumes.
Shared volumes are partitions of an external RAID which are set up as sharepoints on a G5 tower running Server 10.4. Other persons in the office, using machines that are running desktop OS 10.5, can correctly see the assigned Owner and Group permissions (although the "custom access" still shows). This at least lets the 10.5 user know who created a given file or folder, so that they can resolve permissions-restricted issues if they come up (i.e. User A wants to delete file X, but as it was created by User B, A must contact B and have them delete it. In 10.6 it appears that A cannot determine who B is).
I know that ACL's are functioning (enabled on the drive) since we have been making use of ACL-granted write privileges for quite a while (and the custom access seems to be evidence too).
An error I encountered, pertaining to this, is that I used a 10.6 machine to create a working folder, then generated and saved several files in this location. Expected permissions thus would be Owner = me (i.e. the user I was logged in as), R/W, Group = staff, R only, Everyone = R only. However, immediately the permissions shown in Finder / Get Info consisted only of Everyone = R only, with no entry for Owner or Group. Moreover, clicking + to add either an Owner or a Group resulted in error message that I had entered an invalid user or group, even though I typed in correct info (such as trying to add "staff" as a group).

Cluster shared volume disappear... STATUS_MEDIA_WRITE_PROTECTED(c00000a2)

Hi all, I am having an issue hopefully someone can help me with. I have recently inherited a 2 node cluster,
both nodes are one half of an ASUS
RS702D-E6/PS8 so both nodes should be near identical. They are both running Hyper-V Server 2008 R2 hosting some 14 VM's.
Each node is hooked up via cat5e to a Promise
VessRAID 1830i via iSCSI using one of the servers onboard NICs each, whose cluster network is setup as Disabled for cluster use (the way I think it is supposed to be not the way I had originally inherited it) on it's own Class A Subnet and on it's own
private physical switch...
The SAN hosts a 30GB CSV Witness Disk and 2 2TB CSV Volumes, one for each node labeled Volume1 and Volume2. Some VHD's on each.
The Cluster Clients connect to the rest of the company via the Virtual ExternalNIC adapters created in Hyper-V manager but physically are off of Intel ET Dual Gigabit adapters
wired into our main core switch which is set up with class c subnets.
I also have a crossover cable wired up running to the other ports on the Intel ET Dual Port NICs using yet a third Class B Subnet and is configured in the Failover Cluster
Manger as internal so there are 3 ipv4 Cluster networks total.
Even though the cluster passes the validation tests with flying colors I am not convinced all is well. With Hyperv1 or node 1,
I can move the CSV's and machines over to hyperv2 or node 2, stop the cluster service on 1 and perform maintenance such as a reboot or install patches if needed. When it reboots or I restart the cluster service to bring it back online,
it is well behaved leaving hyperv2 the owner of all 3 CSV's Witness, Volume 1 and 2. I can then pass them back or split them up any which way and at no point is cluster service interrupted or noticed by users, duh I know this is how it is SUPPOSED to work
but...
if I try the same thing with Node 2, that is move the witness and volumes to node 1 as owner and migrate all VM's over, stop cluster service on node 2, do whatever I have
to do and reboot, as soon as node 2 tries to go back online, it tries to snatch volume 2 back, but it never succeeds and then the following error is logged in cluster event log:
Hyperv1
Event ID: 5120
Source: Microsoft-Windows-FailoverClustering
Task Category: Cluster Shared Volume
The listed message is:
Cluster Shared Volume 'Volume2' ('HyperV1 Disk') is no longer available on this node because of 'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until
a path to the volume is reestablished.
Followed 4 seconds later by:
Hyperv1
event ID: 1069
Source: Microsoft-Windows-FailoverClustering
Task Catagory: Resource Control Manager
Message: Cluster Resource 'Hyperv1 Disk in clustered service or application '75d88aa3-8ecf-47c7-98e7-6099e56a097d'
failed.
- AND -
2 of the following:
Hyperv1
event ID: 1038
Source: Microsoft-Windows-FailoverClustering
Task Catagory: Physical Disk Resource
Message: Ownership of cluster disk 'HyperV1 Disk' has been unexpectedly lost by this node. Run the Validate
a Configuration wizard to check your storage configuration.
Followed 1 second later by another 1069 and then various machines are failing messages.
If you browse to
\\hyperv-1\c$\clusterstorage\ or
\\hyperv-2\c$\Clusterstorage\, Volume 2 is indeed missing!!
This has caused me to panic a few times as the first time I saw this I thought everything was lost but I can get it back by stopping the service on node 1 or shutting it
down, restarting node 2 or the service on node 2 and waiting forever for the disk to list as failed and then shortly thereafter it comes back online. I can then boot node 1 back up and let it start servicing the cluster again. It doesn’t pull the same
craziness node 2 does when it comes online; it leaves all ownership with 2 unless I tell I to move.
I am very new to clusters and all I know at this point is this is pretty cool stuff but basically if it is running don’t mess with it is the attitude I have taken
with it but there is a significant amount of money tied up in this hardware and we should be able to leverage this as needed, not wonder if it is going to act up again.
To me it seems for a ‘failover’ cluster it should be way more robust than this...
I can go into way more detail if needed but I didn’t see any other posts on this specific issue no matter what forum I scoured. I’m obviously looking for advice
on how to get this resolved as well as advice on whether or not I wired the cluster networks correctly. I am also not sure about what protocols are bound to what nics anymore and what the binding order should be, could this be what is causing my issue?
I have NVSPBIND and NVSPSCRUB on both boxes if needed.
Thanks!
-LW

Hello Ravikumar,
Thanks about your attention!
All disks are Online, see below the status of disks, but the problem continues, any ideas?
PS.: For your information, all disks are delivered to hosts by SAN/HBA and all tests from Cluster Validation are passed.
PS C:\Users\hyperv_admin> Get-ClusterSharedVolume
Name State Node
hyperv-04_vol1_fc
Online vmserver27
hyperv-04_vol2_fc
Online vmserver26
hyperv-04_vol3_sata
Online vmserver25
hyperv-04_vol4_sata
Online vmserver27
See below the patches applied on my hosts:
KB2263829 http://support.microsoft.com/?kbid=2263829
KB2425227 http://support.microsoft.com/?kbid=2425227
KB2484033 http://support.microsoft.com/?kbid=2484033
KB2488113 http://support.microsoft.com/?kbid=2488113
KB2492386 http://support.microsoft.com/?kbid=2492386
KB2494016 http://support.microsoft.com/?kbid=2494016
KB2494162 http://support.microsoft.com/?kbid=2494162
KB2505438 http://support.microsoft.com/?kbid=2505438
KB2506014 http://support.microsoft.com/?kbid=2506014
KB2506212 http://support.microsoft.com/?kbid=2506212
KB2506928 http://support.microsoft.com/?kbid=2506928
KB2507618 http://support.microsoft.com/?kbid=2507618
KB2509553 http://support.microsoft.com/?kbid=2509553
KB2510531 http://support.microsoft.com/?kbid=2510531
KB2511250 http://support.microsoft.com/?kbid=2511250
KB2511455 http://support.microsoft.com/?kbid=2511455
KB2512715 http://support.microsoft.com/?kbid=2512715
KB2515325 http://support.microsoft.com/?kbid=2515325
KB2518869 http://support.microsoft.com/?kbid=2518869
KB2520235 http://support.microsoft.com/?kbid=2520235
KB2522422 http://support.microsoft.com/?kbid=2522422
KB2525835 http://support.microsoft.com/?kbid=2525835
KB2529073 http://support.microsoft.com/?kbid=2529073
KB2531907 http://support.microsoft.com/?kbid=2531907
KB2533552 http://support.microsoft.com/?kbid=2533552
KB2536275 http://support.microsoft.com/?kbid=2536275
KB2536276 http://support.microsoft.com/?kbid=2536276
KB2541014 http://support.microsoft.com/?kbid=2541014
KB2544521 http://support.microsoft.com/?kbid=2544521
KB2544893 http://support.microsoft.com/?kbid=2544893
KB2545698 http://support.microsoft.com/?kbid=2545698
KB2547666 http://support.microsoft.com/?kbid=2547666
KB2550886 http://support.microsoft.com/?kbid=2550886
KB2552040 http://support.microsoft.com/?kbid=2552040
KB2552343 http://support.microsoft.com/?kbid=2552343
KB2556532 http://support.microsoft.com/?kbid=2556532
KB2560656 http://support.microsoft.com/?kbid=2560656
KB2563227 http://support.microsoft.com/?kbid=2563227
KB2564958 http://support.microsoft.com/?kbid=2564958
KB2567680 http://support.microsoft.com/?kbid=2567680
KB2570947 http://support.microsoft.com/?kbid=2570947
KB2572077 http://support.microsoft.com/?kbid=2572077
KB2584146 http://support.microsoft.com/?kbid=2584146
KB2585542    http://support.microsoft.com/?kbid=2585542
KB2588516 http://support.microsoft.com/?kbid=2588516
KB2598845 http://support.microsoft.com/?kbid=2598845
KB2603229 http://support.microsoft.com/?kbid=2603229
KB2607047 http://support.microsoft.com/?kbid=2607047
KB2608658 http://support.microsoft.com/?kbid=2608658
KB2618451 http://support.microsoft.com/?kbid=2618451
KB2620704 http://support.microsoft.com/?kbid=2620704
KB2620712 http://support.microsoft.com/?kbid=2620712
KB2621440    http://support.microsoft.com/?kbid=2621440
KB2631813 http://support.microsoft.com/?kbid=2631813
KB2632503 http://support.microsoft.com/?kbid=2632503
KB2633873 http://support.microsoft.com/?kbid=2633873
KB2633952 http://support.microsoft.com/?kbid=2633952
KB2636573 http://support.microsoft.com/?kbid=2636573
KB2639308 http://support.microsoft.com/?kbid=2639308
KB2640148 http://support.microsoft.com/?kbid=2640148
KB2641653 http://support.microsoft.com/?kbid=2641653
KB2641690 http://support.microsoft.com/?kbid=2641690
KB2643719 http://support.microsoft.com/?kbid=2643719
KB2644615    http://support.microsoft.com/?kbid=2644615
KB2645640 http://support.microsoft.com/?kbid=2645640
KB2647516 http://support.microsoft.com/?kbid=2647516
KB2647518 http://support.microsoft.com/?kbid=2647518
KB2654428
http://support.microsoft.com/?kbid=2654428
KB2656356 http://support.microsoft.com/?kbid=2656356
KB2660075 http://support.microsoft.com/?kbid=2660075
KB2665364 http://support.microsoft.com/?kbid=2665364
KB2667402 http://support.microsoft.com/?kbid=2667402
KB976902 http://support.microsoft.com/?kbid=976902
KB982018
http://support.microsoft.com/?kbid=982018
Thanks
Ricardo

Cluster Shared Volume disappeared after taking the volume offline for Validation Tests.

Hi,
After an unknown issue with one of our Hyper-V 4 Node cluster running on Server 2008 R2 SP1 with fibre channel NEC D3-10 SAN Storage all our cluster shared volumes were in redirecting mode and I was unable to get them back online. Only after rebooting all
the nodes one by one the disks came back online. Eventlog messages indicated that I had to test my cluster validation. After shutting down all the virtual machines I set all the cluster shared volumes offline and started the complete validation test. The following
warnings/errors appeared during the test.
An error occurred while executing the test.
An error occurred retrieving the
disk information for the resource 'VSC2_DATA_H'.
Element not found (Validate Volume Consistency Test)
Cluster disk 4 is a Microsoft MPIO based disk
Cluster disk 4 from node has 4 usable path(s) to storage target
Cluster disk 4 from node has 4 usable path(s) to storage target
Cluster disk 4 is not managed by Microsoft MPIO from node
Cluster disk 4 is not managed by Microsoft MPIO from node (Validate Microsoft MPIO-based disks test)
SCSI page 83h VPD descriptors for cluster disk 4 and 5 match (Validate SCSI device Vital Product Data (VPD) test)
After the test the cluster shared volume was disappeared (the resource is online).
Cluster events that are logged
Cluster physical disk resource 'DATA_H' cannot be brought online because the associated disk could not be found. The expected signature of the disk was '{d6e6a1e0-161e-4fe2-9ca0-998dc89a6f25}'. If the disk was replaced or restored, in the Failover Cluster
Manager snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource. (Event 1034)
Cluster disk resource found the disk identifier to be stale. This may be expected if a restore operation was just performed or if this cluster uses replicated storage. The DiskSignature or DiskUniqueIds property for the disk resource has been corrected.
(Event 1568)
In disk management the disk is unallocated, unknown, Reserved. When the resource is on one node and i open disk management i get the warning that i have to initialize the disk. I did not do this yet.
Reading from other posts i think that the partition table got corrupted but i have no idea how to get it back. I found the following information but it's not enough for me to go ahead with: Using a tool like TestDisk to rewrite the partition table. then
rewriting the uniqueID to the disk brought everything back. But still no explaination as to why we had our "High Availability" Fail Over cluster down for nearly 2 Days. This happened to us twice within the past week.
Anybody that an idea how to solve this? I think my data is still intact.
Thanx for taking the time to read this.
DJITS.

Hi,
Error information you provided indicate disk connection failure issue, please confirm shared disk 4 is available:
To review hardware, connections, and configuration of a disk in cluster storage:
On each node in the cluster, open Disk Management (which is in Server Manager under Storage) and see if the disk is visible from one of the nodes (it should be visible from one node but not multiple nodes). If it is visible to
a node, continue to the next step. If it is not visible from any node, still in Disk Management on a node, right-click any volume, click Properties, and then click the Hardware tab. Click the listed disks or LUNs to see if all expected disks or LUNs appear.
If they do not, check cables, multi-path software, and the storage device, and correct any issues that are preventing one or more disks or LUNs from appearing. If this corrects the overall problem, skip all the remaining steps and procedures.
Review the event log for any events that indicate problems with the disk. If an event provides information about the disk signature expected by the cluster, save this information and skip to the last step in this procedure.
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and
then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that
you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Storage.
In the center pane, find the disk resource whose configuration you want to check, and record the exact name of the resource for use in a later step.
Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type:
CLUSTER RESOURCE DiskResourceName /PRIV >path\filename.TXT
For DiskResourceName, type the name of the disk resource, and for path\filename, type a path and a new filename of your choosing.
Locate the file you created in the previous step and open it. For a master boot record (MBR) disk, look in the file for DiskSignature. For a GPT disk, look in the file for DiskIdGuid.
Use the software for your storage to determine whether the signature of the disk matches either the DiskSignature or DiskIdGuid for the disk resource. If it does not, use the following procedure to repair the disk configuration.
For more information please refer to following MS articles:
Event ID 1034 — Cluster Storage Functionality
http://technet.microsoft.com/en-us/library/cc756229(v=WS.10).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Failover Cluster Quorum Disk is fallen off the shared volume

Hi, we had a Cluster that was holding 40+ VMs and was originally setup with the building 1GB Ethernet adapter, we yesterday installed Qlogic 10 GB NIC teaming for both of the nodes and reconfigured the network on both nodes. However now the Quorum disk
is not a part of Cluster Shared Volume How can I add that disk back to the shared volum please?

Hi Riaz,
Add a quorum disk is easy so please let us know if there is any specific error occurs during the steps provided in following thread:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/0566ede4-55bb-4694-a134-104fac2a7052/replace-quorum-disk-on-failover-cluster-on-different-lun?forum=winserverClustering
If you have any feedback on our support, please send to [email protected]

Color Lables on Shared Volumes

Hi Everyone,
I have just found out that when a user changes the label color for a folder on a shared volume the changes are not reflected real-time. That's to say If I change the colour of a folder called Templates to "Red" another user on another mac who also sees the shared volume will not see the label color change made to the Templates folder. He/She will need to disconnect the shared volume and reconnect in order to see the change. Has anyone out there seen this problem? It's not 100% essential but would be good if there was a solution of some sort.
Just to add did not have this problem on my old mac server which was running 10.2.x our new server is running 10.4.8.
Thanks,
Kwong.

Hi Russell, Sorry been away for a few days. The InDesign documents are already on a shared volume and it wouldn't be feasible to save anywhere else as there is a particular hierarchy on the server as to where files are stored, so that all documents are within their relevant job folders, with images, image bank images & graphics etc stored on other shares. However all acl's are the same for all users, so this shouldn't be an issue. I still can't work out whether this is an Apple OS or an Adobe problem.

Error -50 on a shared volume (SOLUTION)

Similar Messages

Maybe you are looking for