09-13-2005
Yes!! my OS starts up normally and the fs gets mounted as usual.
It is only that when I run fsck I get this error. Even when I have
applied Sun Reccomended patch clusters on the machine this error
is showing up on not 1 but more than 1 machine.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Once in a while, I would think it advisable to run fsck -y to check the disk.
Should I sign in as su or sudo?
What is the difference and which is preferred?
Thank you in Advance! (4 Replies)
Discussion started by: rpatrick
4 Replies
2. UNIX for Dummies Questions & Answers
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
Discussion started by: duke0001
3 Replies
3. UNIX for Dummies Questions & Answers
hy guys
I got a ques
I cant acess root, i tried to fsck it, but gets errors to read file systems. What steps do you take to recover the host before you see if there is any data corruption on the root drive?
Regards
Charneet (1 Reply)
Discussion started by: charneet
1 Replies
4. Solaris
Hello
I am getting this in dmesg:
/mount1: unexpected free inode 1262865, run fsck(1M) -o f
What are the options I should use with fsck?
thanks (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
5. UNIX for Dummies Questions & Answers
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
Discussion started by: farhan_t49
1 Replies
6. UNIX for Dummies Questions & Answers
Hello
I own a SPARC Ultra 10 workstation (standalone) and when issuing the fsck command I get the following output on fs C0t0d0s7:
Phase 1 (checks blocks and sizes):
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1): ATA Transport failed:reason, `incomplete'>
Uncorrectable data... (2 Replies)
Discussion started by: tjwops
2 Replies
7. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
8. UNIX for Advanced & Expert Users
unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)
--------------------------------------------------------------------------------
What can I fix this issue? I have ran below commands but everything is same.
WARNING: Last shutdown is later than time... (2 Replies)
Discussion started by: VijayPuttu
2 Replies
9. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
10. Solaris
Dear all,
solaris version
--------------------
Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 11 August 2010
-bash-3.2$ uname -a
SunOS nblabsvr 5.10 Generic_144488-08 sun4u sparc SUNW,SPARC-Enterprise
... (5 Replies)
Discussion started by: ossupport55
5 Replies
LEARN ABOUT OPENDARWIN
systemd-machine-id-setup
SYSTEMD-MACHINE-ID-SETUP(1) systemd-machine-id-setup SYSTEMD-MACHINE-ID-SETUP(1)
NAME
systemd-machine-id-setup - Initialize the machine ID in /etc/machine-id
SYNOPSIS
systemd-machine-id-setup
DESCRIPTION
systemd-machine-id-setup may be used by system installer tools to initialize the machine ID stored in /etc/machine-id at install time, with
a provisioned or randomly generated ID. See machine-id(5) for more information about this file.
If the tool is invoked without the --commit switch, /etc/machine-id is initialized with a valid, new machined ID if it is missing or empty.
The new machine ID will be acquired in the following fashion:
1. If a valid D-Bus machine ID is already configured for the system, the D-Bus machine ID is copied and used to initialize the machine ID
in /etc/machine-id.
2. If run inside a KVM virtual machine and a UUID is configured (via the -uuid option), this UUID is used to initialize the machine ID.
The caller must ensure that the UUID passed is sufficiently unique and is different for every booted instance of the VM.
3. Similarly, if run inside a Linux container environment and a UUID is configured for the container, this is used to initialize the
machine ID. For details, see the documentation of the Container Interface[1].
4. Otherwise, a new ID is randomly generated.
The --commit switch may be used to commit a transient machined ID to disk, making it persistent. For details, see below.
Use systemd-firstboot(1) to initialize the machine ID on mounted (but not booted) system images.
OPTIONS
The following options are understood:
--root=root
Takes a directory path as argument. All paths operated will be prefixed with the given alternate root path, including the path for
/etc/machine-id itself.
--commit
Commit a transient machine ID to disk. This command may be used to convert a transient machine ID into a persistent one. A transient
machine ID file is one that was bind mounted from a memory file system (usually "tmpfs") to /etc/machine-id during the early phase of
the boot process. This may happen because /etc is initially read-only and was missing a valid machine ID file at that point.
This command will execute no operation if /etc/machine-id is not mounted from a memory file system, or if /etc is read-only. The
command will write the current transient machine ID to disk and unmount the /etc/machine-id mount point in a race-free manner to ensure
that this file is always valid and accessible for other processes.
This command is primarily used by the systemd-machine-id-commit.service(8) early boot service.
--print
Print the machine ID generated or committed after the operation is complete.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), machine-id(5), systemd-machine-id-commit.service(8), dbus-uuidgen(1), systemd-firstboot(1)
NOTES
1. Container Interface
https://www.freedesktop.org/wiki/Software/systemd/ContainerInterface
systemd 237 SYSTEMD-MACHINE-ID-SETUP(1)