Skip to main content

How to get list of all the files which are touched by Red Hat Enterprise Linux during boot process?

Environment

  • Red Hat Enterprise Linux 6

Issue

  • How to get list of all the files which are touched by Red Hat Enterprise Linux during boot process?

Resolution

  • To get such a list, stap script is required.
  • There is an attachment with this Solution which is a zip file containing two programs, bootinit.sh and bootprobe2.1.stp file in stapscripts.zip file. Extract them and use as following. Make sure one has installed kernel-devel and kernel-debuginfo package of the currently booted kernel, otherwise it won't work at all.
  • Follow section 2.1. in the SystemTap Beginners Guide for the systemtap and kernel-debug installation - Run the test at 2.1.3 to verify the install.
1. Create /tmp/stap and /tmp/stap/data
Raw
# mkdir -p /tmp/stap/data
2. Place bootprobe2.1.stp and bootinit.sh into /tmp/stap and make bootinit.sh executable.
Raw
# chmod +x /tmp/stap/boot*
3. Edit bootinit.sh and change exec /sbin/init 3 to exec /sbin/init 5 if 5 is the default runlevel.
4. Create the .ko module from bootprobe2.stp
Raw
# cd /tmp/stap
# stap bootprobe2.1.stp -m bootprobe2 -p4
5. Reboot.
6. Halt grub and press a on the default kernel. At the end of the kernel line enter the following and press enter:
Raw
init=/tmp/stap/bootinit.sh
7. Normal boot will resume. After logging in, kill the stapio process, copy bootprobe2.log out of the tmpfs /tmp/stap/data directory and unmount it.
Raw
# killall stapio
# cp /tmp/stap/data/bootprobe2.log /tmp/stap/
# umount /tmp/stap/data
8. Now check the file /tmp/stap/bootprobe2.log file for the list of all files which are read/wrote/touched during boot.

Attachments

Comments

Post a Comment

Popular posts from this blog

Boot process hangs at dracut: Switching root

Environment Red Hat Enterprise Linux 6 Issue When server is booting the boot process hangs at  dracut: Switching root , and never displays anything else. Raw device-mapper: ioctl: 4.33.1-ioctl (2015-8-18) initialised: xx-xxxx@redhat.com udev: starting version 147 dracut: Starting plymouth daemon dracut: rd_NO_DM: removing DM RAID activation dracut: rd_NO_MD: removing MD RAID activation scsi0 : ata_piix scsi1 : ata_piix ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc120 irq 14 ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc128 irq 15 Refined TSC clocksource calibration: 2599.999 MHz. virtio-pci 0000:00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 virtio-pci 0000:00:05.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, high) -> IRQ 10 virtio-pci 0000:00:07.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 virtio-pci 0000:00:08.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, high) -> IRQ 11 input: ImExPS/2 Gener
Post a Comment
Read more

Interpreting the output of lspci

On Linux, the lspci command lists all PCI devices connected to a host (a computer). Modern computers and PCI devices communicate with each other via PCI Express buses instead of the older Conventional PCI and PCI-X buses since the former buses offer many advantages such as higher throughput rates, smaller physical footprint and native hot plugging functionality. The high performance of the PCI Express bus has also led it to take over the role of other buses such as AGP ; it is also expected that SATA buses too will be replaced by PCI Express buses in the future as solid-state drives become faster and therefore demand higher throughputs from the bus they are attached to (see this article for more on this topic). As a first step, open a terminal and run lspci without any flags (note: lspci may show more information if executed with root privileges): lspci   This is the output I get on my laptop: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Co
Post a Comment
Read more

How to get the SAN environment information and statistics on AIX, HP-UX, Linux, Solaris, and Windows

How to get the SAN environment information and statistics on AIX, HP-UX, Linux, Solaris, and Windows Description NetBackup SAN Client is supported on the Linux , Solaris, Windows, HP-UX and AIX operating systems.  These environments provide the initiator device driver which can login to the SAN client media server and mount an pseudo   target device “ARCHIVE PYTHON” so that the backup or restore can be use the fiber transport (FT).  If there is an issue in the SAN environment, it is necessary to get the information/statistics from the SAN fabric for analysis.  The commands below can be used, on the respective operating system, to gather the necessary information. If the outputs show many or steadily increasing error counts, that indicates one or more issues with  the fabric  infrastructure. The issue(s) can be caused by cabling, SFP, san switch, DWDM, HBA or ISL and those components will need to be analyzed and evaluated.  Linux Get the hardware information fo
Post a Comment
Read more