Mark Minasi's Reader Forum
Mark Minasi's Reader Forum
Home | Profile | Register | Active Topics | Active Polls | Members | Search | FAQ | Minasi Forum RSS Feed
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 HALP! Questions on Windows and Windows Server
 Windows Home Server
 The Device Is Not Connected for All/Most Files
 New Topic  Reply to Topic
 Printer Friendly
Author  Topic Next Topic  

Phylum
Welcome Newcomer

3 Posts
Status: offline

Posted - 01/24/2012 :  10:24:29 AM  Show Profile  Reply with Quote
Accessing WHS share today, tried to open a notepad file containing some licenses and I received an error. I then tried from the WHS itself and got the same error. Every file I've tested in various folders in varying types, has resulted in the same 'The Device is Not Connected error. (You can view an image of the error here: http://social.microsoft.com/Forums/getfile/54580/)

I attempted to access the files via:

  • the UNC path to the share (e.g.: \\my_whs_server\software) and providing credentials when prompted (new desktop; connector Not installed yet)

  • RDP'ing to the server (e.g.: mstsc /v:my_whs_server) and logging on as the Administrator


Everything I've seen online are the results of hard drive failures and disk replacements, but:
  • none of my drives failed

  • none of the drives were replaced

  • no new drives added

  • the server didn't tank in any way

  • no restores or repairs were performed


  • I've run the following in an effort to try to fix it but there's been no change:

    @echo off
     
    rem restart delay: 80secs by default
    set restart_secs=80
    
    echo. & echo Stopping the Windows Home Server Drive Letter Service
    sc stop pdl >nul
    
    echo. & echo Stopping the Windows Home Server Computer Backup Service
    sc stop whsbackup >nul
    
    for %%a in (D C) do (
         echo. & echo Running chkdsk for %%a:
         chkdsk %%a: /x /r
    )
    
    for /D %%a in (C:\fs\*) do (
         echo & echo Running chkdsk on %%a
         start chkdsk /x /r %%a
    )
    
    echo. & echo Restarting server in %restart_secs% seconds
    shutdown -r -f -t %restart_secs%



    Other than that, the server seems to be working fine.

    Somewhat of a disappointment is that although there are icons for 'files', the actual files don't appear to truly be there. I was nearing storage capacity (nearly 1TB) on the server and while checking diskmgmt I noticed it claimed there's 92% free space on the disk. This isn't right at all.


  • How can *.* get deleted/wiped or suddenly/seemingly go missing 'overnight' so to speak?

  • What would cause diskmgmt to think there's no physical data on the drive but leave 'stubs' that Explorer interprets as files?

  • If I can't recover this data, is there anything else I can do to figure out what happened so I can avoid this in the future?



  • This is probably the most important question: If WHS is intended to be a backup solution, how do we go about protecting the backup?

    I get that if I had everything on one hard drive and that drive tanked, I would get the 'we told you so' for not backing up that data. Thankfully WHS is here to not only backup my systems in the event of a situation where a restore is necessary, but also misc files as well. (Music, Photos, Software etc) So here's a situation where the backup (which is WHS) has tanked and I've seemingly lost everything.
    Again I query: What's the backup of the backup (which is WHS)?

    don2007
    Honorable But Hopeless Addict

    1974 Posts
    Status: offline

    Posted - 01/31/2012 :  9:08:21 PM  Show Profile  Reply with Quote
    I have never used WHS, so my following opinions are just that, opinions or better yet guesses. IMO, any drive can go bad instantly. Backups can be on logical partitions or physical partitions. I'm sure you already know the difference. If not, ask for an explanation between the two.

    If I run into a drive where data recovery is needed, I use backtrack Linux to attempt a recovery. There are other distributions that are favored by other users. Either way, a boot CD has to be created & used to boot the machine. Then the original hard drive has to be mounted & read. I use the following commands:
    fdisk -l (that's the letter l)That will tell me if the hard drive is seen. If it is, it will probably say /dev/sda1 or something similar.
    Then I would run the following commands:
    cd /mnt
    mkdir ntfs
    ln -s /dev/sda1 /mnt/ntfs
    cd /mnt/ntfs
    ls -asl |more

    You should see the missing files. If you do there are ways to copy them across the network, once you connect the NIC
    That would be:
    dhclient eth0




    Dyslexic people untie.
    Go to Top of Page
       Topic Next Topic  
     New Topic  Reply to Topic
     Printer Friendly
    Jump To:
    Mark Minasi's Reader Forum © 2002-2011 Mark Minasi Go To Top Of Page
    This page was generated in 0.11 seconds. Snitz Forums 2000