On Thu, Sep 8, 2016 at 2:29 PM, Todd Russell wrote:
> Final update on this issue. When I took it down, I pulled the drive and
> started a Level 2 SpinRite on it while I took out and reseated the RAM then
> ran memtest. I found no errors in either test, so I also took out the
On Fri 02 Sep 2016 13:33:35 NZST +1200, compdoc wrote:
> As for me, these days I install only SSDs in desktop systems that run
> 24/7, and also use them as boot drives for servers. Over the years I
> have had only one SSD fail, and it did show pending sectors in SMART.
That's not my observation
On Fri 02 Sep 2016 10:14:59 NZST +1200, Todd Russell wrote:
> I will just run level 2 SpinRite on the SSD to force the drive to read
> every spot, which should trigger the error correction if that is happening.
Ehh, you use what for that? Toss spinrite into the bit bucket as
suggested. Log into
Compdoc:
Your spinrite comments just show how dangerous some knowledge is without
propper understanding. Spinrite does indeed force SSDs to "fix" themselves
because it reads extensively (causes heat) and forces "half" working areas
to be marked bad. Most SSDs has minor defects from day one. Just
Final update on this issue. When I took it down, I pulled the drive and
started a Level 2 SpinRite on it while I took out and reseated the RAM then
ran memtest. I found no errors in either test, so I also took out the Intel
4 port gigabit card and reseated that, then put everything back together.
>I'd suggest that before you slag programs, you not rely on old, outdated,
>biased information.
Spinrite 6 is a twelve year program that seemed cool back in the day, but I
would never recommend it to anyone now.
Repairing computers for a living, Im always on the lookout for useful
On Thu, Sep 1, 2016 at 6:43 PM, Walter Parker wrote:
> On Thu, Sep 1, 2016 at 3:06 PM, compdoc wrote:
>
>> >>Coming back tonight to do memtest, SpinRite on the SSD, etc...,
>>
>> Spinrite on an ssd is a terrible idea. It's an ancient program thats even a
On Thu, Sep 1, 2016 at 3:06 PM, compdoc wrote:
> >>Coming back tonight to do memtest, SpinRite on the SSD, etc...,
>
> Spinrite on an ssd is a terrible idea. It's an ancient program thats even a
> bad idea to use on hard drives.
>
> It doesn't even work on drives larger
On Thu, Sep 1, 2016 at 4:26 PM, Todd Russell wrote:
> 1 possible clue I didn't mention. Early in the week, I enabled ssh for the
> first time and it started generating ssh keys... but it never finished.
> Hours later I still couldn't ssh in and shrugged my shoulders and forgot
1 possible clue I didn't mention. Early in the week, I enabled ssh for the
first time and it started generating ssh keys... but it never finished.
Hours later I still couldn't ssh in and shrugged my shoulders and forgot
about it. After the first hard lock reboot, the next time I logged into the
>
> If that supermicro atom board is not ecc then memory could be a
> culprit. I agree though: Spinrite on an SSD?
>
See above about SpinRite. Actually have seen Level 2 force a Samsung SSD to
do the error correction to silently recover data that was not being read
back before.
> How are you
I will just run level 2 SpinRite on the SSD to force the drive to read
every spot, which should trigger the error correction if that is happening.
I was planning to check the caps when I get here later tonight as I have
plenty experience with that scourge. :/ I did use the diagnostics in the
web
On Thu, Sep 1, 2016 at 3:53 PM, Todd Russell wrote:
> Everything had been fine for ages. Had a hard lock Tuesday before lunch...
> couldn't ping it, no response at physical kb, had to hard reboot it.
>
> Came back late that night to apply 2.3.2 update. Had another hard lock
>
I have seen those symptoms on three different machines over the years, and
all of them were hardware failures - RAM on one of them, power supply on
another, and an old consumer-grade PCI network card on the third. (Most of
the pfSense machines I support are running low-end salvaged hardware, so in
>>Coming back tonight to do memtest, SpinRite on the SSD, etc...,
Spinrite on an ssd is a terrible idea. It's an ancient program thats even a
bad idea to use on hard drives.
It doesn't even work on drives larger than 1TB, because it was written in a
time when drives were not that big. And there
Everything had been fine for ages. Had a hard lock Tuesday before lunch...
couldn't ping it, no response at physical kb, had to hard reboot it.
Came back late that night to apply 2.3.2 update. Had another hard lock
today a little after noon. Was looking into it and getting set up to ssh in
from
16 matches
Mail list logo