≡ Menu

grub

JBD: Barrier-based Sync Failed On md0-8 – Disabling Barriers Error and Solution

I‘ve used the mdadm command line utility to setup and manage software RAID 6 under Debian Linux server. However, I get the following message in /var/log/messages file:
[ 14.003707] JBD: barrier-based sync failed on md0-8 – disabling barriers

How do I fix the message ‘JBD error message “barrier-based sync failed”‘?
[click to continue…]

Debian Linux: Set a Serial Console

How do I set up a serial console on Debian Linux HP server for troubleshooting and login purpose?
[click to continue…]

Turn on SELinux in Redhat or CentOS Linux Over Remote SSH Session

My hosting company disabled SELinux protection. How do I turn on SELinux over remote ssh session without distributing existing networking services?
[click to continue…]

Linux Disable USB Devices (Disable loading of USB Storage Driver)

In our research lab, would like to disable all USB devices connected to our HP Red Hat Linux based workstations. I would like to disable USB flash or hard drives, which users can use with physical access to a system to quickly copy sensitive data from it. How do I disable USB device support under CentOS Linux, RHEL version 5.x/6.x/7.x and Fedora latest version?
[click to continue…]

Linux: Skip or Bypass a Fsck

Q. I know how to force fsck on the next reboot using /forcefsck file. But how do I skip or bypass a fsck on reboot? How to stop a FSCK from prompting or running automatically when rebooting server.
[click to continue…]

Q. My CDROM drive attached to Stratus ftServer 6210 is not working and it is dumping me with following error:

hdb: lost interrupt
hdb: lost interrupt

hdb: lost interrupt
hdb: status error: status=0x59 { DriverReady SeekComplete DataRequest
Error }
hdb: status error: status=0x40 { LastFailedSense=0x04 }
ide: failed opcode was: unknown
hdb: drive not ready for command
hdb: lost interrupt
hdb: status error: status=0x59 { DriverReady SeekComplete DataRequest
Error }
hdb: status error: status=0x40 { LastFailedSense=0x04 }

How do I fix this error under Linux?
[click to continue…]

How To Check and Use Serial Ports Under Linux

How do I check and configure serial ports under Linux for various purposes such as modem, connecting null modems or connect a dumb terminal?
[click to continue…]

Linux kernel: Uhhuh. NMI received for unknown reason 30

Q. I’ve upgrade my CentOS / RHEL (Red Hat Enterprise Linux) 4.7 on HP ProLiant DL580 G5 and it is showing unknown NMI errors in the logs:

Uhhuh. NMI received for unknown reason 30.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?

Uhhuh. NMI received for unknown reason 20.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?

How do I fix this error?
A. This is caused when the system is hanging under load. Add any one of the following to you /boot/grub.conf file:

  1. Disable the NMI watchdog by adding “nmi_watchdog=0
  2. Disable the high precision event timer (HPET) by adding “nohpet

Open grub.conf, type:
vi grub.conf
Make modification to kernel line as follows:

title Red Hat Enterprise Linux AS (2.6.9-78.0.8.EL)
        root (hd0,0)
        kernel /vmlinuz-2.6.9-78.0.8.EL ro nohpet root=/dev/VolGroup00/LogVol00 nohpet
        initrd /initrd-2.6.9-78.0.8.EL.img

Save and close the file. Reboot the server:
# reboot

Boot Ubuntu Linux into Rescue mode to fix system

Q. How do I boot my Ubuntu Linux server into Rescue mode to fix system?

A. You can boot Ubuntu Linux into rescue mode when things go wrong, there are several ways to work on fixing them. However, you must understand your system and what to fix in case of emergency.

Use this mode only if your system is unbootable. It is also recommended that you make backup of important data.

=> Start Computer / reboot computer

=> Put your Ubuntu install CD

=> Make sure BIOS is set to boot from CD

=> Now booting will start from Ubuntu install CD

=> You will see various option screen – select Recover a broken system

You will system is booting in to rescue mode; system will ask about Network and other information. This is required to setup rescue environment.

Now you will prompted to select root partition or device.

Next it will try to mount root device and it will notify the same.

Now you will see common rescue mode option such as Reinstall GRUB or open / execute a shell etc.

Now you are in rescue mode and you need to use your own knowledge to rescue the system. When things go wrong, there are several ways to work on fixing them.

Few things to remember….

The rescue-mode CD mounts your root filesystem at /target directory. Open or execute a shell and change directory to /target
# ls /target
# cd /target
# mount

If you need to run fsck command use fdisk -l command to find out partition name. Usually they are located at /dev/discs/discX/partY. For example repair 2nd partition (not mounted as /target) you may type command:
# ls -l /dev/discs/disc0
# fsck.ext3 /dev/discs/disc0/part1

To exit type command :
# sync ;sync
# exit
# reboot

As I said earlier in rescue mode, there is no single command that I can recommend to fix problem. You need to use your own knowledge to rescue the system and don’t forget to read command documentation before using any command.

Linux reset forgotten root password

Q. I forgot my root password, how can I get into my system?

A. You can reset forgotten root password under Linux by booting system into single user mode or emergency mode (also known as rescue mode).

My boot loader is GRUB (see LILO boot loader below)

)Following is the procedure to reset root password if you are using GRUB as a boot loader:

  1. Select the kernel
  2. Press the e key to edit the entry
  3. Select second line (the line starting with the word kernel)
  4. Press the e key to edit kernel entry so that you can append single user mode
  5. Append the letter S (or word Single) to the end of the (kernel) line
  6. Press ENTER key
  7. Now press the b key to boot the Linux kernel into single user mode
  8. At prompt type passwd command to reset password:

You need to mount at least / and other partitions:
# mount -t proc proc /proc
# mount -o remount,rw /

Change the root password, enter:
# passwd
Finally reboot system:
# sync
# reboot


My boot loader is LILO

At LILO boot loader type linux single and press [ENTER] key:
Boot: linux single
When you get the # prompt you will need to type passwd root to reset password:
# passwd
Reboot system:
# sync
# reboot

See also: