none
Backup Fails With Error Code "2155348010"

    Question

  • Hello,

    I am attempting to complete a backup on a W2K8 STD server to an external USB drive. The devices are 120GB Samsung S1 Minis. I cannot complete either on-demand or scheduled backups to these devices. When I attempt a backup an error is almost immediately generated and the backup stops.

    The error displayed in WSB is:

    "One of the backup files could not be created. Detailed Error: The request could not be performed because of an I/O device error"

    A System event log error is also generated:

    Log Name:      Application
    Source:        Microsoft-Windows-Backup
    Date:          10/12/2009 1:34:14 PM
    Event ID:      517
    Task Category: None
    Level:         Error
    Keywords:     
    User:          GREYSTONE\administrator
    Computer:      GSERVER.greystone.local
    Description:
    Backup started at '10/12/2009 6:33:44 PM' failed with following error code '2155348010' (One of the backup files could not be created.). Please rerun backup once issue is resolved.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" />
        <EventID>517</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2009-10-12T18:34:14.286Z" />
        <EventRecordID>1906</EventRecordID>
        <Correlation />
        <Execution ProcessID="3060" ThreadID="1028" />
        <Channel>Application</Channel>
        <Computer>GSERVER.greystone.local</Computer>
        <Security UserID="S-1-5-21-3346377497-3916918110-3897609911-500" />
      </System>
      <EventData>
        <Data Name="BackupTime">2009-10-12T18:33:44.051Z</Data>
        <Data Name="ErrorCode">2155348010</Data>
        <Data Name="ErrorMessage">%%2155348010</Data>
      </EventData>
    </Event>

    I have tried several of these drives without success. I can move/copy/create/delete files to and from these devices through Explorer and I am able to complete a backup to an ext. drive from another mfg.

    Please Advise,

    Jay

    • Edited by jayfish Thursday, October 29, 2009 3:21 PM
    Monday, October 12, 2009 6:59 PM

Answers

  • The issue is that the Samsung drive has a 4096 byte sector size.   Windows server backup is not designed to run on such disks.    We will try and address this issue in a future release.

     

    However,  some disks with 4096 byte sector size do support and emulation mode for 512 byte sector.  I could not determine if this Samsung disk supports it or not.  You may need to contact the manufacturer and find if it supports it and what needs to be done to enable it.   

     

    If 512 sector size emulation can be enabled then windows backup will be able to use this disk.

    Thanks
    Abhinav

    Thursday, October 29, 2009 7:01 AM

All replies

  • Hi Jay,
    Can you run chkdsk /R on your USB drive and retry the backup? 

    Thanks
    Abhinav
    Tuesday, October 13, 2009 6:07 AM
  • No luck,

    Same result with the same error(s) generated.

    Jay
    Thursday, October 15, 2009 7:27 PM
  • please reply back to sbaid_at_microsoft.com (replace _at_ with @)

    and send the log files zipped at %windir%\logs\windowserverbackup
    ------- this information is provided as-is without any warranties, implicit or explicit.
    Friday, October 16, 2009 4:34 AM
  • Will do.

    Jay
    Tuesday, October 20, 2009 3:50 PM
  • The issue is that the Samsung drive has a 4096 byte sector size.   Windows server backup is not designed to run on such disks.    We will try and address this issue in a future release.

     

    However,  some disks with 4096 byte sector size do support and emulation mode for 512 byte sector.  I could not determine if this Samsung disk supports it or not.  You may need to contact the manufacturer and find if it supports it and what needs to be done to enable it.   

     

    If 512 sector size emulation can be enabled then windows backup will be able to use this disk.

    Thanks
    Abhinav

    Thursday, October 29, 2009 7:01 AM
  • Can you clarify "future release"? Boy MS, this backup product is a real winner. No tape, no REV, no RDX and only a certain subset of USB HHDs. Well done.

    Jay
    Thursday, October 29, 2009 2:41 PM
  • As of now it is not possible to provide a specific release in which this will be addressed. 

    Thanks
    Abhinav

    Friday, October 30, 2009 6:21 AM
  • Hi Abhinav and Jay

    I wonder if what you say about cluster size is correct.  I have a machine running Hyper-V server with four guest OS's on board.
    I plugged a 1.5 TB drive in an external enlcosure into a Dell computer and ran "wbadmin start backup -backupTarget:\\computername\Backup$  -include:e:,f: -allcritical -quiet" from the command prompt and it ran correctly, the backup was fine and a test restore of files from within it correct. The drive has 4096b clusters.
    I plugged the same drive into ah HP laptop and ran the same command from within a batch file and received the "2155348010" error.  I have not had the opportunity to move the drie back to the Dell just yet but I wonder if it might not be something to do with the block transport mechanism (SCSI subset) of the particular USB chipset.  In the case of HP machine the USB chipset is an Intel  82801G.  I don't have the Dell chipset at the moment.
    I take your statement that WBADMIN is not designed to use 4096b clusters on board but it does not necessarily mean that it won't work with them.  Do you have any thoughts on this?

    Lawrie

    Sunday, November 01, 2009 10:12 AM
  • It *might* work but most probably it will fail.  The real reason is that we use an I/O mode (for performance reasons) which allows I/only in multiples of disk sector size and only at file offsets that are multiple of sector size.  We always do I/O which is multiple of 512 bytes, but not neccessarily multiple of 4096 bytes.

    Note that disk sector size is different from the NTFS cluster size (which is 4096 bytes by default).  

    Also, if the storage stack of 4096 byte target is somehow emulating 512 byte sector size, backup should succeed.

    Thanks
    Abhinav
    Thursday, November 05, 2009 8:20 AM
  • I would just like to say i have the exact same problem.

    Dell Poweredge T605 server
    Server 2008 SP2
    Samsung S2 320GB HDD's

    Windows Server Backup gives error "One of the backup files could not be created. Detailed Error: The request could not be performed because of an I/O device error"

    Bring back NTBACKUP!!!!
    Wednesday, December 09, 2009 2:08 PM
  • This is actually a really annoying problem as very few hard drive manufactuers list the sector size or if it supports emulation. Question....Why is this problem not documented anywhere?????????
    Wednesday, December 09, 2009 4:25 PM
  • Does anyone know of any cheapish 2.5" 320GB external HDD's that do work with Server 2008 backup?

    Im struggling to find any that list the sector size and dont want to buy new drives without knowing for sure.

    Wednesday, December 16, 2009 5:49 PM
  • I'd have to Agree with QWAZ01

    I'm seeing this error code, but Backups have been working fine, for a year now, and just started happening
    However and it's not a SAMSUNG Drive
    But If it's really the case. (The Sector)?

    IMO I think there should be a KB at least on this??
    Is there one?

    Russ
    Russell Grover - SBITS.Biz Microsoft Gold Certified Partner Microsoft Certified Small Business Specialist
    Wednesday, December 30, 2009 10:29 AM
  • I'd have to Agree with QWAZ01

    I'm seeing this error code, but Backups have been working fine, for a year now, and just started happening
    However and it's not a SAMSUNG Drive
    But If it's really the case. (The Sector)?

    IMO I think there should be a KB at least on this??
    Is there one?

    Russ
    Russell Grover - SBITS.Biz Microsoft Gold Certified Partner Microsoft Certified Small Business Specialist

    I have this exact same problem.  my backups have been working fine, and now all of a sudden i get this error :error code 2155348010

    any other help available?
    Thursday, December 31, 2009 8:31 PM
  • if the backups has been working in past on a disk drive and failing now - it can not be the issue with the sector size on the disk.

    please send a email to sbaid_at_microsoft.com and absrivas_at_microsoft.com - we can follow up to help you out on that. (replace _at_ with @)
    ------- this information is provided as-is without any warranties, implicit or explicit.
    Friday, January 01, 2010 5:43 AM
  • Sushil, I refomated the drive and it's working again? (The backup Drive)
    Do you think this means that drive is going bad??
    Russ
    Russell Grover - SBITS.Biz Microsoft Gold Certified Partner Microsoft Certified Small Business Specialist
    Saturday, January 02, 2010 6:50 AM
  • Hi,

    Is there any update on the  4096 sector size issue.  

    We have just implemented SBS 2008 in our company, and brought 4 of these Samsung drives for are backups, only to find that they do not work.  It's a pity that the documentation did not mention that SBS 2008 does not support all portable media and list a selection of portable media that it does support, it would save us wasting £300.00 on these drives.
    Friday, March 12, 2010 2:56 PM
  • I can confirm that these external drives do work.........Western Digital My Passport Essential 320GB
    • Proposed as answer by lsoliveira99br Monday, February 25, 2013 5:49 PM
    Monday, March 15, 2010 11:03 AM
  • I am having the same error message with the Samsung S2 drive.  Does anyone know if there is a way to emulate or format the drive with 512byte (or compatible) sectors?
    Monday, May 24, 2010 6:25 PM
  • I am having this error with a Samsung S1 120GB drive, a new device from 2009 don't work, a old device from 2008 work.

    So is there a solution on this problem? Must we wait for the next Windows release, ServicePack or will there be an update soon?

    I really don't know which model I should buy, because there arn't any exact information which device support emulation or have 512 bytes per sector...

    I hope you are able to understand my english ;-) Greetings Martin

    Friday, July 23, 2010 10:25 PM
  • Same problem for me with a Samsung S2.

    Any updates to this problem?

    Wednesday, September 15, 2010 7:54 AM
  • Drives that work

    Samsung Story 1TB
    WD Passport 320GB and 500GB
    Seagate Expansion 1TB

    Drives that don't work

    Samsung S2
    Freecom Mobile Classic

     

     

     


    Carol
    Monday, October 18, 2010 4:16 PM
  • This is ridiculous, just spent a good sum of money on a Seagate GoFlex Desk 3TB HDD and now I cant backup my server? I mean honestly! Spend so much on a server and OS and cant even backup something.
    Thursday, December 02, 2010 7:01 AM
  • I am encountering this problem, too. New PC running Win7 Ultimate 64-bit, backing up to a 1TB IOMEGA USB drive.

    Saturday, December 18, 2010 11:38 PM
  • Cripes.  I just bought 2 new IOMEGA 1TB eGo drives to backup a small dev site running Windows 2008 R2.  Flush $300 down the tubes. 

    Thanks MS.  No where in the Windows 2008 Server Backup documentation does it state that a specific USB drive must be used.  I.E. require a specific sector size of 512 as I'm now discovering in the forum. 

    "backup the request could not be performed because of an I/O device error"

    This backup tool is utterly worthless with USB drives!

    Saturday, January 15, 2011 7:14 AM
  • I experience the same issue with a WD Mybook Essential 1130 USB-Disk which is used with a Windows Server 2008 r2 x64

    The reply from Abhinav on October 29, 2009 stating "We will try and address this issue in a future release"  is, as far as I know, still not met and the latest release of Windows Server Backup is Version 1.0. I couldn't find any newer release anywhere...

    After more than 1 year this problem should have been fixed, especially because almost all new harddrives are using the new standard of 4096 byte sector sizes.

     

    Please let us know when we can expect a update for Windows Server Backup...

    Wednesday, January 26, 2011 10:33 AM
  • Wow, they didnt fix this in 2008 R2 even though they knew about it? I found it ridiculous enough this was even an issue in 2008 which is what Im using.

    I CANNOT ACCEPT THAT AFTER ALL THIS TIME A HOTFIX/SP FOR THIS HAS NOT BEEN RELEASED.

    Any ETA on this happening?!

    Monday, February 21, 2011 7:37 PM
  • This is still not fixed.  And the silence from Microsoft is infuriating.

     

    Friday, March 18, 2011 2:16 PM
  • Same problem here.  Just installed brand new SBS2008 server and 5 x new iOmega eGo USB3 drives.  Backups fail and I can't use a sector size less than 4096.

    Hugely frustrating.

    Shame on MS for not resolving this undocumented "feature" since it was first reported over a year ago!


    John Auletta
    Tuesday, March 22, 2011 12:09 PM
  • Hello,

    Same here : every new iomega external disk have a 4096 sector size -> enable to use with Windows 7 or Windows Server backup ....

    Micrososft : Please update your backup tool.

     

     

    Friday, April 01, 2011 9:06 AM
  • Also having this problem, Seagate FreeAgent 750 GB drive.
    Saturday, April 09, 2011 12:30 PM
  • To ALL:
    Some of these drives people mention are designed for PC Backups (Yes PC's not servers) Which they will sometime Auto Shutdown, to save energy, and also have other "Energy" saving Features. (Software and sometimes firmware on the drive)

    This means that they will sometimes SHUTOFF When they don't detect I/O for some time and thus you do not get a backup. (This IMO is why you should avoid "GREEN" USB Drives for backups.)

    When the HD shuts down of course BACKUPS WILL FAIL!!

    This is not Microsoft's Fault!!!

    In addition to shutting down another common issue with these is when you power cycle your server and the USB External Drive does not show up. (Because of the "POWER Save Feature of the drive.)

    Because these "Features" are not a Microsoft Issue or there is no way they can fix your drive.

    I recommend getting a Drive that is either designed for Server backup, or get a simple USB External Drive case, (Generic with no Energy saving) and put in your own drive.

    As said ALSO!
    In addition avoid drives with the 4K Sector format.
    Keep to 512k which is what the server was designed for.


    If this is not a good solution and you want the 4K sector drives there are always third party software solutions. (I honestly wouldn't expect Microsoft to Redesign their backup in a product to accept large sectors.)

    Russ

    Russell Grover - SBITS.Biz [SBS-MVP] MCP, MCPS, MCNPS, SBSC
    Remote Small Business Server/Computer Support - www.SBITS.Biz
    Redirect to Microsoft's SBS Public Forum - www.SBSRepair.com 

    (This Thread should be closed IMO)

     




    Saturday, April 09, 2011 9:02 PM
  • To ALL:
    Some of these drives people mention are designed for PC Backups (Yes PC's not servers) Which they will sometime Auto Shutdown, to save energy, and also have other "Energy" saving Features. (Software and sometimes firmware on the drive)

    This means that they will sometimes SHUTOFF When they don't detect I/O for some time and thus you do not get a backup. (This IMO is why you should avoid "GREEN" USB Drives for backups.)

    When the HD shuts down of course BACKUPS WILL FAIL!!

    This is not Microsoft's Fault!!!

    In addition to shutting down another common issue with these is when you power cycle your server and the USB External Drive does not show up. (Because of the "POWER Save Feature of the drive.)

    Because these "Features" are not a Microsoft Issue or there is no way they can fix your drive.

    I recommend getting a Drive that is either designed for Server backup, or get a simple USB External Drive case, (Generic with no Energy saving) and put in your own drive.

    As said ALSO!
    In addition avoid drives with the 4K Sector format.
    Keep to 512k which is what the server was designed for.


    If this is not a good solution and you want the 4K sector drives there are always third party software solutions. (I honestly wouldn't expect Microsoft to Redesign their backup in a product to accept large sectors.)

    Russ
    (This Thread should be closed IMO)

    Did you even read this thread? The first half of your reply suggests otherwise! The issues we are facing have nothing to do with 'green/auto shutdown drives'. Its the 4K sector size thats an issue.

    This thread should NOT be closed. Have you seen where HDD's are heading? Everyone is going the 4K sector size route to cope with bigger HDD size demands. So please, dont come with your 512b sector size drives are enough and all a server needs. Some of us like to keep up with the times.

    Microsoft - Fix this. Now.


    Web Hosting | Web Design | Web Development | SEO (Search Engine Optimisation)



    Monday, April 18, 2011 9:25 AM
  • Russ

     

    Please read the thread before wasting half of your response on irrelevant info.


    John Auletta
    Tuesday, May 10, 2011 10:49 AM
  • It was additional information for those that read it in the future

    Not just current posting

    Remember others will read this and learn.

    That is the purpose of the extra....

    And no this is not Microsoft's fault

    Russ

    Tuesday, May 10, 2011 4:28 PM
  • It was additional information for those that read it in the future

    Not just current posting

    Remember others will read this and learn.

    That is the purpose of the extra....

    And no this is not Microsoft's fault

    Russ


    Well, then I guess we should just post any thing that could be an issue, instead of the issue this thread is about.  People, make certain that your USB drive has power.  Also, make certain that the USB drive is plugged into a USB port.

    See how silly this is?

    And it is Microsoft's fault if they are not going to support off the shelf USB drives but only ones that have certain requirements, then it is up to them to inform us of those requirements on the product, in this case Windows Server 2008 and Windows Server 2008 R2.  And the fact that these requirements are so absurd (name another product that has them!), they should also list some drives that were verified as working.

    They did this with Windows 7 Phone during the whole MicroSD card fiasco - why not with one of their flagship products?

    But you just keep on drinking that MS kool aid, Russ.  It's good work you're doing - asking that this thread be closed and contributing nothing to the actual problem being addressed.  /sarcasm (<- just for you Russ!)

     

    Tuesday, May 10, 2011 5:58 PM
  • Do you have Model #'s for any of the 1TB drives you found that worked?

     

    Thanks,

    Brett M.

    Tuesday, May 10, 2011 6:25 PM
  • Drives that work

    Samsung Story 1TB
    WD Passport 320GB and 500GB
    Seagate Expansion 1TB

    Drives that don't work

    Samsung S2
    Freecom Mobile Classic


    CarolChi
    Wednesday, May 11, 2011 5:17 AM
  • I just ran into this issue myself with a new 1.5TB Iomega eGo.  There's absolutely no doucmentation about the fact it uses a 4K sector size, nothing about emulation, and nothing from Microsoft saying that the Backup program requires 512 sector drives.  This is insane!  This issue is over a year old.  Microsoft has updated their OSes to support larger disks but the Backup program still does not!  Is anyone at Microsoft working to update the backup program?  What am I supposed to do in the meantime?

     

    • Proposed as answer by MW61 Wednesday, May 18, 2011 11:48 PM
    Wednesday, May 11, 2011 11:55 AM
  • I'm getting the sam error I have a WDC 3TB USB 3.0 drive which I just purchasad. This does support Advanced format 4K sector and should be supported by Windows Server 2008 R2 SP1. Microsoft just realeased a hot fix to resolve advanced fromat disk drive issues (4096 hard sectors). I'm trying it now, but thought I'd give folks a heads up. http://support.microsoft.com/kb/982018.


    MW61
    Wednesday, May 18, 2011 11:48 PM
  • I'm getting the sam error I have a WDC 3TB USB 3.0 drive which I just purchasad. This does support Advanced format 4K sector and should be supported by Windows Server 2008 R2 SP1. Microsoft just realeased a hot fix to resolve advanced fromat disk drive issues (4096 hard sectors). I'm trying it now, but thought I'd give folks a heads up. http://support.microsoft.com/kb/982018.


    MW61

    Good catch!  Please let us know your results
    Thursday, May 19, 2011 2:28 PM
  • Update on KB982018 and Windows 2008 R2 SP1 support for advanced format for non-512 byte sector drives. No luck. KB hotfix was applied, but Windows Backup utility still gives same error code, 2155348010. Per the KB article, applications have to be updated to support the format which I'm betting the Backup software is still needed.

    Another question I now if apps have to be updated to support the format, is besides the Backup Utility, do other apps, i.e. Windows Recovery Tools, have to also be updated.

    Any thought?

    Thanks,


    MW61
    Friday, May 20, 2011 4:45 PM
  • I've been looking for a solution to this problem as well.  I have tried both the update mentioned above and Service Pack 1 - no luck.  I tried to create a VHD on the drive with no luck, then created a vhd on another drive and copied it to the seagate 3tb disk.  Copies ok, but when you tried to mount it you get a specific error about the 4k drive not supported.

    This issue is specifically a problem with Windows Backup and M$ will need to fix it so that we can continue to use inexpensive external drives for backup.

    Here's my work around so far:

    1.  Create Dynamically Expanding VHD on an internal drive.

    2.  Attach VHD and configure Windows Backup to use the VHD

    3.  Run the Backup

    4.  Detach VHD

    5.  Copy VHD to External Drive

    6.  Re-Attach VHD

    Ok.  This is a poor solution and the copy is slooower than the backup, but it gets it done if you have enough internal HDD space to do it.

    The next step is to script the "detach / copy / attach" process and schedule it after the backup.  Something like:

    diskpart

    select vdisk file=backup.vhd

    detach vdisk

    exit

    copy d:\backup.vhd e:\backup /Y (this will overwrite the existing file, depending on your retention policy you might need to do something different)

    diskpart

    select vdisk file=backup.vhd

    attach vdisk

    exit

    exit

    It's not an elegant script and I don't have anymore time to test it tonight.  I'll work on it tomorrow.  Does anyone have a better method to script this?


    Thursday, May 26, 2011 5:33 AM
  • You can add Iomega eGo 1TB to the list of drives that don't work.  This is using SBS 2011.
    Thursday, June 02, 2011 1:47 PM
  • Add Iomega Prestige 2 TB USB 2.0/3.0 Desktop Hard Drive to the list of external USB drives that aren't supported by Windows 7 Backup, due to these large capacity drives having 4096 bytes/sector size and Microsoft's software being hard-coded to 512 bytes/sector.

    This needs to be fixed by Microsoft asap.

    Meanwhile, looks like we'll need to find a 3rd-party backup tool...

    Saturday, June 11, 2011 4:05 AM
  • It was additional information for those that read it in the future

    Not just current posting

    Remember others will read this and learn.

    That is the purpose of the extra....

    And no this is not Microsoft's fault

    Russ


    Well, then I guess we should just post any thing that could be an issue, instead of the issue this thread is about.  People, make certain that your USB drive has power.  Also, make certain that the USB drive is plugged into a USB port.

    See how silly this is?

    And it is Microsoft's fault if they are not going to support off the shelf USB drives but only ones that have certain requirements, then it is up to them to inform us of those requirements on the product, in this case Windows Server 2008 and Windows Server 2008 R2.  And the fact that these requirements are so absurd (name another product that has them!), they should also list some drives that were verified as working.

    They did this with Windows 7 Phone during the whole MicroSD card fiasco - why not with one of their flagship products?

    But you just keep on drinking that MS kool aid, Russ.  It's good work you're doing - asking that this thread be closed and contributing nothing to the actual problem being addressed.  /sarcasm (<- just for you Russ!)

     

    The answer was posted by a Microsoft Representative.
    Drinking Cool-Aid has nothing to do with giving the correct answer.
    Taking personal shots at me just shows the professionalism of your comments.
    I hope that you do well in your professional career...
    Best Wishes...
    Subject Closed.
    Russ


    Saturday, June 11, 2011 4:20 AM
  • I found the easiest solution was to purchase an internal WD Caviar Black drive and an external USB enclosure. Most all the external drives now are 4K. 
    Monday, June 13, 2011 12:45 PM
  • Just found a hotfix from Microsoft for this specific issue

    http://support.microsoft.com/kb/982018

    Friday, June 24, 2011 3:34 PM
  • KB982018 ist not fixing this problem.

    I´ve got two Seagate FreeAgent GoFlex Desk 3 TB USB 2.0 and they are not working with Windows Server Backup on SBS 2011 (based on Server 2008 R2 SP1). Thanks to Microsoft!

    Most (All? I don´t know one working with Windows Server Backup!) of these external high capacity drives have 4096 bytes/sector size and Microsoft's software is only able to handle 512 bytes/sector. This thread has been started in October 2009 and nearly two years later, there is no solution from Microsoft. It´s a shame.

    This has to be fixed asap! Under these circumstances a professional use of the integrated backup solution in SBS 2011 is impossible.

     

     

    Wednesday, July 13, 2011 2:22 PM
  • I for one have clicked the NO button on the compatibility page and reported the problem. This problem should be listed as a compatability issue.

    http://www.microsoft.com/windows/compatibility/windows-7/en-us/Details.aspx?type=Hardware&p=Iomega%20500GB%20Prestige%20External%20Hard%20Drive&v=Iomega&uid=34169&l=en-US&pf=0&pi=5&s=iomega&os=64-bit

     Note: this is for Windows 7 / IOMEGA Prestige 500 GB drives. Other manufacturers will have different links...

     


    G H

    Thursday, July 14, 2011 7:25 AM
  • I for one have clicked the NO button on the compatibility page and reported the problem. This problem should be listed as a compatability issue.

    http://www.microsoft.com/windows/compatibility/windows-7/en-us/Details.aspx?type=Hardware&p=Iomega%20500GB%20Prestige%20External%20Hard%20Drive&v=Iomega&uid=34169&l=en-US&pf=0&pi=5&s=iomega&os=64-bit

     Note: this is for Windows 7 / IOMEGA Prestige 500 GB drives. Other manufacturers will have different links...

     


    G H

     

    You are checking NO? on the compatability With Win7 when the issue is a Server?

    Please let me know why that is a no?
    (Or did you give the wrong link?)

    Russ

    Thursday, July 14, 2011 12:42 PM
  • HI Everyone - Same frustrating problem here with new western digital 3tb External Drive Model WDBACW0030HBK. How is this not fixed??? Why the delay MS? THis is ridiculous beyond belief. 
    Monday, July 18, 2011 4:35 PM
  • HI Everyone - Same frustrating problem here with new western digital 3tb External Drive Model WDBACW0030HBK. How is this not fixed??? Why the delay MS? THis is ridiculous beyond belief. 

    This has been answered already, please see answers above.
    Thank you for posting
    Russ Grover
    Monday, July 18, 2011 5:58 PM
  • HI Everyone - Same frustrating problem here with new western digital 3tb External Drive Model WDBACW0030HBK. How is this not fixed??? Why the delay MS? THis is ridiculous beyond belief. 

    This has been answered already, please see answers above.
    Thank you for posting
    Russ Grover


    Hi Russ, I read the whole thread going back to 2009 and tried everything. I installed hotfix KB982018 and still have the isssue, have I missed something? As far as I can tell the only "answer" is that Windows Backup does not support the 4096 kb sector size which at this point in the evolution of hard drives has basicly become the standard for anything but the smallest drives. Are you saiying my only option is dust off an old hardrive with 512kb sector? If so I wouldn't really consider that an answer... more of an explanation for why a problem occurs that should've been fixed a long time ago.

    Also, if this is a well know problem that was actually inherent in Windows 7 from the beginning why can't the error message explain this in detail so the poor users don't have to ferret out this thread amongst the thousands of other unrelated problems people have with backups and external hard drives. It certainly wouldn't have been difficult to have the WIndows 7 backup program check the sector size and tell you right away that is or is not going to work with whatever hardware you have , knowign that I would've just bought a different hard drive.

    Monday, July 18, 2011 8:54 PM
  • Windows 7 was introduced October 22, 2009 about the same time the large block was introduced.
    (As you know RTM and Beta's are closed much before this time.)

    So getting Microsoft to RE Engineer a product for Future hardware would be IMO kind of much to ask.
    IMO since hardware came out after Win7 it is up to the manufacuture to notify of compatability.

    I know you feel that you think this should be public knowledge, but it is in the IT Industry (At Least I've known about it since the begining)

    This is why an IT Advisor is your best bet in getting new hardware for Windows Servers.
    (And I mean QUALIFIED Advisior not friend of a friend who knows a guy.)

    I personally think this thread should be closed. Since this is a closed Topic,
    those posting here hoping complaining to Microsoft to FIX something that is no wrong with Win7 but a built by design. (There is no fix for something that is not designed to work with it.)

    After all You don't take your Analog TV back to the Manufacture and say, HEY I want the Free Upgrade to Ditigal. (No of course not)

    Posting FIX IT is tilting at windmills and Beating the preverably Dead horse.

    The Product stands as IS. (And I think it's a gread product)
    If you have purchased a product that is not compatable with Windows Please seek the return from the vendor or manufacture. (not Microsoft)

    If you are still unsure of what to purchase for Backup, Please seek a Microsoft Professional (Qualified)
    on your Product to get the correct solutions.

    Thanks
    Russ
    www.SBITS.Biz

    Tuesday, July 19, 2011 12:08 AM
  • Russ- converting analog tv's to digital is quite different and would require an actual hardware change vs. what we're talking about here which should be fixable with nothing more than a software change. When Windows 7 came out there was no such thing as USB 3 and yet my computer now supports it thanks to a simple driver update, a far cry from what you characterize as rengineering the whole product, I could name dozens of examples of new hardware or standards gaining support in an OS that was released before the new hardware existed. Your comparison and general basis for argument is irrelevant and seres only to reveal your bias. I'm not sure exactly what your motivation is to stand up for a broken part of the OS that should and could be fixed.  

    Obviously when Microsoft unvielled Windows 7 they were well aware of the impending change in hard drive formats and while perhaps it is acceptable that the OS did not support the feature at the time here we are several yers later and the new 4k format has in fact become the standard and we are left with no new OS that supports it or an update to make the only available verions of Windows work with virtually any new external hard drive.

    BTW I am in IT and while the new format is common knowledge the fact that Windows 7 does not support it is not well known unless you spend alot of time reading KB articles. I have worked IT for over 10 years and I currently run a MS software development shop.

    I came to this forum for a possible solution to a very common and frustrating problem, instead I get an earful from a fanatical and illogical MS fanboy that seems to think you need to hire an IT expert to choose an external hard drive correctly. What a joke !

    Tuesday, July 19, 2011 3:59 PM
  • My Point is asking Microsoft to fix this is NOT GOING TO HAPPEN.
    No matter how much crying people do.

    I actually don't read any KB's they usually actually come after the fact.
    however with any new hardware I buy for a client I check it out before I get a purchase.

    There are a lot of Blogs that can help you keep up with issues like this,
    I honestly can't remember where I read this first, but I aways Question new hardware and never buy the Latest and as you know.

    Assuming things work, and not knowing things as you know doesn't work and makes you look bad to your client.

    As you know keeping up to date in technology is just part of the process.
    Contributions to groups like this and reading groups is a great way to keep up on new technology.

    And if you don't like MS Products there are plenty of other options you might look at.

    Slaming People or a product IMO is kind of unprofessional.
    Some basic time to learn, would have saved you this frustation.
    Take care.

    Russ
    www.SBITS.Biz

    Tuesday, July 19, 2011 5:10 PM
  • Hi Russ, but what about SBS 2011?! This is a new product (?) and the included backup solutions is not working with 4k format drives. There has been a chance to fix this.

    In another german thread an MSFT trys to tell me, that this can be fixed. So Microsoft Pros even don´t know about this issue.

    The information about not compatible drives in this thread is very helpful. I can not test every external usb drive myself, before getting it out to customers. There are more complex things to do for earning money.

    Regards, Mike

     

    Tuesday, July 19, 2011 8:39 PM
  • As you know SBS2011 is based on Server 2008

    it's only the Exchange, SharePoint, etc.
    Interface that is new even then old technolgy.

    Just because something says 2011 doesn't mean that it supports
    everything made in 2011

    Heck even Quickbooks 2011 doesn't support Office 2010
    (LOL)


    Now that we are talking SBS
    The backup of SBS2011 comes Directly from SBS2008
    Thus the reason it still has an issue.

    So don't hold your breath for a fix on this either.

    To fix this in SBS2011 or SBS2008 You'd have to Redesign SBS2011 From it's CORE
    And then Make sure that all the parts fix again.

    As you know companies always move forward in products not backwards.
    If that was the case SBS2011 wouldn't even have shipped this year.
    In fact Microsoft is "ALWAYS" playing catchup on hardware...
    And if they waited they would never put anything out...

    For every 1hr of support I spend about 1hr of Reading and learning.
    (or more sometimes)

    I know you can't test every device, I don't either.
    And yes I've had to eat hardware. It's part of being a IT consultant.

    Part of my job is to divide my time between learning and fixing.
     
    I just call things like this a life lessen, buy another HD and move on...
    Things do get better :)
    And Beating Dead horses is just gross to me. :)
    Russ
    www.SBITS.Biz

    Tuesday, July 19, 2011 9:06 PM
  • For anyone new to this thread, read this first

     

    Basically there are two things that could be causing your backup to fail if it is a removable HD.  I am going to save you the trouble of reading this whole thread and catch you up. 

    1.     Your removable HD has bloatware (crapware, extra software, custom bios, etc etc…) that prevents windows from seeing it for what it should be (a removable HD).  When you plugged your disk in did you also get a new CDROM drive also?  Did you install some special software in order to get to the disk?  Encryption software maybe?  Your disk is not going to work.  Stop reading any further and return it.  Don’t feel bad.  Chances are you didn’t know it was going to be that way and the manufacturer did a poor job of telling you about it before you purchased it. Return your drive and go to this site where there is a nice list developing that tracks disks that have been tested:  http://social.technet.microsoft.com/wiki/contents/articles/1780.aspx

     

    2.     Your disk has more than 512 bytes per physical sector.  If it new and large (like 1TB or more) it probably has 4096 bytes per physical sector.  The windows backup software was designed to work with disks that have 512 bytes per physical sector.  Again, don’t feel bad about getting the wrong disk.  I did a quick check of about 10 disks online and couldn’t find a single one where the manufacturer listed the bytes per physical sector in the specs anywhere.  Also, until you have this problem, you will probably never know about the 512 byte design issue.

    Anyhow, now that you do know about it, you can try to fix it using the Microsoft hotfix here: http://support.microsoft.com/kb/982018 which adds support for 4096 byte disks to server 2008 and 2008 R2 (and any SBS versions based on them).  Once the hotfix is applied and you reboot, try assigning the removable HD a drive letter and formatting it.   Once that is done you can check to see if the disk is going to work by using fsutil.  Here is an example showing the command line and the result:

    C:\Users\administrator>fsutil fsinfo ntfsinfo f:
    NTFS Volume Serial Number :       0x2ebc529bbc525d81
    Version :                         3.1
    Number Sectors :                  0x000000000e8b4eff
    Total Clusters :                  0x000000000e8b4eff
    Free Clusters  :                  0x000000000e8aa566
    Total Reserved :                  0x0000000000000000
    Bytes Per Sector  :               4096
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 4096
    Clusters Per FileRecord Segment : 1
    Mft Valid Data Length :           0x0000000000100000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x0000000000000002
    Mft Zone Start :                  0x00000000000c0000
    Mft Zone End   :                  0x00000000000cc820
    RM Identifier:        42643033-B240-11E0-9765-3C4A92E16BD6

    You see where it says “Bytes Per Physical Sector:” and the result was “<Not Supported>”?  That means this disk will not work with the backup even though the hotfix is installed.  Some disks don’t report their bytes per physical sector correctly and therefore won’t work.   If you get one that does report 512 or 4096 you should be OK.   

    Btw, if you do find one that works, be kind and add it to the list of drives here: http://social.technet.microsoft.com/wiki/contents/articles/1780.aspx with a comment about your test setup and results.

     

     

    oh, and Russ, don't just argue with people in forums for the sake of arguing.  Either post something useful and constructive or don’t post at all.  What you are doing is basically “Trolling”

     

     


    • Proposed as answer by KarlBystrak Wednesday, July 20, 2011 10:27 PM
    • Edited by KarlBystrak Thursday, July 21, 2011 6:18 PM Fixed Broken Hyperlinks
    Wednesday, July 20, 2011 7:00 PM
  • Apparently you didn't read all the posts...

    Hmmm..
    OK
    Russ

    Wednesday, July 20, 2011 8:44 PM
  • I'm sorry Russ.  Which post did i miss that includes relevant information for my summary?  I will be happy to edit the summary if you think i left out something relevant.

     

    Wednesday, July 20, 2011 9:09 PM
  • Thank you so much for posting this Karl. I read the whole thread and I wasn't going anywhere, I went to your link with list of compatible drives and I realized that I already have a "Seagate FreeAgent Desk" and it worked for my backup.

    A super post!


    Thanks again.

    Tuesday, August 02, 2011 7:15 PM
  • Thank you very much for adding something useful to this discussion and also mentioning the worthlessness of the Troll Russ' posts. We all came here to try to find answers to problems not be told the issue should be closed because"asking Microsoft to fix this is NOT GOING TO HAPPEN.
    No matter how much crying people do." 

    Getting back to the problem everyone is having here, I ran the command after installing the hotfix and got this:

    NTFS Volume Serial Number :    0xfa7aa76f7aa726fb
    Version :             3.1
    Number Sectors :         0x000000002ba9f2ff
    Total Clusters :         0x000000002ba9f2ff
    Free Clusters :         0x000000002509878e
    Total Reserved :         0x0000000000000770
    Bytes Per Sector :        4096
    Bytes Per Physical Sector :    4096
    Bytes Per Cluster :        4096
    Bytes Per FileRecord Segment  : 4096
    Clusters Per FileRecord Segment : 1
    Mft Valid Data Length :      0x000000001f700000
    Mft Start Lcn :         0x00000000000c0000
    Mft2 Start Lcn :         0x0000000000000002
    Mft Zone Start :         0x00000000067a6580
    Mft Zone End  :         0x00000000067ae2a0
    RM Identifier:    04E9228F-BBA7-11DF-99AB-90E6BA3C9977
    

    Obviously I'm dealing with the 4096 sector size here but it doesn't say "Not Supported" so am I correct in thinking it should be working now? So far it's still failing with the same error. 

     

    Thanks again for the help

    Wednesday, August 10, 2011 9:25 PM
  • I'm getting the same error (2155348010) code on a Intel based server that runs daily backups of various Hyper-V virtuals to 5 identical WD Caviar Green 2TB drives. Currently, I'm only getting the problem on one of the drives, and this after the backups have been running without a hitch in the current configuration for 2 months. In my case - I can't really see that the sector size could be the root of the problem, as the same backup is working on the other drives.

    I have taken note of the power management issues addressed earlier in the thread, but I don't think it applies to disks that are not running off USB.

    Issues I have experienced in the past - with their apparent solution:

    1. Running out of disk space (vague disk error given) - Got bigger drives
    2. Permission problems on the disks after taking ownership - Reset the disk permissions (Resolution followed from error code)
    3. Sometimes the OS wouldn't pick up that the drive in the hotswap bay has been changed - Installed "Hotswap" software to safely remove hotswap HDD
    4. And sometimes, a single drive would just keep on failing, until I remove it form the backup set and add it again....

    ... which is what I'm going to do tomorrrow. It's not very scientific but it will probably work. Any suggestions on why a disk that has worked perfectly well in the past would just stop working with the topical errorcode?

     


    Getting there
    Thursday, August 11, 2011 8:44 PM
  • You think you guys have problems!!  I'm a pensioner and therefore not very IT-literate, and struggle to understand this stuff above. I bought a new PC (Optiplex 980MT) which came loaded with Windows 7, to which I added Office 2010, and an external drive (Iomega Prestige 2 TB) so I can back up my files.  So far, so simple.  Except that I can't back up my system because either the software doesn't work (looks like) or the new hardware is wrong (probably not).  Surely either Microsoft (having been aware of this for 2 years) should have written a fix, or the hard drive people should have warned Microsoft some time ago that they were going to change the block size. New external hard drives are probably not going to revert to the old system in the future, so this problem is going to grind on and on. I've spent a fair whack of my hard-earned on all this brand new up to date stuff and it simply doesn't work.  For once I don't think it's my fault. I liken it to buying a new car and the brakes fail because the manufacturer had fitted old size brake pads but the parts supplier had fitted a different sized set of disks - not earth-shatteringly clever!  So, MS, what do I do now?
    Sunday, August 14, 2011 5:35 PM
  • I would also like to add a solution that I found that has worked for my 3TB WD Elements drive. Out of the box this drive did not work with Windows backup at all. WD support actually came through for me on this issue and pointed me to the following solution:

    http://wdc.custhelp.com/app/answers/detail/a_id/6618/session/L3RpbWUvMTMxMzUzNzc5My9zaWQvT1hrMSpJQms%3D

    Basically it consists of formatting the drive with their external drive formatting utility in "Factory Default" mode rather than XP-Compatible mode which (ironically) is how the drive ships. After performing the format, the drive works fine with Windows backup in both Windows 7 and Windows Server, but is incompatible with Windows XP. In my case, this is an acceptable compromise.

    This is how the drive appeared out of the box:

    C:\Windows\system32>fsutil fsinfo ntfsinfo H:
    Bytes Per Sector  :               4096
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 4096

    This is how the drive appeared after the "Factory Default" format:

    C:\Windows\system32>fsutil fsinfo ntfsinfo H:
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024

    Finally, I should point out that this utility will probably not work for drives from manufacturers other than Western Digital as it scans for WD drives specifically on launch and is likely working directly with their drives' firmware. That said, I do believe this should cover all WD drives 2.5TB and larger to correct this issue.

    • Proposed as answer by CoreM Friday, August 19, 2011 5:26 AM
    Friday, August 19, 2011 5:26 AM
  • CoreM - AWESOME!  That worked perfectly.

    I downloaded the utility from:
    http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868/c/130/p/85,306

    The drive I had to reformat from 4k to 512 bytes/sector was:
    Western Digital  WD Elements, 3TB, Model: WDBAAU0030HBK-NESN

    Just bought from the external 3TB drive from Amazon: $119.99
    http://www.amazon.com/gp/product/B004SH5VQ4

     

    Thursday, August 25, 2011 7:34 PM
  • Hi

    In July 2011 we purchased a new SBS2011 server with two x 1TG Seagate Freeagent GoFlex USB drives.   Our backup using MS Backup worked OK but were slow.  We then switched to using BackupAssist, which also worked and was much faster.

    Then on August 28th, the backup failed with the error code 2155348010.  Why if the backup had been working why did it suddenly stop.  When I run the back up now, it fails with error code 2155348129.

    Is this likely to be related to the 4k byte sector?

    thanks

    A

    Wednesday, September 07, 2011 9:06 AM
  • Thanks John for the solution. I applied the above KB patch mentioned and had no luck.

    My drives is the WD USB3 1130 3TB drive.      SBS 2011 Standard.

    John's solution was successful to bring the sector size down to 512 bytes on the WD drive.

    This USB drive is using the server backup is a daily redundant system to an RDX solution taken off-site.

    The RDX solution is successful also with Symmantec Backup Exec R2 packaged with the drive. The appropriate extensions for MS Exchange and MS sharepoint would be recommended but the cost of this software is substantial. Its great to know that this alternative for these system files is there. 

    However, we have run Symmantec without the plugins and still have successfully recovered the master database for exchange when a store corrupted.

    Thanks again for the solution John and kudos to all above trying to help.

    Additionally,

    It would be great to see support for the RDX directly through the SBS backup interface.

    It would be great to see this change implemented from Microsoft to support the larger drives successfully.

    Thanks again John. Saved me much time.


    • Edited by techwerks_ca Tuesday, September 27, 2011 1:26 PM
    Tuesday, September 27, 2011 1:26 PM
  • CoreM,

    You're my hero!

    I decided to not take any chances and downloaded the Quick Formatter from the WD site (as opposed to using the older version that came on the drive itself) and now I seem to be in business.

    Thanks,

    josh

    Tuesday, October 11, 2011 4:41 PM
  • CoreM,

    You're my hero!

    I decided to not take any chances and downloaded the Quick Formatter from the WD site (as opposed to using the older version that came on the drive itself) and now I seem to be in business.

    Thanks,

    josh

    Tuesday, October 11, 2011 4:42 PM
  • I have the same problem.

    I have just bought a new Windows 7 PC and connected it to a recently bought 3 TB Seagate Expansion External Drive (STAY3000200) which was working perfectly on my old XP PC.

    The drive is connected via a USB connection and works on the new Windows 7 PC for saving files normally but the Windows 7 Backup to it fails with an I/O error.

    After reading the explanation of the cause that Abhinav wrote, I tried connecting an old Freecom 150 GB USB Drive and the Windows 7 Backup then completed successfully to it.

    I did a chkdsk on both USB Drives and both stated they had 4096 bytes in each allocation unit.

    I am now confused. The 150 GB drive won’t last long so do I go and buy another new USB Drive and hope it works or can I get the 3 TB Seagate to work? Any help gratefully received.

    Saturday, December 31, 2011 9:01 PM
  • Hi Folks,

    I have read this thread and I think it must break some sort of record for length?

    The issue unable to use Windows Backup tool with external drives especially large (1+TB) Western Digital drives.

    I spent several days with WD's tech support and they tried there hardest to get their own Backup Tool to work and it failed at every turn, similar to the Windows Tool.

    SOLUTION:

    Use Western Digitals Anywhere BackUp powered by memeo. -

    It works great. It works similar to Vusual SourceSafe in that it ditects file changes and saves it again. (Sorry do not have a download link for you as I got it from the tech at WD)

    I love it as it has low CPU useage and just rumbles along in the background - as a back up should do!

    I hope this will help all those out there looking for a solution to Windows BackUp Failing.


    SquireDude

    • Edited by SquireDude Friday, January 27, 2012 4:51 PM
    • Proposed as answer by SquireDude Friday, January 27, 2012 4:51 PM
    Friday, January 27, 2012 4:48 PM
  • KarlBystrak

    Glad I finally got to your post! It's a perfect summary of the issue, both Technical and other.

    In my case the customer provided an iomega eGo which has the bloatware that you described.

    Thanks taking the time to put together this informative post.

    Cheers

    Jonpy

    Friday, February 10, 2012 12:08 PM
  • Thank you, thank you! This worked for me with my Western Digital My Book Essential 3TB drive. Factory Default format did the trick.
    Thursday, February 16, 2012 6:32 PM
  • Okay read it all, tried it all..

    What alternative software DOES allow me to make a full system image to my 'HP SimpleSave 1TB' device?

    It was on the list of compatible devices but isnt working sadly..

    i'm not bothering buying new harddisks and want a working backup sollution. since ppl here probably all moved to properly working backup sofware, im wondering what you've bought :)




    • Edited by Johan Schaap Thursday, February 23, 2012 2:31 PM strange HTML in post removed
    Thursday, February 23, 2012 2:20 PM
  • Just thought I would post my reference to the other forums I posted on, anyone looking for answers might find this helpful.

    http://social.microsoft.com/Forums/en-US/whs2011/thread/dfcd61ff-953f-486a-a72c-95f3e17f1b6e?prof=required

    Hey guys with the Seagate Hard Drives STAC3000102 other known as the Seagate FreeAgent GoFlex Desk 3 TB external I have found a work around. It may not be exactly what you are looking for but it maybe. What I have done is taken the Seagate off its dock and connected it directly as an internal hdd (you can reference this also http://www.anandtech.com/show/3858/the-worlds-first-3tb-hdd-seagate-goflex-desk-3tb-review). I got the idea from the website to trim the SATA cables to make a connection WITH OUT DISASSEMBLING the case. So what you can do is buy an extra SATA cable and a molex(4 pin) to SATA connector and trim those so you dont have to worry about ruining your power supply cables or your original SATA cables if you don't have alot hanging around. So what you are doing is bypassing the conversion done on the dock that takes the original specs of the drive from 512b sectors (the internal drive specs) to 4k (4096b) conversion. You can get a further explaination of why it is being converted to 4k in the article I referenced, and it wasn't for them to piss people off but rather to accomodate storage/performance progress. So now that you have a drive connected that supports 512b allocations (sectors) you should be able to use this drive as the backup drive for your server. Keep in mind you will probably have to go into disk management still and initialize the drive (Right-click My Computer>Manage>Storage>Disk Management) I also did use it as a GPT, I don't know why natbr though you can't, I had to previously to have support for over 2tb's of data on my RAID array and for the external before I had it working for backup. Also to clear up something that I have seen on the forums about the 2TB limit, You can have a backup drive of over 2TB's. The 2TB limit refers to the backup image format that WHS backs up the server with, not to be confused with the client computer backups. WHS uses VHD (Virtual Hard Disk) format to make an image of your server, VHD has a limit of 2TB. So what that means is as long as the source of what your backing up as an image does not exceed 2TB you should be able to back it up to a drive of as large as you want (I am being sarcastic and not considering unrelated limitations that may come up but at least a 3TB drive). So again your destination can be Larger than 2TB's, your source of backup cannot exceed 2TB in VHD format. Also this should not be a major limitation depending on your set up, exampling my setup, I have a HDD for my server O/S of an insignificant size, lets say 500GB cause I think thats all that I had lying around, but my OS only takes up 60GB so you could have a HDD of 120GB because your server O/S shoulding be cluddered up with alot of data. In additions I have (3) 2TB HDD's in a RAID-5 Array which gives me roughly 3.6TB of data(if your not familiar with RAID look it up on wikipedia), and in order to have that large of a single volume on Windows it needs to be in a GPT. So my disk management page looks like 3 DISK's right now DISK 0 is 500GB for my server O/S, DISK 1 is 3.6TB GPT RAID-5 which is may share drive and also has my client computer backups, and DISK 2 about 3TB which is the Seagate GPT, Realistically you could change this around to have DISK 0 to include your client computer backups, or data, it does not matter on the configuration. Also noted, I would like to add as an extention of the RAID array conversation bit, I would ideally like to have a RAID-1 set up with larger HDD's say, 4TB or 3TB but when I set it up it was not an option. The reason for this is that in RAID-5 my worry is not with a HDD failing but with My Motherboard failing and if that happens I would then be unable to access my data, and this would be much better setup cause I would then beable to get at my data if one failed.

    Ok everyone I really hope this helps someone I usually don't post to forums but I feel I had something that actually might help people, Excuse me for my spotty punctuation, grammar, sentence structure, and any confusing things that I may have said.

    And lastly here are some other forums that I researched why finding a solutions.

    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/5d9e2f23-ee70-4d41-8bfc-c9c4068ee4e2/

    http://social.technet.microsoft.com/wiki/contents/articles/1780.external-backup-drives-compatibility-list.aspx

    Enjoy,

    Devin

    Saturday, February 25, 2012 9:52 PM
  • if the backups has been working in past on a disk drive and failing now - it can not be the issue with the sector size on the disk.

    please send a email to sbaid_at_microsoft.com and absrivas_at_microsoft.com - we can follow up to help you out on that. (replace _at_ with @)
    ------- this information is provided as-is without any warranties, implicit or explicit.

    Hi ,

    I am facing same issue till now.can you help us.


    Ram Prakash Sharma

    Tuesday, May 15, 2012 6:39 AM
  • For anyone new to this thread, read this first

    Your disk has more than 512 bytes per physical sector.  If it new and large (like 1TB or more) it probably has 4096 bytes per physical sector.  The windows backup software was designed to work with disks that have 512 bytes per physical sector.  Again, don’t feel bad about getting the wrong disk.  I did a quick check of about 10 disks online and couldn’t find a single one where the manufacturer listed the bytes per physical sector in the specs anywhere.  Also, until you have this problem, you will probably never know about the 512 byte design issue.

    Just a heads-up regarding Iomega eGo 1TB Portable Hard Drives.

    In the past, I have found that the Iomega 1TB eGo drives contain 512k sectors and work fine with Windows Server 2008 Backup.

    However, I just bought two additional 1TB eGo drives and (despite the same product code and identical packaging), the enclosure contains a 4K sector drive and fails with the I/O backup error.

    There is no indication anywhere that the specification / compatibility has changed.

    Proceed with caution!

    Regards, Stephen


    • Edited by Studio Two Friday, May 18, 2012 11:34 AM
    Friday, May 18, 2012 11:33 AM
  • Thanks for clarification...


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, May 18, 2012 11:38 AM
  • Can someone please confirm compatibility with WD WD20EARX (internal sata "green" disk)
    Tuesday, June 12, 2012 12:26 PM
  • The issue is that the Samsung drive has a 4096 byte sector size.   Windows server backup is not designed to run on such disks.    We will try and address this issue in a future release.

    Any idea when this "future release" is going to happen?  Hopefully not Server 2012 :p

    BTW - for anyone looking for a large drive (3TB) that works well, the Western Digital MyBooks are great. You can use the WD utility and format them to "Factory Default" (NOT XP Compatible) and they work fine with SBS backup.

    Mine are USB and I connect them to my SBS HyperV VM as Direct Disk - USB works fine for SBS backup.  You have to detach the disk from the VM when rotating disk so there are a few extra steps, but it's not too terrible.

    And I had a problem adding a disk to the backup through the GUI.  I had a similar problem before, searched and didn't find anything.  Today the Search gods were smiling on me and I stumbled on this most excellent post on how to add a stubborn disk to SBS backup manually and it worked perfectly:  http://blog.mpecsinc.ca/2011/06/sbs-2011-backup-error-add-destination.html

    He referenced a USB drive to a directly installed server, but it worked perfectly for me for a USB attached to my HyperV VM as a direct disk.

    Sunday, June 24, 2012 2:58 PM
  • Hi Abhinav

    Unfortunately, I´m having tha same issue.

    Five Samsung USB disks model ST500LM012 and I cannot use to backup data.

    We have not any fix, since 2009 ??

    Tks.


    Paul Haro - Microsoft Certified Professional

    Wednesday, July 04, 2012 1:24 PM
  • Thanks this solution has work for me SBS2011 Essentials on WD MyBook 1130 - Ext USB3 - 3Tb

    Latest version of WD Quick Formatter (1.2.0.10) options are a bit different. You get:

    XP Compatible

    Most Compatible (Vista etc...)

    I used option "most compatible"

    Before:

    Version :                         3.1
    Number Sectors :                  0x000000002ba95fff
    Total Clusters :                  0x000000002ba95fff
    Free Clusters  :                  0x000000002a3e7718
    Total Reserved :                  0x0000000000000000
    Bytes Per Sector  :               4096
    Bytes Per Physical Sector :       4096
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 4096
    Clusters Per FileRecord Segment : 1
    Mft Valid Data Length :           0x0000000000100000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x0000000000000002
    Mft Zone Start :                  0x00000000000c0000
    Mft Zone End   :                  0x00000000000cc820

    After:

    Version :                         3.1
    Number Sectors :                  0x000000015d4b97de
    Total Clusters :                  0x000000002ba972fb
    Free Clusters  :                  0x000000002ba8c5ef
    Total Reserved :                  0x0000000000000000
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    Clusters Per FileRecord Segment : 0
    Mft Valid Data Length :           0x0000000000040000
    Mft Start Lcn  :                  0x00000000000c0000
    Mft2 Start Lcn :                  0x0000000000000002
    Mft Zone Start :                  0x00000000000c0000
    Mft Zone End   :                  0x00000000000cc820

    Tuesday, July 10, 2012 9:38 AM
  • A quick wrap-up about this Problem.

    Problem         When the Windows 7 Backup and Restore tool is used to create a Windows 7 System Image, the backup fails with the error code 2155348010.

                         The issue exists not only in Windows Client Operating System but also in Windows Server, it's the same issue.

    Cause            The hard drive has a 4096 Byte Sector size. Windows is not designed to run on such disks.

    Resolution

    1. Upgrade to a later Version of Windows (Windows 8, Server 2012) , in those versions the issue do not exist (recommended)
    2. Simply backup to another Location that has another hard disk that does not have a 4096 Byte Sector Size (fastest solution)
    3. Reformat the Hard disk with a tool from the harddisk vendor (not recommended, because time-consuming and some vendors do not even have a tool for this)

    Some People believe that applying a hotfix http://support.microsoft.com/kb/982018 will solve the issue, which is NOT the case as this hotfix was not designed to solve this specific backup issue

    • Proposed as answer by John Muller Sunday, July 15, 2012 11:56 AM
    Sunday, July 15, 2012 11:56 AM
  • KarlBystrak,

    You are awesome. Im guessing your parents are very proud of you.

    If not, they should be.

    You got me on the right track.

    I happened to have the WD drive and tried the WD utility mentioned in other post (Thank You, Corm  and all others as well!) you rock!. That didnt work, maybe I didnt reboot.  But had to run the hotfix and formatted it with Windows after the hotfix and lowered the block size

    I must admit, wish I had the balls to post solutions.

    Thank you guys so much for helping the community.

    If you ever want to come to Charleston for vacation. You sound like a good guy to have a beer with and I have plenty of space for the fam...

    I know your a  good guy because you have empathy.

    God bless and keep kicking ass.

    PS. The offer really stands!




    • Edited by Nunya777 Tuesday, July 17, 2012 12:55 AM
    Tuesday, July 17, 2012 12:50 AM
  • KarlBystrak, CoreM, thanks for your helpful answers, exactly what I needed!

    Due to my tape robot failing I plugged in a WD Elements 3TB USB hard drive, thinking it would at least allow me to run backups while I investigate the tape robot issues. However, the backups wouldn't run, ending in lots of VSS errors, both in the backup software (CA ARCServe) as well as at the OS level. The errors were useless, they did not help to pinpoint the problem, but as they started to appear after I had connected the USB drive I knew it was related.

    Your responses fixed the issues, backup is now running without errors!

    Thanks.

    Tuesday, August 07, 2012 11:12 PM
  • I have had success today with the 1TB WD Elements SE Portable (the latest model with the USB 3.0 Micro-B connector): http://support.wdc.com/product/install.asp?groupid=305&lang=en

    P/N: WDBPCK0010BBK-01

    Make sure you reformat the drive with WD Quick Formatter for Windows before use: http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868/c/130/p/85,306

    Regards,
    Stephen

    Wednesday, August 15, 2012 8:29 AM
  • I had success with this issue and a 3TB Seagate Expansion USB 3.0 on WHS 2011.  I tried the hotfix, but the FSUTIL still showed unsupported.  The other workaround I found was to use exFAT, but that would not work for me either because it would always want to reformat the drive NTFS.  So what I did was to format the drive NTFS and then I shared the drive.  When I set up the Windows Backup, instead of using the Server Backup in the Home Server console, I used the regular server backup.  I set it to backup to a network share and I just pointed that at the share on the local drive.  The only drawback of this solution is that you will only have the latest backup available.  For my situation, on my home server, that is fine because I only want to not have to re-rip all my CDs and DVDs.  Plus the backups of the client computers are safe and still have multiple restore dates available.  As always, your mileage may vary.

    -Justin

    Saturday, August 25, 2012 7:42 AM
  • Excellent summary KarlBystrak. Thank you!

    I would like to add one more piece of information, in case it helps others. I have a 3 TB Seagate GoFlex Desk Adapter, for which I was unable to find any way to emulate 512 bytes per sector. So, as expected, Windows Backup failed to create a system image (Event Viewer error code 2155348010 - Windows Backup error 0x8078002a). However, Windows Backup succeeds at copying selected files to the drive. This "solution" works for my purposes for the time being.

    Friday, September 07, 2012 2:18 PM
  • KarlBystrak, CoreM  THANKS for posting and keeping it all on track.  

    Found my solution.

    Friday, October 12, 2012 4:14 AM
  • KarlBystrak,

    Your post was the most useful one out of this entire thread!  Thank you very much for being very informative to all of us experiencing this problem with Windows Backup.  Now I know that I'm stuck with my stupid Iomega eGO 1TB USB drive which shows "<Not Supported>" in fsutil.  I'm off to purchase a different USB drive now...

    Monday, October 15, 2012 11:56 AM
  • I found a solution that worked for me today, and this thread helped point me in the right direction.

    I have two Seagate 1TB drives (STBX1000100) which were experiencing the same issue new out of the box on a Windows Server 2008 R2 system.

    I did not apply the Windows Hotfix. (I was saving for the next possible step.)

    However, I went into Disk Management and performed the following on each drive:

    1. Manually dropped all existing volumes on these drives.

    2. Created a new volume (default to entire drive size).

    3. Formatted the volume with NTFS, 512KB sector size, using a full format. Quick format does not work.

    4. Once the format was complete, I added both drives into a Windows Server Backup set, dedicating the drives as recommended. 

    5. This backup is successfully executing.

    Wednesday, October 17, 2012 10:11 PM
  • I would also like to add a solution that I found that has worked for my 3TB WD Elements drive. Out of the box this drive did not work with Windows backup at all. WD support actually came through for me on this issue and pointed me to the following solution:

    http://wdc.custhelp.com/app/answers/detail/a_id/6618/session/L3RpbWUvMTMxMzUzNzc5My9zaWQvT1hrMSpJQms%3D

    Basically it consists of formatting the drive with their external drive formatting utility in "Factory Default" mode rather than XP-Compatible mode which (ironically) is how the drive ships. After performing the format, the drive works fine with Windows backup in both Windows 7 and Windows Server, but is incompatible with Windows XP. In my case, this is an acceptable compromise.

    This is how the drive appeared out of the box:

    C:\Windows\system32>fsutil fsinfo ntfsinfo H:
    Bytes Per Sector  :               4096
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 4096

    This is how the drive appeared after the "Factory Default" format:

    C:\Windows\system32>fsutil fsinfo ntfsinfo H:
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024

    Finally, I should point out that this utility will probably not work for drives from manufacturers other than Western Digital as it scans for WD drives specifically on launch and is likely working directly with their drives' firmware. That said, I do believe this should cover all WD drives 2.5TB and larger to correct this issue.

    I'd like to chime in that CoreM's comment is what fixed my issue as well for a brand new WD My Book Essentials 3TB USB3 drive (WDBACW0030HKB-NESN).  Windows did not offer a 512K NTFS format option and one would assume formatting as XP compatibility mode would be the 512K sector but in reality it's the Vista mode for the WD format tool.

    Systems Administrator Senior - University of Central Florida

    Thursday, November 15, 2012 3:38 PM
  • I have had success today with the 1TB WD Elements SE Portable (the latest model with the USB 3.0 Micro-B connector): http://support.wdc.com/product/install.asp?groupid=305&lang=en

    P/N: WDBPCK0010BBK-01

    Make sure you reformat the drive with WD Quick Formatter for Windows before use: http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868/c/130/p/85,306

    Regards,
    Stephen

    Additionally, the 1TB WD Elements SE Portable with P/N WDBPCK0010BBK-EESN also works (following use of the WD Quick Formatter noted above).

    Kind Regards,
    Stephen

    Monday, December 17, 2012 9:26 AM
  • I have a client with a Western Digital Storage Server 2011 which came with 4 2TB drives (total space of 4TB). Western Digital pre formats and configures this with the OEM software and since the device doesn't not have a VGA port on it, you are at the mercy of them. When I attempted to backup the data partition of 3TB to an external Seagate USB drive, Windows Backup failed with the same errors everyone else is getting. I did attempt to contact Western Digital who said there is no solution. After reading this thread, I bought an external WD 3TB drive and formatted it with their Quick Format tool, thus changing the 4K sector issue. After doing so, I still could not backup the data partition because Windows Backup will not backup a drive of 2TB or larger, so I ended up selecting to backup folders and then by backing up just folders, I eliminate the limitation of the backup application. Doing this along with the quick format solved my issue. I just want to thank everyone on this thread for all of their help, as even Western Digital said there is no way to make it work!

    Thanks again!

     

    Lyle Epstein
    Kortek Solutions
    http://www.korteksolutions.com

    Saturday, January 26, 2013 10:40 AM
  • Thank so much for your share and my below solution is working fine: (same error on Windows Server 2008 R2 64bit with My Book WD 3TB USB External)

    1. Sure that you're applying the tools from MS: http://support.microsoft.com/kb/982018

    2. Use Quick formatter tool from WD  http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868/c/130/p/85,306

    Then Choose Vista or later compatible format config option.

    3. Run Windows Backup and sure that not any other backup program using the backup disk. When Window Backup scanning file system automatically installs Microsoft VHD HBA then the backup fine running.

    Johnny - System Administrator at XP Power (www.xppower.com)

    Tuesday, July 23, 2013 7:51 AM
  •  I just found I'm in a similar boat.  Does anyone know if a viable workaround could be to use alternative backup software? [edit] sorry, just found @techwerks_ca's post and it... looks like a yes [/edit] It would be great to know if anyone has tried it because I think we have a valid license of backup exec hanging around.
    • Edited by Patrick Vincent Thursday, August 08, 2013 8:33 PM found an answer on the page relevant to my question.
    Wednesday, August 07, 2013 8:57 PM
  • It works fine with REV and RDX.

    Install command line tools and schedule your backup using task manager, scripts (batch,etc), and command line tools.

    I've been backing up using 2008 Windows Server Backup to RDX for years with no issues.

    Thursday, April 24, 2014 3:52 PM
  • This, from a guy who cannot even spell "Kool-Aid" correctly.  Is this someone that you want to get technical support from?
    Tuesday, July 15, 2014 4:19 PM