It needs to be "512" for Windows to support it. Note where it says, "Bytes Per Physical Sector". However, if I run it on the same model drive, just older (and works) it gives me the the secon set of results below. If I run this command (change x for the drive letter) "fsutil fsinfo ntfsinfo x:", On a working drive (same model) give me the results of the 1st set of results below. So Windows Server Backup can see the drive, sort of, but can't add it as a destination. Then when I pick it and click OK, it doesn't snow up on the list "Select Destination Drive" I tried again to add the drive as a backup destination. I can select it in "Show all available drives", but it shows on the list as "Unmounted". (A device which does not exist was specified.) Corruption may occur in VolumeId: ?, DeviceName. The system failed to flush data to the transaction log. It tried reformatting manually it from Server Manager with default settings for NTFS, not sure what happened, no response in the gui, but event manager showed: Now the drive has a new volume label courtesy of Windows Backup and is invisible from Windows Explorer. It started formatting the first drive and died with : "Formatting the disk has failed - The parameter is incorrect" (Thanks, Bill for that wonderful error message.) Tried adding these drives as additional destinations to my existing backup job. I've been using the card successfully with WD drives until I started seeing disk errors on one of the drives, so decided to replace them both with the Seagate drives. Running the drives from an add on controller card that supports USB 3.0. I just got 2 new Seagate Backup Plus Desktop Drive Model SRD00F2 P/N 1KBAP3-500 4TB.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |