Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Boot Sequence changed After Image Restore Post 302336852 by shamik on Thursday 23rd of July 2009 04:54:47 AM
Old 07-23-2009
Here it is-


#root# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/sda1 / ext3 defaults 0 0
/dev/sda6 /root2 ext3 rw,nosuid,noexec,auto,nouser,async,noatime,nodev 00
/dev/sda5 /var ext3 rw,nosuid,noexec,auto,nouser,async,noatime,nodev 00
/dev/sda7 swap swap defaults 1 2
/dev/sda2 /opt/ ext3 defaults 0 0
/dev/sda3 /opt/ ext3 defaults 0 0
/dev/sda8 /DVD_OPS ext3 defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 2
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/scd0 /media/cdrecorder auto pamconsole,exec,noauto,managed 0 0

---------- Post updated at 03:54 AM ---------- Previous update was at 01:33 AM ----------

Here's some updates-

The message that does not get displayed are the init messages. Those that are getting displayed are the kernel messages.

I checked the following files-
/etc/inittab
/etc/rc.d/rc.sysinit-- in which all the messages are stored
/etc/rc3.d/* -- for default run-level

all are same as those on the machine where the init messages appear on the console.

So now the problem is - why are init messages not shown on the console during the system start-up/reboot
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Boot Sequence

Hi everybody, I have to create a script and put it in the boot up sequence . Can you give me the path where i can put it? Sorry it's my first script. DElphine (3 Replies)
Discussion started by: delphine
3 Replies

2. Solaris

how to change the boot sequence?

Hi all, I have solaris and xp installed... Usually solaris occupies the first boot slot. So i wanted to know if it is possible to change the boot sequence to xp first and then solaris? (5 Replies)
Discussion started by: wrapster
5 Replies

3. AIX

AIX 5.2 Maksysb Image backup/restore

Hello, I am new to AIX, as I was primarily working on HP-UX servers. We have some production servers and a couple of lab servers. We have upgraded over 40 servers from 5.2 to 5.3 running a particular application(1) using the golden 5.3 upgraded servers copy of makesysb. We have only two... (3 Replies)
Discussion started by: dayinthelife
3 Replies

4. Shell Programming and Scripting

Reverse numbering of image sequence

Hi, I have several folders full of image sequences from an animation. The image frames are named Frame0001.png to Frame0900.png, somewhere along the way the images have been named in reverse order. Is there a script that read the contents of a folder and renumber the files Frame0001.png -... (1 Reply)
Discussion started by: BlightyDevil
1 Replies

5. AIX

has bosboot command changed characteristics of boot image?

hi all i just found one of my p650 server showing a warning message when i tried to run bosboot command after upgrading TL to AIX 530803. i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still showed... (0 Replies)
Discussion started by: rs6000er
0 Replies

6. Red Hat

Boot Messages changed after mondorestore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image (by mondorestore) on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- "... (13 Replies)
Discussion started by: shamik
13 Replies

7. Solaris

flar restore with svm mirrors failing to create boot image

In a Solaris9 environment I'm trying to restore flash archive (flar) with SVM mirrored devices to same server via jumpstart server and it is failing to create boot file and drops down to a command prompt in single user mode, metastat -i and metastat -p output looks good when compared to the ones... (0 Replies)
Discussion started by: mbak
0 Replies

8. AIX

AIX Tivoli Image Restore

Dear Team: I am new to this Forum and I need your help for my AIX restoration problem its very urgent my problem as follow failure I have a Tivoli Storage Manger was installed on that server. I created backup image using Tivoli and it created a set of files each file is around 2GB so... (1 Reply)
Discussion started by: Firas_Abed
1 Replies

9. AIX

Restore mksysb image on cloned LPAR

Hi Folks, How to restore mksysb image on LPAR which is already having cloned AIX OS installed on hdisk0 (nothing configured, only full partition image is sitting on hdisk0) Let me know. Thank a lot. (1 Reply)
Discussion started by: snchaudhari2
1 Replies

10. Solaris

Solaris 10 Restore from flar image

Hi! I want to migrate Sun Fire v240 server (sun4u) with Solaris 10 update 6 to LDOM virtual host (sun4v). I was mount NFS directory from another server in /mnt and did this steps on v240 1) I add to the /var/sadm/system/admin/.platform PLATFORM_GROUP=sun4v # cat... (1 Reply)
Discussion started by: pbubentsov
1 Replies
MKIMAGE(1)						      General Commands Manual							MKIMAGE(1)

NAME
mkimage - Generate image for U-Boot SYNOPSIS
mkimage [options] DESCRIPTION
The mkimage command is used to create images for use with the U-Boot boot loader. These images can contain the linux kernel, device tree blob, root file system image, firmware images etc., either separate or combined. mkimage supports two different formats: The old legacy image format concatenates the individual parts (for example, kernel image, device tree blob and ramdisk image) and adds a 64 bytes header containing information about target architecture, operating system, image type, compression method, entry points, time stamp, checksums, etc. The new FIT (Flattened Image Tree) format allows for more flexibility in handling images of various types and also enhances integrity pro- tection of images with stronger checksums. OPTIONS
List image information: -l [uimage file name] mkimage lists the information contained in the header of an existing U-Boot image. Create old legacy image: -A [architecture] Set architecture. Pass -h as the architecture to see the list of supported architectures. -O [os] Set operating system. bootm command of u-boot changes boot method by os type. Pass -h as the OS to see the list of supported OS. -T [image type] Set image type. Pass -h as the image to see the list of supported image type. -C [compression type] Set compression type. Pass -h as the compression to see the list of supported compression type. -a [load addess] Set load address with a hex number. -e [entry point] Set entry point with a hex number. -n [image name] Set image name to 'image name'. -d [image data file] Use image data from 'image data file'. -x Set XIP (execute in place) flag. Create FIT image: -D [dtc options] Provide special options to the device tree compiler that is used to create the image. -f [image tree source file] Image tree source file that describes the structure and contents of the FIT image. EXAMPLES
List image information: mkimage -l uImage Create legacy image with compressed PowerPC Linux kernel: mkimage -A powerpc -O linux -T kernel -C gzip -a 0 -e 0 -n Linux -d vmlinux.gz uImage Create FIT image with compressed PowerPC Linux kernel: mkimage -f kernel.its kernel.itb HOMEPAGE
http://www.denx.de/wiki/U-Boot/WebHome AUTHOR
This manual page was written by Nobuhiro Iwamatsu <iwamatsu@nigauri.org> and Wolfgang Denk <wd@denx.de> 2010-05-16 MKIMAGE(1)
All times are GMT -4. The time now is 01:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy