-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sanitize Overwrite Started - Device Removed - Sanitize Overwrite Aborted - How to proceed #102
Comments
Hi @FurkanGozukara, The sanitize feature will resume after power loss where it left off. So if the device was unplugged from power, it will resume sanitizing itself as soon as it gets power again based on the last checkpoint the firmware made during the erase as soon as it spins up again. Same thing for any reset on the bus during this time, it will continue sanitizing where it left off until the sanitize has completely erased the entire drive and all previously reallocated user-data sectors. There is no way to stop a sanitize once it has been started; no power removal, reset, or command can stop it once it has been started. The drive must complete the erase or hit a failure condition, but I have not seen a failure up to this point on any drive I have tested. Erasing an HDD takes about 1.5-2 hours per terabyte. So a rough estimate would be approximately 16 hours to erase these drives. If you wanted to try openSeaChest_Erase, you might be able to get a progress indication out of them, but it will depend on what the OS/driver/HBA has done (if it removed the handle associated with the device). If these drives "disappeared" on their own while SeaTools was running, this could be because the driver, the OS, or the HBA it was connected to while it was sanitizing is trying other management operations or monitoring of its own and does not know how to handle the state the drive enters during a sanitize. This state is a limited set of commands that can return responses at this time while it is erasing. It could be counting on reading something that is now aborting the command instead of a normal response, so it thinks something has gone wrong and stopped attempting to communicate with the drive. I have found that sometimes under Windows, a device may disappear because something did not understand how to handle it, but if you boot up a Linux on the same system it may have a better ability to continue communicating with it in these other states. So if you really need a progress indicator, maybe try the same commands I mentioned earlier under Linux. Even a live-boot of something like Ubuntu would be sufficient for this. |
@vonericsen excellent answer. Thank you very much. unfortunately command didnt list the drives probably I need a restart May I ask another question? The disks have this label on them However their model and firmware were displayed like below on seatools and crystaldiskmark info What do you think about this? |
@FurkanGozukara, |
After discussion with some internal sources, it appears that the pictured drive you shared is not a valid Seagate product. Can you share where you purchased these drives so Seagate can continue to investigate how this happened? We will do our best to continue supporting you with this tool, but since we cannot verify that this is an authentic product, we cannot verify the drive's health and cannot guarantee its ability to store data either. However, Seagate is extremely interested that you get closure on this. Please keep us in the loop on this post with anything you find or any concerns you have. |
I have purchased it from https://www.teknolojibayi.com/ in Turkey They said that they are getting products from china How can I be sure it is not a valid product of Seagate? Because then I should return them back and I have to explain they are not real Seagate to the seller. Can you explain me verification so that I can return disks and tell the seller verification method. this is their product listing : https://www.teknolojibayi.com/seagate-3.5---8-tb-skyhawk-st8000vx0022-sata-3.0-7200-rpm-hard-disk-st8000vx0022 I can also use openSeaChest tools to show you more information. just tell me commands. |
Hi @FurkanGozukara, Thank you for sharing that information! I have passed it along to the correct people inside Seagate. The best way to verify a drive is authentic is through the website verify.seagate.com and follow the instructions on there. I learned that you also reached out over email. I have passed that email address you used on to one of my contacts in Seagate to reach out to you directly as well to help some more with the verification. |
@vonericsen it has been 22 hours. I did a computer shut down and open again 1 disk is returned back to the available disks but 2 disks are still displayed like this what should I do? should i clear meta data? or something else? this is the info of the available disk and I see a lot of Number Of Reallocated Logical Sectors that means this disk is gone? this is the speed test of the disk looks like this disk is not even refurbished |
Hi @FurkanGozukara, My first question is, were these drives configured as part of a RAID when you first started all of this?
Not necessarily dead, but it is also not a good sign that this drive is healthy and I would say this is more evidence that this drive is not as new as the listing led you to believe. I would try to return these drives to try and get new ones that are authentic. |
yes i will return back but first i need to return them back to normal clear metadata fails i didn't set them raid the disks are not visible in administrative tools what can I do? I tried to make raid on bios and it failed too |
over 9 hours sanitize is almost never progressing :/ I think opening seatools of windows is halting progress. this is my idea. testing atm yep after restart i didnt open seatools and now it is progressing much faster. before i did restart, it wasnt even showing progress. i think definitely seatools windows halting the process. |
Hi @FurkanGozukara, Sorry that this is taking so long. These drives are clearly not new or working well if they are taking this much extra time. A brand new out of box drive would not take anywhere near this long to complete this overwrite. I have seen in the past that requests for progress that are too frequent from software can interrupt error recovery when the drive recalculates the progress, then it has to restart that error recovery process again. That may be what is happening and causing some additional delays. I can look into some changes that may help with alleviate this issue for future updates to SeaTools and to SeaChest/openSeaChest as well. As it seems leaving SeaTools open is causing some additional delay, I would leave it closed and check for progress about once every 30 minutes as this will cause a lot less for the drive to process and let the firmware do what it needs to without as many interruptions. |
@vonericsen ty so much for answers I would like to ask few more questions if you reply I would appreciate very much All disks are normal now Could you evaluate their smart attributes and tell me how well they are looking for? One of the disk has low health I will send it back. For those 2 others, the company may cause me problems since they look normal. so could you check values and tell me are they looking healthy? For example what is Read Error Rate and how to evaluate it? it is displayed as current 66 worst 64 threshold 44 raw 00000036C2D1 what is Seek Error Rate rate ? current 61 worst 60 threshold 45 raw 00000013225F what is Hardware ECC recovered? current 9 worst 8 threshold 0 raw 00000036C2D1 results of --smartAttributes analyzed
pd3
pd4
results of --deviceInfo
results of --deviceStatistics
|
Hi @FurkanGozukara,
I cannot really assist with analysis of drive data like this, especially since we have already determined these drives are not authentic Seagate products. I'm also not a failure analysis engineer so I cannot do much as far as analysis goes as that is more specialized than the knowledge that I have. My full response for the discussion you started (#103) will go into this a bit more once it has been reviewed by our failure analysis team for accuracy. If you run into trouble returning these to where you bought them, you could try Seagate's official support to see if they are able to help you further. |
Thank you!!!!! you are a lifesaver!!! I had lost my mind, as I have been trying to understand why I was experiencing what looked like disk corruption / detection issues on relatively new IronWolf Pro drives. I ended up leveraging SeaChest (after failing to get SeaTools Linux to stop at a command prompt). Anyhow, I managed to get one of the drives to recognize on a system where it's running in legacy ata mode and once SeaTools X ran, I tried a variety of commands and then tried Sanitize in the Advanced menu and voila! the drive indicated it was at 14.87%. Now that I know that these things will just continue to Sanitize without input from me, I can get some much needed sleep! I had the indication that things would continue, but knowing the drives simply need to remain powered on, and they will continue on their merry way is a huge relief, I seriously thought I had bricked 2 IronWolf Pro 16tb's and 2 18Tbs... Thanks for this information, it's amazing how much nonsense is on the internet!! now I know what this looks like. Cheers! |
I'm glad to hear this worked for you as well!
If you think this message is good or could use additional information, let me know and I'll work on adding it in. |
my disk was showing no errors during these operations but raid 1 always failed at random times randomly, the disk access times was sometimes taking minutes i purchased new disks and no issues i dont know why these tests are still not dependable |
Hi vonericsen, I think it's a fantastic idea, it would make a big difference to anyone else attempting to use the sanitize command. What I had originally attempted was to use --poll to see if I could keep an eye on things but that didn't quite work out. One other user lens here is that I was surprised that once I ran the sanitize command, I was able to start targeting more drives. I originally had the perspective that the command was a very quick wipe (duh on my part) thus ran it on 4 drives, thinking that when I came back to the shell prompt I was done (LOL). I think a real nice to have would be in addition to the message you are indicating above is to say... "Note - Sanitize may take 1-2 hours per TB (then you read the drive size and give a notional estimate), and while I do appreciate these aren't newbie tools, a "are you sure?" along with the extra warning of time would take this tool out of the park. Thanks for the reply and for asking for feedback! I can't wait for these drives to return to normal state. Cheers. |
The sanitize option in openSeaChest_Erase has been overhauled to allow specifying "allow unrestricted sanitize exit", "zone no reset", and "no deallocate" for applicable devices/standards. Ex: zone no reset is only for ZBDs Ex: no deallocate is only for NVMe devices. This allows for more verification of erasure or allowing sanitize to run in unrestricted mode, whereas previously only restricted mode was supported. Also added the ability to specify the number of overwrite passes and the ability to invert the pattern between overwrite passes. Sanitize info also outputs more information about when a write is required after crypto or block erase on SAS devices, the maximum number of overwrite passes allowed in the standard for a given device, and when freezelock/antifreezelock are supported. Also added more information about removing the interface cable while sanitize is running in case it takes a long time due to an HBA/OS not handling the sanitize overwrite state and constantly attempting to reset the drive, which slows progress to a crawl. [#102] Signed-off-by: Tyler Erickson <tyler.erickson@seagate.com>
Hello. I am using SeaTools 5.1.176 Windows version
I have purchased 3x ST8000VX0022 so I wanted to test them before start actually using them
So I have started Sanitize Overwrite on all disks
After like 2%, first disk got removed from the computer entirely. Like shown below
Then other 2 disks are also got removed like at 10%
I still didn't restart or closed the computer. How should I proceed? All 3 brand new disks are now invisible. Nothing displayed in their ports as shown below
So here my questions
What happens if I shut down PC and open back?
How can I see the status? It has been 8 hours since Sanitize Overwrite started
If I restart, does it resume wherever it left?
Thank you
The text was updated successfully, but these errors were encountered: