![]() Here we highly recommend AnyRecover.ĪnyRecover is an expert in data recovery field. And the fastest and securest way to do that is using a professional data recovery tool. Therefore it's necessary to retrieve the data stored in the disk and put it in a safe location before we officially start to initialize the disk. How to Initialize Disk Without Losing Data? Preparation: Retrieve Data First to Avoid Data LossĪs is known to all, initializing disk means erasing the data stored in it to make it usable. There is an inaccessible/unwriteable/bad sector on your external hard drive. There is a partition loss on your external hard drive.Ī corrupted master boot record is causing the error. There is a file system corruption on your computer.Ī connection problem is rendering your external hard drive useless. Your external hard drive has experienced a virus attack. There are various potential causes for the "Disk Unknown Not Initialized" error and the most common ones are listed below: Why "Disk Unknown Not Initialized" Error Happens? Initialize Disk With Disk Management Part 1. Preparation: Retrieve Data First to Avoid Data Loss How to Initialize Disk Without Losing Data? LineRescue Recover Deleted files from Win/Hard Drive My guess is that something in the drive got corrupt and needs "reset".AnyRecover for PC Recover Deleted files from Win/Mac/Hard DriveĪnyRecover for iOS Recover Deleted files from iPhoneĪnyRecover for Android Recover Deleted files from Android I'm hesitant to install it in the NAS until I get the problem with Drive A resolved.Īgain, I find it strongly coincidental that a drive that worked fine for years suddenly failed at the exact moment I made a software change in Synology DSM. It may be worth noting that I can read Drive B just fine in the Sabrent USB dock. AOMEI sees the drive as 0 bytes and 0 sectors. Initiallizing, wiping, creating a partition, recreating a GPT or MBR record, etc all fail. I've tried everything I can think of using Windows Disk Manager and AOMEI Partition Assistant. The drive spins up when power is applied and seems to make "normal" drive noises. I tried using my Sabrent (JMicron controller) USB to SATA adapter to fix the disk under Windows 11 Pro. The error log in the Synology Storage manager shows "The system detected an I/O time out" I have a hard time believing that a drive that was working perfectly just coincidentally had a catastrophic failure while I was clicking on some options. I tried rebooting the NAS and moving the drive from Bay 5 to Bay 5, but cannot get DSM to see the drive again. I don't remember what exactly I clicked (SMART Quick Test maybe?) and suddenly DSM disconnected the drive. While I was initializing it, I was messing around in the Storage Manager app in DSM. It saw the drive and I began initializing it. ![]() I installed Drive A in the NAS and logged into DSM. I had planned to install Drive A in the NAS and once it was configured, I'd connect Drive B to my desktop with a SATA to USB adapter and copy the contents over to Drive A in the NAS. Over the weekend, I booted up the old PC to copy some files I needed before pulling the drives. ![]() The drives were configured as RAID1 in the desktop and never had an issue with them. I figured I'd remove the drives and install them in my Synology DS1621+ since I have two empty bays. ![]() I had a pair of WD Red 3TB HDD's in an old desktop which I'm selling. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |