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 CENTOS
volrmmount
volrmmount(1) User Commands volrmmount(1)NAME
volrmmount - call rmmount to mount or unmount media
SYNOPSIS
volrmmount [-i | -e] [name | nickname]
volrmmount [-d]
DESCRIPTION
The volrmmount utility calls rmmount(1M) to, in effect, simulate an insertion (-i) or an ejection (-e). Simulating an insertion often
means that rmmount will mount the media. Conversely, simulating an ejection often means that rmmount will unmount the media. However,
these actions can vary depending on the rmmount configuration and media type (see rmmount.conf(4)).
For example, if you use the default /etc/rmmount.conf and insert a music CD, it will not be mounted. However, you can configure rmmount so
that it calls workman whenever a music CD is inserted.
This command allows you to override Volume Management's usual handling of media (see EXAMPLES below).
OPTIONS
The following options are supported:
-i Simulates an insertion of the specified media by calling rmmount.
-e Simulates an ejection of the specified media by calling rmmount.
-d Displays the name of the default device for volrmmount to handle. This device is used if no name or nickname is supplied.
OPERANDS
The following operands are supported:
name The name that Volume Management recognizes as the device's name. See volfs(7FS).
nickname A shortened version of the device's name. Following is the list of recognized nicknames:
+-----------------------------+-----------------------------+
| Nickname | Path |
+-----------------------------+-----------------------------+
|fd |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd0 |/dev/rdiskette |
+-----------------------------+-----------------------------+
|fd1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|diskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|diskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|diskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|rdiskette |/dev/rdiskette |
+-----------------------------+-----------------------------+
|rdiskette0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|rdiskette1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|floppy |/dev/rdiskette |
+-----------------------------+-----------------------------+
|floppy0 |/dev/rdiskette0 |
+-----------------------------+-----------------------------+
|floppy1 |/dev/rdiskette1 |
+-----------------------------+-----------------------------+
|cdrom0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|zip0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|jaz0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
|rmdisk0 |/vol/dev/rdsk/cXtYdZ/label |
+-----------------------------+-----------------------------+
EXAMPLES
Example 1: Using the volrmmount command
When Volume Management finds a floppy that contains a filesystem, it calls rmmount to mount it. If you wish to run tar(1) or cpio(1) on
that floppy, it must first be unmounted. To unmount the floppy use:
example% volrmmount -e floppy0
After volrmmount unmounts the floppy, if you wish to re-mount it (rather than ejecting it and reinserting it) use:
example% volrmmount -i floppy0
Notice that if you are using a named floppy, you can use its name in place of floppy0.
FILES
/dev/volctl Volume Management control port
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWvolu |
+-----------------------------+-----------------------------+
SEE ALSO cpio(1), eject(1), tar(1), rmmount(1M), vold(1M), rmmount.conf(4), attributes(5), volfs(7FS)NOTES
Volume Management (vold) must be running to use this command.
SunOS 5.10 30 Aug 2000 volrmmount(1)