locked
WHS server Chkdsk stuck at stage 4 for 2.5 days and still stuck RRS feed

  • Question

  • The server has 2 1TB drives and was working fine until it just started to drop the nic connection and then reconnect and drop. Then i was getting this in the from Remote Notification



    Log: Application

    Type: Error

    Event: 0

    Agent Time: 2012-03-24 21:03:14Z

    Event Time: 02:02:50 AM 25-Mar-2012 UTC

    Source: Remote Notification

    Category: None

    Username: N/A

    Computer: HMESERVER

    Description: Got Error: qsm.bbe136ee-0000-0000-0000-000000000000.Object Type:WHS_NOTIFICATION_ADD Head:Storage Status Desc:Hitachi HDS721010CLA332 has failed. Ensure it is connected. If this problem continues, add a new hard drive and then remove the failed hard drive from your server storage using the console.

    I also noticed the server is blue screening with this error code

    Log: System

    Type: Error

    Event: 1003

    Agent Time: 2012-03-24 09:34:38Z

    Event Time: 02:36:24 PM 24-Mar-2012 UTC

    Source: System Error

    Category: (102)

    Username: N/A

    Computer: HMESERVER

    Description: Error code 00000077, parameter1 c000000e, parameter2 c000000e, parameter3 00000000, parameter4 00905000.

    So i ran Hard Disk Sentinal and that showed both drives as perfect. THen i ran a chkdsk on C: and that came up good so i ran a chkdsk on D: and now its stuck at CHKDSK is verifying file data (Stage 4 of 5)...

    No percentage showing and now files counting either. I know a 1TB drive will take long but i didnt think 3 days.

    What is the procedure to replace this D: Drive. If i can get passed this chkdsk and replace the D drive will i have to reinstall the OS.

    Wednesday, March 28, 2012 3:20 PM

Answers

  • I will respond to my own answers so this may help someone else with the same issue.

    I did a hard shutdown and reinserted the old drive along with the new drive. I booted up and checked the drives to see if they were in UDMA one was PIO so i uninstalled the IDE Drivers in Device Manager and rebooted.  Then couldn't get into the Console so i looked at the logs and saw something related to network connection so i reconnected the LAN connection and rebooted. Now i could access the console. I did a removal of the drive that was giving me issues and it was a 1TB and it took about 30 min to complete. When that finished i ran the updates and for whatever reason it reinstalled PP3 did that and rebooted and rechecked the drives to see if they were in UDMA and so far everything working back to normal. Hope the helps anyone.

    • Marked as answer by Valcon54 Friday, March 30, 2012 10:37 PM
    Friday, March 30, 2012 10:37 PM

All replies

  • Also i think the HDD error log is related to the BSOD when it crashes i think that Remote Notification sends this error out.
    Wednesday, March 28, 2012 3:21 PM
  • Which version of WHS are you using?

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Wednesday, March 28, 2012 5:13 PM
  • Windows Home Server Console: 6.0.2423.0
    Windows Home Server Backup & Restore: 6.0.2423.0
    Windows Home Server Drive Extender: 6.0.2423.0
    Windows Home Server Remote Access: 6.0.3436.0
    Windows Home Server Storage Manager: 6.0.3039.0

    Also i have PowerPack 3 and all windows updates as of March 20 2012

    Wednesday, March 28, 2012 5:57 PM
  • chkdsk finally finished and this is the result so i assume the drives are fine and possible that the crashing is caused by the Nic Driver or RAM

    Checking file system on D:

    The type of the file system is NTFS.

    Volume label is DATA.

    A disk check has been scheduled.

    Windows will now check the disk.

    CHKDSK is verifying Usn Journal...

    Usn Journal verification completed.

    CHKDSK is verifying file data (stage 4 of 5)...

    File data verification completed.

    CHKDSK is verifying free space (stage 5 of 5)...

    Free space verification is complete.

    CHKDSK discovered free space marked as allocated in the

    master file table (MFT) bitmap.

    Windows has made corrections to the file system.

    955771109 KB total disk space.

    599854112 KB in 68383 files.

    33436 KB in 11122 indexes.

    0 KB in bad sectors.

    252605 KB in use by the system.

    65536 KB occupied by the log file.

    355630956 KB available on disk.

    4096 bytes in each allocation unit.

    238942777 total allocation units on disk.

    88907739 allocation units available on disk.

    Internal Info:

    d0 de 01 00 9d 36 01 00 e6 0e 02 00 00 00 00 00 .....6..........

    50 1c 00 00 83 85 00 00 b8 00 00 00 00 00 00 00 P...............

    72 20 9a 19 00 00 00 00 0e aa 59 84 00 00 00 00 r ........Y.....

    e6 c6 83 1a 00 00 00 00 e6 8a 6f c1 d9 01 00 00 ..........o.....

    ac e9 63 ea 07 00 00 00 38 b0 ec aa e2 01 00 00 ..c.....8.......

    d0 d5 fa 9a 00 00 00 00 ad 9d 82 7c e3 00 00 00 ...........|....

    1f 0b 01 00 00 00 00 00 00 80 30 04 8f 00 00 00 ..........0.....


    Wednesday, March 28, 2012 8:18 PM
  • I ran the manufactures hdd test utility and it passed the drive but the bios had an error on the drive in the event log. So i removed the drive that is supposedly bad and replace it. When i boot up to windows i clicked on remove drive (bad One) and it said it will take several hours but it has been running for 24 now is this normal for a 1TB drive? Also while this is removing the bad drive the system is really slow.
    Friday, March 30, 2012 2:20 PM
  • I will respond to my own answers so this may help someone else with the same issue.

    I did a hard shutdown and reinserted the old drive along with the new drive. I booted up and checked the drives to see if they were in UDMA one was PIO so i uninstalled the IDE Drivers in Device Manager and rebooted.  Then couldn't get into the Console so i looked at the logs and saw something related to network connection so i reconnected the LAN connection and rebooted. Now i could access the console. I did a removal of the drive that was giving me issues and it was a 1TB and it took about 30 min to complete. When that finished i ran the updates and for whatever reason it reinstalled PP3 did that and rebooted and rechecked the drives to see if they were in UDMA and so far everything working back to normal. Hope the helps anyone.

    • Marked as answer by Valcon54 Friday, March 30, 2012 10:37 PM
    Friday, March 30, 2012 10:37 PM