The cool thing here is that we only need 1 drive to make a RAID 10 or RAID 1 array, we just tell the Linux mdadm utility that the other drive is "missing" and we can then add our original drive to the array after booting into our new RAID array.
Step#1 Install tools we need
yum -y install mdadm rsync
Step #2 Create your partitions on the drive that will be our RAID array
Here I assume it is /dev........
This happens on any file an even just typing "vi"whereas it never happened before. I suspect an update or environment variable is causing this issue
When entering vi I get this weird stuff
E488: Trailing characters: t_Sbet
E171: Missing :endif
When exiting vi I get this weird stuff
I've only ever seen this in Ubuntu for some reason and it is because of the /etc/nsswitch.conf settings.
So the issue is that if the hostname's reverse DNS cannot be found that you need to go back to DNS which was not the default in this nsswitch.conf file for some strange reason.
Edit /etc/nsswitch.conf and replace your "hosts" line with this:
#hosts: files dns mdns4_minimal [NOTFOUND=return] mdns........
This booting error is because the Xen PV guest image uses the Xen kernel, this is not compatible with anything but a host running a Xen kernel.
I did a kpartx -av virtual.img and then it created some partitions that showed up in fdisk.
I mounted it and did a chroot into it and removed the xen kernel and installed a normal kernel but Xen still shows the same kernel in Grub (only the Xen one).
This is strange but it seems like this Xen PV guest has some sort of hidden or........
I've encountered this problem before and I believe it may affect other drivers (I could test but I don't have time). This was happening on my custom Linux system with the pcnet32 driver.
pcnet32: eth0: transmit timed out, status 97fb, resetting (and some other kernel module tracing in dmesg)
Basically it means the card is connected (it shows connected in full duplex etc.. and recognized if the cable is disconnected too) but no packets can be sent or received........
This is a very weird, annoying and bizarre quirk with many distributions, especially Debian. The home and end keys don't work, but it's a simple fix as long as you found this article :)
You just have to edit /etc/inputrc:
Find the commented lines as shown below:
# "e[1~": beginning-of-line
# "e[4~": end-of-line
*If you can't find the above, just copy and paste the code below into your inputrc, it will en........