SYS volume is failing
- 0
It's now almost every day that the yellow network health warning pops up, it reports that the SYS volume is failing and needs to be repaired. After running the repair task (which does a chkdsk scan and rebuilds the server storage index) I am fine for a day or two, until I get the next warning...
How can I find out what is causing it ? I looked through the log files, and in qsm.log I find these log lines repeatedly (don't know if they are causing the warnings though):
Monitor::CheckDisk FmIfsFinished MSG:CHKDSK is verifying indexes (stage 2 of 3)..
ERROR: could not get free space for volume c482adad-d499-4238-8e74-2b3428c09e12 (0x80070003)
ERROR: could not get free space for volume 466d0d60-99d5-4afa-8bf4-7c6706867609 (0x80070003)
I do not think that there is anything physically wrong with the drive, I ran a drive check just recently and everything seemed fine. It would be great if anyone could help me with this...
Thanks,
Dirk
Answers
- 0Dirk, in every case I've seen, when you get into a repeated cycle of chkdsk/more errors/chkdsk again/more errors/lather/rinse/repeat, you have a hard drive (or controller, but more likely the drive) that's about to fail. So planning now to replace it is the right thing to do.
- 0Also, if it's plugged into a faulty UPS it can cause weird issues as well.
- 0I've been experiencing the same behavior where every day or so, WHS will report that the SYS drive is failing. Running repair as well as CHKDSK seemed to temporarily resolve the problem but it always returned.
In any event, the problem was that my primary hard drive was overheating. I didn't discover this until running some extended drive diagnostics which indicated that the drive was reporting a SMART heat warning. I installed a new 90mm fan in front of my drives and they are running at a steady 38 degrees Celsius and the "drive failing" message has yet to reappear.
Hopefully this will help others who are at their wits end.
Cheers,
Ted - 0
We aren't ignoring the problem, we are treating this issue with the appropriate priority. And this is NOT connected to the KB946676 bug. Answers do not come overnight or after a few days when I have to go work with the PMs and Developers, go to meetings to discuss the issue, and then give them time to analyse and try to figure out a solution.
We are changing the way we collect logs in a forthcoming update and looking at a solution to deal with False Positives and how often CHKDSK runs and how home server will try to inform the user when it thinks something is going wrong with a disk.
Quite a few of these SYS... messages have been reporting problems with hard drives, while some have not.
- 0
T. Headrick wrote: We aren't ignoring the problem, we are treating this issue with the appropriate priority. And this is NOT connected to the KB946676 bug. Answers do not come overnight or after a few days when I have to go work with the PMs and Developers, go to meetings to discuss the issue, and then give them time to analyse and try to figure out a solution.
We are changing the way we collect logs in a forthcoming update and looking at a solution to deal with False Positives and how often CHKDSK runs and how home server will try to inform the user when it thinks something is going wrong with a disk.
Quite a few of these SYS... messages have been reporting problems with hard drives, while some have not.
Bump back to the answer I gave over a month ago ... The forthcoming update is "Power Pack 1"
It helps to read the answered posts in the thread.
All Replies
- 0Try downloading UBCD and using it to test your hard drive. It sounds as if you have a malfunctioning drive, but not necessarily bad sectors. The problem could be in the firmware or SMART section of the drive. See what UBCD provides for you.
- 0
mtgarden wrote: Try downloading UBCD and using it to test your hard drive. It sounds as if you have a malfunctioning drive, but not necessarily bad sectors. The problem could be in the firmware or SMART section of the drive. See what UBCD provides for you.
Thanks for pointing me to UBCD, this is really a neat tool. I ran the Seatools on the drive, but it reported no errors. It's now every day that the server status changes to yellow because of the failing SYS volume. Interestingly, after I run "Repair" from the WHS console, it turns green again - but when I run chkdsk afterwards again, it still reports errors with the filesystem. It suggests to run it with /f /r, and after doing this (it gets scheduled for the next boot since it cant lock the drive), and running chkdks again, it still reports the same error. This makes me believe that it might not actually be a physical problem, but something hosed in the WHS internal structures.
Anyway, to rule out a physical defect, I ordered a new disk as a replacement. Since I don't know of any way to clone the C: and D: drive to avoid reinstalling everything right now, I probably wait until RC1 comes out where most likely I will have to do a new install anyway.
Thanks for the feedback,
Dirk - 0
Hi Dirk,
I have had the same issue, I initially thought it was the hard drive so replaced it with a new 320G Seagate PATA Drive. I re-installed WHS and within a week experienced the same issue. I then assumed it must be the hard drive controller, so I swapped the drives around so that the system drive was on the second ATA controller. Again the problem went away to then come back. I then decided it must be the M/board (it was an old A7N8X running a Athlon 2400XP).
I went out and bought a new M/B, CPU & RAM (Core 2 Duo). Re-installed RTM version of WHS and again one week later have had the same issue. I have changed the drives around and the problem seems to re-occur. When I 'repair' the drive the issue goes away for a few days.
It is interesting to note that this issue only warrants a yellow warning and is not rated as severe. I would be keen to better understand what determines the 'SYS volume failing' error.
Cheers
Paul. - 0
Evening,
I don't know if it's the same in your case, but I had problems similar to this, which turned out to be a failing power supply.
HTH,
Colin
- 0
I've been seeing the same problem for the last 2-3 weeks. sys volume goes yellow every couple days, run repair and all's well for a while. I've downloaded the ultimate boot cd and run the vendor specific tools on the drive (a Seagate 300 gb PATA) and not found any problems. No SMART errors reported at all. I guess it could be a power supply that's starting to go but I would think one of the five other internal drives would be having issues as well (not to mention the mobo, memory, cpu).
Is there a WHS specific log file we should be checking to determine what is actually causing the drive to be flagged as failing? I'd actually put this on the back burner since I was planning on ordering a replacement hard drive.
- 0
I contemplated whether it was the power supply, but it is a high end unit running 5 internal hard drives, plus M/B, Vid Card,... I would have thought other components would have had issues if the PS was failing.
I can not see how this could be it, yet I must admit it is the only common factor through all the changes I have made. I am interested to see if this is a common fault that people have seen?
Cheers
- 0
Is there any information logged about what is failing? My SYS drive is listed in the WHS console as Unhealthy (was healthy last night before I went to bed) and there's nothing in any of the event logs to indicate any errors. There may be some buried in the WHS logs (C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs) but I'm not finding anything obvious.
What symptoms make a drive appear "Unhealthy" to WHS?
tomf
- 0
Strange as it sounds, it seems that the UPS may have been my issue. I was running about 70% capacity on a 350 VA UPS so I didn't think that would be an issue but it must have been spiking higher or mis-reporting capacity. I swapped in an 800 VA UPS and the SYS volume failures have dissappeared.
Thanks Joel!
I'd still like to see some detail on what WHS is using to determine that the drive is failing since there is nothing in the event log and nothing obvious in the WHS logs.
- 0UPS only have a 2 year life or sometimes less. Whether they appear to work or not, when they go bad they cause major problems. :-) Glad it helped!
- 0
I also have a failing SYS drive. I am going to try the UBCD to check the drive integrity, but as the system case on my WHS has been very warm to the touch lately I suspect the drive may be overheating.
Is there a method in place to swap out the sys drive? the storage pool on all other installed drives needs to be seperated because they are linked by default) can I able to at least syphon off any user data stored on it, like with the other drives "remove" option?
Having to rebuild WHS from scratch every time including a users sys drive needed replacing would realy suck the big one.
- 0
Joel Burt wrote: UPS only have a 2 year life or sometimes less. Whether they appear to work or not, when they go bad they cause major problems. :-) Glad it helped! I've never had one that lasted 2 years. The batteries always die on me and they cost more to replace than the ups does when you add shipping.
- 0I've been experiencing the same behavior where every day or so, WHS will report that the SYS drive is failing. Running repair as well as CHKDSK seemed to temporarily resolve the problem but it always returned.
I´ve change computer and the same behavior where every day or so comes back.
Have anyone get this right?
///Bizit - 0
Jeshimon wrote: Joel Burt wrote: UPS only have a 2 year life or sometimes less. Whether they appear to work or not, when they go bad they cause major problems. :-) Glad it helped! I've never had one that lasted 2 years. The batteries always die on me and they cost more to replace than the ups does when you add shipping.
I too had noticed that my home UPS units (typical small, 350 - 500 consumer-oriented APC units) were only lasting 1-2 years; however, the larger (1200 - 2000) APC UPSs I purchased for work were at 7+ years and still ticking. So I bought 2 APC 1200 UPSs for the home and they have been running for over 4 years now, and the work UPSs are still going as well.
- 0
My $0.02
I was getting regular error messages about my sys drive as well. I plugged the PC into a non-battery backed-up outlet and pulled out the UPS' USB cable, and the problem disappeared. I am now testing to see if the UPS was simply overloaded, or if the battery is failing, or if the UPS iself is failing.
- 0
I am currently experiencing the same. My UPC is not even a month old.
The SYS harddrive has been purchased specially for the server about 4 months ago. All SMART diagnostics are green, no problems reported...
I never had an UPC before so I am majorly confused now how this can happen at all...
Has it "oficially" been acknowledged that the UPC is the problem?
What exactly is happening and why is only the SYS drive affected?
Is "it" concerning the complete drive including the DATA partition?
Can I ignore the issue as long as the independantly read out SMART values are OK? - 0
I hade the same thing happening to me yesterday after installing the latest AVAST antivirus.
Never had this problem before, so I removed AVAST and the problem went away.
- 0
So did anybody find out yet what exactly is urging WHS to describe a drive as imminently failing? - 0Something about the UPS service, if I am diagnosing my problem right.
jdifool wrote:
So did anybody find out yet what exactly is urging WHS to describe a drive as imminently failing?I said above that moving my WHS off the battery backup onto a normal outlet solved my problem. It ran this way for about 2 weeks without seeing the error message pop up again. I thought it was a dying UPS or something.
So I bought a new APC 850W (overkill) UPS and hooked it up. Within two days I saw the same message.
- 0Nope. I've seen this error, I wont have a UPS any more. I feel strongly that they are a waste of energy, time and money.
- 0I have a brand new HP MediaSmart server and this error appeared right after running an automatic update. I ran the repair utility and it found nothing wrong. I ran chkdsk at the server level and it found nothing wrong. Now the drive is reporting that it is healthy. I am *not* running a UPS.
- 0
Jeshimon wrote: Joel Burt wrote: UPS only have a 2 year life or sometimes less. Whether they appear to work or not, when they go bad they cause major problems. :-) Glad it helped! I've never had one that lasted 2 years. The batteries always die on me and they cost more to replace than the ups does when you add shipping.
My suggestion would be 'you get what you pay for'. Cheap UPSes are generally a waste of time, IMO.
I've also never seen a UPS (worth owning) that's cheaper to replace than putting in new batteries.
As an example, I run an APC SmartUPS (700VA) for my PC, and a Liebert UPStation GTX (700VA) for my WHS. A set of batteries for either of these are about $40 at my local electronics shop. The APC is about $500 to replace, and the Liebert is more like $800-$900 (we get stung on pricing of these locally). Both of these devices are fantastic - particularly the Liebert which is a true online model. I picked them both up second-hand for about what you'd pay for a 'cheap' UPS - the Liebert is probably 7 years old or more already.
Seriously - if you want a UPS, get a real one. Buying a cheap UPS is akin to buy a $50 power supply, or using the one that 'came with the case'.
- 0
Tenoq wrote: Jeshimon wrote: Joel Burt wrote: UPS only have a 2 year life or sometimes less. Whether they appear to work or not, when they go bad they cause major problems. :-) Glad it helped! I've never had one that lasted 2 years. The batteries always die on me and they cost more to replace than the ups does when you add shipping.
My suggestion would be 'you get what you pay for'. Cheap UPSes are generally a waste of time, IMO.
I've also never seen a UPS (worth owning) that's cheaper to replace than putting in new batteries.
(...)
Seriously - if you want a UPS, get a real one. Buying a cheap UPS is akin to buy a $50 power supply, or using the one that 'came with the case'.
Well, this is all very nice to learn but I still just can not understand how an UPC however cheap it might have been is triggering WHS to claim that a certain harddrive will fail...
Any idea about this? - 0
My last one was an APC Smart ups 1000. It was far from cheep. That was the LAST one I'll ever have. From my experience all a UPS in the home does is WASTE energy for a couple of years and then fail. I may have gotten through a few power outages with them, but the benefits are not worth the cost to me, especially when you consider the life expectancy.
- 0
Tenoq wrote: The APC is about $500 to replace, and the Liebert is more like $800-$900 (we get stung on pricing of these locally).
No one locally has the batteries.
UPS refurbed with new batts:
http://www.upsforless.com/index.asp?PageAction=VIEWPROD&ProdID=35 - 0
So did anybody find out yet what exactly is urging WHS to describe a drive as imminently failing?
I'm curious about that too. What is WHS actually saying is wrong when this error is reported? There's nothing that shows up in any of the event logs, so is this an error that should be getting raised and logged by the OS but isn't in most cases?
I'd be interested in knowing if your failing UPS's are Auto Voltage Regulating too. - 0Where do you live? I live in a country town in a backwater country (Australia) and I can still easily get batteries for either UPS by driving about 20 minutes to the nearest Jaycar. As I said, they cost a pittance. They're obviously not 'APC-approved' ones, but a 12V lead-acid battery is a 12V lead-acid battery. It's not car or bike battery that might need so much CCA to start the thing - they just need to be an appropriate voltage and Ah rating.
As for why a faulty UPS can cause HDDs issues - that's an easy one to answer. Bad power can cause pretty much any hardware component in a PC to fail: but the two most likely to die are RAM and HDDs. If a HDD is receiving intermittent or insufficient power then it's bound to have trouble storing data properly, and I'd be surprised if it wasn't permanently electrically damaged. The reason I know all this is because I work in a computer shop in an area where power is atrocious. Every storm half a dozen boxes come in with blown PSUs and/or HDD corruption. Some of our customers walk away with a UPS; others come back in 6 months with the same problem and then get a UPS. - 0
Tenoq wrote: Where do you live? I live in a country town in a backwater country (Australia) and I can still easily get batteries for either UPS by driving about 20 minutes to the nearest Jaycar. As I said, they cost a pittance. They're obviously not 'APC-approved' ones, but a 12V lead-acid battery is a 12V lead-acid battery. It's not car or bike battery that might need so much CCA to start the thing - they just need to be an appropriate voltage and Ah rating. I am stranded in Iowa. There is also from factor and terminal connections. A battery for a John Deere combine would be easy to come by. Small form factor sealed lead acid, not so much. There is lot of lithium and ammonia though. I had to wait almost a week for a fan belt for my Dakota pickup, and that was from the Dodge dealer when it was still very new.
- 0Maybe try accessing the WHS via remote desktop and changing the power options in the control panel so that the hard disk spins down afte 5 minutes. That would reduce any heat issues you may be having.
- 0
A bunch of folks on the thread have asked 'How do I see what's going on when .... ?'
Um, I don't know, but the 1st place I'd look to see details behind an uninformative warning message is the event log.
In case anyone is really low on the learning curve, do the following fom a PC on your home network:
Click Start -> Run and type "MSTSC"
enter the name of your WHS ("Server" by default)
username is administrator, password is your WHS password
you'll see the desktop of the WHS
Click Start -> All Programs -> Adminstrative Tools -> Event View
Poke around. There is a separate WHS log, as well as the system logs. If any of the guys getting odd error reports via the console learn anything from the logs, please post it here!
Thanks,
-andy
- 0
Andy,
don't forget the multitude of logs in:
C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs
Those logs do show in the event viewer.
Jim
- 0I've tried all these things on my HP MediaSmart but still get the "Sys drive is failing message"--with or without power supply, with or without setting the drives to spin down, etc. However HP will not replace the unit because they say this is a "false" message. It's not very comforting, though. If the SYS drive does go, does that mean I'll lose all the data stored on the three other drives or just the 20 gig partition for the SYS drive?
- 0I have long said that this was an 'erroneous error message'. I guess HP agrees. I doubt you have a hardware problem, but if the drive itself was really failing you would see other failure indications. If it really fails and you only have the one drive then all is indeed lost. After 100+ days of 24/7 operation I have come to trust mine. I run repair when told and go about my business.
- 0
Was also having same problem. I formatted and reinstalled the software on the server and havent had any problems since
- 0I'm not in a position to even try a full format. If it is happening on HP servers I'm not sure even that will make it go away forever. I've had as long as 3 weeks without it showing up, but it still came back.
- 0
If it really fails and you only have the one drive then all is indeed lost.
I have four drives in the unit altogether. I just want to make sure I understand--if the SYS drive really does go bad, will the data on the other three drives get wiped out if I put in a new hard drive and reinstall WHS or will that data still be accessible?
I'm mostly thinking about the security on the folders in which that data is stored, i.e. if the SYS drive goes I assume the security is lost even if the files are there?
I'm not sure how this works -- I bought this server and the extra drives as storage space for about 1 terrabyte of stuff and currently am not feeling too comfortable storing data on this drive due to the "SYS Drive is Failing" messages. Thanks! - 0
Boaster01 wrote: If it really fails and you only have the one drive then all is indeed lost.
I have four drives in the unit altogether. I just want to make sure I understand--if the SYS drive really does go bad, will the data on the other three drives get wiped out if I put in a new hard drive and reinstall WHS or will that data still be accessible?
I'm mostly thinking about the security on the folders in which that data is stored, i.e. if the SYS drive goes I assume the security is lost even if the files are there?
I'm not sure how this works -- I bought this server and the extra drives as storage space for about 1 terrabyte of stuff and currently am not feeling too comfortable storing data on this drive due to the "SYS Drive is Failing" messages. Thanks!Nope. Given that you have folder duplication on the files in duplicated folders are on 2 different physical drives. If the drive really does fail you just replace it and do a 'repair install'. It will take a while to balance, you will loose any customization, user accounts and PC backups, but the data will be there.
- 0
Hello all!
Reading the whole thread, I still didn't find an answer to the question asked by several contributors: What makes WHS give this (probably false) error message? Reading other threads about "sys failing" also, there are people having exchanged most parts of their systems, without getting rid of the message (for more than days or a few weeks) - still most of those failing sys drives seems to have survived for months! I've had mine for nearly half a year. It seems more and more WHS owners are resting assured the error message is indeed false. It would be fine to have this officially acknowledged by someone at MS. When the user interface presents error messages, there should be some kind of explanation in the underlying system. WHS isn't built from scratch, it's built upon Windows. What makes WHS report that all those sys drives are failing, when we can't find anything in the Windows event logs or anywhere else I can think of? Somebody should point all of us to the underlying system actually reporting the error. I doubt WHS is so hardware-aware that it makes the conclusion about the failing sys drive all by itself (if it's not only one of its internal databases that have become inconsistent, but in that case it is still a WHS bug and shouldn't tell people that they have failing hardware).
Regards, Christen
- 0
My HP MediaSmart gives me the "Sys volume is failing" message from time to time.
From what I can gather in these forums, the cause is likely one of these two things:
#1 --> This is a FALSE message, turning our network status to yellow. This is unnacceptable. A bug, needs fixing.
#2 --> There really is a hardware failure, but it is NOT the UPS, and it is NOT the system drive.
Either way, I'm going to contact HP and demand that they either replace my HP MediaSmart / System drive (if they want to waste time and money on a wild goose chase), otherwise, HP should put pressure on Microsoft to fix the bug.
- 0
For anyone with a minute... My WHS had a melt down and I was wondering if
anyone has any ideas as to what I could have done different. It was a bad drive, just notthe sys vol.
For some reason yesterday WHS started telling me that the backup service
could not start. I would try to start it manually but all I would get was a
window telling me that the service started and then stopped as some services
do when there is nothing to do. I could not do backups or restores from any
PC in the house. Turns out that one of the hard drives failed and had to be
removed. I did that, and 6 hours later WHS was still trying to remove the
drive, but the drive was not responding. So I was stuck with no options. I
rebooted and all seemed to be well, no more error messages when the server
booted, but upon launching the console, I got the message that the backup
service was not started and some functionality would not be available. I
tried a reinstall of the server only to have the same problem. The error
logs (which I should have saved, duh, but didn't) showed the service not
running. The only thing left was to try and copy most of my files in the
personal folders and shared folders to an external drive and reinstall. Did
that and all is well this morning (with a drive replacement). I thought
that if a drive failed, WHS was not to do what it did to me, but to just
keep on truckin' as it were.
Any insights would be greatly appreciated.
Billy The Kidd - 0
Yep, whenever my UPS battery dies I discard the battery at the local recycling center, and then resell the UPS on eBay. Even with complete honesty, it's not unusual to get 50% to 60% of the original cost of the UPSfor it w/o battery. There's one born every minute on eBay... ;-)
Oh, I also see about 18 to 24 months before battery goes belly up. It's almost like clockwork. I've been using variants of the 2200va Back UPS and Back UPS Pro for almost 10 years now, and they usually die right aorund 20 to 22 months of age.
- Ryan - 0Sure sounds like a power supply to me. It could be the cable though and that is cheaper to try than a power supply.
Poofy2007 wrote: Hi Dirk,
I have had the same issue, I initially thought it was the hard drive so replaced it with a new 320G Seagate PATA Drive. I re-installed WHS and within a week experienced the same issue. I then assumed it must be the hard drive controller, so I swapped the drives around so that the system drive was on the second ATA controller. Again the problem went away to then come back. I then decided it must be the M/board (it was an old A7N8X running a Athlon 2400XP).
I went out and bought a new M/B, CPU & RAM (Core 2 Duo). Re-installed RTM version of WHS and again one week later have had the same issue. I have changed the drives around and the problem seems to re-occur. When I 'repair' the drive the issue goes away for a few days.
It is interesting to note that this issue only warrants a yellow warning and is not rated as severe. I would be keen to better understand what determines the 'SYS volume failing' error.
Cheers
Paul. - 0I am having the same problem.
- 0
I too am having this problem and I know it is not a hardware issue because I replaced every single component in the system and I am still getting error messages. If I reboot the server there seems to be a much longer time between errors than if I just run chkdsk.
This is obviously another problem with the OS. Can it possible have something to do with the corruption of files issue?
Any word on when that fix will be released?
- 0At the risk of banging my well-worn drum again, wouldn't it be nice if WHS actually gave accurate error messages, instead of telling you things that are completely erroneous?
- 0I'm with Jeshimon here - most (if not all) error messages you receive in WHS other than backup failures have been, in my experience, unwarranted, and the suggested fixes simply not targeted at the reported problem.
- 0
catsaver wrote: At the risk of banging my well-worn drum again, wouldn't it be nice if WHS actually gave accurate error messages, instead of telling you things that are completely erroneous?Yes, it would be nice. It seems everything you try lets you think it is fixed for a while. In 137 days I have had the drive failing message 16 times. That means that chkdsk was run without error at least 260 times during that period WITHOUT error, not exactly an indicator of impending disaster.
- 0
I tried to find this bug (the "System volume is failing" message issue) on Microsoft Connect but couldn't find it. It surely must be on there, so I didn't resubmit it. If we could find the issue number we could track it that way.
- 0I think we must all be making it up. I would think by now someone with some credibility would have seen it. I know I see it, I know other here see it, yet they still insist it is a hardware problem. Others have changed everything in the computer only to see the problem come back. We have 4 pages of posts on this topic and the problem affects HP Mediasmart Servers.
- 0
There are much more than 4 pages of posts about this issue, as there are numerous other threads dealing with it. I don't have the HP Mediasmart, but the same sys failing issue all the same. It sure isn't hardware. It's the corruption bug or another bug, and it really annoys me that nobody at Microsoft makes a statement about it.
Christen
- 0Christen, the WHS team is very much "heads down" working on KB946676 right now. Don't look for them to make statements about relatively minor user interface issues.
- 0
Ken, I really like the first part of your answer, the part about the team being "heads down" on the corruption issue. That's perfectly understandable.
But you are being too clever when saying "relatively minor". While that's technically true because the corruption bug is so significant it overshadows this one, you make it sound like this one's not a showstopper on it's own. In case you haven't noticed, people are buying new hard drives and/or changing hardware because of this possibly incorrect message.
If it turns out in the final analysis that it IS hardware problems and not related to the WHS software, then great. But if it is determined to be a bug, my guess would be that once the corruption bug is taken care of, this could become as much of a showstopper...
- 0
I agree that it's more than a "minor" user interface issue. After I upgraded from RC to the evaluation version (with a brand new system drive), everything was running fine for about 3 weeks, and then I got the infamous yellow warning again. Since then I am getting the warning in regular intervals, about every 7 to 8 days. Once I repair the disk I have my peace for a week, and then I get the next warning. That's going on now for months. It is definitely not a hardware issue - I tested the drive extensively multiple times with different tools - and they never detected any problem with the drive.
The point is: it's not just an user interface issue, but it defeats the very purpose of running an OS that should give you good indications about the health of your system. If I can't rely on the warnings that WHS issues, I'll simply get used to ignore them (basically what I am doing right now), and in case there will be a *real* problem down the line, I won't have the chance to detect it.
Based on the numerous reports from other users here in the forum, I really hope that this issue will get some more attention from the developers in the future.
Regards,
Dirk
- 0At the very least an admission that there is a problem worth looking into.
dflachbart wrote: Based on the numerous reports from other users here in the forum, I really hope that this issue will get some more attention from the developers in the future.
- 0
I agree this probably boils down to a user interface issue, but in the meantime users have been buying new harddrives and having a lot of work with replacements, reinstallation etc. Probably some are still doing so, unaware it is a bug. I was among those told by serious posts in this forum that this was hardware failure for sure. Luckily, I trusted myself more. But to avoid more frustration, work and cost - I think it is worth a statement.
- 0
Christen A wrote: I agree this probably boils down to a user interface issue, but in the meantime users have been buying new harddrives and having a lot of work with replacements, reinstallation etc. Probably some are still doing so, unaware it is a bug. I was among those told by serious posts in this forum that this was hardware failure for sure. Luckily, I trusted myself more. But to avoid more frustration, work and cost - I think it is worth a statement.
Yeah, I bought into the MVPs telling me it was a hardware problem, I bought a new hard drive and put it as secondary storage, when it was failing too I was told it must be the motherboard. I stopped listening there. I knew the hardware was pretty solid from gaming on it. Others have bought new motherboards, hard drives, entire computers have been replaced and the issue is still there. If you WHS gets rebooted about once a week you'll probably never see it.
- 0
Well this was wishful thinking on my part... I reinstalled my WHS server a week ago (switched from the eval to the OEM version) and hoped that maybe this might end now. But this morning, exactly one week after the install, the yellow SYS volume failing warning came back.Also note that I switched drives around when I performed the new install - I am now using a SATA drive for my system partition that had been functioning as a DATA drive in my previous WHS installations - and this drive had never had any WHS warnings before.
Regards,
Dirk - 0ok i to am having the same problem here.
I have 3 different OEM software custom builds using different hardware and configs and am getting the error on all 3 and i cannot get any of them to go away. Actually when i try a repair it hangs for days and wont stop until i restart. I have ran spinrite and still doesn't help.
actually on one it only has 2 drives but i get
sys failing
primary failing
secondary failing.
all of them
replaced drives and still same thing.
mixed use of pata and sata drives so it is not an either or
one 6 drives and i get sys failing error even after replacing sys drive.
Got to be a software bug because i have different MB and still the same problem. lets keep this to the top so something gets solved - 0
smartmoney wrote: ok i to am having the same problem here.
Actually when i try a repair it hangs for days and wont stop until i restart. I have ran spinrite and still doesn't help.My symptoms are quite different than yours. I can run repair and it completes in fairly short order. Next time (there WILL be one) I will time it and post GB/sec, I track the occurances of this problem. In 163 days of data I've had it appear 19 times on various disks, that means that chkdsk ran at least 307 time without error. On one of the drives it happened the day after I added it to the pool, and it has only happened once since on that drive. Virtually the only time my server gets restarted is when a software update requires it or I make a hardware change. It usually occurs when I make massive changes to the data on the server, but the longest I've gone without seeing it is about 3 weeks.
- 0
Regarding the “SYS Volume …” failing messages, we don’t want to summarily rule out that these are false messages, as people may indeed being having problems with one or more hard drives in their home servers. However, it may not be the SYS partition (the C Drive) that in some cases may be causing the issue. To help narrow the issue down, please answer the following questions so we can understand each person’s specific environment / circumstances:
· What is the exact text of the error message you are seeing?
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
· How many hard drives, what size? Internal? External?
· Do you have have UPS system hooked up to your home server? which one?
· Are you running any Add-Ins? Which ones?
· Have you loaded any software on your home server using a Remote Desktop session?
· How much free space do you have on your C: drive (SYS) on your home server?
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
· Did “Repair” fix the issue? For how long?
Assuming the “Repair” option does not fix your issue, and you keep seeing this error message come back, then please try the following:
· Open a Remote Desktop session to your home server
· Open a CMD prompt from the Administrative Desktop – Start – Run – CMD
· Run the CHKDSK command for each of the hard drives on your home server and save the results into a log file:
o Operating System partition (SYS)
§ CHKDSK C: > SYS_volume.log
o Primary Data partition (DATA)
§ CHKDSK D: > DATA_disk0.log
o If you have more than 1 hard drive, then you will need to find the ‘Mount Points’ for your additional hard drives by navigating to the C:\FS directory and type ‘dir’ to see the ‘Mount Points’ for your other hard drives. For example, you have 3 hard drives, you may see 2 sub-directories, listed as “<JUNCTION>” under the c:\FS directory (for example, you may see E and F)
§ CHKDSK C:\fs\E > DATA_disk1.log
§ CHKDSK C:\fs\F > DATA_disk2.log
§ Etc. (if you have more disks)
· Analyze these log files and report any error messages or inconsistencies that you may see - what drive is reporting errors via CHKDSK? (SYS, DATA, Data Disk 1, Data Disk 2, etc.)?
- 0Hi Todd,
I am excited to see some official response to this issue. Here are my answers to your specific questions:
What is the exact text of the error message you are seeing?
I get the yellow health warning icon, and when I log into the WHS console it tells me that my SYS volume is failing and needs to be repaired. I always find the same output in the qsm log file:
[3/16/2008 6:04:19 PM e74] Executing C:\WINDOWS\system32\cmd.exe /C chkdsk.exe C: >"C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk.log"
[3/16/2008 6:07:05 PM e74] Chkdsk done
[3/16/2008 6:07:05 PM e74] SetObjectSelfHealth (SYS) QSM_OS_HEALTHY => QSM_OS_FAILING
Unfortunately it seems the ouput is piped via ">" and not ">>" into the chkdsk.log, so that the following runs on the other hard drives overwrite the error logs.
Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
This is a home-built server (Abit P35 Pro motherboard, Intel Q6600, 2 GB RAM).
How many hard drives, what size? Internal? External?
3 x internal SATA (500 GB system, 500 GB data, 250 GB data) in WHS storage pool
1 x internal IDE (350 GB), not managed by WHS
1 x external USB (200 GB), not managed by WHS
Do you have have UPS system hooked up to your home server? which one?
Yes, I recently (about a month ago) installed a new APC ES 500. It can be ruled out that this has anything to do with the problem, since I am experiencing this issue over half a year now, and I didn't have any UPS before
Are you running any Add-Ins? Which ones?
I am running the following Add-Ins:
- SageTV
- mtorrent
- only recently: Server Storage, and Program Launcher
Have you loaded any software on your home server using a Remote Desktop session?
Yes, several:
- SVN server
- SyncBackSE
- DirMon2 / Comskip (commercial detection of TV recordings)
- various drivers (PVR-150, STB Firewire, Canon printer)
- Windows Resource Kit
How much free space do you have on your C: drive (SYS) on your home server?
12 GB
What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
The ones in the WHS pool are all "Healthy", except for the drive containing the SYS volume which is turning unhealthy once a week
Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes, once I get the yellow health warning I run "Repair" on the system drive
Did “Repair” fix the issue? For how long?
Yes, "Repair" always fixes the issue. But it lasts only for about a week, after 7-8 days the warning comes back.
If you read through my previous posts you will see that this issue is haunting me for a long time now, with different hardware configurations. I had the problem with my old Celeron board and RC1, it continued with my new board/CPU and the Evaluation copy, and it is still persisting after I upgraded to the OEM version. I had it happening with an IDE system drive (tested error free several times with appropriate tools), and now it continues to happen on a SATA drive (when I reinstalled to OEM I thought I might try this out for a change) - the same SATA drive that I had previously running in WHS as a DATA drive for several months and which *never* failed on me before.
I appreciate that your are taking time to look into this further. Hope you guys will finally figure out whether this is indeed a false message or not. It seems a *lot* of people are experiencing the same problem.
Regards,
Dirk - 0
What is the exact text of the error message you are seeing?
Volume with name "SYS" is failing. Please try to run Repair to fix errors for disk ST350063 0AS SCSI disk drive
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
OEM, HP MediaSmart
· How many hard drives, what size? Internal? External?
4 hard drives, 3 500 gigs and one 750 gig
· Do you have have UPS system hooked up to your home server? which one?
APC Back-UPS ES550 (but got this same error many times before I had a UPS)
Are you running any Add-Ins? Which ones?
WHIIST
· Have you loaded any software on your home server using a Remote Desktop session?
No
· How much free space do you have on your C: drive (SYS) on your home server?
15.1 gigs
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
Drive that contains System partition is flagged as "Unhealthy", others are "Healthy"
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes
· Did “Repair” fix the issue? For how long?
Fixes it for 3-4 days, then it recurs. Sometimes it goes away on its own without repair.
- 0The next time I see it I will take screen shots of the whole thing. Nice to see someone admit it might be a problem after all this time.
- 0
dflachbart wrote: Hi Todd,
Unfortunately it seems the ouput is piped via ">" and not ">>" into the chkdsk.log, so that the following runs on the other hard drives overwrite the error logs.This is a known issue and will be fixed in Power Pack 1, such that each disk volume will have a separate CHKDSK log file. For now, if you do see this error. Try to follow the steps in my post for gathering CHKDSK logs before using the 'REPAIR' option in the Console. Be sure to note the exact error in the Console and which drive(s) are 'supposedly' having issues...
thx in advance.
- 0
Thanks Todd, will do. I'll probably have the next chkdsk output by Monday...
Regards,
Dirk
- 0
What is the exact text of the error message you are seeing?
Volume with name "SYS" is failing. Please try to run Repair to fix errors for disk ST3120814A
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
Home Built Server Asus P4B P4 1.5ghz 512mb Ram oem software cd bought software not test vers home server software
· How many hard drives, what size? Internal? External?
3 hard drives 1. 120gb 2. 200gb 3. 40gb
· Do you have have UPS system hooked up to your home server? which one?
APC Back-UPS ES550 (but got this same error many times before I had a UPS)
Are you running any Add-Ins? Which ones?
WHIIST, Webfolders4WHS, Jungle Disk
· Have you loaded any software on your home server using a Remote Desktop session?
Eset Nod 32 antivirus. only installed software on the server
· How much free space do you have on your C: drive (SYS) on your home server?
16.0 gigs
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
Drive that contains System partition is flagged as "Unhealthy" (120gb hd), others are "Healthy" (200gb and 40gb)
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes
· Did “Repair” fix the issue? For how long?
Sometimes it just hangs on repair for days and i have to restart and sometimnes it Fixes it for 3-4 days, then it recurs. Sometimes it goes away on its own without repair.
· Run CHKDSK on Failing Disk
done that and it shows no errors in the log file on the failing drive.
I have replaced the drive and same error. I have shuffeled the drives around in different order and same error on sys drive only no matter which one is in place currently.
- 0log file for sys drive for above posting. SYS drive is currently showing failing msg when this was ran.
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is SYS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 17840 file records processed)
1 percent complete. (1784 of 17840 file records processed)
2 percent complete. (3568 of 17840 file records processed)
3 percent complete. (5352 of 17840 file records processed)
4 percent complete. (7136 of 17840 file records processed)
5 percent complete. (8920 of 17840 file records processed)
6 percent complete. (10704 of 17840 file records processed)
7 percent complete. (12488 of 17840 file records processed)
8 percent complete. (14272 of 17840 file records processed)
9 percent complete. (16056 of 17840 file records processed)
101784017840
17840 file records processed.
File verification completed.
10 percent complete. (1 of 17 large file records processed)
101717
17 large file records processed.
1000
0 bad file records processed.
1000
0 EA records processed.
1055
5 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
10 percent complete. (1 of 60140 index entries processed)
10 percent complete. (507 of 60140 index entries processed)
11 percent complete. (764 of 60140 index entries processed)
11 percent complete. (1271 of 60140 index entries processed)
12 percent complete. (1526 of 60140 index entries processed)
12 percent complete. (2027 of 60140 index entries processed)
13 percent complete. (2282 of 60140 index entries processed)
13 percent complete. (2785 of 60140 index entries processed)
14 percent complete. (3044 of 60140 index entries processed)
14 percent complete. (3549 of 60140 index entries processed)
15 percent complete. (3807 of 60140 index entries processed)
15 percent complete. (4314 of 60140 index entries processed)
16 percent complete. (4571 of 60140 index entries processed)
16 percent complete. (5071 of 60140 index entries processed)
17 percent complete. (5332 of 60140 index entries processed)
17 percent complete. (5837 of 60140 index entries processed)
18 percent complete. (6098 of 60140 index entries processed)
18 percent complete. (6604 of 60140 index entries processed)
19 percent complete. (6857 of 60140 index entries processed)
19 percent complete. (7362 of 60140 index entries processed)
20 percent complete. (7614 of 60140 index entries processed)
20 percent complete. (8115 of 60140 index entries processed)
21 percent complete. (8376 of 60140 index entries processed)
21 percent complete. (8883 of 60140 index entries processed)
22 percent complete. (9139 of 60140 index entries processed)
22 percent complete. (9640 of 60140 index entries processed)
23 percent complete. (9900 of 60140 index entries processed)
23 percent complete. (10404 of 60140 index entries processed)
24 percent complete. (10666 of 60140 index entries processed)
24 percent complete. (11171 of 60140 index entries processed)
25 percent complete. (11425 of 60140 index entries processed)
25 percent complete. (11932 of 60140 index entries processed)
26 percent complete. (12191 of 60140 index entries processed)
26 percent complete. (12698 of 60140 index entries processed)
27 percent complete. (12952 of 60140 index entries processed)
27 percent complete. (13455 of 60140 index entries processed)
28 percent complete. (13709 of 60140 index entries processed)
28 percent complete. (14211 of 60140 index entries processed)
29 percent complete. (14476 of 60140 index entries processed)
29 percent complete. (14983 of 60140 index entries processed)
30 percent complete. (15233 of 60140 index entries processed)
30 percent complete. (15735 of 60140 index entries processed)
31 percent complete. (15995 of 60140 index entries processed)
31 percent complete. (16497 of 60140 index entries processed)
32 percent complete. (16758 of 60140 index entries processed)
32 percent complete. (17263 of 60140 index entries processed)
33 percent complete. (17525 of 60140 index entries processed)
33 percent complete. (18031 of 60140 index entries processed)
34 percent complete. (18287 of 60140 index entries processed)
34 percent complete. (18787 of 60140 index entries processed)
35 percent complete. (19043 of 60140 index entries processed)
35 percent complete. (19543 of 60140 index entries processed)
36 percent complete. (19805 of 60140 index entries processed)
36 percent complete. (20305 of 60140 index entries processed)
37 percent complete. (20566 of 60140 index entries processed)
37 percent complete. (21066 of 60140 index entries processed)
38 percent complete. (21328 of 60140 index entries processed)
38 percent complete. (21828 of 60140 index entries processed)
39 percent complete. (22090 of 60140 index entries processed)
39 percent complete. (22590 of 60140 index entries processed)
40 percent complete. (22852 of 60140 index entries processed)
40 percent complete. (23352 of 60140 index entries processed)
41 percent complete. (23614 of 60140 index entries processed)
41 percent complete. (24114 of 60140 index entries processed)
42 percent complete. (24376 of 60140 index entries processed)
42 percent complete. (24876 of 60140 index entries processed)
43 percent complete. (25138 of 60140 index entries processed)
43 percent complete. (25638 of 60140 index entries processed)
44 percent complete. (25900 of 60140 index entries processed)
44 percent complete. (26400 of 60140 index entries processed)
45 percent complete. (26662 of 60140 index entries processed)
45 percent complete. (27162 of 60140 index entries processed)
46 percent complete. (27424 of 60140 index entries processed)
46 percent complete. (27924 of 60140 index entries processed)
47 percent complete. (28186 of 60140 index entries processed)
47 percent complete. (28686 of 60140 index entries processed)
48 percent complete. (28947 of 60140 index entries processed)
48 percent complete. (29447 of 60140 index entries processed)
49 percent complete. (29709 of 60140 index entries processed)
49 percent complete. (30209 of 60140 index entries processed)
50 percent complete. (30471 of 60140 index entries processed)
50 percent complete. (30971 of 60140 index entries processed)
51 percent complete. (31233 of 60140 index entries processed)
51 percent complete. (31733 of 60140 index entries processed)
52 percent complete. (31995 of 60140 index entries processed)
52 percent complete. (32495 of 60140 index entries processed)
53 percent complete. (32757 of 60140 index entries processed)
53 percent complete. (33257 of 60140 index entries processed)
54 percent complete. (33519 of 60140 index entries processed)
54 percent complete. (34019 of 60140 index entries processed)
55 percent complete. (34281 of 60140 index entries processed)
55 percent complete. (34781 of 60140 index entries processed)
56 percent complete. (35043 of 60140 index entries processed)
56 percent complete. (35543 of 60140 index entries processed)
57 percent complete. (35805 of 60140 index entries processed)
57 percent complete. (36305 of 60140 index entries processed)
58 percent complete. (36566 of 60140 index entries processed)
58 percent complete. (37066 of 60140 index entries processed)
59 percent complete. (37328 of 60140 index entries processed)
59 percent complete. (37828 of 60140 index entries processed)
60 percent complete. (38091 of 60140 index entries processed)
60 percent complete. (38591 of 60140 index entries processed)
61 percent complete. (38852 of 60140 index entries processed)
61 percent complete. (39352 of 60140 index entries processed)
62 percent complete. (39614 of 60140 index entries processed)
62 percent complete. (40114 of 60140 index entries processed)
63 percent complete. (40376 of 60140 index entries processed)
63 percent complete. (40876 of 60140 index entries processed)
64 percent complete. (41138 of 60140 index entries processed)
64 percent complete. (41638 of 60140 index entries processed)
65 percent complete. (41900 of 60140 index entries processed)
65 percent complete. (42400 of 60140 index entries processed)
66 percent complete. (42662 of 60140 index entries processed)
66 percent complete. (43162 of 60140 index entries processed)
67 percent complete. (43424 of 60140 index entries processed)
67 percent complete. (43924 of 60140 index entries processed)
68 percent complete. (44186 of 60140 index entries processed)
68 percent complete. (44686 of 60140 index entries processed)
69 percent complete. (44947 of 60140 index entries processed)
69 percent complete. (45447 of 60140 index entries processed)
70 percent complete. (45709 of 60140 index entries processed)
70 percent complete. (46209 of 60140 index entries processed)
71 percent complete. (46471 of 60140 index entries processed)
71 percent complete. (46971 of 60140 index entries processed)
72 percent complete. (47233 of 60140 index entries processed)
72 percent complete. (47733 of 60140 index entries processed)
73 percent complete. (47995 of 60140 index entries processed)
73 percent complete. (48495 of 60140 index entries processed)
74 percent complete. (48757 of 60140 index entries processed)
74 percent complete. (49257 of 60140 index entries processed)
75 percent complete. (49519 of 60140 index entries processed)
75 percent complete. (50019 of 60140 index entries processed)
76 percent complete. (50281 of 60140 index entries processed)
76 percent complete. (50781 of 60140 index entries processed)
77 percent complete. (51043 of 60140 index entries processed)
77 percent complete. (51543 of 60140 index entries processed)
78 percent complete. (51805 of 60140 index entries processed)
78 percent complete. (52305 of 60140 index entries processed)
79 percent complete. (52566 of 60140 index entries processed)
79 percent complete. (53066 of 60140 index entries processed)
80 percent complete. (53328 of 60140 index entries processed)
80 percent complete. (53828 of 60140 index entries processed)
81 percent complete. (54090 of 60140 index entries processed)
81 percent complete. (54590 of 60140 index entries processed)
82 percent complete. (54852 of 60140 index entries processed)
82 percent complete. (55352 of 60140 index entries processed)
83 percent complete. (55614 of 60140 index entries processed)
83 percent complete. (56114 of 60140 index entries processed)
84 percent complete. (56376 of 60140 index entries processed)
84 percent complete. (56876 of 60140 index entries processed)
85 percent complete. (57138 of 60140 index entries processed)
85 percent complete. (57638 of 60140 index entries processed)
86 percent complete. (57900 of 60140 index entries processed)
86 percent complete. (58400 of 60140 index entries processed)
87 percent complete. (58662 of 60140 index entries processed)
87 percent complete. (59162 of 60140 index entries processed)
88 percent complete. (59424 of 60140 index entries processed)
88 percent complete. (59924 of 60140 index entries processed)
886014060140
60140 index entries processed.
Index verification completed.
8855
5 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
89 percent complete. (177 of 17840 descriptors processed)
90 percent complete. (3224 of 17840 descriptors processed)
91 percent complete. (6272 of 17840 descriptors processed)
92 percent complete. (9319 of 17840 descriptors processed)
93 percent complete. (12367 of 17840 descriptors processed)
94 percent complete. (15415 of 17840 descriptors processed)
941784017840
17840 security descriptors processed.
Security descriptor verification completed.
9521452145
2145 data files processed.
CHKDSK is verifying Usn Journal...
98 percent complete. (0 of 33939264 USN bytes processed)
98 percent complete. (1048576 of 33939264 USN bytes processed)
98 percent complete. (2097152 of 33939264 USN bytes processed)
98 percent complete. (3145728 of 33939264 USN bytes processed)
98 percent complete. (4194304 of 33939264 USN bytes processed)
98 percent complete. (5242880 of 33939264 USN bytes processed)
98 percent complete. (6291456 of 33939264 USN bytes processed)
98 percent complete. (7340032 of 33939264 USN bytes processed)
98 percent complete. (8388608 of 33939264 USN bytes processed)
98 percent complete. (9437184 of 33939264 USN bytes processed)
98 percent complete. (10485760 of 33939264 USN bytes processed)
98 percent complete. (11534336 of 33939264 USN bytes processed)
98 percent complete. (12582912 of 33939264 USN bytes processed)
98 percent complete. (13631488 of 33939264 USN bytes processed)
98 percent complete. (14680064 of 33939264 USN bytes processed)
98 percent complete. (15728640 of 33939264 USN bytes processed)
99 percent complete. (15773696 of 33939264 USN bytes processed)
99 percent complete. (16822272 of 33939264 USN bytes processed)
99 percent complete. (17870848 of 33939264 USN bytes processed)
99 percent complete. (18919424 of 33939264 USN bytes processed)
99 percent complete. (19968000 of 33939264 USN bytes processed)
99 percent complete. (21016576 of 33939264 USN bytes processed)
99 percent complete. (22065152 of 33939264 USN bytes processed)
99 percent complete. (23113728 of 33939264 USN bytes processed)
99 percent complete. (24162304 of 33939264 USN bytes processed)
99 percent complete. (25210880 of 33939264 USN bytes processed)
99 percent complete. (26259456 of 33939264 USN bytes processed)
99 percent complete. (27308032 of 33939264 USN bytes processed)
99 percent complete. (28356608 of 33939264 USN bytes processed)
99 percent complete. (29405184 of 33939264 USN bytes processed)
99 percent complete. (30453760 of 33939264 USN bytes processed)
99 percent complete. (31502336 of 33939264 USN bytes processed)
99 percent complete. (32550912 of 33939264 USN bytes processed)
99 percent complete. (33599488 of 33939264 USN bytes processed)
100 percent complete. (33935360 of 33939264 USN bytes processed)
1003393926433939264
33939264 USN bytes processed.
Usn Journal verification completed.
20972825 KB total disk space.
4032888 KB in 15425 files.
4468 KB in 2146 indexes.
0 KB in bad sectors.
118421 KB in use by the system.
65536 KB occupied by the log file.
16817048 KB available on disk.
4096 bytes in each allocation unit.
5243206 total allocation units on disk.
4204262 allocation units available on disk. - 0Screenshots
- 0
Todd,
I just had the same problem this morning and documented it (along with detailed screen shots) on my blog at: http://www.homeserverhacks.com/2008/03/volume-with-name-sys-is-failing.html
In any case, here are the answers to your form questionnaire:
· What is the exact text of the error message you are seeing?
Volume with name SYS is failing. Please try to run Repair to fix errors for disk XXXX.
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
OEM. It is from an HP EX470
· How many hard drives, what size? Internal? External?
3 x 500 GB internal (including the SYS drive), 2 x 500 GB external (i.e. in an eSATA port multiplier external enclosure) and 1 x USB (used for System Backups with Power Pack 1)
· Do you have have UPS system hooked up to your home server? which one?
It is plugged into an APC Back-UPS Pro 1100, although I don't have the data cable attached
· Are you running any Add-Ins? Which ones?
Jungle Disk for WHS 1.02.2, Window Home Server Toolkit 6.0.1639.0
· Have you loaded any software on your home server using a Remote Desktop session?
More than likely, but not in the past few days.
· How much free space do you have on your C: drive (SYS) on your home server?
10.9 GB
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
All Storage Hard Drives now read "Healthy", 2 Non Storage Drives read "Not Added" and the Server Backup Hard Drive reads "100% Free"
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes, on the SYS drive as suggested in the error message above
· Did “Repair” fix the issue? For how long?
Yes, not sure for how long. I'm writing this only 10 minutes after it was corrected. - 0LiveGadgets
" **** Update ****
There is some speculation on the Windows Home Server MSDN forum that this is caused by a faulty UPS. I'll keep you informed as things progress."
this is misinformation posted on your blog. If you follow this thread there are several people including me that have the errors without the ups. I currently have it installed as a safe measure but i have had it happen without it and even with a different ups. I have 3 different systems running (office, home and friends) and all exibit the same failure. only thing in common is they are custom builds but different configs. dont spread rumor as this is not the problem. - 0It CANNOT be ups because people without one see it.
- 0
Thanks guys for the updated info. One new small request, BEFORE you hit the Repair button in the Console, try to collect the CHKDSK logs for all of your hard drives.
· Open a Remote Desktop session to your home server
· Open a CMD prompt from the Administrative Desktop – Start – Run – CMD
· Run the CHKDSK command for each of the hard drives on your home server and save the results into a log file:
o Operating System partition (SYS)
§ CHKDSK C: > SYS_volume.log
o Primary Data partition (DATA)
§ CHKDSK D: > DATA_disk0.log
o If you have more than 1 hard drive, then you will need to find the ‘Mount Points’ for your additional hard drives by navigating to the C:\FS directory and type ‘dir’ to see the ‘Mount Points’ for your other hard drives. For example, you have 3 hard drives, you may see 2 sub-directories, listed as “<JUNCTION>” under the c:\FS directory (for example, you may see E and F)
§ CHKDSK C:\fs\E > DATA_disk1.log
§ CHKDSK C:\fs\F > DATA_disk2.log
§ Etc. (if you have more disks)
· Analyze these log files and report any error messages or inconsistencies that you may see - what drive is reporting errors via CHKDSK? (SYS, DATA, Data Disk 1, Data Disk 2, etc.)?
- 0· What is the exact text of the error message you are seeing?
- I get the yellow health warning icon, and when I log into the WHS console it tells me that my SYS volume is failing and needs to be repaired
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
- It is homebuild: IBM T40 - Pentium M 1,50 GhZ - 1,50 GB RAM -
· How many hard drives, what size? Internal? External?
- 100 GB internal HardDisk - 2x 500 GB external USB WesternDigital harddisks
· Do you have have UPS system hooked up to your home server? which one?
- No
· Are you running any Add-Ins? Which ones?
- WIndows Home Server Disk Management Add in
· Have you loaded any software on your home server using a Remote Desktop session?
Yes: eMule, Napster, mTorrent,
· How much free space do you have on your C: drive (SYS) on your home server?
13,8 GB
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
internal harddisk is red, external harddisks are green
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes
· Did “Repair” fix the issue? For how long?
Yes, it always repairs the issue for about 6 or 7 days
I receive the following (german) error message for SYS_volume, when I run chkdsk as you suggest:
" CHKDSK hat freien Speicher gefunden, der in der Volumebitmap als
zugeordnet gekennzeichnet ist.
Windows hat Probleme im Dateisystem festgestellt.
Fuehren Sie CHKDSK mit der Option /F (Fehlerbehebung) aus, um die Probleme zu
beheben."
Translation:
CHKDKS has found free space, which has been marked in the volumebitmap as assigned.
Windows found problems in the filesystem.
Execute CHKDSK with option /F to solve the problems. - 0Arrrgghhh....this just happened to me this morning...Of course here I am cooking Easter supper for my wife's family so I don't have a ton of time to play with this.
Some background. Last night I set up another media center PC with Vista and had it updating the shared media from the home server over the network. The music is in a share on a drive that is outside of the storage pool. 95% of my data with the exception of backups and some stuff needed remotely is outside of the storage pool.
I have 4 computers in my office including the Home server that run off a switch that is plugged into the wall which goes back to the wiring closet patch panel and the router etc.
The switch hung up last night and I had to unplug and replug in the switch. The mediacenter PC was updating the files when I went to bed so I did not back it up. This morning I checked before starting my samosa's and I had a red error saying that the mediacenter PC did not have an antivirus on it. Fair enough. I click on it to back it up and went upstairs to the kitchen. When I came back I checked the console of WHS and the back was proceeeding but there was a Sys Drive Failing message. GREAT!
So I let the back up finish and check out his message and saw that many people had it fix itself by rebooting the WHS. So I did that and check on it 1/2 hour latter. The drive message is gone. Yeah..
But wait so are all my backups. They still show in the console but if you try to access them you get an error.
The server space is showing too much space available for the backups to be there. Looks like only the last backup for the MediaCenter PC I just set up is there.
What is the exact text of the error message you are seeing?
- I get the yellow health warning icon, and when I log into the WHS console it tells me that my SYS volume is failing and needs to be repaired
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
- It is homebuild: ASUS P5S00 MB, P4 550J 3.0 CPU, 1 gig blitz memeory DDR
· How many hard drives, what size? Internal? External?
- 120 WD1200JB IDe HardDisk - 2x 500 GB WD5000AAKS Sata Drives
· Do you have have UPS system hooked up to your home server? which one?
- Yes APC 500
· Are you running any Add-Ins? Which ones?
- Tool Kit, Webguide
· Have you loaded any software on your home server using a Remote Desktop session?
Yes: Media Portal
· How much free space do you have on your C: drive (SYS) on your home server?
13,8 GB
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
internal harddisk was red, external harddisks are green, After reboot all are green.
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
No
· Did “Repair” fix the issue? For how long?
So now when I try and access the backups they error out and then disappear from the console
So...what to do?
Do I try to reinstall bearing in mind that the new MediaCenter4 PC looks like it has a backup. This makes me think that I will not get all the rest back.
What to do????? Any other options other than a reinstall?? I really like to recover the backups if possbile.
Oh well back to cooking supper while I ponder this... - 0
T. Headrick wrote: Thanks guys for the updated info. One new small request, BEFORE you hit the Repair button in the Console, try to collect the CHKDSK logs for all of your hard drives.
Hi Todd,
as promised, exactly 8 days after the last health warning, my WHS icon turned yellow again. I performed chkdsk on all four disks, and only the system drive (partition C) showed an error in the log. The exact message in the WHS console was:
Volume with name SYS is failing. Please try to run repair to fix errors for Disk Samsung HD501LJ
And here's the chkdsk log:
The type of the file system is NTFS.
Volume label is SYS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 27872 file records processed)
1 percent complete. (2788 of 27872 file records processed)
2 percent complete. (5575 of 27872 file records processed)
3 percent complete. (8362 of 27872 file records processed)
4 percent complete. (11149 of 27872 file records processed)
5 percent complete. (13936 of 27872 file records processed)
6 percent complete. (16724 of 27872 file records processed)
7 percent complete. (19511 of 27872 file records processed)
8 percent complete. (22298 of 27872 file records processed)
9 percent complete. (25085 of 27872 file records processed)
102787227872
27872 file records processed.
File verification completed.
10 percent complete. (1 of 28 large file records processed)
102828
28 large file records processed.
1000
0 bad file records processed.
1000
0 EA records processed.
1044
4 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
10 percent complete. (1 of 97914 index entries processed)
10 percent complete. (501 of 97914 index entries processed)
10 percent complete. (1010 of 97914 index entries processed)
11 percent complete. (1221 of 97914 index entries processed)
11 percent complete. (1723 of 97914 index entries processed)
11 percent complete. (2233 of 97914 index entries processed)
12 percent complete. (2441 of 97914 index entries processed)
[...]
88 percent complete. (95387 of 97914 index entries processed)
88 percent complete. (95887 of 97914 index entries processed)
88 percent complete. (96387 of 97914 index entries processed)
89 percent complete. (96610 of 97914 index entries processed)
89 percent complete. (97110 of 97914 index entries processed)
89 percent complete. (97610 of 97914 index entries processed)
90 percent complete. (97833 of 97914 index entries processed)
909791497914
97914 index entries processed.
Index verification completed.
9055
5 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
91 percent complete. (4564 of 27872 descriptors processed)
92 percent complete. (9456 of 27872 descriptors processed)
93 percent complete. (14348 of 27872 descriptors processed)
94 percent complete. (19240 of 27872 descriptors processed)
95 percent complete. (24132 of 27872 descriptors processed)
952787227872
27872 security descriptors processed.
Security descriptor verification completed.
9624032403
2403 data files processed.
CHKDSK is verifying Usn Journal...
98 percent complete. (0 of 37043760 USN bytes processed)
98 percent complete. (1048576 of 37043760 USN bytes processed)
98 percent complete. (2097152 of 37043760 USN bytes processed)
[...]
99 percent complete. (29847552 of 37043760 USN bytes processed)
99 percent complete. (30896128 of 37043760 USN bytes processed)
99 percent complete. (31944704 of 37043760 USN bytes processed)
99 percent complete. (32993280 of 37043760 USN bytes processed)
99 percent complete. (34041856 of 37043760 USN bytes processed)
99 percent complete. (35090432 of 37043760 USN bytes processed)
99 percent complete. (36139008 of 37043760 USN bytes processed)
1003704376037043760
37043760 USN bytes processed.
Usn Journal verification completed.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
20972825 KB total disk space.
8228876 KB in 25308 files.
7908 KB in 2404 indexes.
0 KB in bad sectors.
131521 KB in use by the system.
65536 KB occupied by the log file.
12604520 KB available on disk.
4096 bytes in each allocation unit.
5243206 total allocation units on disk.
3151130 allocation units available on disk.
Regards,
Dirk - 0
· What is the exact text of the error message you are seeing?
Same as the others in this thread.
· Is this an OEM product (e.g. HP, Fujitsu Siemens, Tranquil) or a home-built home server?
Home-built based on Proliant ML1xx.
· How many hard drives, what size? Internal? External?
All drives (3) are internal SATA, the sys drive is 160G, the others 320G and 400G.
· Do you have have UPS system hooked up to your home server? which one?
Yes - Powerware 5115, but didn't have in the beginning.
· Are you running any Add-Ins? Which ones?
None
· Have you loaded any software on your home server using a Remote Desktop session?
None
· How much free space do you have on your C: drive (SYS) on your home server?
Not sure (16G according to the log below)
· What is the status of the hard drives in the Server Storage tab on the Windows Home Server Console?
Healthy, except when the sys drive turns unhealthy.
· Did you run the “Repair” option on any hard drives using the Windows Home Server Console?
Yes, every time I'm told to (about once a week).
· Did “Repair” fix the issue? For how long?
Yes, seemingly (if I'm to trust the colour of the home server icon). I haven't logged the dates, but it seems the exact same error occurs with quite regular intervals of a week or two.
Junctions were named 4 and N. Here are my logs (all of them, but truncated):
The type of the file system is NTFS.
Volume label is SYS.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 17088 file records processed)
1 percent complete. (1709 of 17088 file records processed)
.. 8 percent complete. (13671 of 17088 file records processed)
9 percent complete. (15380 of 17088 file records processed)
101708817088
17088 file records processed.File verification completed.
10 percent complete. (1 of 10 large file records processed)
101010
10 large file records processed.1000
0 bad file records processed.1000
0 EA records processed.1033
3 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)...
10 percent complete. (1 of 57475 index entries processed)
10 percent complete. (505 of 57475 index entries processed)
..75 percent complete. (56610 of 57475 index entries processed)
76 percent complete. (56973 of 57475 index entries processed)
765747557475
57475 index entries processed.Index verification completed.
7655
5 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)...
77 percent complete. (1438 of 17088 descriptors processed)
78 percent complete. (4891 of 17088 descriptors processed)
79 percent complete. (8344 of 17088 descriptors processed)
80 percent complete. (11797 of 17088 descriptors processed)
81 percent complete. (15250 of 17088 descriptors processed)
811708817088
17088 security descriptors processed.Security descriptor verification completed.
8217431743
1743 data files processed.CHKDSK is verifying Usn Journal...
97 percent complete. (0 of 37162512 USN bytes processed)
97 percent complete. (1048576 of 37162512 USN bytes processed)
..99 percent complete. (36544512 of 37162512 USN bytes processed)
100 percent complete. (37158912 of 37162512 USN bytes processed)
1003716251237162512
37162512 USN bytes processed.Usn Journal verification completed.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.20972825 KB total disk space.
4006312 KB in 15167 files.
4472 KB in 1744 indexes.
0 KB in bad sectors.
120741 KB in use by the system.
65536 KB occupied by the log file.
16841300 KB available on disk.4096 bytes in each allocation unit.
5243206 total allocation units on disk.
4210325 allocation units available on disk.The type of the file system is NTFS.
Volume label is DATA.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 24000 file records processed)
1 percent complete. (2400 of 24000 file records processed)
.. 8 percent complete. (19200 of 24000 file records processed)
9 percent complete. (21600 of 24000 file records processed)
102400024000
24000 file records processed.File verification completed.
10 percent complete. (1 of 2 large file records processed)
1022
2 large file records processed.1000
0 bad file records processed.1000
0 EA records processed.11 percent complete. (3399 of 10707 reparse records processed)
12 percent complete. (6800 of 10707 reparse records processed)
13 percent complete. (10201 of 10707 reparse records processed)
131070710707
10707 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)...
13 percent complete. (1 of 65735 index entries processed)
13 percent complete. (506 of 65735 index entries processed)
..89 percent complete. (64987 of 65735 index entries processed)
90 percent complete. (65337 of 65735 index entries processed)
906573565735
65735 index entries processed.Index verification completed.
9055
5 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)...
91 percent complete. (1804 of 24000 descriptors processed)
92 percent complete. (5205 of 24000 descriptors processed)
93 percent complete. (8606 of 24000 descriptors processed)
94 percent complete. (12006 of 24000 descriptors processed)
95 percent complete. (15407 of 24000 descriptors processed)
96 percent complete. (18808 of 24000 descriptors processed)
97 percent complete. (22208 of 24000 descriptors processed)
972400024000
24000 security descriptors processed.Security descriptor verification completed.
97672672
672 data files processed.CHKDSK is verifying Usn Journal...
98 percent complete. (0 of 34960464 USN bytes processed)
98 percent complete. (1048576 of 34960464 USN bytes processed)
..99 percent complete. (34136064 of 34960464 USN bytes processed)
100 percent complete. (34959360 of 34960464 USN bytes processed)
1003496046434960464
34960464 USN bytes processed.Usn Journal verification completed.
135307462 KB total disk space.
1675316 KB in 10763 files.
4416 KB in 673 indexes.
0 KB in bad sectors.
128414 KB in use by the system.
65536 KB occupied by the log file.
133499316 KB available on disk.4096 bytes in each allocation unit.
33826865 total allocation units on disk.
33374829 allocation units available on disk.The type of the file system is NTFS.
Volume label is DATA.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 13808 file records processed)
1 percent complete. (1381 of 13808 file records processed)
.. 8 percent complete. (11047 of 13808 file records processed)
9 percent complete. (12428 of 13808 file records processed)
101380813808
13808 file records processed.File verification completed.
10 percent complete. (1 of 1019 large file records processed)
1010191019
1019 large file records processed.1000
0 bad file records processed.1000
0 EA records processed.1000
0 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)...
11 percent complete. (289 of 44046 index entries processed)
11 percent complete. (803 of 44046 index entries processed)
..92 percent complete. (43898 of 44046 index entries processed)
93 percent complete. (43931 of 44046 index entries processed)
934404644046
44046 index entries processed.Index verification completed.
9355
5 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)...
94 percent complete. (1663 of 13808 descriptors processed)
95 percent complete. (3792 of 13808 descriptors processed)
96 percent complete. (5922 of 13808 descriptors processed)
97 percent complete. (8051 of 13808 descriptors processed)
98 percent complete. (10181 of 13808 descriptors processed)
99 percent complete. (12310 of 13808 descriptors processed)
991380813808
13808 security descriptors processed.Security descriptor verification completed.
100631631
631 data files processed.
312560608 KB total disk space.
252543004 KB in 10767 files.
3512 KB in 633 indexes.
0 KB in bad sectors.
89424 KB in use by the system.
65536 KB occupied by the log file.
59924668 KB available on disk.4096 bytes in each allocation unit.
78140152 total allocation units on disk.
14981167 allocation units available on disk.The type of the file system is NTFS.
Volume label is DATA.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.CHKDSK is verifying files (stage 1 of 3)...
0 percent complete. (0 of 11264 file records processed)
1 percent complete. (1127 of 11264 file records processed)
.. 8 percent complete. (9012 of 11264 file records processed)
9 percent complete. (10138 of 11264 file records processed)
101126411264
11264 file records processed.File verification completed.
1000
0 large file records processed.1000
0 bad file records processed.1000
0 EA records processed.1000
0 reparse records processed.CHKDSK is verifying indexes (stage 2 of 3)...
11 percent complete. (463 of 38287 index entries processed)
12 percent complete. (921 of 38287 index entries processed)
..92 percent complete. (37572 of 38287 index entries processed)
93 percent complete. (38030 of 38287 index entries processed)
933828738287
38287 index entries processed.Index verification completed.
9355
5 unindexed files processed.CHKDSK is verifying security descriptors (stage 3 of 3)...
94 percent complete. (801 of 11264 descriptors processed)
95 percent complete. (2634 of 11264 descriptors processed)
96 percent complete. (4466 of 11264 descriptors processed)
97 percent complete. (6299 of 11264 descriptors processed)
98 percent complete. (8132 of 11264 descriptors processed)
99 percent complete. (9965 of 11264 descriptors processed)
991126411264
11264 security descriptors processed.Security descriptor verification completed.
100533533
533 data files processed.
390700768 KB total disk space.
13004600 KB in 10657 files.
3112 KB in 535 indexes.
0 KB in bad sectors.
89140 KB in use by the system.
65536 KB occupied by the log file.
377603916 KB available on disk.4096 bytes in each allocation unit.
97675192 total allocation units on disk.
94400979 allocation units available on disk. - 0
Jeshimon wrote: The next time I see it I will take screen shots of the whole thing. Nice to see someone admit it might be a problem after all this time. One of the volumes in the data store was reported as failing. This drive has been reported as failing once before. It was installed new on 03/06/2008. The chkdsk of D: shows:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.C:\Documents and Settings\Administrator>d:
D:\>chkdsk
The type of the file system is NTFS.
Volume label is DATA.WARNING! F parameter not specified.
Running CHKDSK in read-only mode.CHKDSK is verifying files (stage 1 of 3)...
11344 file records processed.
File verification completed.
38 large file records processed.
0 bad file records processed.
0 EA records processed.
10495 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
45325 index entries processed.
Index verification completed.
5 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
11344 security descriptors processed.
Security descriptor verification completed.
575 data files processed.
CHKDSK is verifying Usn Journal...
36495136 USN bytes processed.
Usn Journal verification completed.291587782 KB total disk space.
15575708 KB in 10691 files.
6528 KB in 576 indexes.
0 KB in bad sectors.
122598 KB in use by the system.
65536 KB occupied by the log file.
275882948 KB available on disk.4096 bytes in each allocation unit.
72896945 total allocation units on disk.
68970737 allocation units available on disk.D:\>
on 3/26/2008 I had run WHSCleanup, it came up with a single error, the doc file for WHSCleanup which I had open in word on another computer.
It is unclear to me at this point in time how things are really working. I am unclear on a couple of things. I have read and understand the theory, but realistic observations lead me to question some things...
In observing Duplication info while copying large video files to my WHS it is clear that they are landing on a drive other than DATA, which happens to be the largest available drive which also happens to have the least free space. The files get migrated off, the volume goes from 91% full and red as indicated by disk management add in down to about 84% and yellow.
When I do a directory /s of D: I get:
Total Files Listed:
9622 File(s) 596,115,715,083 bytes
1671 Dir(s) 282,785,558,528 bytes freeWhat should be my D: DATA drive is what is left from a 298 GB drive after 20 GB system partition is taken from it or 278 GB clearly we don't fully the mechanism and it is not fully documented.
- 0
Dear T. Headrick
We felt hope when you entered this discussion, as you seemed honest and admitted this might be a bug, which should be dealt with. You asked for more details, and several WHS operators have answered. Could you please take the time to look at this matter? The WHS still indicates the SYS volume is failing about once a week.
Regards,
Christen
- 0
Christen A wrote: Dear T. Headrick
We felt hope when you entered this discussion, as you seemed honest and admitted this might be a bug, which should be dealt with. You asked for more details, and several WHS operators have answered. Could you please take the time to look at this matter? The WHS still indicates the SYS volume is failing about once a week.
Regards,
Christen
Hi Christen,
I'm sure they aren't simply ignoring the problem, it's probably just that with the corruption bug situation our issue naturally doesn't have the highest priority. My SYS volume also keeps failing once a week, so I guess I simply have to remain patient.
Regards,
Dirk
- 0
OK, OK, but I think it is worth looking into. First, it might be connected to the corruption issue. Files becoming corrupt and file system errors (or strange warnings of such) are more than likely related. It's anyway a serious issue, making people exchange hardware and spending hours on testing - so there should be a warning about this a place everybody would notice it. Furthermore, both issues make me wonder how WHS passed the beta phase. The corruption issue must be caused by bad design (it wouldn't take so long to fix it unless there is need for some serious rewriting of the whole thing). To this date, WHS has cost me too many hours of work, and with these errors it's not really to any use yet. Microsoft should give away some serious extras to fix this first impression. WHS obviously isn't their flagship product, but it could have given people a far better impression (I'll stick to Novell at work and buy as few Windows servers as at all possible). I wrote in my first post that I missed a way to backup the server itself, but was told by several "besserwissers" that there was really no reason for doing that. Then I was told that I certainly had a HDD problem when I reported the sys failing message. Turns out I was right both times, there are definitely reasons for backing up WHS (like people losing files due to the corruption issue), and the sys failing message is false (or at least not hardware related). So what can I really trust WHS to do? To this date, nothing.
I just hoped that the fact that one of the moderators asked us detailed questions, would mean that they would start troubleshooting this.
Christen
