Need help to boot a server and mount all partitions
Hello, I am having an issue with a SUN FIRE V440. First of all, lots of mirrors and submirrors needed maintenance, so I applied #metasync to fix all of them, but I still couldn't mount all the partitions
of the server .
I tried to mount manually all the partitions that appear in the /etc/vfstab but 2 very important partition still couldn't mount. So I applied #mountall and the error bellow appeared
I tried to applied fsck on those partitioon but still couldn't . Then I reboot the server, other error appeared (error bellow) and the all the disc errors that i fixed before (with metasync) came back. Does anyone knows what can I do???
---------- Post updated at 05:13 AM ---------- Previous update was at 05:09 AM ----------
this is a Critical Production Servers, so I will appreciate any tips or help to fix this issue
I have an issue with booting NTFS partitions with Grub.
I have two HHD
1st HDD with Red Hat 9.0 and Grub as bootloader
2nd HDD with 8 Win partitions all ntfs.
I have added the following line in my grub.conf:
title Windows2000/Domino 6
root (hd1,0)
makeactive
chainloader +1
When I... (4 Replies)
Hi,
Can someone help me on this?
I'm not able to enable a well working mounting process for NFS filesystems on boot time.
On the server side (AIX 5.2) everything seems to be OK and correctly exported, seeing other clients (AIX 5.2) are able to mount normally on boot time.
On a client in... (5 Replies)
hi, I' ve found an error while starting up solaris 10, so I booted in safe mode from grub and modified the menu.lst with vi, to obtain a verbose output of the error. It says
failed to readsuperblock
diskread reading beyound end of ramdisk
start = 0x800 size=0x800
...
...
panic: cannot... (9 Replies)
Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
I am trying to dd an entire hard drive and copy it to another harddrive and experiencing problems for which I can't seem to find an answer.
Questions:
What do the error messages below indicate? Is there a solution?
Are the error messages due to the difference in drive sizes?
Is it possible... (4 Replies)
Hello,
As a purely learning purpose I am trying to make another set of partitions along my existing Ubuntu11.10 box. The reason to do this partition is to try a new Linux system by myself following "Linux From Scratch" (LFS). Because the instruction of LFS seems for very advanced user (I am... (3 Replies)
After applying the latest patchset on a Sun v240 (SPARC, 64b Solaris 10), I got the below error:
Boot device: disk File and args:
|
Evaluating:
Out of memory
Warning: Fcode sequence resulted in a net stack depth change of 1
Evaluating:
Evaluating:
The file just loaded does not... (2 Replies)
I'm preparing to recover a Oracle Fire X4170 server in a disaster recovery test at a different location than in prod. I have some questions about fdisk partitions. I'm using Solaris 10 update 10.
On my prod server, the boot disk has 2 partitions, diagnostic and solaris. Is the diagnostic... (1 Reply)
Hello, fellow Unixers and Macers,
I'll run several OS X versions each on its own dedicated partition. Partitions won't be seeing each other (by editing fstab). Question: will I be able to copy files between those partitions? Partition #1: Mavericks. Partition #2: HighSierra (2 Replies)
Discussion started by: scrutinizerix
2 Replies
LEARN ABOUT OSF1
fsck_udfs
fsck_udfs(1M) System Administration Commands fsck_udfs(1M)NAME
fsck_udfs - file system consistency check and interactive repair
SYNOPSIS
fsck -F udfs [generic_options] [special ...]
fsck -F udfs [generic_options] [-o specific_options] [special ...]
DESCRIPTION
fsck audits and interactively repairs inconsistent conditions on file systems. A file system to be checked can be specified by giving the
name of the block or character special device or by giving the name of its mount point if a matching entry exists in /etc/vfstab.
special represents the character special device, for example, /dev/rdsk/c0t2d0s0, on which the file system resides. The character special
device, not the block special device should be used. fsck does not work on a mounted block device.
If no special device is specified, all udfs file systems specified in the vfstab file with a fsckdev entry are checked. If the -p (preen)
option is specified, udfs file systems with an fsckpass number greater than 1 are checked in parallel. See fsck(1M).
In the case of correcting serious inconsistencies, by default, fsck asks for confirmation before making a repair and waits for the operator
to respond with either yes or no. If the operator does not have write permission on the file system, fsck defaults to the -n (no correc-
tions) option. See fsck(1M).
Repairing some file system inconsistencies can result in loss of data. The amount and severity of data loss can be determined from the
diagnostic output.
fsck automatically corrects innocuous inconsistencies. It displays a message for each corrected inconsistency that identifies the nature of
the correction which took place on the file system. After successfully correcting a file system, fsck prints the number of files on that
file system and the number of used and free blocks.
Inconsistencies checked are as follows:
o Blocks claimed by more than one file or the free list
o Blocks claimed by a file or the free list outside the range of the file system
o Incorrect link counts in file entries
o Incorrect directory sizes
o Bad file entry format
o Blocks not accounted for anywhere
o Directory checks, file pointing to unallocated file entry and absence of a parent directory entry
o Descriptor checks, more blocks for files than there are in the file system
o Bad free block list format
o Total free block count incorrect
OPTIONS
The following options are supported:
generic_options
The following generic_options are supported:
-m
Check but do not repair. This option checks to be sure that the file system is suitable for mounting, and returns the appropriate
exit status. If the file system is ready for mounting, fsck displays a message such as:
udfs fsck: sanity check: /dev/rdsk/c0t2d0s0 okay
-n | -N
Assume a no response to all questions asked by fsck; do not open the file system for writing.
-V
Echo the expanded command line, but do not execute the command. This option can be used to verify and to validate the command line.
-y | -Y
Assume a yes response to all questions asked by fsck.
-o specific_options
Specify udfs file system specific options in a comma-separated list with no intervening spaces. The following specific_options are
available:
f
Force checking of file systems regardless of the state of their logical volume integrity state.
p
Check and fix the file system non-interactively (preen). Exit immediately if there is a problem that requires intervention. This
option is required to enable parallel file system checking.
w
Check writable file systems only.
FILES
/etc/vtstab List of default parameters for each file system.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWudf |
+-----------------------------+-----------------------------+
SEE ALSO fsck(1M), fsdb_udfs(1M), fstyp(1M), mkfs(1M), mkfs_udfs(1M), mountall(1M), reboot(1M), vfstab(4), attributes(5)WARNINGS
The operating system buffers file system data. Running fsck on a mounted file system can cause the operating system's buffers to become out
of date with respect to the disk. For this reason, use fsck only when the file system is unmounted. If this is not possible, take care that
the system is quiescent and that it is rebooted immediately after running fsck. A panic will probably occur if running fsck on a file sys-
tem that modifies the file system while it is mounted.
If an unmount of the file system is not done before the system is shut down, the file system might become corrupted. In this case, a file
system check needs to be completed before the next mount operation.
DIAGNOSTICS
not writable
You cannot write to the device.
Currently Mounted on
The device is already mounted and cannot run fsck.
FILE SYSTEM WAS MODIFIED
File system has been modified to bring it to a consistent state.
Can't read allocation extent
Cannot read the block containing allocation extent.
Bad tag on alloc extent
Invalid tag detected when expecting an allocation extent.
Volume sequence tag error
Invalid tag detected in the volume sequence.
Space bitmap tag error
Invalid tag detected in the space bitmap.
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Use fsck in interactive mode.
SunOS 5.10 5 September 2000 fsck_udfs(1M)