locked
Is this a "Normal" recovery experience? RRS feed

  • Question

  • Ok here goes...1 of my 3 drives failed today, no warning just showed up as "missing" after a reboot.  I tried to remove it a couple of times and each time it would get to almost the end and then just stop so i disconnected it and it still shows in the drive pool.  Subsequently a ton of file conflict errors showed up saying that the files cannot be found, but when i go to the folders the files are there.  Luckily i had backed up the files that i needed from the shared folders yesterday so for some things i needed to access i deleted the folder that had the conflicts, created them again and copied the back-up files to the newly created folder and now no conflicts for the new folder but ones that i've not done this process to, the conflicts are still there.  i can do this for the other folder also but i'm just wondering if this is normal?  it seems to me that the major issue here is that the failed drive still shows in the drive pool even though i've disconnected it.  also how can i get this drive out of my pool?  i've rebooted the system a few times since i disconnected it, from the console and from the start menu.  should i try to remove it again and let it run all night while my office is closed?  while i'm open we need to access the server and while it's being removed we can't access anything.
    Wednesday, November 5, 2008 8:55 PM

All replies

  • Hi,

    If it doesn't complete the Drive Removal operation through the Console, (this can appear to be very slow towards it's completion, especially if there is limited free space), then just unplug the drive, just as you did, but then run the Drive Removal tool once again.
    If you had Duplication enabled, then replacing that failed drive and enabling Duplication again, should start WHS duplicating the missing files.

    Colin





    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    • Marked as answer by ncinsguy Wednesday, November 5, 2008 9:17 PM
    • Unmarked as answer by ncinsguy Thursday, November 6, 2008 4:03 PM
    Wednesday, November 5, 2008 9:02 PM
    Moderator
  • duplication has already begun and is working though most of the duplication is being done to the free space on the sys drive.  you mentioned enabling duplication again...are you saying i should disable it on all folders then enable it again?
    Wednesday, November 5, 2008 9:09 PM
  • Hi,

    If it's started itself, then no worries. It's just that sometimes, if time is short, disabling/re-enabling Duplication will trigger it into action sooner.

    Colin





    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Wednesday, November 5, 2008 9:11 PM
    Moderator
  • ncinsguy said:

    are you saying i should disable it on all folders then enable it again?


    interpreting this way could lead to data loss. Imagine, you disable duplication, the original disk is broken, but the duplicates are still there. Maybe the existing duplicates are getting deleted (as one user in the forums experienced in the past, if I understood his description correctly). So you don't have the originals and the duplicates any more.
    Removing the disk with the original files via console will cause die former duplicates become the new original. Only after that process is completing and the files are not duplicated again, a short toggle of folder duplication may be helpfull.
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 12:00 AM
    Moderator
  • Olaf Engelke said:

    interpreting this way could lead to data loss. Imagine, you disable duplication, the original disk is broken, but the duplicates are still there. Maybe the existing duplicates are getting deleted (as one user in the forums experienced in the past, if I understood his description correctly).
     
    FYI Olaf, if the server is completely up-to-date with all critical updates installed, that should no longer be an issue.  See KB950193.

    Olaf Engelke said:

    So you don't have the originals and the duplicates any more.
    Removing the disk with the original files via console will cause die former duplicates become the new original. Only after that process is completing and the files are not duplicated again, a short toggle of folder duplication may be helpfull.
    Best greetings from Germany
    Olaf



    Thursday, November 6, 2008 2:45 AM
    Moderator
  • i took the hdd that came up as "missing" home and guess what...i put it in an external hdd enclosure and it reads fine.  i ran check disk and it checked out fine though it did make two unusual clicks when it spun up.  why did WHS say it failed but it reads fine?  should i hook it back up to WHS to see if it works?  did it show up as misssing because of a glitch or could the drive be going bad?  i started the disk removal process again when i left the office to see it would finish overnight.  like i said earlier the duplication process had already begun and most of the files i checked were already done when i left about 4 hrs ago.  what should i do?
    Thursday, November 6, 2008 3:25 AM
  • Hi,
    sometimes we cannot be fully sure, what causes a disk to jump out.
    The best method usually is to check the event log of the server.
    You tried already a chkdsk /f /r on that disk, while it was connected to another PC?
    If this did not bring up anything, it may be, that there have been some wierd timing issues (spinning up too late or something like that). If the disk supports SMART (what usually each modern disk does) you could try to check the SMART parameters of the disk.
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 7:13 AM
    Moderator
  • the chkdisk i ran was from the disk properties, is that the same as chkdsk /f /r?  How do i check SMART parameters? 
    Thursday, November 6, 2008 3:17 PM
  • ncinsguy said:

    the chkdisk i ran was from the disk properties, is that the same as chkdsk /f /r?  How do i check SMART parameters? 

    if you have set the two check boxes on the dialog window, it is the same.
    S.M.A.R.T parameters you cannot check with built in tools, there are a lot of hardware monitoring tools outside as freeware or shareware, which read the relevant status informations from the hard disks.
    I have not such a tool installed currently, and it may depend from your hardware what works fine.
    But the whs diskmanagement add on is well known and should do the job
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 3:35 PM
    Moderator
  • These are the errors i get when it told me the drive was missing:

    Event Type: Error
    Event Source: HomeServer
    Event Category: Backup
    Event ID: 272
    Date:  11/5/2008
    Time:  10:05:47 AM
    User:  N/A
    Computer: LSSERVER
    Description:
    Unexpected error 0x48f from CreateFile on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Commit.dat: The device is not connected.

    Event Type: Error
    Event Source: HomeServer
    Event Category: Backup
    Event ID: 267
    Date:  11/5/2008
    Time:  10:05:47 AM
    User:  N/A
    Computer: LSSERVER
    Description:
    Client Backup server failed at d:\wssg_src\whs_pp1\qhs\src\backup\util\diskfile.cpp(145)

    The following 3 errors have occurred everyday since I built the system the drive that failed was at Position 3:

    Event Type: Error
    Event Source: HomeServer
    Event Category: PersistentDriveLetter
    Event ID: 1280
    Date:  11/5/2008
    Time:  10:05:52 AM
    User:  N/A
    Computer: LSSERVER
    Description:
    Persistent Drive Letter Service failed: Starting service: No attempts to start the service have been made since the last boot.

    Event Type: Error
    Event Source: atapi
    Event Category: None
    Event ID: 5
    Date:  11/5/2008
    Time:  10:01:36 AM
    User:  N/A
    Computer: LSSERVER
    Description:
    A parity error was detected on \Device\Ide\IdePort0.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 0050000f 00a40001 00000000 c0040005
    0010: 80000003 00000000 00000000 00000000
    0020: 00000000 00000000 00000006 00000000
    0030: 00000000 00000007 8f000040 00000002
    0040: 120a2000 00200340 00000000 0000000a
    0050: 82726000 827ba988 00000000 827434c8
    0060: 00000002 02800fd3 80020028 0000d30f
    0070: 00000020 00000000

    Event Type: Error
    Event Source: Disk
    Event Category: None
    Event ID: 11
    Date:  11/5/2008
    Time:  10:01:36 AM
    User:  N/A
    Computer: LSSERVER
    Description:
    The driver detected a controller error on \Device\Harddisk0.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00680403 00ba0001 00000000 c004000b
    0010: 00000101 00000000 00000000 00000000
    0020: 001fa600 00000005 000000f8 00000000
    0030: ffffffff 00000002 8f000040 00000002
    0040: 120a2000 00200340 00000000 0000000a
    0050: 82726000 827ba988 00000000 827434c8
    0060: 00000002 02800fd3 80020028 0000d30f
    0070: 00000020 00000000 000400f0 0b000000
    0080: 00000000 00000308 00000000 00000000

    This warning caught my eye this was when I built the system:

    Event Type: Warning
    Event Source: Ftdisk
    Event Category: Disk
    Event ID: 57
    Date:  9/27/2008
    Time:  5:44:46 PM
    User:  N/A
    Computer: LSSERVER
    Description:
    The system failed to flush data to the transaction log. Corruption may occur.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00000000 00be0001 00000002 80040039
    0010: 00000000 c000000e 00000000 00000000
    0020: 00000000 00000000



     

    Thursday, November 6, 2008 3:48 PM
  • Hello, looks bad and ugly.
    One of the disks seems to have failed, as you already mentioned - physically, cabling issues, driver problems, bad controller, whatever.
    You do not happen to have one of the 1.5 GByte Seagate drives? (These seem to be well known for trouble currently.)
    Since tombstones, which are pointing to another disk, are located on disk 0, I cannot determine which disk is really affected from these errors.
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 4:01 PM
    Moderator
  •  i had 3 160gb drives on the system, 2 Maxtors and 1 Western Digital.  The WD drive is the sys drive and 1 of the Maxtors is the one that showed up missing which subsequently has tested to be ok.  what should i do with this system?  This is the first problem i've had, it works fine otherwise.  Are these errors going to continue?
    • Edited by ncinsguy Thursday, November 6, 2008 4:13 PM
    Thursday, November 6, 2008 4:10 PM
  • I'm suspicious of cabling or controller. Have all the drives you've had problems with been connected to the same controller/channel on the controller? Have you tried cable replacement?
    I'm not on the WHS team, I just post a lot. :)
    Thursday, November 6, 2008 5:31 PM
    Moderator
  • i've only had a problem with the one drive.  i replaced the problem drive with a temporary replacement and shows up.  i have not tried replacing the cable.  Drive 0 and 1 are on one cable and the problem drive and the dvd rom were on another cable.
    Thursday, November 6, 2008 5:50 PM
  • Hi,
    sometimes it is trivial - the SATA cables are not sitting well, so at a minor rearrangement in the case the can loose contact somewhat - at least the cheaper ones.
    Best greetings from Germany
    Olaf
    Thursday, November 6, 2008 8:46 PM
    Moderator
  • this is an ide setup.  if it were the cable would the replacement drive work?  sorry about all the questions but i just would like to know what i can do to minimize this and possible other issues that could pop up.  if i should change something just tell me so cause i can't lose the data on this server cause this one is in my office.  My tower is a business class IBM Netvista P4 2.53 GHZ with 512mb of ram. 
    Thursday, November 6, 2008 8:59 PM
  • Hi,
    if the SATA or IDE cable has some wear and tear, it may work as bad with the new drive as with the former drive.
    Best greetings from Germany
    Olaf

    Thursday, November 6, 2008 10:26 PM
    Moderator
  • temp replacement drive works fine with the same cable.  should i put the old drive back in to see what happens.  i'm gonna add a sata drive after i pull it from my system at home.  the temp drive is only 40gb and the one that told me it was missing is 160gb so i'd like to have the larger in the pool.
    Thursday, November 6, 2008 10:50 PM