PTY allocation request failed on channel 0 You may have messed up your environment and specifically under /dev you may have remounted a wrong source point or otherwise killed /dev/pts The solution is to recreate /dev/pts or fix whatever caused it to be wiped out or broken. In verbose mode the client may show this: #verbose client Authenticated to 172.16.17.2 ([172.16.17.2]:22). debug........

Do you hate how Centos 7 defaults to allocating most of your valuable space to /home even though it is a production server? Here is a quick guide on how to take back that space live, while online (of course make sure you have backups just in case something goes wrong!): First we will reduce our home dir by 100G: lvreduce -L -100G /dev/mapper/centos-home WARNING: Reducing active and open logical volume to ........

systemd is like the service manager for your Centos and other modern Linux distributions (including Debian/Mint/Ubuntu) allows you to enable services, stop them, restart them, check their status and even reboot your system. The key commands or arguments you will use with systemctl are the following: Unit Commands: list-units [PATTERN...] List loaded units &nbs........

1.) Replicate the number of partitions in your new drives. gdisk /dev/sda gdisk /dev/sdb I created 3 partitions of the same same size. partition #1: +1G (/boot) partition #2: +60G (swap) partition #3: rest of it (/) #note if you are using GPT/gdisk you need to create separate a partition at least 1MB in size (in my case I would a 4th partition and mark it type ef02).........

This is one in a series of weird things whichIthought was motherboard related (I RMA'd the motherboard), the RAM tests fine with memtest86 and I used badblocks on both RAID 1 members with no errors and smartctl is happy with them. Basically the array crashes the kernel a lot and has issues when writing. [112322.723465] md0: rw=0, want=14958668696, limit=1887460480 [112322.731077] attempt to access beyond end of device [112322.731087] md........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........