On Sat, Jul 2, 2016 at 1:55 PM, Chris Murphy wrote:
> On Fri, Jul 1, 2016 at 4:19 PM, Richard Shaw wrote:
>> Thanks for the detailed reply so forgive me for not quoting :)
>>
>> I'm not ready to believe the drive is bad, I think what happened is that I
>> didn't realize it but playing around with
On Fri, Jul 1, 2016 at 4:19 PM, Richard Shaw wrote:
> Thanks for the detailed reply so forgive me for not quoting :)
>
> I'm not ready to believe the drive is bad, I think what happened is that I
> didn't realize it but playing around with cockpit I accidentally installed
> tuned, which is interes
Thanks for the detailed reply so forgive me for not quoting :)
I'm not ready to believe the drive is bad, I think what happened is that I
didn't realize it but playing around with cockpit I accidentally installed
tuned, which is interesting in concept but the aggressive power management
did not pl
On Thu, Jun 30, 2016 at 1:40 PM, Richard Shaw wrote:
> Ok, I think I was able to catch the error without having to get that
> desparate :)
>
> I logged in from work and did journalctl -f and got the following:
>
> http://pastebin.com/3JAL297z
>
> Looks disk hardware related but it's not getting wo
On 06/30/2016 12:40 PM, Richard Shaw wrote:
> Ok, I think I was able to catch the error without having to get that
> desparate :)
>
> I logged in from work and did journalctl -f and got the following:
>
> http://pastebin.com/3JAL297z
>
> Looks disk hardware related but it's not getting worse so
Ok, I think I was able to catch the error without having to get that
desparate :)
I logged in from work and did journalctl -f and got the following:
http://pastebin.com/3JAL297z
Looks disk hardware related but it's not getting worse so I doubt it's the
disk itself, driver problem instead?
Thank
On Thu, Jun 30, 2016 at 8:56 AM, Chris Murphy wrote:
>
>
> On Thu, Jun 30, 2016, 6:21 AM Richard Shaw wrote:
>>
>> Ok, apparently I need to reboot this conversation :)
>>
>> The filesystem is not corrupted (other than what occurs during a forced
>> power off). Many days, it boots and runs just fi
On Thu, Jun 30, 2016, 6:21 AM Richard Shaw wrote:
> Ok, apparently I need to reboot this conversation :)
>
> The filesystem is not corrupted (other than what occurs during a forced
> power off). Many days, it boots and runs just fine for the whole day,
> when it does have a problem, it's not a bo
Ok, apparently I need to reboot this conversation :)
The filesystem is not corrupted (other than what occurs during a forced
power off). Many days, it boots and runs just fine for the whole day, when
it does have a problem, it's not a boot but rather towards the latter part
of the day.
So somethi
On Tue, Jun 28, 2016 at 6:24 AM, Richard Shaw wrote:
> On Sun, Jun 26, 2016 at 12:33 AM, Chris Murphy
> wrote:
>>
>>
>> On Sat, Jun 25, 2016, 8:26 PM Richard Shaw wrote:
>>>
>>> I recently upgraded my wife's laptop to an Acer with a fairly stock
>>> i5-6200U system using the UFEI boot (that was
On Sun, Jun 26, 2016 at 12:33 AM, Chris Murphy
wrote:
>
> On Sat, Jun 25, 2016, 8:26 PM Richard Shaw wrote:
>
>> I recently upgraded my wife's laptop to an Acer with a fairly stock
>> i5-6200U system using the UFEI boot (that was an adventure)
>>
>> About a month ago I started getting strange is
On Sat, Jun 25, 2016, 8:26 PM Richard Shaw wrote:
> I recently upgraded my wife's laptop to an Acer with a fairly stock
> i5-6200U system using the UFEI boot (that was an adventure)
>
> About a month ago I started getting strange issues. Not lockups per se but
> it seems that the drive is somehow
I recently upgraded my wife's laptop to an Acer with a fairly stock
i5-6200U system using the UFEI boot (that was an adventure)
About a month ago I started getting strange issues. Not lockups per se but
it seems that the drive is somehow going into read only. Since that's the
case after it starts
13 matches
Mail list logo
