Disk /dev/sdb: 15.22 GiB, 16336814080 bytes, 31907840 sectors Disk model: SD/MMC Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 The fdisk output is above and below is the error you may get when trying to use the d........

Edit your /etc/hostapd/hostapd.conf file like below and restart hostapd. #WPS stuff # Enable control interface for PBC/PIN entry wpa_psk_file=/etc/hostapd/hostapd.psk ctrl_interface=/var/run/hostapd eap_server=1 wps_state=2 ap_setup_locked=1 wps_pin_requests=/var/run/hostapd.pin-req config_methods=label display push_button keypad #WPS model info stuff change to suit your needs d........

This is certainly a poor design, as you can read many seasoned admins who have updated their iDRAC only to have it killed. One possible cause is not by doing all the incremental updates, doing updates from an old iDRAC to one many revisions newer is a sure way to kill things, but even then there is no guarantee based on the amount of failures. List of threads of people's dead iDRAC's:........

apt install tftpd-hpa #change TFTP_ADDRESS to by setting address to 192.168.1.1:69 or the IP you need, otherwise it will listen on all IPs and interfaces which could be a security risk. # edit /etc/default/tftpd-hpa TFTP_USERNAME="tftp" TFTP_DIRECTORY="/srv/tftp" TFTP_ADDRESS="192.168.1.1:69" TFTP_OPTIONS="--secure"........

This sometimes happens when trying to install the EFIversion of grub to a device when you are booted into Legacy/MBR mode. It doesn't seem to occur on all machines, but some and seems somewhat BIOS dependent. grub-install --target=x86_64-efi /dev/sda Installing for x86_64-efi platform. grub-install.real: warning: Couldn't find physical volume `(null)'. Some modules may be missing from core image.. grub-install.real: warning: Couldn't find physica........

Here is an easy way to restore things if you have the starting point and size of each partition using fdisk: In this example we pretend that /dev/sda was wiped out, but the running system still has the info in /sys/class/block/sda Go into each partition and record the "start" and "size" hostdev@box /sys/class/block/sda/sda1 $ cat start 2048 hostdev@box /sys/class/block/sda/sd........

This may be necessary if you have a VM or if for some reason you just want to be more efficient with your space and have the flexibility of changing your swap space at will. What we mean is the ability to use a "swap file" or similar to the Windows "pagefile" that normally resides on the root or c: partition of Windows. Here's all you have to do and then you to can have a single partiton with everything, including the swap file on the root partition if you........

The Best Docker Tutorial for Beginners We quickly explain the basic Docker concepts and show you how to do the most common tasks from starting your first container, to making custom images, a Docker Swarm Cluster Tutorial, docker compose and Docker buildfiles.........

This assumes that you've already installed the relevant HWIC cards eg. Cisco Asynchronous Serial NIM These are essentially cards that you install into your router, once installed you connect an Async cable to one of the ports on the card which normally gives you 8 console cables and are normally labelled 1 through 8. You connect all of the cables to the devices you need (even non-Cisco devices) whether switches, routers or firewalls, they will usually work. The real m........

There aren't too many simple guides that show you how to use commands to setup your USB or other drive as a normal bootable drive where you can easily boot custom kernels or whatever OS you would like. 1. Get the tools we need: We install "syslinux" for MBR and "syslinux-efi" for EFI and "MBR" as we need a tool that embeds the actual MBR into our USB: sudo apt install syslinux syslinux-efi mbr........

Use fdisk on your USB drive to create a bootable NTFS partition (in my case /dev/sdb): sudo fdisk /dev/sdb Welcome to fdisk (util-linux 2.27.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free)........

This is a security hole in my opinion and should be plugged by editing the lock screen ui layout: vi /usr/share/mate-screensaver/lock-dialog-default.ui #find these objects and set the visible property to false object class="GtkLabel" id="note-tab-label" object class="GtkLabel" id="auth-username-label> object class="GtkLabel" id="auth-realname-label"........

Install Errors on Version 12: This error happened on QEMU emulator version 2.11.1 pve-qemu-kvm_2.11.1-5 on Proxmox/Debian but installing on QEMU.12 on Centos 6 did not produce the error. *Update it is not related to the OS or QEMU version. This happened in Centos 6 too after a second install. What really causes this even though you successfully install........

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs. qemu-kvm command: /usr/libexec/qemu-kvm -version QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard ........

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........

It has been a big pain for a long-time to install Windows from a Linux environment. I used to run a windows install server and it never worked right for some reason (the install would fail on most servers). Before getting start be sure to setup your samba share so once you boot into WinPE you can mount the install for whatever Windows you want /etc/samba/smb.conf [smbwinstall] path = /tftpboot/images/winstall guest ok = yes........

This guide will work for most modern Linux versions like Centos RHEL 7, Debian, Mint, Ubuntu etc... In Centos 7 the days of editing the "kernel"line and adding "single"are gone. On top of that sometimes after a new install passwords do not work, maybe you forgot your password or for some other reason you need to break in or fix your system? It could also be because you can't mount your root / or some other /etc/fstab error and many other err........

yum -y install samba vi /etc/samba/smb.conf https://www.kernel.org/pub/linux/utils/boot/syslinux/syslinux-6.03.zip mkdir syslinux;cd syslinux;unzip syslinux-6.03.zip mkdir -p /tftpboot/libs/ cp bios/com32/modules/linux.c32 /tftpboot/libs/ cp bios/com32/libutil/libutil.c32 /tftpboot/libs/ cp bios/com32/lib/libcom32.c32 /tftpboot/libs/ #add lib path echo "PATH libs" >> /tftpboot/pxeli........

Done on Centos 7.3 very important as clearly based on older guides it was a lot easier and more simpler! Hint do not use grub2-install! If you have trouble booting after this check this CentOS mdadm RAID booting/fixing guide. One huge caveat if you are an oldschool user or sysadmin who has avoided UEFIbooting The nor........

*Update so this doesn't work it must be something to do with the path of nfs or something else but the installer fails with "Installer crashed" at the end whereas with the CD/USB it works. This assumes you've already installed and configured a separate PXE/DHCP server somewhere else and your /tftpboot directory is setup. This is for Linux Mint 18.1 but generally applies to most versions although you may have tro change things like "casper"........

You may get this after a long time of not rebooting but especially if you have rsync'd a / partition or deployed an image to another VPS or computer, you will often have this issue. The good thing it usually just takes a reboot. Here is more info from Centos........

grub> root (hd0,0) root (hd0,0) Filesystem type is ext2fs, partition type 0xfd grub> setup (hd0) setup (hd0) But if you do: root (hd1,0) setup (hd1) it does work, I think hd0/sda had a GPT partition that was not removed properly (what I did was just dd bs=512 count=1 the partition table from another drive since the partition table should be identical). Checking if "/boot/grub/........

I am getting this error: kernel:[14277.697049] EDAC MC0: UE row 4, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=0 RDWR=Read RAS=7048 CAS=0 FATAL Err=0x4 (>Tmid Thermal event with intelligent throttling disabled)) But many people believe this is a bug/false message and the server is running stably.........

Here is the scenario you or a client have a remote machine that was installed as a standard/default minimal Centos 6.x machine on a single disk with LVM for whatever reason. Often many people do not know how to install it to a RAID array so it is common to have this problem and why reinstall if you don't need to? In some cases on a remote system you can't easily reinstall without physical or KVM access. So in this case you add a second physical or disk or already ha........

If you remove the white label on the chip (near the CMOS battery) you will find the following details about it: SST 49LF080A 33-4C-NHE It is the PLCC32 type and can be pried and removed safely (but be very careful) with an eye glass flat head screw driver. If you just have a bad flash you may be able to reprogram your original or just buy another one with the part# above and reprogram it. This is great news for people who have bricked th........

I'm not sure why I'm getting these but all memory modules are the exact same and all passed memtest successfully although they are ECC. I've heard that ECC RAM can't be tested as well and the kernel seems to indicate they are non-fatl recoverable errors. I wonder if the BIOS has aggressive RAM timing or maybe the controller or motherboard is bad. [ 12.716515] EDAC MC: Ver: 2.1.0 [ 12.717771] EDAC MC0: Giving out device to........

http://deepxw.blogspot.ca/search/label/Universal%20Termsrv.dll%20Patch The above site has the patch that does this essentialy turning a Desktop Windows into a full fledged RDP server.........

LSi Megaraid At first it was configured as a RAID 0, then I deleted the Virtual Disk Group. I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing. To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........

kernel: EDAC MC0: CE page 0x0, offset 0x0, grain 1073741824, syndrome 0x1a, row 2, channel 0, label "": i3200 CE I believe this is a hardware issue, it's usually bad RAM, incompatible RAM or bad timing or even a motherboard/RAM controller.........

I find it very annoying that this mouse has buttons on the side where you grip it and the left one goes back in the browser and the right one goes forward. Imagine if you're filling out a form and hit it, most forms/websites have no protection against it. Source: http://ubuntuforums.org/showthread.php?t=2065400 Here's how I fixed it with xinput, it's too bad there's no good standard GUI to........

This is something I often setup for clients because it's very helpful for people in datacenters, this allows custom OS installs on demand, you can customize it more by using kickstart etc.. but here's a base I use before customizing more: This little script below will install everything you need to get booting by PXE Linux. It also assumes you set a local IP (be sure not to overwrite your existing IP) on eth0:0 (note the :0) as 192.168.1.10 and it........

I installed 5.5 with a 300GB RAID 1 partition (boot is also on this partition). It booted up fine the first few times until after I used a Live CD and accessed the array, and it became named /dev/md127 for some reason. Now whenI boot into CentOS I get a kernel panic and different errors, once I got "invalid superblock", even though the array is fine (it didn't happen again, probably because I was sure to dismount and stop the mdadm array properly). Here's what........

Before we start I take no responsibility for this, you should have a backup and if you make a mistake during this process you could wipe out all of your data. So backup somewhere else before starting this as a precaution, or make sure it's data you could afford to lose. The RAID 1 Setup (Hardware Wise) I've already setup my 2 x 1TB (Seagate) drives with identical partitions, make sure your new hard drive (the empty one) is setup like your curr........