mgutt Posted April 25, 2022 Share Posted April 25, 2022 What happened: This is the second time I notice that a user killed his data (another topic). Their disk lost it's connection, so it was thrown out of the array, but parallel the disk partition was corrupt. First problem: This means the user had as a result an emulated disk without partition (with defective partition table) and the GUI offered them to format the disk. Second problem: The user formatted the disk as they thought this could be a necessary step to rebuild the data. Instead it resetted the file system and updated the parity accordingly. Third problem: Their caching rules applied. The mover moved new data to the fresh formatted and emulated disk. Now important sectors with data were overwritten (the chances to recover the data through a third-party software shrunk). Fourth problem: The user started a data rebuild with the same disk that was disconnected before (hardware problem was solved, like a defective cable or sata port). After the rebuild process was finished all its original data was replaced against a fresh formatted disk + the moved data from the cache. What should happen instead: a) do not offer to format an emulated disk. Instead it should advise the user to repair the partition table b) do not allow to replace a "defective" disk by itself. By that its impossible to kill the original data 2 Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.