No, no, no. You don't run fsck on slice2 (??????s2) of any disk because that defines the whole disk to Solaris and does NOT hold a filesystem.
You cannot currently mount c1t0d0s0 and c1t0d0s0. Take a look again at the vtoc for that disk (see my earlier post as to how to do that) and see whether either or both are filesystems. Quite often ??????s1 is defined as swap space. If both are indeed filesystems then fsck those slices:
Note that I have included the '-n' switch to check the filesystems without correcting anything first just to see how much damage, if any, there is. Don't use the '-y' switch at the outset because telling it to correct all errors might destroy the filesystem on the ground if damage is extensive. If errors are few simply run again without the '-n' and say 'y' to each question to correct the error(s).
On a production system I would expect there to be entries in /etc/vfstab to mount these filesystems at boot time?
I am getting the below mentioned error while trying to unistall a package from a 2.8 Solaris box. Please help..
pkgrm: ERROR: unable to determine current run-state
Removal of <PDMgr> failed (internal error).
No changes were made to the system. (1 Reply)
Hi,
I'm attempting to build a raid Z NAS using solaris, but I only have 4 sata ports on my MB, so I bought a Rosewill RC-211 PCIe controller (adds 2 sata II ports).
I'm new to solaris, but I understand that to add a new drive, you first run #devfsadm, which puts the files into /dev/dsk. I... (3 Replies)
hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient.
/etc(R)-bash-3.00$ init 6
/etc(R)-bash-3.00$ svc.startd: The system is coming down. Please wait.... (7 Replies)
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
hi friends, i had this problem in a Solaris 10 server
when i inserted my thumbdrive, i can't find the device file containing usb.
what should i do ? (2 Replies)
I have inherited a solaris 10 server. I went to log into it the other day over the console connection, and after sucessfully entering the password, I was booted back to the login prompt with no errors visible.
If I enter an incorect password, the console displays 'incorrect password' and kicks... (8 Replies)
Hi,
All of our servers run Solaris (currently 10, but looking to upgrade to 11). In each of our offices we have a server configured as a Primary Domain Controller via Samba to provide naming services to our Windoze users. I would like to continue with that arrangement, but I would also like... (2 Replies)
HI
I am unable to add printer in solaris (architecture is SUN and OS is Solaris 10) as I try to print the file it gives following error
Failed to contact service for erp-cljCP2025: not-found
Need help
Regards (7 Replies)
Hi,
we have a sun sparc solaris 10 machine and recently there was a power failure and one of the server domain was down. So today morning i have powered up the domain and it returned me to ok prompt then i have booted the machine with disk from devalias, the system was up as normal and no error... (0 Replies)
Hello, I followed these instructions to create a Solaris 11 zone:
http://www.oracle.com/technetwork/articles/servers-storage-admin/o11-092-s11-zones-intro-524494.html
And I am unable to ping anything from the Local Zone except for the IP address of the global zone.
My global zone has an IP... (6 Replies)
Discussion started by: unblockable
6 Replies
LEARN ABOUT OSX
fsck
FSCK(8) BSD System Manager's Manual FSCK(8)NAME
fsck -- filesystem consistency check and interactive repair
SYNOPSIS
fsck -p [-f]
fsck [-l maxparallel] [-q] [-y] [-n] [-d]
DESCRIPTION
The first form of fsck preens a standard set of filesystems or the specified filesystems. It is normally used in the script /etc/rc during
automatic reboot. Here fsck reads the filesystem descriptor table (using getfsent(3)) to determine which filesystems to check. Only parti-
tions that have ``rw,'' ``rq'' or ``ro'' as options, and that have non-zero pass number are checked. Filesystems with pass number 1 (nor-
mally just the root filesystem) are checked one at a time. When pass 1 completes, all remaining filesystems are checked, running one process
per disk drive. The disk drive containing each filesystem is inferred from the shortest prefix of the device name that ends in one or more
digits; the remaining characters are assumed to be the partition designator. In preening mode, filesystems that are marked clean are
skipped. Filesystems are marked clean when they are unmounted, when they have been mounted read-only, or when fsck runs on them success-
fully.
It should be noted that fsck is now essentially a wrapper that invokes other fsck_XXX utilities as needed. Currently, fsck can invoke
fsck_hfs, fsck_msdos, fsck_exfat, and fsck_udf. If this underlying process that fsck invokes encounters serious inconsistencies or the
filesystem type is not one of the above, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected
inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, and the nature of the
correction.
If sent a QUIT signal, fsck will finish the filesystem checks, then exit with an abnormal return status that causes an automatic reboot to
fail. This is useful when you want to finish the filesystem checks during an automatic reboot, but do not want the machine to come up multi-
user after the checks complete.
Without the -p option, fsck audits and interactively repairs inconsistent conditions for filesystems. It should be noted that some of the
corrective actions which are not correctable under the -p option will result in some loss of data. The amount and severity of data lost may
be determined from the diagnostic output. If the operator does not have write permission on the filesystem fsck will default to a -n action.
The following flags are interpreted by fsck and passed along to the underlying tool that it spawns.
-f Force fsck to check `clean' filesystems when preening.
-l Limit the number of parallel checks to the number specified in the following argument. By default, the limit is the number of
disks, running one process per disk. If a smaller limit is given, the disks are checked round-robin, one filesystem at a time.
-p "Preen" mode, described above.
-q Do a quick check to determine if the filesystem was unmounted cleanly.
-y Assume a yes response to all questions asked by fsck; this should be used with great caution as this is a free license to con-
tinue after essentially unlimited trouble has been encountered.
-n Assume a no response to all questions asked by fsck except for 'CONTINUE?', which is assumed to be affirmative; do not open the
filesystem for writing.
If no filesystems are given to fsck then a default list of filesystems is read using getfsent(3).
Because of inconsistencies between the block device and the buffer cache, the raw device should always be used.
SEE ALSO fs(5), fsck_hfs(8), fsck_msdos(8), getfsent(3), reboot(8)4th Berkeley Distribution May 18, 2010 4th Berkeley Distribution