- #SEAGATE SEATOOLS DOS NO ERASE HOW TO#
- #SEAGATE SEATOOLS DOS NO ERASE INSTALL#
- #SEAGATE SEATOOLS DOS NO ERASE SERIAL#
- #SEAGATE SEATOOLS DOS NO ERASE PATCH#
- #SEAGATE SEATOOLS DOS NO ERASE FULL#
Then we switch 512e to 4k, unless, of course they are 4Kn Whenever we refresh our drives we always flash each batch with the same firmware revision. I manage PB scale storage arrays for a research center.
#SEAGATE SEATOOLS DOS NO ERASE HOW TO#
I stumbled across this thread after running into some of the same issues mentioned and thought I would add how to flash your drives to the same rev. In an elevated (admin) Command Prompt window, scan for your drive with the command: Here's the solution for Windows (you can do it in Linux also, with similar command line options) PS- Yes, I know that using ashift=12 works fine with 512e drives, that's not my question, I want to convert the drives to 4Kn using the Fast Format feature. What tool or command line option can I use to do this? Do you have to use the Seagate Seatools (it doesn't even appear to support it)? Does BSD or Windows support this? Or sg_format? Or parted? I've search all over the web and cannot find any information on this. This is documented in the Seagate documentation, but they neglect to say how you do it, and with what tool. They come formatted in 512e by default, but they support "Fast Format" to convert to 4Kn so that they appear as a true 4Kn to the OS. What do you mean by "clone disk"? If everything works fine, I would expect to see my drive in Windows/Linux, and I can save my data.I'm planning to purchase some Seagate Exos X16 (model ST16000NM001G) 16TB drives.
#SEAGATE SEATOOLS DOS NO ERASE PATCH#
Thanks for the warm welcome, this will be my last Seagate product! It will take a while until I will find a EEPROM programmer, seems that I cannot found one in my country but when I will have it, I will share here the ROM content here.Īs far as I understand somebody must patch the ROM, in order to grant access to the terminal? Am I right? I was not aware of that. I don't have a PC3000 and it's quite expensive I think.
#SEAGATE SEATOOLS DOS NO ERASE SERIAL#
Can I make a secure erase via serial port?
#SEAGATE SEATOOLS DOS NO ERASE FULL#
Regarding the donor HDD, should I have the HDA also? (or only the PCB it's ok) I found one full sshd but with bads, and the seller told me that it was not able to secure erase it using Seatools.
I think it should work, do you have other recommendations? I'm seeking for a EEPROM Programmer, and I found this one: Īs far as I understand it's a 5V or 3.3V and I will get a 1.8V adapter. Some users may even be satisfied if the drive continues to function in read/write mode without cache, especially if it has outlasted the warranty period.Ģ0200214_075618.jpg Better still, the firmware should initialise the NAND, retire any bad blocks, and keep using it, if at all possible. At the very least, the drive should continue functioning in cache-less read-only mode so that users can recover their data. No intelligent firmware designer would kill a drive just because of a bad NAND cache. I expect that it will be a 1.8V or 2.5V part, so you will need an appropriate programmer to read it.Īs for the ROM patch, I suspect that PC3000 injects a JMP instruction to bypass the NAND check.īTW, welcome to Seagate's sh*tty firmware. There is a tool called F3RomExplorer which could help with this, otherwise I have my own ROM parsing methods. If this doesn't work, then we could analyse the ROM contents and determine if there are any drive specific data that need to be modified.
#SEAGATE SEATOOLS DOS NO ERASE INSTALL#
Then I would reprogram the donor's ROM with the dump from the patient, and install the donor PCB on the patient HDA. That should initialise its NAND and clear its cached data. Then I would procure a donor HDD and secure erase it. I don't know if it will work, but I would first try to dump your serial flash memory chip ("ROM"). I expect that Ctrl-Z won't invoke the prompt either. I'm not a data recovery professional, and I don't know exactly what transpired in that other thread, but ISTM that you are unable to reach the F3> prompt.
0 kommentar(er)
