You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be considered something of a footgun, but waiting 15 seconds for a format is extremely annoying when you have a 108 bay chassis filled with disks that need to be fast formatted to 4Kn.
It would be really nice to have a switch to bypass the wait, I'm already typing --confirm this-will-erase-data-and-may-render-the-drive-inoperable so if I blow something up, it's on me.
The text was updated successfully, but these errors were encountered:
Are you seeing this delay with each drive you are running? Or just once with the initial warning message that has a countdown?
This operation is not done in parallel within the tools using -d all and 15-45 seconds is approximately how long it takes to convert to 4Kn inside the drive. It's a foreground operation so it is not possible to skip the time the drive is running this. The drive must return a completion status before it can move to the next one.
If you are attempting to parallelize this you could use a script instead. That may have other issues though depending on how the controller handles drives being busy running this command.
For example: Some controllers will allow you to issue another command to another drive while one is busy, others you must wait until the drive is no longer holding the bus busy to start a command on another drive.
This may be considered something of a footgun, but waiting 15 seconds for a format is extremely annoying when you have a 108 bay chassis filled with disks that need to be fast formatted to 4Kn.
It would be really nice to have a switch to bypass the wait, I'm already typing
--confirm this-will-erase-data-and-may-render-the-drive-inoperable
so if I blow something up, it's on me.The text was updated successfully, but these errors were encountered: