![]() ![]() I hoped that this final step would proof where I can rely on. If I sync this data to a PC and compare this data to both the the data on the nas or the hyper backup, some files just remain binary different. I have let's say 50% of the data in the cloud. ![]() Should I rely on the current state the system is after the remap and just restore the affected files in the REMAP log?Īnd that is not even the last thing that puzzles me. And I wonder to what extend I can rely on this backup right now.Īt this stage I don't know what to trust. So when the system was still in good state I made a Hyper backup. So the backup was made before any of the SMR was swapped for a CMR). (As I mentioned before I started swapping SMR disks vor CMR. Disk 3 shows initialized, the log file shows bad sectors, however, when I run the SMART test, it shows normal. Or the hyper backup is faulty and not capable of creating a binary equal backup of the source files before I started changing any hardware. My new Synology RS814RP+ (installed around June 25th) running 4 4TB WD Red Hard drives (RAID 10) from Synologys own list of drives has now entered a degraded state. This makes me wonder is the remap procedure of Synology, and mores specific the logging of affected files due to bad sectors is faulty. *BUT* the file comparison proofs there are much more files on the (hyper) backup that are binary unequal to the current state of the files on the NAS. But even the second tool shows exactly the same binary differences.) (I even tried a second file comparison tool. The file comparison proofs that the files mentioned in the Synology Log to be damaged (as a result of the remap) are indeed binary different from the backup. A short name will be similar to a locally mapped drive name. You can map the network drive here, but short of registry edits, you are unable to apply a short name of the mapped drive. Now click the ' Map network drive ' button. That is, after the faulty drives have been swapped and after remap procedure. In the left column click ' This PC ' or ' Computer '. I ran a binary file comparison between (hyper) backup and the current state of the NAS (after repair). Both drives had a total of 1300+ bad sectors.Īnyway I just have to restore these files from a backup and I expect the Synology to be in the same state as just before the disk errors occurred.īut there is a bigger problem now. These are only something like 30 to 40, which seems like good news. when 'r' - Locates bad sectors and recovers readable information. They just advised me to do so.Īs a result in de Log all the files that are (or might?) be corrupted are listed. If chkdsk cannot lock the drive, a message appears that asks you if you want to check the drive the next time you restart the computer. The support engineer had to pass this question to development. If a sector comes back with a bad read the NAS will tell the drive to mark the sector as bad and use a spare sector from the pool of hidden spares that all drives have. "Remapping the disk runs a task of writing/reading data to every sector of the suspect disk. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |