Hi All

I have a 475 with 2 x 500gig disks. Twice now I have had an error on the console that I have an error in the secondary drive.

Each time it recommends that I "repair" the drive from the console with the repair utility, and this has worked so far, but takes ages1

Logging onto the server directly, I can see not problems and the drive itself looks healthy in Disk Management.

I have read the article on data corruption on WHS by Microsoft, and I don't know if this if what I'm seeing, or if its a disk failure in progress. I never edit files directly from the MSS, so It should not be the Microsoft issue.

The MSS is only two months old.

Any thoughts?
Dave

Hi Dave,

This doesn't seem like the data corruption bug, WHS does not detect that itself to my knowledge. The error you're seeing is usually due to bad indexes discovered by chkdsk routinely run by WHS on the disks. I've seen it once or twice, but not in a while on my system.

I wouldn't worry about 2 times in 2 months, but if you see it more frequently then you might have a concern to take up with HP support.

Hope this helps,
Alex

Hmmm

It seems strange that this is common. It has happened again today.

I think it must be a HHD fault.

I'm also very surprised, that a device which is supost to be an appliance for the home should need so much intervention.

If it need this level is easy fix, it should do it itself!! Also why does the backup service not start itself up again after? It needs a reboot to get it going again.

I think you are having an unusual experience, I hardly have to intervene with my server at home at all. Is it possible that you are shutting down the server via a hard power-off (holding power button down more than 4 seconds), or power outtages? This can cause disk inconsistencies...

I am getting the following error message

"Volume with name SYS is failing. Please try to run Repair to fix errors for disk ST350063 0AS SCSI Disk Device."

This is coming via Remote Notification. The WHS Console then informs me to fix the drive, etc. A check disk is run and after a while all seems ok. This has happened twice (Sat and Mon).

My fear is that I have a failing drive. But, once the chkdsk runs, all seems fine. Both times.

I have the 1TB version (2 x 500gb). I am adding 2x750gb this weekend to bring the server up to 2.5tb. Should I rebuild and use the 750gb's as the primary drives? Or, am I over-reacting just yet.

Any suggestions?

I would rebuild and use the 750 as the primary drive anyway -- that is the preferred configuration!

I would also run a detailed test of each drive AND the Storage Diagnostics in the WHS Toolkit before loading up any data...

Those errors typically mean that the regularly scheduled chkdsk run by WHS found some issue, often an index inconsistency that is easily repaired. This can be exascerbated by improperly shutting down the server.

I started this thread and it seems I'm not the only one having this issue. I'm on my forth error now, but after a repair and re-start ( to get backup working again) all seems OK till the next time.

I'm NOT happy about this! This box is supposed to look after itself and be an appliance for the home, not a server requiring constant admin attention and intervention.

Is this an issue of the HP MediaSmart or any WHS?

if you have had even a single error please respond, so we cant see if there is a patten
Dave

This is a WHS process, and I agree it's unfortunate that it doesn't try to repair this itself before notifying the user.

I've had my 1tb system for 1 week and just received that same error. I've never shut down the server nor have I had any power failures. The repair is running now -- for the past 15 minutes or so.

I have had mine for a bit now and it has been shut down numerous times, I've tinker with it, and I've used RDC. Generally I've done everything you are not suppose to do to see how I can break it. I have not seen that error. I have NEVER had my EX475 offer to repair anything, and I'm inclined to believe it is not normal. You **might** consider installing Client ID it has the ability to read the SMART STATUS of your drives, and check the smart status the next time you get that message. My assumption is if anyone should be seeing that message it would be me.

Have either of you done the memory upgrade? My guess is both of you haven't.

Nope -- no memory upgrade -- probably not until I'm beyond HP's warranty. I have used Remote Desktop to connect and poke around a bit but no data manipulation/software install from Remote Desktop. I have done a couple of add-ins that might still be "bleeding edge." Tivo Publisher 1.1 has crashed my Tivo a few times and caused my server Console to hang once. The only other add-ins are ASoft's AutoExit which seems to be behaving and the Toolkit.

The repair finished -- requiring a reboot at the end. I'm guessing it took about 30-45 minutes to complete. I'm not used to being at so "high" a level that I cannot see the extent of the corruption or the repairs being made by chkdsk. I was surprised it did not give me a report of the error recovery.

You can check the logfiles on the server to find out some more detail. In the Toolkit, choose the Support Tab, Logs, Copy.

You can now access from \\server\software\LogsCopy

Thanks -- I was in the toolkit checking the Event Logs for any telling details of a problem but the other logs give me enough detail to keep me busy for quite awhile.

I did notice something in the system event log that seemed unusual "The flush and hold operation for volume C: was aborted because of low available system memory." The source was VolSnap. This event occurred around the time of the notification of the failing disk.

I wonder if something is leaking memory. I certainly haven't been pushing the system.

I've only ever seen this on "real" Windows 2003 servers, and the cause has always been low memory so your theory on a leak might hold true, or it might just mean the server really does need more ram.

I havent upgraded mine yet, but I do "experiment" a lot with it, and have a fair few addins. I also stream music almost constantly from it, and quite frequently video. The only time I've seen a disk issue was when I played a little too much with the Perfect Disk config. I just ran a repair and its been fine ever since, and I've just left Perfect Disk to do it's thing.