[ale] Can't write to SSD

[Jim Kinney]

I'm wondering how to force that ssd to call those blocks bad. Maybe the
hdparm secure erase can trigger the wear leveling algo in the unit.

On Nov 21, 2016 10:15 PM, "Chris Fowler" <cfowler at outpostsentinel.com>
wrote:



------------------------------

*From: *"Jim Kinney" <jim.kinney at gmail.com>
*To: *"Atlanta Linux Enthusiasts - Yes! We run Linux!" <ale at ale.org>
*Sent: *Monday, November 21, 2016 9:20:25 PM
*Subject: *Re: [ale] Can't write to SSD

Reformat that disk and wiggle sectors/partitions around and try again. I'm
wondering if the inode that holds dir data is failing. Don't know if
badblocks will work for ssd.


I'm seeing these repeat

EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks not in
datazone - block = 151587081, count = 1
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks not in
datazone - block = 151587081, count = 1
EXT3-fs error (device sda2): ext3_free_blocks: Freeing blocks not in
datazone - block = 151587081, count = 1


I may do a hdparm secure-erase.  This is somewhat of a boot disk.  The real
system runs from memory, but logging is done to SSD.  I could kick that
part and maybe do the secure erase, create part and format, restore files,
restore grub, and restart.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20161121/5999c367/attachment.html>