05-17-2006
RedHat hang after VFS Mounted Root
I can install RedHat ASE3 on a virtual machine (Ram set to 600Mb) without any problems. However if I start a Virtual machine with greater than 600Mb then either try and boot an existing image or install a new one it will stop at the line:
VFS: Mounter Root (ext2 fielsystem)
Ocastionally I will see an error "i8253 count to high".
If I then wind down the RAM to below 600Mb I can boot existing images or install new ones.
Anyone have an Ideas how I can start the machine with more that 600Mb?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
In my Solaris 10 based server, I have noticed the following mounts when a use DF -K
/dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% /
/ 5062414 3213876 1797914 65% /net/se420
I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect.... (1 Reply)
Discussion started by: jimthompson
1 Replies
2. Linux
can somebody help me out in editing the /etc/fstab. I am on RHEL5 (Tikanga).
**The problem is that i have given a wrong LABEL in /etc/fstab for root volume and so after reboot, it is unable to resolve the wrong LABEL;
so, i have to edit the /etc/fstab :-(
-ilan (3 Replies)
Discussion started by: ilan
3 Replies
3. Filesystems, Disks and Memory
Hi,
Im running RHEL. How do I find the time a particular filesystem was mounted?
Please Let me know
Thanks (1 Reply)
Discussion started by: neuralninja
1 Replies
4. UNIX for Advanced & Expert Users
Hi,
Im running RHEL. How do I find the time a particular filesystem was mounted?
Please Let me know
Thanks (1 Reply)
Discussion started by: neuralninja
1 Replies
5. Red Hat
hlow all,
i want to know how we do insert big file in VFS and how we do to call that file again
can anyone explain about that
thx before (0 Replies)
Discussion started by: zvtral
0 Replies
6. UNIX for Dummies Questions & Answers
I have logged into single user mode and
whenever i issue
passwd root
nothing happens the cursor simply returns back without asking new password.
what can be issue? (5 Replies)
Discussion started by: pinga123
5 Replies
7. Red Hat
Hi,
We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL.
We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies
8. UNIX for Dummies Questions & Answers
Hi.
I'm starting to use minix and the version I'm using is 3.2.1. I didn't understand why in this version there are MFS/VFS/PFS file systems and in the other versions there is only FS. I'm trying to modify the file system but I don't know where should I modify. Does anyone know why are there... (0 Replies)
Discussion started by: ReonarudoB
0 Replies
9. UNIX for Advanced & Expert Users
Anyone has met the error following:-
1. Only root could login Redhat
2. Trying su another user by root, the error will be
su: warning: cannot change directory to /home/user: permission denied
su: /bin/bash: permission denied
3. I have checked the permission of the folder given and even... (2 Replies)
Discussion started by: jc0616
2 Replies
LEARN ABOUT OPENSOLARIS
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)