Sponsored Content
Full Discussion: Grub Issues ; Prominent.
Special Forums Hardware Boot Loaders Grub Issues ; Prominent. Post 302554588 by Corona688 on Monday 12th of September 2011 11:54:28 AM
Old 09-12-2011
Quote:
Originally Posted by fpmurphy
Probably because the added OS is on a different disk or partition.
Agreed... never blindly copy data from config files -- always understand its meaning first.

theKbStockpiler: It'd really help if you could post the entire file, as well as which entries do and don't work, so we don't have to guess.
 

10 More Discussions You Might Find Interesting

1. Linux

GRUB and windows XP

After playing a bit with GRUB I got it to boot my windows XP and my Fedora (yeay!). But now my windows became awfully slow (hd seems to be the problem). Does anybody have an idea what could cause this? settings: default=1 timeout=10 splashimage=(hd1,0)/grub/splash.xpm.gz title Fedora... (1 Reply)
Discussion started by: Micky
1 Replies

2. Linux

Remove GRUB

hello i just uninstall fedora core 4 and would like to remove the GRUB from my system. i try to use windows xp startup disk and tryout the fixmbr command. however the system warn me that my computer do not have a proper mbr and performing this action may make all partition in my harddisk... (5 Replies)
Discussion started by: wsc
5 Replies

3. Linux

grub help

in dual os grub will ask like this (linux 9 (red hat)) linux(bigmem) linux(smallmem) dos so i want that grub will ask like this dos linux(bigmem) linux(smallmem) how to do this (8 Replies)
Discussion started by: seshumohan
8 Replies

4. UNIX for Dummies Questions & Answers

grub problem- keeps rebooting as soon as it tries to do grub

Hi, I installed solaris 10 a few weeks ago. It was working fine during the past two weeks. However, now when I start to load to the drive, I get this problem: The BIOS screen comes up like normal, then screen goes blank and a message "Grub loading stage 2" flashes real quick then the computer... (1 Reply)
Discussion started by: moesays
1 Replies

5. Linux

Grub.Conf

Hi, During the Initial startup of the Linux machine. Grub.conf has a entry to mount the root partition as read only after the initialistation of the Kernel. Is there any specific reason for this or the root partition can be made to mounted with read write options. Regards Arun (1 Reply)
Discussion started by: Arun.Kakarla
1 Replies

6. Solaris

grub problem

hi , was using solaris in dual boot with xp , then I ' ve installed ubuntu too . The solaris grub has been in some way damaged , maybe because during the linux installation i've delete an old partition that I was not using by some months. It's normal that the solaris grub has been overriden by... (7 Replies)
Discussion started by: freeware
7 Replies

7. Red Hat

Can we specify which grub.conf to use in grub-install.

Hi, Can we specify which grub.conf to use while installing grub on RHEL. We are working on application which requires different grub configurations needed, depending on certain criteria we need to update grub with correct grub.conf. Can we use grub-install for this purpose? (4 Replies)
Discussion started by: successlin
4 Replies

8. UNIX for Dummies Questions & Answers

"/boot/grub/grub.conf" VS "/etc/grub.conf"

can someone please explain me the difference between these two files: "/boot/grub/grub.conf" and "/etc/grub.conf" .. (7 Replies)
Discussion started by: stunn3r
7 Replies

9. Debian

Cannot install GRUB

Hello, I cannot install grub to my ESP it seems. I have a PC with both Windows 8.1 and Debian installed and I can only boot into Windows since GRUB is not installed on my PC. I am using a Ubuntu Live USB to install GRUB on /dev/sda1 (my ESP). I am using the following commands from Ubuntu... (12 Replies)
Discussion started by: sreyan32
12 Replies

10. Linux

Grub password

what if grub had a password and prevented you from getting in, what should I do, regards (2 Replies)
Discussion started by: abbya
2 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible. This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes referring the disk are restarted. This reattach action is performed by calling the volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 05:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy