05-15-2011
10 More Discussions You Might Find Interesting
1. Linux
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)
Discussion started by: KDE Man
4 Replies
2. AIX
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)
Discussion started by: padawan75
5 Replies
3. Ubuntu
Is it possible to make multiboot partitions of Ubuntu and red hat Linux? (4 Replies)
Discussion started by: sito
4 Replies
4. Solaris
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)
Discussion started by: freeware
9 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: kryclear
3 Replies
6. UNIX for Dummies Questions & Answers
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)
Discussion started by: SmithJ
4 Replies
7. UNIX for Advanced & Expert Users
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)
Discussion started by: yifangt
3 Replies
8. Solaris
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)
Discussion started by: LittleLebowski
2 Replies
9. Solaris
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)
Discussion started by: TKD
1 Replies
10. OS X (Apple)
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 LINUX
mddb.cf
mddb.cf(4) File Formats mddb.cf(4)
NAME
mddb.cf - metadevice state database replica locations
SYNOPSIS
/etc/lvm/mddb.cf
DESCRIPTION
The /etc/lvm/mddb.cf file is created when the metadb(1M) command is invoked. You should never directly edit this file.
The file /etc/lvm/mddb.cf is used by the metainit(1M) command to find the locations of the metadevice state databases replicas. The metadb
command creates the file and updates it each time it is run. Similar information is entered in the /kernel/drv/md.conf file.
Each metadevice state database replica has a unique entry in the /etc/lvm/mddb.cf file. Each entry contains the driver and minor unit num-
bers associated with the block physical device where a replica is stored. Each entry also contains the block number of the master block,
which contains a list of all other blocks in the replica.
Entries in the /etc/lvm/mddb.cf file are of the form: driver_name minor_t daddr_t checksum where driver_name and minor_t represent the
device number of the physical device storing this replica. daddr_t is the disk block address. checksum is used to make certain the entry
has not been corrupted. A pound sign (#) introduces a comment.
EXAMPLES
Example 1: Sample File
The following example shows a mddb.cf file.
#metadevice database location file do not hand edit
#driver minor_t daddr_t device id checksum
sd 152 16 id1,sd@SSEAGATE_JDD288110MC9LH/a -2613
In the example above, the value for daddr_t indicates that the offset from the start of a given partition is 16 disk blocks from the start
of that partition.
FILES
/etc/lvm/mddb.cf
/kernel/drv/md.conf
SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metassist(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M),
md.cf(4), md.tab(4), attributes(5), md(7D)
Solaris Volume Manager Administration Guide
SunOS 5.10 8 Aug 2003 mddb.cf(4)