• Why SMART is not smart at all and doesn't properly predict disk errors that cause a kernel panic or crash


    Before getting into the output here is my typical experience with SMART, there is what I call a "bad disk" with pending and uncorrectable sectors that cannot be reallocated. It has caused a kernel panic and system crash repeatedly as we can see from the logs. But SMART says it has "PASSED" its self assessment. SMART is still useful to me but it is more about looking at Current_Pending_Sector. Any time I have had anything but 0 for that attribute it........
  • Centos 6.6/6.9 KVM VM Kernel Panic On Boot - Kernel panic - not syncing: Attempted to kill init!


    Iam not sure why this is happening neither the hostnode or VM changed. All I did was reboot the hostnode and startup the Centos VM again, also note it happened with the original kernel on the VM and also the latest 6.9 kernel as of this writing as shown below. Host Node: Centos 6.9 Kernel:2.6.32-696.6.3.el6.x86_64 Kernel: 2.6.32-042stab123.9 Same result in any kernel above........
  • cudaminer freezes Linux Mint taints kernel


    When running cudaminer once it tries to initialize the card the entire screen freezes. The computer itself is still running but the Xorg is done for, you cannot even switch to another console window and must reboot (even an mdm or Xorg restart does not help). At first cudaminer will give you these errors: stratrum_recv_line failed ...retry after 15 seconds GPU #0: Geforce 210 with compute ca........
  • mdadm frozen and doesn't realize array is dead/missing failed due to unplugged drives


    This was a surprising bug but I unplugged all drives for an array md127. At first it was just 1 drive and mdadm seemed to notice this. I unplugged the second drive taking the array offline but mdadm did not realize it was offline and still showed a non-existent disk as being part of it. This created problems trying to unmount it or even to stop this array with mdadm freezing. As for how to fix it I can only think of making sure you are not in a mounted path of........
  • fdisk wq causes hung process


    I created a new partition table on a newly plugged in device and it caused fdisk to hang (even force kill does not work). It also may be a bad drive or some other issue because fdisk -l hangs after the first 2 HDDs (totaly of 8 HDDs on this system): [1232879.903596] INFO: task fdisk:27176 blocked for more than 120 seconds. [1232879.903607] Tainted: P&nbs........
  • Linux Centos 6 Weird Kernel Panic


    Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tained: 3.2.51-3.el6.x86_64 #1 Call Trace: panic+0x8c/0x1a2 forget_original_parent+0x34d/0x360 exit_notify+0x12/0x140 do_exit+0x1d8/0x400 do_group_exit_+0x50/0xc0 sys_exit_group+0x12/0x20 system_call_fastpath+0x16/0x1b panic occurred, switching back to text console........
  • Kernel panic - not syncing: Attempted to kill init! Pid: 1,comm: init Tained: G I------------- 2.6.32-358.el6.x86_64 #1 Call Trace: [] ? panic+0xa0/0x16f [] ? do_exit+0x862/0x870 [] ? fput+0x25/0


    Kernel panic - not syncing: Attempted to kill init! Pid: 1,comm: init Tained: G I------------- 2.6.32-358.el6.x86_64 #1 Call Trace: [] ? panic+0xa0/0x16f [] ? do_exit+0x862/0x870 [] ? fput+0x25/0x30 [] ? do_group_exit+0x58/0xd0 [] ? sys_exit_........
  • Latest Articles

  • Linux How To Create A RamDisk
  • mdadm force resync when resync=PENDING solution
  • Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG
  • Proxmox trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-102.conf' - got timeout
  • Debian 9 SSH root password authentication failure password not working problem / solution
  • QEMU / KVM How To Manually Create Basic Virtual Machine VM
  • Linux wlan0 check all wireless clients
  • PHP Issues With Decoding Strange Smart Quotes And Non-Standard ASCII Characters
  • /etc/iproute2/rt_tables default settings file in Linux Centos 6,7 and most other NIX's
  • bind named error solutions named[2169]: error (no valid DS) resolving / error (broken trust chain) resolving / : error (no valid RRSIG) resolving 'com/DS/IN':
  • iptables how to log ALL dropped incoming packets
  • How To Edit Linux Based NM Network Manager Connection Settings Without GUI
  • Linux Disable IPV6 Centos / Debian / Mint Howto
  • Linux use growisofs to burn a larger file on a BD-R / Bluray Disc
  • Linux partprobe/partx cannot access last and 4th partition
  • DRBD Errors Caused By Physical Corruption
  • mdadm: add new device failed for /dev/sdb4 as 3: Invalid argument solution
  • Linux named / bind how to dump, view and clear the cache!
  • Centos 6 / 7 / 8 How To Change Default nameservers in /etc/resolv.conf when using DHCP / dhclient
  • Adobe Acrobat Reader for Linux to use and view XFA Fillable Forms