[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] Can't write to SSD
- Subject: [ale] Can't write to SSD
- From: cfowler at outpostsentinel.com (Chris Fowler)
- Date: Mon, 21 Nov 2016 22:15:37 -0500 (EST)
- In-reply-to: <CAEo=5PzojOHwff8dHuekCmcHWOSBfk9T_4q=iNaUtRr2VkBXOg@mail.gmail.com>
- References: <1325811461.13108359.1479776223578.JavaMail.zimbra@outpostsentinel.com> <CAEo=5PzojOHwff8dHuekCmcHWOSBfk9T_4q=iNaUtRr2VkBXOg@mail.gmail.com>
> 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/d70876bf/attachment.html>