Got an older server here, running CentOS 6.6 (64-bit). Suddenly, at
0-dark-30 yesterday morning, we had failures to connect.
After several tries to reboot and get working, I tried yum update, and
that failed, complaining of an python krb5 error. With more investigation,
I discovered that logins
On Mon, April 6, 2015 4:37 pm, m.r...@5-cent.us wrote:
Got an older server here, running CentOS 6.6 (64-bit). Suddenly, at
0-dark-30 yesterday morning, we had failures to connect.
After several tries to reboot and get working, I tried yum update, and
that failed, complaining of an python
On 2015-04-07, Valeri Galtsev galt...@kicp.uchicago.edu wrote:
before even running fsck or badblocks (BTW, badblocks has
non-destructive mode) - too late to mention now. You may need this image
for future forensics.
e2fsck -c will run badblocks in read-only mode, so it may not be too
late.
On 04/06/2015 02:37 PM, m.r...@5-cent.us wrote:
I then loaded the drive in another server, and examined it. fsck reported
both / and /boot were clean, but when I redid this with fask -c, to check
for bad blocks, it found many multiply-claimed blocks.
Just running fsck with no arguments will
4 matches
Mail list logo
