Sponsored Content
Operating Systems Linux Red Hat Boot Messages changed after mondorestore Post 302337137 by RiSk on Thursday 23rd of July 2009 12:52:28 PM
Old 07-23-2009
Okay,

So reboot the box, append to the end of grub "single" and boot the os; after you are at the bash prompt run fsck /dev/sda1 (or w/e your drives are) and make sure they pass an fsck. If all is good after that mount the drive and double check you dont have any .autofsck files on the fs. Then reboot and see what happens.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot messages - how to eliminate them

Anyone would know how to get rid off a message that comes up during a boot-up on Solaris? It says that the clusters for this software are not installed. I deleted the software because it was crashing some other stuff but it did not get rid off all the stuff. Yes, I am coming from windows and... (2 Replies)
Discussion started by: softarch
2 Replies

2. Solaris

boot messages

(Solaris 8, 4 cpu's) When I look at my boot messages (/var/adm/messages or dmesg) I noticed the following: Sep 23 08:53:00 server1 unix: cpu0: SUNW,UltraSPARC-II (upaid 0 impl 0x11 ver 0xa0 clock 450 MHz) Sep 23 08:53:00 server1 unix: cpu1: SUNW,UltraSPARC-II (upaid 1 impl 0x11 ver... (1 Reply)
Discussion started by: finster
1 Replies

3. Linux

boot messages

Where do all those messages at boot time get stored / logged? like: starting eth0 : OK starting mysql : OK etc... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

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

5. Red Hat

mondorestore

Hi Guys :) I am finding out the way to use mondorestore via command line only, no GUI. I am able to use mondoarchive in the same way but not mondorestore. can anybody help me out.... Thanks in advance! halides:b: (0 Replies)
Discussion started by: halides
0 Replies

6. Filesystems, Disks and Memory

Boot Sequence changed After Image Restore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image 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- " ..... EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies

7. Shell Programming and Scripting

Script to echo "File permissions or ownership changed from required " when accidentally changed.

Hi All, I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :( which have similar names ( /var in root and var of some other directory ).:confused: Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies

8. Red Hat

Grub.conf kernel field boot messages verbosity configuration

I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf From my research, there appear to be three levels: quiet verbose debug I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies

9. Red Hat

Custom-Spin doesnt boot to GUI when /etc/skel is changed

Heyas So i have my custom Fedora with AwesomeWM spin with alots of customizations using the kickstart method for a liveimage. A few weeks (2-3 months) ago, i've done some changes i cannot remember. Those changes made the image from bootable to gui, to not booting to gui any more. Just... (3 Replies)
Discussion started by: sea
3 Replies

10. Red Hat

Customized boot log messages

Hi all Many years ago, I found online this script that was incredibly funny and I had blogged it Unfortunately because of my poor record-keeping, I seem to have lost the shell script Would somebody be kind enough to tell me how to replicate this? Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies
vfstab(4)                                                          File Formats                                                          vfstab(4)

NAME
vfstab - table of file system defaults DESCRIPTION
The file /etc/vfstab describes defaults for each file system. The information is stored in a table with the following column headings: device device mount FS fsck mount mount to mount to fsck point type pass at boot options The fields in the table are space-separated and show the resource name (device to mount), the raw device to fsck (device to fsck), the default mount directory (mount point), the name of the file system type (FS type), the number used by fsck to decide whether to check the file system automatically (fsck pass), whether the file system should be mounted automatically by mountall (mount at boot), and the file system mount options (mount options). (See respective mount file system man page below in SEE ALSO for mount options.) A '-' is used to indicate no entry in a field. This may be used when a field does not apply to the resource being mounted. The getvfsent(3C) family of routines is used to read and write to /etc/vfstab. /etc/vfstab can be used to specify swap areas. An entry so specified, (which can be a file or a device), will automatically be added as a swap area by the /sbin/swapadd script when the system boots. To specify a swap area, the device-to-mount field contains the name of the swap file or device, the FS-type is "swap", mount-at-boot is "no" and all other fields have no entry. EXAMPLES
The following are vfstab entries for various file system types supported in the Solaris operating environment. Example 1: NFS and UFS Mounts The following entry invokes NFS to automatically mount the directory /usr/local of the server example1 on the client's /usr/local directory with read-only permission: example1:/usr/local - /usr/local nfs - yes ro The following example assumes a small departmental mail setup, in which clients mount /var/mail from a server mailsvr. The following entry would be listed in each client's vfstab: mailsvr:/var/mail - /var/mail nfs - yes intr,bg The following is an example for a UFS file system in which logging is enabled: /dev/dsk/c2t10d0s0 /dev/rdsk/c2t10d0s0 /export/local ufs 3 yes logging See mount_nfs(1M) for a description of NFS mount options and mount_ufs(1M) for a description of UFS options. Example 2: pcfs Mounts The following example mounts a pcfs file system on a fixed hard disk on an x86 machine: /dev/dsk/c1t2d0p0:c - /win98 pcfs - yes - The example below mounts a Jaz drive on a SPARC machine. Normally, the volume management daemon (see vold(1M)) handles mounting of remov- able media, obviating a vfstab entry. If you choose to specify a device that supports removable media in vfstab, be sure to set the mount- at-boot field to no, as below. Such an entry presumes you are not running vold. /dev/dsk/c1t2d0s2:c - /jaz pcfs - no - For removable media on a SPARC machine, the convention for the slice portion of the disk identifier is to specify s2, which stands for the entire medium. For pcfs file systems on x86 machines, note that the disk identifier uses a p (p0) and a logical drive (c, in the /win98 example above) for a pcfs logical drive. See mount_pcfs(1M) for syntax for pcfs logical drives and for pcfs-specific mount options. Example 3: CacheFS Mount Below is an example for a CacheFS file system. Because of the length of this entry and the fact that vfstab entries cannot be continued to a second line, the vfstab fields are presented here in a vertical format. In re-creating such an entry in your own vfstab, you would enter values as you would for any vfstab entry, on a single line. device to mount: svr1:/export/abc device to fsck: /usr/abc mount point: /opt/cache FS type: cachefs fsck pass: 7 mount at boot: yes mount options: local-access,bg,nosuid,demandconst,backfstype=nfs,cachedir=/opt/cache See mount_cachefs(1M) for CacheFS-specific mount options. Example 4: Loopback File System Mount The following is an example of mounting a loopback (lofs) file system: /export/test - /opt/test lofs - yes - See lofs(7FS) for an overview of the loopback file system. SEE ALSO
fsck(1M), mount(1M), mount_cachefs(1M), mount_hsfs(1M), mount_nfs(1M), mount_tmpfs(1M), mount_ufs(1M), swap(1M), getvfsent(3C) System Administration Guide: Basic Administration SunOS 5.10 21 Jun 2001 vfstab(4)
All times are GMT -4. The time now is 12:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy