pbatard
commented
10 years ago Progress was extremely slow
The only way I can see this happening is if your device was connected at USB 1.0 low speed rate (~180 KB/s). At an expected USB 2.0 write speed of 5 MB/s, the default test should take a few hours at worst for a 32 GB card, or faster if you have a card with a decent write speed (5 MB/s is low, even for USB 2.0).
Rufus does write as fast as Windows lets it (we're just calling on the standard Windows API to write data during the bad blocks check, the same as the ones that are called to copy a file), so if the write operation was slow, it was either a configuration issue (plugged on a USB 1.0 port, such as the one you could find on an USB keyboard that doubles as a hub), a Windows issue (might have some heavy handed security application filtering access to USB devices), or something wrong with your card.
4 days for 40% of the first pass on a 32 GB card means that 32000 * .8 = 25600 MB or data was written in 4 days, which gives an approximate write speed of circa 75 KB/s, which is not something you would ever expect from an USB 2.0 or USB 3.0 device. I also never heard of anybody else seeing that slow a speed with the bad blocks check with Rufus, so I can only conclude that there is something wrong with either your PC or your card.
I have also never heard of a non-fake card or USB device actually becoming unusable after interrupting a bad blocks check. I have interrupted the Rufus bad blocks check many times, on many different devices, and I've had many reports of users also doing so after finding that the test took longer than they expected, but these devices were all usable afterwards. The warning notice is mostly there to prevent novice users from believing that their flash device is destroyed, when it is simply not formatted, but there again, I have never heard from anyone seeing a device rendered inoperable from running a bad blocks check (apart from people using fake USB flash drives, which are not devices you can use to their advertised capacity in the first place anyway).
I would be very curious to get the full log from Rufus when you plug your card. I would also encourage you to find out what the Windows device manager shows when you plug it in.
But really, the fact that your write speed was abnormally slow to start with seems to indicate that your card had an issue in the first place. The speed you saw is not common at all!
HenryS137
GlassedSilver
lock[bot]
I had a new 32GB SDHC card which I planned on using a lot, and I decided to experiment with your format option of "check device for bad blocks". I had already done a quick check under Windows.
Progress was extremely slow, but when I tried to abort the check it said that it would make the card unusable. So I continued the check for about four days, at which point it was about 40% of the way through the first pass, when I had to abort because Windows 8.1 was forcing a shutdown for a forced update.
When I tried the card after rebooting, it would not format or accept any operations.
To be forced to tie up a PC for weeks or ruin a card is NOT a good forced choice for your users without any warning.
Other than this, I have been a very happy user, and have preferred your utility to any of the other alternatives, many of which I have tried. I am using 1.4.10.514 on a very fast PC.