Unable to Login into my server via ssh or Linode Shell (Lish)

Thanks for including the links to the screen shots.

Looking at the second one, it looks little cut off, but I believe the first line reads:

VFS: Mounted root (ext4 filesystem) readonly on device 8:0.^M

This message basically means that your Linode's primary disk has been mounted as readonly.

To address this, a filesystem check using the fsck utility will identify any bad sectors on your disk and attempt to repair them. You'll want to boot your Linode into Rescue Mode, and follow our guide to Performing a File System Check. Please note that fsck should never be run on a mounted disk.

To read the output from your console in Weblish, you can use the following commands to enable scrolling:

CTRL-A + ESC

Thank you for your help.
Does the fsck utility will hurt my data? because i don't have a backup :(

The fsck will hopefully fix any current issues with your disk. There's no promise that there won't be some data loss.

If data loss is a concern, you could, there are two ways that I can think of to create a copy of what you currently have. You can then perform actions on this copy, rather than doing anything to the original disk.

Manually copy disk or files from one Linode to another:

1. Spin up a new Linode
2. Boot into Rescue Mode
3. Using scp, move data over to the new Linode
4. try running fsck on the new Linode to check the data integrity
5. Either fix the disk on the old Linode, or delete the old Linode after you've confirmed the new Linode has what you need.

Utilizing our Backups service, here's an alternative to those manual steps above:

• Add the Backups service to your Linode
• Take a Snapshot
• Restore to a new Linode, and then follow from step 4 from above.

If DNS records are important, you can swap your IP addresses, as long as the new Linode is in the same data center.

Hi, I follow the steps to perform a file system check in rescue mode, and I got this

root@ttyS0:~# e2fsck -f /dev/sda
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda: 99789/1213056 files (0.1% non-contiguous), 4404408/5111808 blocks

Great! After performing the file-system check you can reboot your server. If fsck fixed the issues, your Linode should boot normally.

Nope…My server is still down. I got this logs in Lish

[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Record successful boot for GRUB...
         Starting LSB: starts Apache Web Server...
         Starting LSB: daemon to balance interrupts for SMP systems...
         Starting Login Service...
         Starting LSB: Start/stop sysstat's sadc...
         Starting System Logging Service...
         Starting LSB: starts the nginx web server...
         Starting Accounts Service...
         Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
         Starting Permit User Sessions...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started System Logging Service.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started LSB: starts Apache Web Server.
[  OK  ] Started LSB: daemon to balance interrupts for SMP systems.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[FAILED] Failed to start LSB: Start/stop sysstat's sadc.
See 'systemctl status sysstat.service' for details.
[FAILED] Failed to start LSB: starts the nginx web server.
See 'systemctl status nginx.service' for details.
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Started Permit User Sessions.
[FAILED] Failed to start Raise network interfaces.
See 'systemctl status networking.service' for details.
[FAILED] Failed to start Accounts Service.
See 'systemctl status accounts-daemon.service' for details.

This is just a guess but I'm wondering if you're possibly running out of disk resources which might prevent your Linode from booting up all the way.

To confirm: If you boot into Rescue Mode and chroot into your disks, you can run the below commands to check if you're running out of disk space, memory or inodes.

To chroot into your disks run the following in the Finnix (Rescue Mode) environment:

mount -o exec,barrier=0 /dev/sda
cd /media/sda
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount -t devpts pts dev/pts/
chroot /media/sda /bin/bash

Then run:

df -h

free -m

df -i

You should see something like the following:

root@finnix:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda         25G  962M   22G   5% /
devtmpfs         10M     0   10M   0% /dev
root@finnix:/# free -m
              total        used        free      shared  buff/cache   available
Mem:            990          81         837           0          71         893
Swap:             0           0           0
root@finnix:/# df -i
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/sda       1505280 33142 1472138    3% /
devtmpfs        125814  1397  124417    2% /dev

https://linode.com/docs/troubleshooting/rescue-and-rebuild/#change-root

If you are running out of disk space or memory, it might simply be a matter of increasing your plan size:

https://linode.com/docs/platform/disk-images/resizing-a-linode/

If this isn't the issue, you could always boot back into Rescue Mode, start SSH, then download your data so you can preserve it and use it when rebuilding your Linode.

root@ttyS0:~# cd /media/sda
root@ttyS0:/media/sda# mount -t proc proc proc/
root@ttyS0:/media/sda# mount -t sysfs sys sys/
root@ttyS0:/media/sda# mount -o bind /dev dev/
root@ttyS0:/media/sda# mount -t devpts pts dev/pts/
root@ttyS0:/media/sda# chroot /media/sda /bin/bash
I have no name!@finnix:/# 
I have no name!@finnix:/# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda         20G   17G  1.8G  91% /
devtmpfs         10M     0   10M   0% /dev
I have no name!@finnix:/# free -m
              total        used        free      shared  buff/cache   available
Mem:            990          71         832           0          86         889
Swap:             0           0           0
I have no name!@finnix:/# df -i
Filesystem      Inodes IUsed   IFree IUse% Mounted on
/dev/sda       1213056 99789 1113267    9% /
devtmpfs        125814  1396  124418    2% /dev
I have no name!@finnix:/#

It seems not out of disk space or memory. I think maybe the system is broken or lost some system files. Maybe I should rebuilding my Linode, so sad :(

In looking at the output of df -h it's showing the size of /dev/sda to be 20GB. Since our Nanode plan provides 25GB of space, it looks like you may not be taking advantage of all your disk space.

Since you're almost running out of storage space (Avail 1.8GB) you may want to try resizing your disk to be larger (before you rebuild), just to test it out:

https://linode.com/docs/quick-answers/linode-platform/resize-a-linode-disk/

1.8GB seems like it should be a sufficient amount of extra space to start up your server, but since you're cutting it very close, I'd try increasing the disk size before rebuilding.

Thank you but it does not help. I have resize my disk to 25GB, but got the same error messages.