• 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.

WHS freezing

R

Ronco

[H]ard|Gawd
2FA
Joined
Oct 6, 2005
Messages
1,308
So I've started getting a lot of freezes on the WHS I use most heavily - an HP X510 runing WHS V1. Yesterday, it froze again so I switched it off and turned it back on - and it will now freeze about 10 mins after startup. I get no disk-related errors, in fact no alerts before it stops responding via the console. It's also unresponsive via straight-up RDP.

Thinking it might be a unit issue, I swapped over all the disks over to a spare X510 - and exactly the same problem. So it appears to be a disk, or software, issue.

What would the hive suggest I do?
 
Oh yes, when WHS freezes I ought to point out that I have the 'Windows 7 freezing after logon with blank screen and pointer' on the desktops connected to it until I turn the WHS off.
 
Did you check your event log and WHS logs? Those usually tell you something.
 
That's the next step - it's just a matte of getting into the WS2003 RDP session before it freezes. It also makes the connected desktops freeze as well after the WHS itself goes down until I turn the WHS off - I'll have to time it right and do it from a machine which doesn't have the WHS connector installed.

I'm going to do that tomorrow but any tips in the meanwhile appreciated.
 
Can't you check logs from the previous crash after rebooting?
 
OK, so the 4 events in the Application log just before it grinds to a halt are all 9000's generated on CqvSvc.exe.

The RDP session that I kept up and running until it froze threw up a Search Indexer error before freezing.
 
Steps I've taken since then:

Removed and reinstalled Search.
Still freezes about 10-15 minutes after boot. Now no illuminating error messages at all.
Restored WHS (first option - i.e. keep data). Same problem cropped up while applying the first service pack, i.e. freeze. Rebooted a couple of times to complete the setup.
Still does exactly the same thing.

It can't be a unit issue since as I mentioned before, I own actually a small huddle of X510's - although now I really only use this one as the main one - and I tried swapping the discs over, which makes no difference to the issue, i.e. it still freezes while the disks are in a different machine.

Failing SYS HDD? I took the drive out, CHKDSKed SYS on a W7 machine and that found no issues.

I'm completely out of options. Any other recourse before I elect to copy over all data and crank up another X510 with new disks?
 
Check CPU / memory stability? Long shot but it's possible.
 
As I said, it's not a unit issue as I've tried plugging in the same set of disks to other machines and there's no change in the lack of stability.

I'm going to try a new SYS disk.
 
Failing SYS HDD?
Click to expand...

CrystalDiskInfo would have told you if any disk was likely failing.

http://crystalmark.info/software/CrystalDiskInfo/index-e.html

CHKDSKed SYS on a W7 machine and that found no issues.
Click to expand...

Chkdsk is more about checking for filesystem corruption. Its not that good at discovering a disk going bad.

I'm completely out of options. Any other recourse before I elect to copy over all data and crank up another X510 with new disks?
Click to expand...

Have you checked for viruses / malware? Although I suspect that to be hard to check if you only get 10 minutes.
 
Last edited:
Viruses - no chance. System never gets exposed to the nets and I'd know if there are any share-propagating viruses.

Crystaldiskinfo does throw up some minor issues. Perhaps they're not so minor as far as function of WHS goes. Either way I'm going to try and clone the SYS disk - which is not a simple matter since you need to clone the disk ID as well - and see how far I get. If no luck - well, I guess this is the ideal time to look at an upgrade.
 
disk cloned, problem solved (I think - so far). So I guess a bad disk. Wish they'd make it more obvious, drive shows up 'Healthy'.
 
Last edited:
You must log in or register to reply here.
Back
Top