Unsolved
This post is more than 5 years old
12 Posts
0
2883
February 2nd, 2011 07:00
Volume (not disk) marked "Read Only" after installing KB2419640 and server reboot
Problem - After a reboot ot shutdown/restart volume is online, marked Read Only
Equipment - Dell 2650 server, fiber connected to CX4-120
SAN volume mounted to a 2008 (not R2) 32bit enterprise server had been working fine. After a reboot of the server, the disk was offline. Putting it back online, no problem, diskpart details for the Disk show "Read Only: No".
Got support from Dell and found the the Volume was listed as "Read Only: Yes". Simple fix, change the Volume to "Read Only: No" with Diskpart. Rebooted server to test, this time LUN/disk was online, but Volume marked as read only again. Changed to "Read Only: No" with Diskpart again.
4 hours later, the Volume is marked as "read only" again. No changes made by us, nothing in the Windows logs. The disk is an Dell/Emc SAN LUN, fiber connected, exclusive use to this machine. Have another LUN, almost the same size attached the same way to this machine, no problems with that. No issues with SAN or LUN as far as we can tell from logs and testing.
Now it has been working fine for 4 days.
Appreciate any thoughts or places to look.
Back to original problem. I understand the OS is likely the culprit with the Read Only flag. We did some testing last night, with a few reboots, and one thing is now consistent - when the server comes up from either restart or shutdown/start, the Disk is Offline.
Bringing the Disk online forces us to change the Read Only flag, as well as redo the Share permissions.
Originally, after changing the Read Only, and restarting, the Disk came back as Online. Now it is consistently Offline when bringing up the box.
I would suspect FCard bios, etc, but again, another Disk/LUN attached works with no errors.
Again, any thoughts of where to look would be appreciated. I can't visualize either Microsoft or EMC doing anything to the Disk at restart/shutdown.
Message was edited by: kelleg
kelleg
6 Operator
•
4.5K Posts
0
February 2nd, 2011 11:00
Hate to say it, but this sounds like a Microsoft issue. Have you contact MS? There is no way on the array that you can mark a LUN as "Read-Only". A host can put a LUN into SCSI Reservation mode and that would lock the LUN to other hosts - clusters do this.
glen
Sam Claret
86 Posts
0
February 2nd, 2011 23:00
Hello
Typically a VSS operation will mark the Read Only: Yes flag.
The place to investigate is the application event log to see if there are any VSS operations outstanding(
).
There are a large variety of software that make use of VSS including the Microsoft Volume Shadow Copy process.
Many backup products make use of the Volume Shadow Copy process.
I hope this gives you a direction to start investigating.
Thankyou
Sam Claret EMC TSE3
gritz1
12 Posts
0
February 3rd, 2011 04:00
Thank you - I agree - please see aditional info posted.Before I go to MS I wanted to start with the EMC forum to make suer I was not missing something obvious.
gritz1
12 Posts
0
February 3rd, 2011 04:00
Thank you, we have been monitoring the logs religously, and there does not seem to be anything relevant. This may be a case where we are missing some innocous message, so I sent the loges to a colleague after our testing last night.
gritz1
12 Posts
0
February 3rd, 2011 09:00
Update -
Need to try a few more reboots, BUT...
Since this just started, we decided to look at the other variables, specifically what had been installed on that box in the past two weeks.
One item - Security Patch KB2419640 - back story below.
Different server at a clients location: This is a new SBS 2008 (not R2) 64BIT OS, running on a new Dell box. It has been humming along with no issues since it's startup in July. On 1/18/2011, KB2419640 was installed automatically by WSUS push. Within three hours of restart (5 AM), the server was unresponsive, email could not be received, remote sessions could not connect, etc, etc. Everything that could go wrong, did. Shutting down and rebooting the server took 45 minutes to get to a login screen! I went down the same troubleshooting path - what had been installed? KB2419640. I restarted in safe mode, shut down all services, rebooted, and uninstalled the patch. Rebooted again, re-enabled all services, and rebooted one more time. Absolutely no issues with the server, came back brilliantly. Opened a case with MS to see what they would say, and after running a ton of diagnostics they wanted me to reinstall the patch from a separate install since I already uninstalled (have not been that brave yet).
Back to current issue; found that KB2419640 had been installed on the server. This was the only change that had occurred to the box, and we found the online drive dropping after it was installed.
I uninstalled the Patch, rebooted the server - no issues at all; Disk, Volume on line, reattached, all shares in place. Obviously we have to do a few more reboots to verify this was the issue, but since I now have two points of reference I feel confident.
This patch specifically refers to the Microsoft Data Access Components, contains an ODBC dll and a few ADO dlls. I do not have a clue why/how it affected Exchange, RPC, and so many other things on the SBS server, and the Disk/LUN on our Fileserver. Microsoft does not go into any details on what the patch changes or addresses. A simple uninstall/reinstall may be the answer. There are quite a few hits on KB2419640 failing to install or causing startup issues, but most are tied to Windows 7.
kelleg
6 Operator
•
4.5K Posts
0
February 3rd, 2011 12:00
Thanks very much for providing the level pf detail - this will be very helpful to others that get this patch installed automatically. Please mark the question as Answered when you finish with your testing. This was an interesting problem.
Was this a security patch? Marked to disks Read-Only to protect the data
glen