10-30-2003
WARNING - /usr/sbin/fsck not found - Please help
WARNING - /usr/sbin/fsck not found. Most likely the mount of
/usr failed or the /usr filesystem is badly
damaged. The system is being halted.
Either re-install the system of boot with -b
option in an attempt to recover
Anyone help me on restoring this without having to reinstall. it is a test machine I have so I can do anything on it at anytime (that's probably why I am in this situation in the first place! ;-)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How can i restart the console getty without rebooting the system on HPUX 11.0
Normally it will be stated by ps -ef | grep getty
console 0:00 /usr/sbin/getty console console
many thanx (4 Replies)
Discussion started by: iceman_denmark
4 Replies
2. UNIX for Advanced & Expert Users
I have a solaris 5.8 system, it wont boot because /usr is corrupt, which means i cannot bring up fsck to run a disk check. Any ideas? (3 Replies)
Discussion started by: frankkahle
3 Replies
3. Solaris
root@test09 # ls -al /sbin/init
-r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init
root@test09 # ls -al /usr/sbin/init
-r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies
4. HP-UX
hi friends,
what is the meaning of this error ?
syslog: /usr/sbin/envd: (2 Replies)
Discussion started by: cromohawk
2 Replies
5. Solaris
I noticed in my cron log file for my solaris 8 servers the rc=1. I imagine that is return code and something did not process. Does anyone know what that is, is there fix or the implications of leaving it?
Thank you
> CMD: && /usr/sbin/rtc -c > /dev/null 2>&1
> root 22049 c Fri Dec 19... (1 Reply)
Discussion started by: csgonan
1 Replies
6. UNIX for Advanced & Expert Users
I thought I would document this error since its not documented very well. The package or file may be different but the idea is the same.
$ sudo yum updateLoaded plugins: langpacks, presto, refresh-packagekit, versionlock
Setting up Update Process
Resolving Dependencies
--> Running... (0 Replies)
Discussion started by: cokedude
0 Replies
7. Shell Programming and Scripting
Hello.
I am currently on HPUX and migrating to Linux RHEL 6.4
This program on hpux:
/usr/sbin/userdbset
is puzzling me on linux.
Does anyone know the equivilent program forked or used on linux.
This program is mentioned in our user reset script.
here is a strings of the... (2 Replies)
Discussion started by: olyanderson
2 Replies
8. AIX
Dear Expret,
Help me about my issue,
I trying add new disk to volume Group but error:
step add new disk to volume group.
1. ~Change a Volume Group
Add a Physical Volume to a Volume Group
Remove a Physical Volume from a Volume Group
Reorganize a Volume Group... (6 Replies)
Discussion started by: williamen
6 Replies
9. HP-UX
Hi,
I'm not an HP-UX SysAdmin and work with Linux Systems a bit more but I have a question about the logging level for the snmpdm. We don't specify or modify anything so we're probably taking the default? What is the default?
I see in the man page these options are available:
Turn off... (0 Replies)
Discussion started by: hlutz
0 Replies
10. Red Hat
Dear Concern,
We have observed that following command stuck/does not work in some RedHat nodes. Please advise us to troubleshoot the issue.
/usr/sbin/hpacucli ctrl all show
Note: HP Array Configuration Utility CLI for Linux 64-bit
With Best Regards,
Md. Abdullah-Al Kauser (3 Replies)
Discussion started by: makauser
3 Replies
LEARN ABOUT DEBIAN
bup-fsck
bup-fsck(1) General Commands Manual bup-fsck(1)
NAME
bup-fsck - verify or repair a bup repository
SYNOPSIS
bup fsck [-r] [-g] [-v] [--quick] [-j jobs] [--par2-ok] [--disable-par2] [filenames...]
DESCRIPTION
bup fsck is a tool for validating bup repositories in the same way that git fsck validates git repositories.
It can also generate and/or use "recovery blocks" using the par2(1) tool (if you have it installed). This allows you to recover from dam-
aged blocks covering up to 5% of your .pack files.
In a normal backup system, damaged blocks are less important, because there tends to be enough data duplicated between backup sets that a
single damaged backup set is non-critical. In a deduplicating backup system like bup, however, no block is ever stored more than once,
even if it is used in every single backup. If that block were to be unrecoverable, all your backup sets would be damaged at once. Thus,
it's important to be able to verify the integrity of your backups and recover from disk errors if they occur.
WARNING: bup fsck's recovery features are not available unless you have the free par2(1) package installed on your bup server.
WARNING: bup fsck obviously cannot recover from a complete disk failure. If your backups are important, you need to carefully consider
redundancy (such as using RAID for multi-disk redundancy, or making off-site backups for site redundancy).
OPTIONS
-r, --repair
attempt to repair any damaged packs using existing recovery blocks. (Requires par2(1).)
-g, --generate
generate recovery blocks for any packs that don't already have them. (Requires par2(1).)
-v, --verbose
increase verbosity (can be used more than once).
--quick
don't run a full git verify-pack on each pack file; instead just check the final checksum. This can cause a significant speedup
with no obvious decrease in reliability. However, you may want to avoid this option if you're paranoid. Has no effect on packs
that already have recovery information.
-j, --jobs=numjobs
maximum number of pack verifications to run at a time. The optimal value for this option depends how fast your CPU can verify packs
vs. your disk throughput. If you run too many jobs at once, your disk will get saturated by seeking back and forth between files
and performance will actually decrease, even if numjobs is less than the number of CPU cores on your system. You can experiment
with this option to find the optimal value.
--par2-ok
immediately return 0 if par2(1) is installed and working, or 1 otherwise. Do not actually check anything.
--disable-par2
pretend that par2(1) is not installed, and ignore all recovery blocks.
EXAMPLE
# generate recovery blocks for all packs that don't
# have them
bup fsck -g
# generate recovery blocks for a particular pack
bup fsck -g ~/.bup/objects/pack/153a1420cb1c8*.pack
# check all packs for correctness (can be very slow!)
bup fsck
# check all packs for correctness and recover any
# damaged ones
bup fsck -r
# check a particular pack for correctness and recover
# it if damaged
bup fsck -r ~/.bup/objects/pack/153a1420cb1c8*.pack
# check if recovery blocks are available on this system
if bup fsck --par2-ok; then
echo "par2 is ok"
fi
SEE ALSO
bup-damage(1), fsck(1), git-fsck(1)
BUP
Part of the bup(1) suite.
AUTHORS
Avery Pennarun <apenwarr@gmail.com>.
Bup unknown- bup-fsck(1)