Sponsored Content
Full Discussion: Volume problem
Top Forums UNIX for Advanced & Expert Users Volume problem Post 302291250 by rene_metaal on Wednesday 25th of February 2009 05:03:53 AM
Old 02-25-2009
[QUOTE=Saurabh78;302288326]WE are working on Mac and our end user

I think this post will receive better response in an Mac OS/X forum

/ is the default mountpoint Macintosh HD uses.
You can check with fdisk /dev/rdisk0
if you have a valid partiotion table.

Try the harddisk utility tool which comes with your Mac.
It is the Applications/Utility directory.

With this tools you can check and repair.
But first of all try to make a backup copy.
For this you might need to boot your Mac from the OS/X cdrom by pressing the C button.
Hope this helps
Regards,
René
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

2. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies

3. UNIX for Advanced & Expert Users

Problem syncing logical volume in root vg

Hello. I have a test server that I'm messing around with, and just recently received an error on startup that a logical volume in the root volume group couldn't be re-synchronized. Server boots fine, as the root vg is mirrored, but I'd like to get rid of the error. Here are the details: ... (1 Reply)
Discussion started by: matt.d
1 Replies

4. UNIX for Advanced & Expert Users

Ownership problem using a CIFS-mounted volume

Hello, I am trying to use a storage service for backing large amounts (terabytes) of data. The service uses Linux machines and allows mounting of their disks using the CIFS/SMB protocol. I do have the option of using rsync directly over the network without mounting. But in order to... (4 Replies)
Discussion started by: same1290
4 Replies

5. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

6. Solaris

problem in volume resizing in veritas

Hi all i have a veritas volume with the size of 600MB and formatted with vxfs filesystem. I want to grow the filesystem to 700MB. I knew that three ways are there to resize. vxresize, vxvol and vxassit. vxresize works fine. I want to try the same thing with vxvol and vxassist. Can someone tell me... (4 Replies)
Discussion started by: kingston
4 Replies

7. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

8. Solaris

Veritas volume manager installation problem in Intel machine

i have downloaded veritas storage foundation 5.1 sp1 from veritas website. when i tried to install veritas through the installation script.. installation proceeds fine and then when it reaches Installing VRTSsfmh package - it doesnt proceed further it is stuck with this package. when i checked... (2 Replies)
Discussion started by: chidori
2 Replies

9. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
FSCK_HFS(8)						    BSD System Manager's Manual 					       FSCK_HFS(8)

NAME
fsck.hfs -- HFS file system consistency check SYNOPSIS
fsck.hfs -q [-df] special ... fsck.hfs -p [-df] special ... fsck.hfs [-n | -y | -r] [-dfgl] [-m mode] [-c size] special ... DESCRIPTION
The fsck.hfs utility verifies and repairs standard HFS and HFS+ file systems. The first form of fsck.hfs quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck.hfs preens the specified file systems. It is normally started by fsck(8) during systen boot, when a HFS file system is detected. When preening file systems, fsck.hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more serious problems are found, fsck.hfs does not try to fix them, indicates that it was not successful, and exits. The third form of fsck.hfs checks the specified file systems and tries to repair all detected inconsistencies. If no options are specified fsck.hfs will always check and attempt to fix the specified file systems. The options are as follows: -c size Specify the size of the cache used by fsck.hfs internally. Bigger size can result in better performance but can result in deadlock when used with -l option. Size can be specified as a decimal, octal, or hexadecimal number. If the number ends with a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively. -d Display debugging information. This option may provide useful information when fsck.hfs cannot repair a damaged file system. -f When used with the -p option, force fsck.hfs to check `clean' file systems, otherwise it means force fsck.hfs to check and repair journaled HFS+ file systems. -g Causes fsck.hfs to generate its output strings in GUI format. This option is used when another application with a graphical user interface (like Mac OS X Disk Utility) is invoking the fsck.hfs tool. -l Lock down the file system and perform a test-only check. This makes it possible to check a file system that is currently mounted, although no repairs can be made. -m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created. The lost+found directory is only created when a volume is repaired and orphaned files or directories are detected. fsck.hfs places orphaned files and directories into the lost+found directory (located at the root of the volume). The default mode is 01777. -p Preen the specified file systems. -q Causes fsck.hfs to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -y Always attempt to repair any damage that is found. -n Never attempt to repair any damage that is found. -r Rebuild the catalog file on the specified file system. This option currently will only work if there is enough contiguous space on the specified file system for a new catalog file and if there is no damage to the leaf nodes in the existing catalog file. SEE ALSO
fsck(8) BUGS
fsck.hfs is not able to fix some inconsistencies that it detects. HISTORY
The fsck.hfs command appeared in Mac OS X Server 1.0 . Mac OS X November 21, 2002 Mac OS X
All times are GMT -4. The time now is 07:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy