Problems with headless system

[Jay Ridgley]

On 04/14/2017 10:14 AM, Ralf Mardorf wrote:
> On Sat, 15 Apr 2017 00:20:33 +1000, Karl Auer wrote:
>> On Fri, 2017-04-14 at 08:27 -0500, Jay Ridgley wrote:
>>> Input/output error
>>
>> IMHO this is almost certainly evidence of a failing disk.
>
> A failing disk and/or some other hardware is fishy. I got lots of those
> errors with my old mobo, at the same time at least one disk had pending
> sectors. To make a long story short, even the HDD that definitively has
> got bad blocks, doesn't cause I/O errors, when "using" it with the new
> mobo. I would check the disk and replace it, if it should be fishy,
> since it's much likely that a fishy disk, is also the
> culprit causing the I/O errors. Unfortunately something else could be
> borked, too.
>
> sudo smartctl --all /dev/...
> sudo fsck -vcck /dev/...
>
>
All,

I rebooted, a message was displayed from the ssh connection that reads:

*** /dev/mapper/mateo-root will be checked for errors at next reboot ***

I did a powerdown and powerup waited for the system to come up and 
connected again, same message. Can't use fsck since the drive is mounted...

I tried to do a sudo du / and toward the end I got several messages: 
"du: cannot access '(file name here)': Transport is not connected"
du did complete, however.
The drive has plenty of free space.

I did a sudo reboot and the same message appears upon connection.

I think a visit to my favorite computer shop is in order here.

I will let you know...

Cheers,
Jay
-- 
Jay Ridgley
jridgley2 at austin.rr.com
Registered Linux User ID - 9115
https://linuxcounter.net/cert/9115.png
Registered Ubuntu User ID - 23320