Asked by:
File Conflict Error - Another Unhappy Customer

Question
-
Folks - you need to provide some more detail re this issue. I've reviewed all the exisiting messages and questions re the issue after finding this evening I have a series of Failing Shares /Healthy Shares, a pair of missing 500GB drives (showing as "healthy" non storage drives in server storage that has a Total Size of "empty"), and a whole bunch of File Conflicts within the failed shares. And yes when I go in via the console I get full access to all the files and see no disk corruption at this stage. No doubt I'll find tombstones like others have. And yes I'm rapidly dumping my small (thankfully) amount of pictures and music off to USB drives and what ever storage I can spare.
However good it is - the advice telling me and others previously to back my data off to another device and "rebuild or replace failed" drives and "rebuild" or the other various attempts to resolve this issue is clearly not addressing the root cause - we are merely bandaging the symptoms. Its very clear there is a bug that is being uncovered by multiple customers overtime.
So - can you update your loyal supporters and enthusiasts what are the current bug fix plans and is there a timeframe to address the issue ? Is there any triage happening on this ?
You guys are winning awards and accolades for what is becoming a very positive product offering for many people.
For an issue thats had over 2000 views - clearly it deserves real attentionThursday, March 26, 2009 4:17 AM
All replies
-
There are many causes of "file conflict" errors; it seems they're all external to Windows Home Server so far, i.e. some hardware issue, or some software issue outside of WHS is causing the error. Have you reviewed this FAQ? Have you submitted a bug as requested there?
I'm not on the WHS team, I just post a lot. :)Thursday, March 26, 2009 4:47 AMModerator -
Tubster said:I don't agree. If it was a bug, there would be a lot more users complaining about it. Besides, the File Conflict notification is a good thing to have. Without it (the way it was pre-PP1), WHS would just merrily go along without any notification while files are messed up in the background. That would be a disservice to every single person who owns one. Also, the "root cause" is almost always A) hardware related (which is your problem) or B) some app keeping file(s) open for more than 24 hours so DE can't make a duplication pass on that file. Either way, it's not the fault of the OS.
Folks - you need to provide some more detail re this issue. I've reviewed all the exisiting messages and questions re the issue after finding this evening I have a series of Failing Shares /Healthy Shares, a pair of missing 500GB drives (showing as "healthy" non storage drives in server storage that has a Total Size of "empty"), and a whole bunch of File Conflicts within the failed shares. And yes when I go in via the console I get full access to all the files and see no disk corruption at this stage. No doubt I'll find tombstones like others have. And yes I'm rapidly dumping my small (thankfully) amount of pictures and music off to USB drives and what ever storage I can spare.
However good it is - the advice telling me and others previously to back my data off to another device and "rebuild or replace failed" drives and "rebuild" or the other various attempts to resolve this issue is clearly not addressing the root cause - we are merely bandaging the symptoms. Its very clear there is a bug that is being uncovered by multiple customers overtime.
Now as to your specific problem, it's would seem to be tied to your missing drives. What types of drives are those (SATA, PATA, USB, FireWire)? Please give as many details about your hardware as possible.
Tubster said:The reason it has so many views is because most users who do get that message don't know what it means.So - can you update your loyal supporters and enthusiasts what are the current bug fix plans and is there a timeframe to address the issue ? Is there any triage happening on this ?
You guys are winning awards and accolades for what is becoming a very positive product offering for many people.
For an issue thats had over 2000 views - clearly it deserves real attentionThursday, March 26, 2009 4:53 AMModerator -
Thanks for the prompt answer guys. Seems on further checking I have had an unplanned shutdown and subsequent recovery ("the previous system shutdown at 1:08:00 AM on 3/24/2009 was unexpected.") All the issues are post that from the event logs that I've studied.
Re the server - its a stock build fully patched HP Mediasmart ex470 with two SATA 500GB drives in it. Its been 100% ok until I found the issue. It provides backup for some 8 machines in my home network.
The drives in question are are not missing - they are showing as Non Storage Hard drives that are healthy and available for use. The server storage shows them as being empty. (Ie Total Size and Free Space show as Empty). As of two days ago they showed as duped drives with about 35% shared usage.
When when I access the box via the console the drives and all their attached files are there and accessible and the files are not corrupted or missing. Ie they open (pictures), and they play (music) etc
Seems all the log entries errors point to software issues from the power failure.
From System Event Log- Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on Thursday, March 26, 2009 at 10:00 AM: - Windows Home Server Power Pack 2 (KB956587)
- (whats this then - Power Pack 2 ?)
- Application popup: Windows - Registry Hive Recovered : Registry hive (file): SOFTWARE was corrupted and it has been recovered. Some data might have been lost.
(Ouch )
And from Home server Event Log - Assertion failure at d:\wssg_src\whs_pp1\qhs\src\storage\qsm\qsm.hxx(932): !g_pSysLock->IsLocked()
- The Windows Home Server Console cannot open because the following file is blocking it: C:\Program Files\Windows Home Server\HomeServerConsoleTab.AutoExit.dll.
Clearly I'm rebuilding...sigh
I wonder how many other "hardware issues" are actually really software corruption from similar events.Thursday, March 26, 2009 6:26 AM