Solved

SBS 2008 USB Drive not detecting

Posted on 2015-02-16
47
278 Views
Last Modified: 2016-06-26
We have a SBS 2008 server that has 2 removable USB hard drives which are rotated on a daily basis, everything has been working fine for the last 2-3 years on this basis however recently the SBS server has stopped detecting one of the removable USB hard drives when its rotated and plugged in.

When I run the Western Digital utils the hard drive is connected and can be scanned but USBTools reports Access denied and the volume could not be mounted as shown below, I have no idea whats going on and nothing has recently changed to my knowledge.

Mountpoints       = no recognized volumes on disk
Bus Type          = USB
Drive Type        = fixed
Device Types      = ReadAccessDenied
Drive DevID       = USBSTOR\DISK&VEN_GENERIC&PROD_USB3.0_DEVICE&REV_0000\AA3000000135&0
Ctrl  DevID       = USB\VID_152D&PID_0539\AA3000000135
Ctrl2 DevID       = USB\ROOT_HUB20\4&2F77B1A7&0
Host Ctrl DevID   = PCI\VEN_8086&DEV_293A&SUBSYS_03321025&REV_02\3&E89B380&0&EF
Host Controller   = Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
Disk DosDevNames  = \Device\Harddisk1\DR5, \Device\00000077
Removal Policy    = surprise removal ('Optimize for quick removal')
Hotplug Device    = yes
Hotplug Media     = no
Removable Media   = no
Friendly Name     = Generic USB3.0 Device USB Device
Requested Power   = 2 mA (self powered)
USB Version       = 2.1 (High-Speed)
USB Friendly Name = JMicron USB3.0 Device
USB Serial        = AA3000000135
USB Port Name     = 7-2
Problem           = device didn't respond for 6 Seconds

If the SBS server is rebooted the drive is detected and works fine until it is removed and re-inserted at which point a repeat of the above occurs and it does not appear even in the computer management console.

Any ideas?
0
Comment
Question by:Tahir2008
  • 19
  • 14
  • 8
  • +3
47 Comments
 
LVL 46

Expert Comment

by:noxcho
ID: 40613898
Once the USB drive is detected and has a drive letter - check it with CHKDSK x:/f where x: is a drive letter of the volume on USB drive.
Then check in registry if automount is enabled. Per Start - regedit - start regedit.exe navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MountMgr\NoAutoMount
NoAutoMount must be set to 0.

Check this drive on different computer. Connect/disconnect several times. Does it behave the same?
And finally check if the problem is in detection or mounting. Once you connect the drive to SBS server and it does not show itself - go to Windows Disk Management - is there a drive without drive letter?
if yes then this tool can be a solution for you: http://www.uwe-sieber.de/usbdlm_e.html
0
 
LVL 76

Expert Comment

by:arnold
ID: 40613908
The issue might be that the drive or the enclosure is dying.
can you attach the USB drive to any other system without an issue?

Check whether the drive letter is in use when you run into this issue.
i.e. when the drive is attached, it has been associated with the drive letter F:
something has changed i.e. an admin mapped F: as \\someotherserver\someshare


But in this case, the message is that it is a hardware related issue.
Does the enclosure have its own AC connected power supply or tries to draw power from the USB feed?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40613913
The USB drive seems to work fine on any other computer when plugged in and works fine on the SBS 2008 server but only after a reboot, the CHKDSK /F shows the following:

C:\Windows\system32>chkdsk z: /f
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is BackupDrive2.

CHKDSK is verifying files (stage 1 of 3)...
  256 file records processed.
File verification completed.
  0 large file records processed.
  0 bad file records processed.
  0 EA records processed.
  0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  282 index entries processed.
Index verification completed.
  0 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  256 security descriptors processed.
Security descriptor verification completed.
  13 data files processed.
Windows has checked the file system and found no problems.

 976759807 KB total disk space.
 518715944 KB in 12 files.
        20 KB in 15 indexes.
         0 KB in bad sectors.
     96015 KB in use by the system.
     65536 KB occupied by the log file.
 457947828 KB available on disk.

      4096 bytes in each allocation unit.
 244189951 total allocation units on disk.
 114486957 allocation units available on disk.

The drive does not even appear in Disk Management to check for drive letter assignments however it is present when running the Western Digital utility.
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40613920
So this is a USB3.0 drive, right? Can you connect it to USB2.0 and see if you get it detected?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40613921
I don't believe the server itself supports USB3.0 and I have 2 of these drives, the other works first time no problem.
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40613940
Does this drive have its own power supply?
Get another USB drive and see if it works same well. You need to narrow the problem either to server or to the drive.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40613941
The issue is likely that when it is removed, it is not done so cleanly. so at times, the system still sees the device as connected even though it is not.

Yes, I see the USB policy is for such removal.  One thing to check when the drive is not mounting, whether it is still reflected in device manager i.e. uninstall/rescan of HW changes ......
0
 
LVL 76

Expert Comment

by:arnold
ID: 40613942
Are both drives connected at the same time and does each have their own drive letter or are they configured to use the same drive letter?
0
 
LVL 70

Expert Comment

by:Merete
ID: 40613948
Completely agree with above suggestion,
 as you say here> that has 2 removable USB hard drives which are rotated on a daily basis, <<
Are you using the safely remove? mass storage device?
If you use that and get a message you cannot then go the task manager explorer and stop it then go to file in task manager and new task > explorer. That may remove any dependencies software accessing it.
Windows maybe accessing it with some back ground tasks, I feel you just need to release any hold windows has on it.
Why rotate them?
Have you ever defragged them?
0
 
LVL 37

Expert Comment

by:Gerwin Jansen
ID: 40613961
The drive itself looks to be a small Western Digital 2.5" USB powered drive (self powered), if that's the case and you've swapped it on a daily basis for 2-3 year I'm afraid it may just be end of life. I'd just get a new one, copy the data onto it and use the new one from now on. These bus powered drives have usually a 1 year warranty.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40614094
Hi,

Both of these drives are standard 3.5" drives which are externally powered and are rotated on a daily basis. I use a program called USB Tools to assign the same drive letter to both drives when they are rotated daily, this ensures the backup software can perform the backup as required.

I have never used the safely remove hardware option, we just unplug the power and data, then swap it over and re-insert and this has always worked without any issues until now. I have tested using the safely remove hardware option and it does the same thing, the drive after being disconnected and reconnected is not detected in the OS.

The problematic drive does not appear in device manager under storage volumes or in the disk management and is only accessible via the Western Digital diagnostic tool and when outputting the information from USBTools to notepad as pasted above.

The problematic drive works fine when removed and reinserted multiple times in other computers except the SBS 2008 server, it only appears after a reboot of the server. Automount does seem to be enabled as when the other drive is plugged in it loads and is mounted fine and when the server is rebooted this drive is also detected and auto mounted.

Any suggestions as its really annoying?
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40614163
Well, a dumb question, are you connecting it to the same USB port or tried different?
Furthermore, do you have a powered USB hub where you could connect the drive through? This way you can be sure that power is not an issue here. As you know yourself the list of suspects is pretty long in this very moment thus we need to narrow it.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40614168
I looked at other forums and have tried different USB ports and the result is the same. There is no USB hub powered or otherwise involved, the external USB drive is connected directly to the server.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40614189
This was mentioned earlier, the only reason it is not redected is that when it was removed the OS reflected it as being in use.  One option you can is uninstall it when it does show up in the device manager (after reboot if necessary) and then let the OS reinstall/adds it.

Yes, I do understand that the two are the same and have the same driver.  You can also look at the registry key for the device since they each have a unique identifier. HKLM\software\microsoft\windows\mountpoint2
HKLM\hardware\devicemap\scsi\ and see whether this is where it is
HKLM\system\currentcontrolset\mounteddevices

One of these or perhaps another that I can not think of at this time, has the reference as to why this particular device is having an issue.
Was suggested, since a reboot of an SBS is not always available, getting another one and adding it into the rotation instead of this one.  Since the issue only exists with one of identical drives, it is simpler to diagnose an issue by removing this device.  If the issue reoccurs with another device, one could look at the server, but I suspect the issue is with the device (external enclosure)
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40614331
Have you tried completely uninstalling USB concentrator from Device Manager - reboot and reinstall it again?
Powered USB hub was a suggestion that you try the drive with it.
0
 
LVL 30

Expert Comment

by:pgm554
ID: 40614935
And the WDiag says everything looks good?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615003
The Wdiag just detects the drive and allows me to run tests on the drive, these all pass.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40615028
Note your error message points to a non-response to access of more than 6 seconds.
The testing part does not require the drive to be mounted.
But it is of little consequence.  
Here is the summary of the situation.  you have two identical external enclosures/drives that you've been using for more than a year (two, etc.)
one drive recently started misbehaving.  There drives are used for backup in a rotation, presumably the rotation is for offsite DR type of consideration.  How comfortable are you with this drive that is exhibiting these types of issue to be the drive that is offsite should anything bad happen. If you are comfortable with this risk, I will be more that glad to try and see if it can be determined what the issue is.
If you rather have a stable setup without any hiccups, issues, get another drive to replace this one, make sure it too when connected to the SBS is recognized and gets the correct letter assigned. Then monitor whether the issue reoccurs with the new drive and the older twin in the rotation.  If no issues, you are set and can use the misbehaving drive as you see fit, I would not use it to store important/sensitive information  just in the event the enclosure/drive is dying.

What you will know from this is that should the other identical drive that will remain in the rotation starts exhibiting similar symptoms, you will know right away that it is going bad, and will replace it.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615111
Hi Arnold,

Thanks for the reply however this is an Enterprise Hard Drive, and I have performed all the standard diagnostics on which clearly indicate there is no problem with the drive. When inserting this drive onto another computer it works without any problems and also works on the SBS 2008 server but only after a reboot. This to me does not appear to indicate an issue with the drive or enclosure but instead points to a problem somewhere on the OS.

A lot of people have reported similar issues without a suitable fix and I would like to get to the bottom of it as I had an issue such as this previously but found a workaround which was ideal at the time but is not suitable in this scenario. I need to fix this problem moving forward, replacing a working drive/enclosure is viable if there are time constraints but at present I do not have any.

Can anyone shed any further light on the matter?
0
 
LVL 76

Expert Comment

by:arnold
ID: 40615130
One way to validate whether the issue is with the enclosure would be to crack it open, replace the drive and see if the behavior persists.

The issue with the SBS which clears up after reboot points to a resource that for one reason or another bound to this drive. Try stopping/restarting the backup service/vss/volume shadow presumably this is one of the resources on which the backup relies to avoid having an impact on the operation of the system.

i.e. you ran a backup, but it took longer than usual, the person charged with rotating the drives, pulled this drive not knowing that the backup software still had it open for ......

etc.
when the drive is reinserted, the SBS still sees a "resource" that is "accessing it" and thus does nothing.

you could try getting procmon from the sysinternals MS site and check the resources your system has versus the resources some components are accessing to identify.........

The question is not whether or not what you have is suitable (enterprise or otherwise) you are having an issue, which can be resolved, while the underlying issue with the enclosure/drive is assessed.  

Have you looked at the backup software logs to see whether it has an event dealing with the drive becoming inaccessible prior to completing the tasks?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615183
Hi Arnold,

I doubt that is the issue because I can reboot the server and the drive is then detected, I can unplug the drive and then re-plug with the drive not being detected by the OS, at this point no backup software or resources are in use.

The enclosure can be replaced as its a custom enclosure meaning its not one supplied with an enclosed hard drive inside.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40615204
The custom enclosure could make it better. Do you have another enclosure laying around?
Or an extra drive? Looking to change one item, the enclosure or the drive to see whether the issue still exists. if replacing the drive and the issue remains, the enclosure might be the culprit.
The other option using your existing enclosures would be to swap the drives between the enclosures. to see whether the issue follows the drive or follows the enclosure.

i.e. currently you have
Enclosure 1 with Drive A
Enclosure 2  with Drive B
Since the data and drive assignments are preset and bound to the USB enclosure. you change to have:
Enclosure 1 with Drive B
Enclosure 2 with Drive A.

Now which enclosure is experiencing this issue if any.
If enclosure 2, you know the issue is likely with Drive A,
If enclosure 1 is till having this issue, you know it is enclosure 1 or the OS reference to this USB ID.....

If it shifts with the drive, you've solved the problem, if not, you will have to continue hunting.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615212
Hi Arnold,

I will give that a shot tomorrow and provide an update as this may help pinpoint some issues with either the enclosure or drive if any.
0
Scale it in WD Gold

With up to ten times the workload capacity of desktop drives, WD Gold hard drives employ advanced technology to deliver among the best in reliability, capacity, power efficiency and performance.

 
LVL 70

Expert Comment

by:Merete
ID: 40615512
Adding to Arnold thoughts as they seem to run in similar lines,  if you could copy/transfer the data off problem drive then format the drive  put the data back on.
I sometimes see a message from windows that it can't access one of my USB drive and wants to format it.
Allowing windows to format it seems to give it a new footprint.
I also occasionally see a message that certain USB ports are slower than others and windows recommends using a different port.
Do you have front and rear?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615515
Hi Merete,

Yes i already tried this approach and formatted the volume but it did nothing to resolve the issue. I did read somewhere that formatting the volume via XP helps but have not tried this as of yet.

There is a front and rear but like i said the other drive works fine and so does this problematic drive after the server is rebooted using the same and different USB ports.

Thanks for the input, really appreciate it, the more the merrier as this is a real annoying problem.
0
 
LVL 70

Expert Comment

by:Merete
ID: 40615560
Tahir2008
Could you also look into the USB tool your using?
SuperSpeed USB Software and Hardware Tools
http://www.usb.org/developers/tools/#compliancedevice
http://www.usb.org/developers/tools/
Possibly a windows updates changed something in the registry and now forces you to update this tool?
My line of thinking there is a problem between this software assigning the drive letter and how windows detects your drive/s.
I'll leave you to test the suggestion from Arnold.
Thankyou and good luck :)
regards Merete
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40615972
Hi Merete,

No windows updates have been performed as far as I am aware so I dont think this could be the problem but will take a look at this as well thanks.
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40616032
Tahir, have you tried uninstalling USB devices via Device Manager as suggested?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40616262
Hi,

Just tried a brand new HDD enclosure and the drive did the same thing, when server is rebooted it is detected but the moment the drive is removed and put back on the server is it not seen by the OS. Plugging the drive with new enclosure in another machine works fine as it did in its older enclosure.

I have also tried to format the drive on a Windows XP PC as someone said this could resolve the issue but this has not resolved the problem either.

I have uninstalled USB devices and then re-scanned and this also did not resolve the issue.

Any further ideas? I do think its more of a OS issue though the backup job that failed last night said a hardware device was not functioning but does not provide details.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40616313
If the issue follows the drive, the drive might be the issue.  You said the drives are enterprise class, but the error says no response in more than 6 seconds.  I think ENT class should respond within 4 seconds.

Note your issue follows drive given you have two identical enclosure and only one has issued. Drive is the common thread.
0
 
LVL 70

Expert Comment

by:Merete
ID: 40616332
Can you see it in safemode?
have you tried unmounting just for windows?
looking at your events>
Friendly Name     = Generic USB3.0 Device USB Device
Requested Power   = 2 mA (self powered)
USB Version       = 2.1 (High-Speed)<<<could this be related?
USB Friendly Name = JMicron USB3.0 Device
Could be a problem with a registry logging a bad unclean dismount?
Try cleaning up registry
Over time your registry can become cluttered with errors and broken settings  CCleaner’s patented registry cleaner clears out this clutter
https://www.piriform.com/ccleaner
GUIDE recommended reading first.
registry cleaning
https://www.piriform.com/docs/ccleaner/using-ccleaner/registry-cleaning
Main how to
http://obrienpc.net/recommended-programs-ccleaner/

and then this>
USBTools reports Access denied and the volume could not be mounted

please see this option below, to use a terminal cmd to format the drive,
Partitioning USB hard drives that fail in Disk Utility with 'POSIX' error..
Quote>If the problem is just a matter of overcoming a default partition scheme or format incompatibility over USB connections when using Disk Utility, you can use terminal commands as alternatives to initially format the drive and hopefully allow it to be accessible via Disk Utility again.
Before running these commands, you will need to find the disk identifier for the attached USB drive device.
To do this, open Disk Utility and select the drive device itself. Then click the "info" button and note the name of the "Disk Identifier" field. Pictures included
continue here
http://www.cnet.com/news/partitioning-usb-hard-drives-that-fail-in-disk-utility-with-posix-error/

Running out of ideas, Replace the drive or face considering re-installing SBS 2008 server as the registry may have conflicts?
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40616361
If you put another drive into the same enclosure - does it work properly?
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40633066
I have installed a brand new 1 TB Western Digital drive to replace the existing one in the caddie and it seems to mount by the server with no problems. Clearly there is something wrong with the drive or the OS which doesnt like it, the caddie itself is fine. This is the new report from the replacement drive, can anyone see why the previous one would not mount?

MountPoint        = Z:\
Volume Label      = BackupDrive2
Volume Size       = 1 TB (NTFS, 4 KB clusters)
Volume Serial     = E0B7-DB90
Disk Size         = 1 TB
Volume Name       = \\?\Volume{26be6f1a-b7b3-11e4-a68b-00241dbaf1c8}\
Partition Name    = \Device\Harddisk1\Partition1
Bus Type          = USB
Drive Type        = fixed
Device Types      = ---
INI Sections      = [DriveLetters10]
Volume DevID      = STORAGE\VOLUME\1&19F7E59C&0&SIGNATUREDBABE910OFFSET100000LENGTHE8E0B00000
Drive DevID       = USBSTOR\DISK&VEN_GENERIC&PROD_USB3.0_DEVICE&REV_0000\AA3000000135&0
Ctrl  DevID       = USB\VID_152D&PID_0539\AA3000000135
Ctrl2 DevID       = USB\ROOT_HUB20\4&2F77B1A7&0
Host Ctrl DevID   = PCI\VEN_8086&DEV_293A&SUBSYS_03321025&REV_02\3&E89B380&0&EF
Host Ctrl Name    = Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
Volume DosDevName = \Device\HarddiskVolume9
Disk DosDevNames  = \Device\Harddisk1\DR10, \Device\00000080
Removal Policy    = surprise removal ('Optimize for quick removal')
WriteCache        = yes (because NTFS)
Hotplug Device    = yes
Hotplug Media     = no
Removable Media   = no
Partition Number  = 1 of 1
Friendly Name     = Generic USB3.0 Device
Requested Power   = 2 mA (self powered)
USB Version       = 2.1 (High-Speed)
USB Friendly Name = JMicron USB3.0 Device
USB Serial        = AA3000000135
USB Port Name     = 7-2

I don't have the time to check this but I may try a low level format of the drive which is not recognized by the OS and see if that could resolve any issues as to why the OS/Drive is not being detected. I guess as before no solution to the problem but just another workaround.
0
 
LVL 46

Expert Comment

by:noxcho
ID: 40633095
Can you connect that suspect drive internally to any SATA port on other machines and do full test with its vendor made tools?
Lifeguard or Seatools (depending on the drive). It would be interesting to know if anything is reported.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40633228
The issue is that the caddie/drive did not respond in time.  Based on the error it took the caddie/drive more than 6 seconds
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40633440
Hi Arnold,
I don't agree, the problem may be appearing like that but the drive itself is fine as is the caddie, we have already gone over this multiple times. I have also tested on a new caddie with the same result.

Noxcho, the life-tools report no problems, I have also tested using SeaTools, both long test and short test pass with no errors.

Tahir
0
 
LVL 76

Expert Comment

by:arnold
ID: 40633613
Agree, We went over the caddie being fine, the operation of the caddie/drive in a different computer without an issue, The issue with this system, various caddies ( you used at least three) and this drive have the same results. i.e. one system, three caddies, one drive results in the drive not being mounted (seen by the system) and thus not being assigned a drive letter).

I would agree that there is a possibility/likelyhood that the SBS within the registry (services/hardware) map after reboot does not have an entry for this any Caddie/drive combination (since you confirmed that the caddie is not the culprit, I'll refer to the combination as the drive) mapping and will see the drive and will assign it a drive letter. Once the drive is detached from the system, it will not be recognized.

Done with drive as caddie/drive reference.

Depending on your SBS, attach the drive directly into the SBS since it sounds as though the impression is that the drive is dead and can not be used. On the contrary as long as you take into account that this drive might have issues, you can use it in any capacity you wish directly plugged into the SBS via cable.

Here is the situation, the replacement of the drive resolved your issue.

SBS <=> USB INPUT Caddie <=> Caddie SATA INTERFACE  <=> Drive

What we know so far is that the SBS will not wait more than 6 seconds for the caddie to present the DRIVE ID DATA.
Other system (workstation) might be by default more tolerant i.e. they will wait for 10 seconds.
Replacing the drive results in no issues/ delay exceeding 6s when connecting to this SBS.
With that said, the SBS to Caddie via USB communication is not the cause for the delay.
We could make the assumption/presumption that the data transfer within the caddie logic SATA interface to USB output is reasonable and uniform no matter the drive attached.
The only issue is left deals with SATA communications between the caddie interface and the drive.
In a worse case scenario: The SBS to Caddie via USB consumes 5 seconds, the time it takes the caddie controllers to transfer data from the SATA side to the USB side consumes .9 seconds
or we can do the SBS to caddie via USB is .9 and the internal logic within the caddie consumes 5 seconds.

now new drives or the other existing drives to caddie via SATA interface respond in less than .1 seconds consistently; thus not exceeding the 6 second threshold of SBS timeout for HW connection via USB.

This drive takes .11 seconds to respond to the caddie command thus exceeding the 6 second wait time on the SBS.
Spin up delay, read head into position delay, etc. pick one.

blaming the drive for the issue is the straight forward conclusion.  Unless the drive is made of paladium, with gold circuitry with diamonds adorning the controller interface, and unless it is required to be used in this rotation for this purpose, its use can be shifted elsewhere.
The alternative to prove us all wrong, you would format the SBS, reinstall everything, .......?

The difficult part is that the drive does not show up when attached not in the device manager nor does it remain in the device manager when detached (i.e. when it is detached, the system still reflects this particular drive as attached under the disks) trying to hunt for its key/id within the HKLM hardware\software\mountpoint2 location might be something you wish to explore, i.e. deleting its reference/key may resolve this.

Though as you pointed out several time, rebooting the SBS only makes the drive work once (as long as it is not disconnected).


I believe the culprit in your situation has been identified (the drive) and the issue resolved.
0
 
LVL 1

Accepted Solution

by:
Tahir2008 earned 0 total points
ID: 40662045
I believe I may have managed to fix this issue now. It clearly is not related to the hard drive caddie or speeds of the HDD as mentioned above as a far as I can see. After swapping Drive 2 for a brand new 1 TB drive which fixed the issue Drive 1 started having the same problem so I attempted a low level format by downloading a utility online and after this completed, I re-created the partitions as normal and the drive started working as normal.

I believe that something may cause the drive to become corrupted at a particular level which prevents the OS from re-mounting the drive and as far as I can see at present the low level format resolves this by clearing the drive properly.

I hope this resolves the issue again if it re-occurs and hope it at least helps others with a similar issue.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40662499
When you need to reformat a drive to regain functionality suggest there is an issue with the drive.  Use the smart interface to get a report about the drive.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40662834
As outlined already both long and short tests on the hard drive do not indicate any faults or problems.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40664692
Drives developing bad blocks, bad sectors, are dying drives I've found.  Reformatting/rechecking the drive such that those bad blocks/bad sectors are labeled. The smart technology is not a guarantee if the drive passes the minimum criteria that it is not .......

Given you had two drives with the same enclosures and of the same age encounter a similar issue, You can not attribute the issue in the way the SBS writes/reads the data nor can you attribute it to the Enclosure controller/interface.

Not sure how the drive is used is the backup a clone/imaging type i.e. images the source onto the drive in the enclosure?

I wish you the best.
0
 
LVL 1

Author Closing Comment

by:Tahir2008
ID: 40670006
Resolved the issue directly and resolution provided.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40789975
Just to add to this case, the issue occurred again and the only solution to resolve it was to use Diskpart to wipe the volume data and then format the drive from the system that needs to access it, this resolved the issue.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40790037
If you are fine with periodically wiping data off, that is one thing. IMHO, based on "Murphy's Law" the data on the drive will be needed in the most inconvenient circumstance but would not be accessible.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40790052
It works fine in any other machine to access, its just for some reason when the drives are rotated on the SBS server maybe once in 6-7 months it will then just stop mounting the device and throwing the above read error, but if connected to any other computer/server it will load fine so access of the data is not the issue.

The issue is having a notification that the backup has failed because the drives were rotated and the server failed to mount it and assign the appropriate drive letter, this in itself can also be fixed by just rebooting the server but having to do that each time the drives are rotated is a pain and not necessary. So, the above fix on the drive which is a pain resolves the issue from my testing on this problem so far.
0
 
LVL 76

Expert Comment

by:arnold
ID: 40790115
When you rotate the drives, do you make sure it is not in use and eject it?
If you are comfortable with this.
0
 
LVL 1

Author Comment

by:Tahir2008
ID: 40790118
Yes, the rest of the process works fine. The response above was specifically for the purpose of the rotated drive not being assigned a drive letter when swapped.
0

Featured Post

Give your grad a cloud of their own!

With up to 8TB of storage, give your favorite graduate their own personal cloud to centralize all their photos, videos and music in one safe place. They can save, sync and share all their stuff, and automatic photo backup helps free up space on their smartphone and tablet.

Join & Write a Comment

Before I left on my recent vacation to float, boat and waterski on a lake in Minnesota for a week, I checked my phone to make sure there was enough room for photos of my obsession: sunsets. There wasn't. Has this ever happened to you?
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now