03-27-2002
fsck -y it works!
Well, it works well!
For those who use a Macintosh(and I am one) this is "part of" Disk First Aid being built in.
The steps follow:
sudo ShutDown Now Hit return
Enter password
You are "sudo user"
You are in single user mode:
type fsck -y
The disk is checked. If you receive a "message" that the Macintosh appears to be OK type reboot.
This saves a CD Rom Start which is slow as molasses.
If errors are found they will be repaired -y for yes repair.
Wonderful to learn this.
10 More Discussions You Might Find Interesting
1. Solaris
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
Discussion started by: run_time_error
5 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 OPENSOLARIS
gksu
GKSU(1) General Commands Manual GKSU(1)
NAME
gksu - a Gtk+ su frontend
SYNOPSIS
gksu [ options ] <command>
gksudo [ options ] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is
included below.
Common Options:
--user <user>, -u <user>
Calls <command> as the specified user
--message <message>, -m <message>
Replaces the standard message shown to ask for password for the argument passed to the option
--sudo-mode, -S
Use sudo instead of su as backend authentication system. Notice that the X authorization magic will not work when using sudo for
target users other than root.
--title <title>, -t <title>
Replaces the default title with the argument
--icon <icon>, -i <icon>
Replaces the default window icon with the argument
--print-pass, -p
Asks gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--disable-grab, -g
Disables the "locking" of the keyboard, mouse, and focus done by the program when asking for password
--ssh-fwd, -s
Strip the host part of the $DISPLAY variable, so that GKSu will work on SSH X11 Forwarding.
--login, -l
Makes this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display! This is ignored if running with sudo as backend for authentication.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
FILES
/etc/gksu.conf
Configuration file to setup system-wide defaults for gksu/gksudo. It provides an option to force the display grabing, also.
RETURN VALUE
On success, gksu will return 0. If an authentication error ocurred, it will exit with error code 3. If the user canceled the dialog or
closed the window, it will return error code 2. On other error conditions, gksu will return 1.
NOTE
Note that <command> and all its arguments should be passed as one single argument to gksu just like one would to when using su.
SEE ALSO
su(1), gksuexec(1).
AUTHOR
This manual page was written by Gustavo Noronha Silva <kov@debian.org> for the Debian GNU/Linux system (but may be used by others).
2003 GKSU(1)