Jump to content
Division-M Community
Sign in to follow this  
philzgr8

BSOD after installing 1.8.1.0 on WHS 2011

Recommended Posts

After I installed 1.8.1.0 I immediately had issues whereby my server went into a cycle of BSOD's and spontaneous reboots. Because of limited time I immediately restored the server system image from backup and it is now running again. My suspicion from having read some of the event logs is that there was corruption on one of the pool member drives or on the system drive itself and so having run a chkdsk on the system drive I am wondering what limitations there are to running Windows native disk tools against member drives and/or the pool drive itself. Are there any specific procedures or risks given that windows will take the drive off line for this process? Note that the disk check within the Drivebender dashboard reports that it cannot run on 2 of my 3 member drives and this has been the case since I first installed. Any advice would be appreciated.

Share this post


Link to post
Share on other sites

You should be able to assign a drive letter to any member drive in the pool to run chkdsk. You probably wouldn't want any pool activity while the chkdsk runs. When done you should probably take the drive letter away from the drive so that no native disk activity happens.

Share this post


Link to post
Share on other sites

You should be able to assign a drive letter to any member drive in the pool to run chkdsk. You probably wouldn't want any pool activity while the chkdsk runs. When done you should probably take the drive letter away from the drive so that no native disk activity happens.

Thanks for that. What about the pool drive itself? If I go to the drives section of the dashboard and look at the properties of the pool drive I can select check and repair. I have not actually run repair but if I run check only I get the following:

 

The first NTFS boot sector is unreadable or corrupt.

Reading second NTFS boot sector instead.

All NTFS boot sectors are unreadable or corrupt.  Cannot continue.

 

Is that an indication that there is a problem or that this operation is not supported on a pool drive.

 

P.S. If this isn't supported, what's the best way to check that everything is hunky dory. I'm pretty sure something is wrong but not sure how to troubleshoot it.

Share this post


Link to post
Share on other sites

You cannot use tools like chkdsk on the pool drive. A pool drive is like a "virtual image" of one or more physical drives. Tools like chkdsk work against a physical drive.

I suspected as much. Any comment on the best way to assess the health of the system? I'm concerned about installing 1.8.1.0 until I have a better understanding of what caused the problem in the first place. Should I be running the DB repair pool process? Would it make sense to just move everything off the pool and delete and recreate it? Would it be safer to uninstall 1.8.0.0 and then install 1.8.1.0?

Share this post


Link to post
Share on other sites

Download the trial version of HD Sentinel and it will show you the SMART status of your drives.

 

You can do this within DB, but if you're having problems, the stand-alone install might assist.

 

At least you can determine if you have a dodgy drive or not.

 

 

Did you raise a Support Ticket ??

 

 

 

Share this post


Link to post
Share on other sites

Another question along with the CBers question on if you've submitted a ticket...

 

What version were you running prior to the 1810 install? You say that you restored the system image and all was well except you couldn't get the disk tools to run using the DB facility to start them. What is the DB version you're running now that you say is working?

 

I also had a issue with 1810 on my WHS2011 box and just went back to 1720 which was my last good version. After reinstalling 1720 all was well with my server so I didn't try to run any tools against the pool or its drives since it appeared that 1810 itself was the problem. And yes, I do have a ticket submitted and I'm waiting for feedback.

Share this post


Link to post
Share on other sites

Another question along with the CBers question on if you've submitted a ticket...

 

What version were you running prior to the 1810 install? You say that you restored the system image and all was well except you couldn't get the disk tools to run using the DB facility to start them. What is the DB version you're running now that you say is working?

 

I also had a issue with 1810 on my WHS2011 box and just went back to 1720 which was my last good version. After reinstalling 1720 all was well with my server so I didn't try to run any tools against the pool or its drives since it appeared that 1810 itself was the problem. And yes, I do have a ticket submitted and I'm waiting for feedback.

Thanks for that. I have been running 1800 and that's what I rolled back to. In fairness, the DB disk check has never worked on the drive in question but no other tool reports any error with that particular drive.

 

I will probably log a ticket when/if I feel ready to spend the time to troubleshoot but with the problems I've had with DB already and the lack of support for shadow copies I'm beginning to think I'll either wait until VSS support is added or abandon DB altogether. Right now all it appears to be doing for me is adding complexity to my server that I don't need.

Share this post


Link to post
Share on other sites

Subsequent to my last post I have made another attempt to install 1810 with similar results and I have now logged a support ticket. The contents of my ticket are as follows:

A couple of weeks ago I upgraded my WHS2011 from version 1800 to version 1810 by simply running the installer. All seemed to go well until the server needed to reboot to complete the installation. Once the server rebooted, I received a BSOD and the machine went into a cycle of reboot, BSOD, reboot, BSOD etc. As I was not prepared to be without my home server for any length of time I decided to restore a system image backup which quickly resolved the problem.

 

This morning I decided to attempt the upgrade once again since the Drive Bender Service keeps sending me notifications and I have concerns that future upgrades may be reliant on this version being in place. This time I uninstalled version 1800 and rebooted before installing 1810. This time the server fully booted up but simple actions such as opening the event viewer resulted in a BSOD and spontaneous reboot. Unfortunately I had little opportunity to read the contents of the blue screen so I cannot provide much info. After a couple of cycles I decided to uninstall 1810 and revert to 1800 but found that this did not resolve the issue so once again I restored from a system image and all is now good again under 1800. I did find after restoring that running chkdsk against the system disk found errors which were corrected but I suspect that these came about as a result of the spontaneous reboots. Obviously I cannot be 100% confident of this fact.

 

Having read the forums, I have seen at least one other user has reported this issue and I was wondering if there has been any research done to establish a cause and solution. Any information you can give me would be appreciated. I am happy to provide whatever information about my system that you deem relevant if you feel it will help.

 

On a related note, I have enquired on a couple of occasions as to the time frame for introducing VSS support in Drive Bender and I am wondering if there is any update on that. Any guidance on this would be appreciated.

I should say that subsequent to logging that ticket I found a lot of problems including the fact that when shutting down there was still a BSOD as well as countless errors in the windows logs and corruption on the system drive. The errors suggested bad video drivers and/or bad ram and I have painstakingly gone through the process troubleshooting each error. After reverting to a generic video driver and running chkdsk in the system drive I still had problems so I then uninstalled a couple of apps from the server including Virtual CloneDrive and IsoMount since errors in the even log were suggesting some issue with virtual drives. I also had an issue with authentication by my Windows Media Centre which was resolved by removing and recreating some share permissions on WHS and disabling and re-enabling media streaming. The other thing that I changed was to turn offline files on one of my machines which may or may not have been causing trouble. Unfortunately I can't say which of the actions did the trick but 1800 now seems to be happy and I am no longer having BSOD's and the event log is relatively free of errors.

 

Unfortunately all of this brings me no closer to having the confidence to reinstall 1810 but I have posted this info here for the benefit of others and in case anyone can see something in what I have posted that may help. Any comments are welcome.

Share this post


Link to post
Share on other sites

Did you try v1.8.6.0,which was released today?

Not yet but I have downloaded it. This morning I found some entries in my event log that are quite worrying. The event ID is 134 which is an NTFS error which can indicate disk failure. Oddly this occurred at almost the exact time that my backup was due to commence. I ran Western Digital Data Lifeguard over the drive which happens to be my system drive and it reports no issues. I also noticed some VSS issues relating to the underlying drives which form a part of the pool around the same time.

 

Right now I am running chkdsk against the system drive with the /F switch to make sure that any bad sectors are found but I'm suspecting that the issues are not really related to hard disk failure. Once I've done that I might give 1860 a try but it's difficult when I'm running remotely over TeamViewer because I can't see what's happening during a reboot. It might be better for me to try it when I get home tonight.

Share this post


Link to post
Share on other sites

Happily, after some analysis of crash dump files I seem to have narrowed down my BSOD issues to webcam drivers from Logitech and these have now been uninstalled. The chkdsk didn't find any issues so all seems well now so I may have a go at 1860 and report back.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...