Skip to contentSkip to conversation

Problem with NAND memory data retention

DISCUSSION Lukasz Majewski 3 participants 5 messages Apr 27, 2017 – Apr 28, 2017 1 message not in the archive Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Dear All,

I'd like to ask you for sharing your experience with NAND Flash devices
- which may be older that their data retention time.

I've a problem with Flash NAND memory (Samsung 128Mx8).

In the data sheet [1] the manufacturer claims that it has 10 years for data retention. The device equipped with it is a bit older than 10 years.

How one can diagnose that data retention time for NAND Flash has been exceeded?

Is that:

- The number of bit flip errors on a RW page so large that ECC cannot fix it?

- Or are whole RW pages erased (0xFF)/corrupted/cleared (0x00)?

- Or any other evidence?

Thanks in advance for your help.

[1] -
http://www.sst-ic.com/File/Seriea/PDF/100923163334f47b2ce6-13b7-43d0-9b8c-ec1c75ca2c6f.pdf

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]

#1 lore raw
Quoted 15 lines · Lukasz Majewski

I'd like to ask you for sharing your experience with NAND Flash devices
- which may be older that their data retention time.

I've a problem with Flash NAND memory (Samsung 128Mx8).

In the data sheet [1] the manufacturer claims that it has 10 years for data retention. The device equipped with it is a bit older than 10 years.

How one can diagnose that data retention time for NAND Flash has been exceeded?

Is that:

Quoted 8 lines

- The number of bit flip errors on a RW page so large that ECC cannot fix it?

- Or are whole RW pages erased (0xFF)/corrupted/cleared (0x00)?

- Or any other evidence?

Thanks in advance for your help.

I think the interpretation is that the manufacturer guarantees that under the circumstances specified (temperature, supply voltage, erase cycles etc) that the data will be retained for at least ten years, beyond that it's just not specified. It doesn't mean that something catastrophic will happen after ten years, i.e. ten years is not a hard limit beyond which things start going haywire.

I can't say I have experience with old NAND flashes loosing their data, but technically I would expect that what happens is that eventually the charge leaks away from the bit cells, causing bit flips, quite simply, so it's the same mechanism that requires the flash to be 'scrubbed' periodically to check if the data needs to be rewritten.

I.e. it's the first case in your list, the number of bit flips increases.

The fewer erase cycles that a given flash block has seen, the less wear there has been on the insulation, and the better the retention would be. The ten year spec is under the worst case condition of the maximum number of erase cycles having been performed on the flash.

/Ricard

Signature · 3 lines
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30
#2 lore raw

Hi Ricard,

Quoted 26 lines · Lukasz Majewski
Quoted 24 lines

I'd like to ask you for sharing your experience with NAND Flash devices
- which may be older that their data retention time.

I've a problem with Flash NAND memory (Samsung 128Mx8).

In the data sheet [1] the manufacturer claims that it has 10 years for data retention. The device equipped with it is a bit older than 10 years.

How one can diagnose that data retention time for NAND Flash has been exceeded?

Is that:

- The number of bit flip errors on a RW page so large that ECC cannot fix it?

- Or are whole RW pages erased (0xFF)/corrupted/cleared (0x00)?

- Or any other evidence?

Quoted 8 lines
Quoted 1 line

Thanks in advance for your help.

I think the interpretation is that the manufacturer guarantees that under the circumstances specified (temperature, supply voltage, erase cycles etc) that the data will be retained for at least ten years, beyond that it's just not specified. It doesn't mean that something catastrophic will happen after ten years, i.e. ten years is not a hard limit beyond which things start going haywire.

Thanks for your explanation.

Quoted 10 lines

I can't say I have experience with old NAND flashes loosing their data, but technically I would expect that what happens is that eventually the charge leaks away from the bit cells, causing bit flips, quite simply, so it's the same mechanism that requires the flash to be 'scrubbed' periodically to check if the data needs to be rewritten.

I.e. it's the first case in your list, the number of bit flips increases.

Unfortunately with my device I do experience the second scenario.

I do observe pages read as zeros.

For example in the middle of a file - page sized (2K) data is read as zero. And this file is RO (no modification). And such zero read is persistent - happens all the time. The only way is to replace the whole file (erase it and write again).

We use yaffs file system.

And such errors pop up in random places.

Quoted 7 lines

The fewer erase cycles that a given flash block has seen, the less wear there has been on the insulation, and the better the retention would be. The ten year spec is under the worst case condition of the maximum number of erase cycles having been performed on the flash.

/Ricard

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]

#3 lore raw
Quoted 48 lines · Lukasz Majewski

Hi Ricard,

Quoted 26 lines · Lukasz Majewski
Quoted 24 lines

I'd like to ask you for sharing your experience with NAND Flash devices
- which may be older that their data retention time.

I've a problem with Flash NAND memory (Samsung 128Mx8).

In the data sheet [1] the manufacturer claims that it has 10 years for data retention. The device equipped with it is a bit older than 10 years.

How one can diagnose that data retention time for NAND Flash has been exceeded?

Is that:

- The number of bit flip errors on a RW page so large that ECC cannot fix it?

- Or are whole RW pages erased (0xFF)/corrupted/cleared (0x00)?

- Or any other evidence?

Quoted 8 lines
Quoted 1 line

Thanks in advance for your help.

I think the interpretation is that the manufacturer guarantees that under the circumstances specified (temperature, supply voltage, erase cycles etc) that the data will be retained for at least ten years, beyond that it's just not specified. It doesn't mean that something catastrophic will happen after ten years, i.e. ten years is not a hard limit beyond which things start going haywire.

Thanks for your explanation.

Quoted 8 lines

I can't say I have experience with old NAND flashes loosing their data, but technically I would expect that what happens is that eventually the charge leaks away from the bit cells, causing bit flips, quite simply, so it's the same mechanism that requires the flash to be 'scrubbed' periodically to check if the data needs to be rewritten.

Quoted 6 lines
Quoted 2 lines

I.e. it's the first case in your list, the number of bit flips increases.

Unfortunately with my device I do experience the second scenario.

I do observe pages read as zeros.

Hello,

I think I have seen the same issue: one defective device did not respond to CFI QRY.

http://lists.infradead.org/pipermail/linux-mtd/2014-May/053872.html

These devices were sold in 2002-2003 so they are now >15yrs old and I have two of them working flawlessy.

Regards
Andrea

Quoted 35 lines

For example in the middle of a file - page sized (2K) data is read as zero. And this file is RO (no modification). And such zero read is persistent - happens all the time. The only way is to replace the whole file (erase it and write again).

We use yaffs file system.

And such errors pop up in random places.

Quoted 7 lines

The fewer erase cycles that a given flash block has seen, the less wear there has been on the insulation, and the better the retention would be. The ten year spec is under the worst case condition of the maximum number of erase cycles having been performed on the flash.

/Ricard

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

A message that is not in the archive (sent off-list or not yet received): CAAQYJAtBGn_-8z-1NQbVYPiVm6W3zquibLK9jutWWKGn0RBWuQ@mail.gmail.com

#5 lore raw

Hi Andrea,

Thanks for your response!

Quoted 59 lines
Quoted 48 lines · Lukasz Majewski

Hi Ricard,

Quoted 28 lines · Lukasz Majewski
Quoted 17 lines

I'd like to ask you for sharing your experience with NAND Flash devices
- which may be older that their data retention time.

I've a problem with Flash NAND memory (Samsung 128Mx8).

In the data sheet [1] the manufacturer claims that it has 10 years for data retention. The device equipped with it is a bit older than 10 years.

How one can diagnose that data retention time for NAND Flash has been exceeded?

Is that:

Quoted 8 lines

- The number of bit flip errors on a RW page so large that ECC cannot fix it?

- Or are whole RW pages erased (0xFF)/corrupted/cleared (0x00)?

- Or any other evidence?

Thanks in advance for your help.

Quoted 7 lines

I think the interpretation is that the manufacturer guarantees that under the circumstances specified (temperature, supply voltage, erase cycles etc) that the data will be retained for at least ten years, beyond that it's just not specified. It doesn't mean that something catastrophic will happen after ten years, i.e. ten years is not a hard limit beyond which things start going haywire.

Thanks for your explanation.

Quoted 8 lines

I can't say I have experience with old NAND flashes loosing their data, but technically I would expect that what happens is that eventually the charge leaks away from the bit cells, causing bit flips, quite simply, so it's the same mechanism that requires the flash to be 'scrubbed' periodically to check if the data needs to be rewritten.

Quoted 7 lines
Quoted 2 lines

I.e. it's the first case in your list, the number of bit flips increases.

Unfortunately with my device I do experience the second scenario.

I do observe pages read as zeros.

Quoted 6 lines

Hello,

I think I have seen the same issue: one defective device did not respond to CFI QRY.

http://lists.infradead.org/pipermail/linux-mtd/2014-May/053872.html

I do not have (yet) the CFI commands dump, but in my case Erase-> Reflash sequence causes the file content to be correct.

IMHO, If the Flash memory controller itself is broken, then "re-flashing" would not help.

Maybe - in my case the NAND flash driver (2.6 kernel) causes the issue (with zero filled page showing up in the middle of a YAFFS file) by some write done at mistakingly calculated address?

Any ideas/hints are more than welcome :-)

Best regards,
Łukasz Majewski

Quoted 47 lines

These devices were sold in 2002-2003 so they are now >15yrs old and I have two of them working flawlessy.

Regards
Andrea

Quoted 37 lines

For example in the middle of a file - page sized (2K) data is read as zero. And this file is RO (no modification). And such zero read is persistent - happens all the time. The only way is to replace the whole file (erase it and write again).

We use yaffs file system.

And such errors pop up in random places.

Quoted 8 lines

The fewer erase cycles that a given flash block has seen, the less wear there has been on the insulation, and the better the retention would be. The ten year spec is under the worst case condition of the maximum number of erase cycles having been performed on the flash.

/Ricard

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang
Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email:
[email protected]

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected]