For example, 1) If I try High Level Format, about 30800MB(30GiB) of storage is usable.Here is H2testw result: The media is likely to be defective.GByte OK (61692806 sectors) 703.5 MByte DATA LOST (1440890 sectors) Details:0 KByte overwritten (0 sectors) 0 KByte slightly changed ( 703.5 MByte corrupted (1440890 sectors) 0 KByte aliased memory (0 sectors) First error at offset: 0x0000000001541008 Expected: 0x0154100013ecf011 Found: 0x0154100013ecf211 H2testw version 1.3 Writing speed: 6.01 MBytes Reading speed: 1.96 MBytes H2testw v1.4 29.4GB is general capacity of normal 32GB flashes, so I think my flash is not in so bad condition.
![]() Speed optimize doesnt work. No matter the other options, such as SortProduct, Scan Mode, Scan Level, it always says 50400 Too many bad block error b. With Product - Capacity optimize - Natural or Halfcap or Disturb Check - Full Scan4 - ECC15 or AutoECC only about 9500MB(9.3GiB) of storage is usable. Why it turns out that the volume is two times less, its hard to say. Alcor Recovery Tool Driver Determine FlashThe rest of the volume shows how bad the blocks are What exactly is written in the window at the end of the firmware And how does the flash driver determine flash memory Change in Settings: AdjustPower500mA Try AlcorDSMP 16.12.09.00. And AlcorDSMP result is like this: SDYNAIAMA-032G ID: 45,3C,98,B3,76,79 CE:1 Time: 93s Cap: 11160M and marked 3P on the left. Ive tried some more LLF during last weekend but anything changed, except now LLF with FullScan4 option(and sort mode) is only showing 80508070MB of it. If I use FullScan1 or FullScan2 instead, I still can get around 15GiB. In contrast, when it is showing 30GB(High Level Formatted), BB was only 454. And Ive also tried h2testw with it, but there are still some bad blocks in there(about 8MB out of 15GB, about 48KB out of 8GB).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |