On Friday 17 February 2012, m.r...@5-cent.us wrote:
> SMART Self-test log structure revision number 1
> Num Test_DescriptionStatus Remaining
> LifeTime(hours) LBA
> _of_first_error
> # 1 Extended offlineCompleted without error 00% 2536
> -
> # 2 Short offl
On Friday 17 February 2012, Andrzej Szymański
wrote:
> As the location and contents of this sector are quite hard to find,
> the simplest, but the most troublesome way of solving the problem is
> moving all data away from this disk, writing the whole surface with
> zeros (dd) and moving the data
Mike VanHorn wrote:
>
> FWIW, on some of my workstations, when I have gotten the "sector pending"
> messages, I have been able to take the drive out and run the
> manufacturer's diagnostics on it (in my case, Seatools), and that fixed
> some things and I haven't had any issues since.
>
Well, since
W dniu 2012-02-17 21:25, m.r...@5-cent.us pisze:
> Mike Burger wrote:
> Ok, but my thinking was, first, that after the fsck, the system wouldn't
> try to write to the bad sector, thus not provoking smart. The more
> annoying thing is that I don't understand why smartctl doesn't give the
> same info
FWIW, on some of my workstations, when I have gotten the "sector pending"
messages, I have been able to take the drive out and run the
manufacturer's diagnostics on it (in my case, Seatools), and that fixed
some things and I haven't had any issues since.
---
Mike VanHorn
Senior Computer Systems A
Mike Burger wrote:
>
>> A few weeks ago, one of my servers started complaining, via smartd, that
>> one drive had one unreadable sector. I umounted it, and ran an fsck -c,
>> then remounted it. Error didn't go away. Now, what's really annoying is
>> that I've gotten back to it today, and it's repor
> A few weeks ago, one of my servers started complaining, via smartd, that
> one drive had one unreadable sector. I umounted it, and ran an fsck -c,
> then remounted it. Error didn't go away. Now, what's really annoying is
> that I've gotten back to it today, and it's reporting the problem, as it
A few weeks ago, one of my servers started complaining, via smartd, that
one drive had one unreadable sector. I umounted it, and ran an fsck -c,
then remounted it. Error didn't go away. Now, what's really annoying is
that I've gotten back to it today, and it's reporting the problem, as it
has for w
8 matches
Mail list logo
