07-26-2012
Hi Getrue,
If the storage was down I'd start by trying to find out what was done, either as part of the planned work or if it was an unplanned outage then what happened.
If it was a failure and a disk was replaced then you may have to recover from your last VMware copy or snapshot.
But I'd start by asking the storage guys what has happened.
Regards
Dave
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi..
i am using sun solaris...and this is the filesystem information...
you can see th slice(swap) c0t0d0s1 is giving some absord information......and during rebooting it is asking to run fsck mnually..when i run fsck manually it is giving error incorrect starting and end header...smthing like... (1 Reply)
Discussion started by: Prafulla
1 Replies
2. UNIX for Advanced & Expert Users
While rebooting one of the UNIX systems here at work, the boot-up process halted and a message appeared telling me that I had to run the fsck command. The command to the best of my knowledge went something like :
fsck -F ufs /dev/rdsk/c0t0d0s0
Can someone give me a full list of this command... (4 Replies)
Discussion started by: Kanu77
4 Replies
3. Solaris
Hi,
Can anybody tell me that is it the command "fsck" can be run by the root account only?
Thanks. (2 Replies)
Discussion started by: efang
2 Replies
4. UNIX for Dummies Questions & Answers
so i am pretty dumb when it comes to unix. but i am in the navy and the system i work on is unix based. and we have come across this problem.
COULD NOT FIX FILE SYSTEM WITH fsck -P, RUN fsck INTERACTIVELY! LOGGING IN AS root FOR MANUAL fsk, ENTER ^D WHEN FILE SYSTEM FIXED
(in bcheckrc)#
... (4 Replies)
Discussion started by: afouts
4 Replies
5. Solaris
Hi,
I need to fsck the root file system on my Solaris 9 server. It is a UFS file system but it is under Veritas control. I want to know which fsck I need to use to check the file system. The default Solaris fsck (/usr/sbin/fsck) or the Veritas (/lib/fs/vxfs/sparcv9/fsck) fsck? I take it I... (3 Replies)
Discussion started by: gwhelan
3 Replies
6. HP-UX
Hi,
please consider, I'm pretty new to HP-UX, thanks.
Our server (rp7420 with HP-UX 11.31) has crashed due to disk write error (not boot partition). So I replaced damaged device with the new one of the same size and performed dd copy 1:1 to restore data - vxfs partition "/dev/vg01/lvol1"... (4 Replies)
Discussion started by: Morhoo
4 Replies
7. AIX
One of our tasks in the office is to do database backups. We were taught (us all operators working here) that it is done via a bunch of specialized scripts. Those scripts are at least 10 years old (system is an AIX 4.1).
One of those script does an fsck against the databases. Everytimes we run... (2 Replies)
Discussion started by: Browser_ice
2 Replies
8. Solaris
I installed solaris 9u8 and flar image and put on my jumpstart server which is running 10u3. Then I do jumpstart with new image with same hardware. Jumpstart acts like it installs, configures, and looks generally good. However, During the boot process, it reports the following errors.
The / file... (4 Replies)
Discussion started by: rushingfish
4 Replies
9. Solaris
Hi,
I am getting this error while server booting up, not sure how to fix this. Unable to mount these file systems
/dev/md/rdsk/d51: No such device or address
Can't open /dev/md/rdsk/d51: No such device or address
/dev/md/rdsk/d51: CAN'T CHECK FILE SYSTEM.
/dev/md/rdsk/d51: UNEXPECTED... (1 Reply)
Discussion started by: bobby320
1 Replies
10. Solaris
NOTICE: /: unexpected free inode 45262, run fsck(1M)
fsck: cannot open vfstab
Looks like /etc/vfstab (and a few other files has gone)
Any ideas?
Boot from cd, mount disk and recreate vfstab so that I can run fsck? (1 Reply)
Discussion started by: psychocandy
1 Replies
LEARN ABOUT ULTRIX
systemd-fsck
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)
NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but
only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root
file system in the initramfs.
These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
rotating disk.
systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
mounts, unclean unmount, etc.
If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
fsck.repair=
One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.
SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)
systemd 237 SYSTEMD-FSCK@.SERVICE(8)