On 06/03/2015 03:51 AM, Petter Adsen wrote:
On Tue, 2 Jun 2015 18:36:43 +0300
Selim T. Erdoğan wrote:
On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote:
This just in:
[12675.977977] ata5: hard resetting link
[12680.979063] ata4: softreset failed (1st FIS failed)
[12680.979080]
On Tue, 2 Jun 2015 18:36:43 +0300
Selim T. Erdoğan wrote:
> On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote:
> >
> > This just in:
> > [12675.977977] ata5: hard resetting link
> > [12680.979063] ata4: softreset failed (1st FIS failed)
> > [12680.979080] ata4: hard resetting link
>
On Tue, 02 Jun 2015 13:46:55 -0400
Gary Dale wrote:
> On 30/05/15 02:17 AM, Petter Adsen wrote:
> > On Fri, 29 May 2015 13:18:17 -0600
> > Bob Proulx wrote:
> >
> >> Jochen Spieker wrote:
> >>> Petter Adsen:
> I'm starting to suspect that it is. Either that, or the
> controller on the
On 30/05/15 02:17 AM, Petter Adsen wrote:
On Fri, 29 May 2015 13:18:17 -0600
Bob Proulx wrote:
Jochen Spieker wrote:
Petter Adsen:
I'm starting to suspect that it is. Either that, or the
controller on the motherboard, which would be even worse.
Or just the cable (if we are not talking about
On Fri, May 29, 2015 at 11:18:35AM +0200, Petter Adsen wrote:
>
> This just in:
>
> [12490.684280] ata4.00: exception Emask 0x0 SAct 0x7f007fff SErr 0x0 action
> 0x6 frozen
> [12490.684296] ata4.00: failed command: WRITE FPDMA QUEUED
> [12490.684312] ata4.00: cmd 61/b8:00:e8:7d:87/00:00:06:00:00
On Fri, 29 May 2015 13:18:17 -0600
Bob Proulx wrote:
> Jochen Spieker wrote:
> > Petter Adsen:
> > > I'm starting to suspect that it is. Either that, or the
> > > controller on the motherboard, which would be even worse.
> >
> > Or just the cable (if we are not talking about a laptop). I got rid
Jochen Spieker wrote:
> Petter Adsen:
> > I'm starting to suspect that it is. Either that, or the controller on
> > the motherboard, which would be even worse.
>
> Or just the cable (if we are not talking about a laptop). I got rid of
> similar errors in the past by replacing the SATA cable.
If i
Petter Adsen:
> On Fri, 29 May 2015 11:04:09 +0200
>>
>> It's probably a good idea to test with the manufacturers own
>> diagnostic tool to make sure nothing is wrong with the disk.
>
> I'm starting to suspect that it is. Either that, or the controller on
> the motherboard, which would be even wo
On Fri, 29 May 2015 11:04:09 +0200
Sven Arvidsson wrote:
> On Fri, 2015-05-29 at 09:08 +0200, Petter Adsen wrote:
> > When I woke up this morning, one of my boxen had spewed out a ton of
> > errors from one of my SSDs (the root drive), remounted read-only,
> > and went into a kernel panic.
>
> I
On Fri, 2015-05-29 at 09:08 +0200, Petter Adsen wrote:
> When I woke up this morning, one of my boxen had spewed out a ton of
> errors from one of my SSDs (the root drive), remounted read-only, and
> went into a kernel panic.
It's probably a good idea to test with the manufacturers own diagnostic
> 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail
Always - 0
Reallocated_Event_Count is 0 meaning no bad sectors were ever found. I
have a failing drive atm and this number slowly piles up.
> 201 Unc_Soft_Read_Err_Rate 0x001c 120 120 000Old_age
Offlin
On 29/05/2015 5:08 PM, "Petter Adsen" wrote:
>
> When I woke up this morning, one of my boxen had spewed out a ton of
> errors from one of my SSDs (the root drive), remounted read-only, and
> went into a kernel panic.
>
> After rebooting everything seems fine, though. I've ran a SMART long
> test,
When I woke up this morning, one of my boxen had spewed out a ton of
errors from one of my SSDs (the root drive), remounted read-only, and
went into a kernel panic.
After rebooting everything seems fine, though. I've ran a SMART long
test, but as I found out the SMART error log is not supported on
13 matches
Mail list logo
