Serveurs Dédiés Eco-old - Kimsufi - Unable to ssh due to bash input output error
... / Kimsufi - Unable to ssh d...
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Frage

Kimsufi - Unable to ssh due to bash input output error

Von
^FabL
Beitragender
Erstellungsdatum 2022-05-31 12:29:34 (edited on 2024-09-04 11:55:37) in Serveurs Dédiés Eco-old

## Kimsufi - Unable to ssh due to bash input output error

----------
siljrath
15/02/2014, 12h59
~ new update. ^_^

switched the netboot from rescue pro to a 3.10.23 option from the dropdown menu, instead of back to "hd"... is this is a standard/acceptable long-term resolution to the issue? ~ to just run from this kernel netboot option instead of actually fixing the kernel on the hd (which presumably was the case, some kind of kernel mismatch ~ Hwh called it).

well anyways, after it rebooted, i retried ssh'ing in as standard, and it's all looking good. can ssh.

all in all, this has been a good experience, nice to see more of the wonderful support tools ovh offers. server uptime had been mere days away from 300 last i had looked (surely past it by the time of this first and only hiccup), which was nice [uptime] in itself, and now i'm even happier with my ovh/kimsufi service now i know a bit more of what is at my disposal should things go wrong again in the future.

----------

siljrath
15/02/2014, 12h18
big thnx for the responces.
i'm now in the recue system. poked around with the web interface tests a bit, and then went to ssh in. with the drives mounted, i can confirm that the disks are not full:
Code:

/dev/sda1 9.8G 5.6G 3.7G 61% /mountsda1
/dev/sda2 907G 25G 836G 3% /mountsda2

with the connection here, it'd take a day choking out our bandwidth to get a full backup of all the 25G in home.

somewhat scared to attempt chrooting into it from the rescue system to se what i could accomplish.

this post is effectively just an update.. still rather daunted and clueless, in need of help. thnx

----------

Rindus
13/02/2014, 17h14
siljrath: boot from rescue and move all stuff from home to [whereever]. Give it another shot. Whilst in rescue you might want to do a diskcheck too.

----------

RawrDragon
13/02/2014, 16h58
I'm not sure what the issue might be, but I've experienced similar problems with a full root partition. Are you out of free space maybe?

----------

Hwh
13/02/2014, 16h41
you could start with an "ssh ... dmesg" to see the kernel log (hardware failure related notices?). Or do an "ssh ... smartctl -a /dev/sda" (but that will need root login)...

----------

siljrath
13/02/2014, 16h22
if it's got to be one of those two, i hope it's the former, since surely that'll be easier to remedy... but then, i suppose it's not me who has to fix the hardware.

also, just tried "ssh -t ks392457.kimsufi.com /bin/sh" (and every other shell i could think of), which all only got me to either the same bash errors, or command not found. oh how i regret not installing zsh now, it might have helped me avert this.

*gone to look for "rescue system"*

----------

Hwh
13/02/2014, 16h15
Kernel mismatch or hardware failure, I'd say. You will probably have to take a look via rescue system.

----------

siljrath
13/02/2014, 16h08
unable to ssh into my server.

can ping, can mount with sshfs, can use ssh if i tell it not to do so non-interactively (like for use as a proxy or whatever)
~ just found out i cant scp either (see below)

Code:

$ ssh 176.31.109.148
Password:
Gentoo Base System release 2.1
Linux ks392457.kimsufi.com 3.2.13-grsec-xxxx-grs-ipv6-64 #1 SMP Thu Mar 29 09:48:59 UTC 2012 x86_64 Intel(R) Atom(TM) CPU D425 @ 1.80GHz GenuineIntel GNU/Linux

server : 195967
hostname : ks392457.kimsufi.com
eth0 IPv4 : 176.31.109.148
eth0 IPv6 : 2001:41d0:8:1e94::1/64

-bash: /etc/profile: Input/output error
-bash: /home/digit/.bash_profile: Input/output error
Connection to 176.31.109.148 closed.

Code:

$ scp thing ovhtoo:/home/digit/ │
Password: │
bash: /home/digit/.bashrc: Input/output error │
lost connection

("ovhtoo" being the name i have for it in my local /etc/hosts)

I'm not sure what's causing this.
some update and configuration error on my part? (not that i recall doing anything that could cause this)
some error from a hardware reset or from ddos recover or something? (surely i'd have seen notification of any such)
something else, i know not what...

any help resolving greatly appreciated.

----------
**https://docs.ovh.com/fr/dedicated/ovh-rescue/**


Antworten sind derzeit für diese Frage deaktiviert.