Sponsored Content
Operating Systems HP-UX Creating a bootable disk in 9.10 Post 302210500 by vbe on Tuesday 1st of July 2008 05:21:14 AM
Old 07-01-2008
Start by seing what is on your boot disk:

On a 10.20 I get:
civ:/home/vbe $ lifls -l /dev/dsk/c1t6d0
volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13
filename type start size implement created
===============================================================
ODE -12960 584 848 0 01/10/11 16:50:53
MAPFILE -12277 1432 128 0 01/10/11 16:50:53
SYSLIB -12280 1560 353 0 01/10/11 16:50:53
CONFIGDATA -12278 1920 231 0 01/10/11 16:50:53
SLMOD -12276 2152 132 0 01/10/11 16:50:53
SLDEV -12276 2288 202 0 01/10/11 16:50:53
SLDRIVERS -12276 2496 475 0 01/10/11 16:50:53
SLSCSI -12276 2976 117 0 01/10/11 16:50:53
MAPPER -12279 3096 233 0 01/10/11 16:50:53
IOTEST -12279 3336 208 0 01/10/11 16:50:53
PERFVER -12279 3544 198 0 01/10/11 16:50:53
PVCU -12801 3744 64 0 01/10/11 16:50:53
SSINFO -12286 3808 2 0 08/06/26 18:01:07
ISL -12800 3816 240 0 96/05/28 04:10:13
AUTO -12289 4056 1 0 96/05/28 04:10:13
HPUX -12928 4064 848 0 96/05/28 04:10:13
LABEL BIN 4912 8 0 07/11/13 10:33:09
civ:/home/vbe $

On a 9.XX you should see at least:
SYSHPUX
SYSDEBUG
SYSBACKUP
SYSTEST
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Bootable disk

I have a SCO Openserver 5.0.6 running Raid 5. and want to make a bootable disk but the boot image is 5MB ie unix file on root is around 5M and the size is obviously too large for a floppy diskette. Please help on how I can make any bootable device. The aim is to change the filesystem size. ... (6 Replies)
Discussion started by: sshokunbi
6 Replies

2. UNIX for Dummies Questions & Answers

recover DIsk and make bootable

Hello all, I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 Replies

3. HP-UX

Size of LVM header in non bootable disk

hi, i have a query regarding the size of the LVM header. Since the LVM header of a bootable disk is always 2912KB. The header size of a non bootable disk is not fixed. In Bootable disk after the LVM header (2912 KB=5824 sectors)the user data starts or we can say LV extents starts. If i extend any... (0 Replies)
Discussion started by: gorayen
0 Replies

4. BSD

Creating a bootable CD

Hi to all, Iam using FreeBSD 5.4. I want to write a kernel file with an option "CD9660_ROOT" in it. When i start to compile this kernel, it gives a message "unknown option CD9660_ROOT". Could anyone hellp with this as soon as possible. Bye, tadakamalla (3 Replies)
Discussion started by: tadakamalla
3 Replies

5. Solaris

How to make a bootable disk?

The second disk that I'm trying to make bootable is to hold another version of Solaris (9). I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories. ...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies

6. Filesystems, Disks and Memory

Make non-bootable scsi drive, bootable

In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible: 1) Make the non-bootable scsi drive bootable? How? 2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive? I seek... (1 Reply)
Discussion started by: bfisk
1 Replies

7. Red Hat

Looking for help with creating bootable USB key

I am currently trying to create a bootable USB key that I can use to boot a couple different X86 single slot processors. Creating a basic key is as easy as can be but I am looking to customize this boot image to meet two important criteria: 1. The system must boot in text only mode as my only... (4 Replies)
Discussion started by: kingfish1760
4 Replies

8. Linux

Creating a bootable dvd/cd disk

Hi all, thanks for so many helps in many problems! Can anyone guide, how to create a bootable cd/dvd from downloaded iso images of CentOS 5? I have collected all the iso in a dvd but it is not booting the system. Any response will be appreciable... (2 Replies)
Discussion started by: naw_deepak
2 Replies

9. Red Hat

Trouble creating RHEL 6.5 bootable image with custom kickstart file

Hi everyone, I have a custom kickstart file from a software vendor and I'm trying to package that with a RHEL 6.5 and then attach it to a VM and install RHEL with the settings in the kickstarter file. I'm doing this from a windows PC using an app called InfraRecorder. I've extracted the... (0 Replies)
Discussion started by: 911Eric
0 Replies
SYSTEMD-GPT-AUTO-GENERATOR(8)				    systemd-gpt-auto-generator				     SYSTEMD-GPT-AUTO-GENERATOR(8)

NAME
systemd-gpt-auto-generator - Generator for automatically discovering and mounting root, /home and /srv partitions, as well as discovering and enabling swap partitions, based on GPT partition type GUIDs. SYNOPSIS
/lib/systemd/system-generators/systemd-gpt-auto-generator DESCRIPTION
systemd-gpt-auto-generator is a unit generator that automatically discovers root, /home, /srv and swap partitions and creates mount and swap units for them, based on the partition type GUIDs of GUID partition tables (GPT). It implements the Discoverable Partitions Specification[1]. Note that this generator has no effect on non-GPT systems, or where the directories under the mount points are already non-empty. Also, on systems where the units are explicitly configured (for example, listed in fstab(5)), the units this generator creates are overridden, but additional implicit dependencies might be created. This generator will only look for root partitions on the same physical disk the EFI System Partition (ESP) is located on. It will only look for the other partitions on the same physical disk the root file system is located on. These partitions will not be searched on systems where the root file system is distributed on multiple disks, for example via btrfs RAID. systemd-gpt-auto-generator is useful for centralizing file system configuration in the partition table and making manual configuration in /etc/fstab or suchlike unnecessary. This generator looks for the partitions based on their partition type GUID. The following partition type GUIDs are identified: Table 1. Partition Type GUIDs +-------------------------------------+--------------------------------+--------------------------------------+ |Partition Type GUID | Name | Explanation | +-------------------------------------+--------------------------------+--------------------------------------+ |44479540-f297-41b2-9af7-d131d5f0458a | Root Partition (x86) | On 32-bit x86 systems, the first x86 | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |4f68bce3-e8cd-4db1-96e7-fbcaf984b709 | Root Partition (x86-64) | On 64-bit x86 systems, the first | | | | x86-64 root partition on the disk | | | | the EFI ESP is located on is mounted | | | | to the root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |69dad710-2ce4-4e3c-b16c-21a1d49abed3 | Root Partition (32-bit ARM) | On 32-bit ARM systems, the first ARM | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |b921b045-1df0-41c3-af44-4c6f280d3fae | Root Partition (64-bit ARM) | On 64-bit ARM systems, the first ARM | | | | root partition on the disk the EFI | | | | ESP is located on is mounted to the | | | | root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |993d8d3d-f80e-4225-855a-9daf8ed7ea97 | Root Partition (Itanium/IA-64) | On Itanium systems, the first | | | | Itanium root partition on the disk | | | | the EFI ESP is located on is mounted | | | | to the root directory /. | +-------------------------------------+--------------------------------+--------------------------------------+ |933ac7e1-2eb4-4f13-b844-0e14e2aef915 | Home Partition | The first home partition on the disk | | | | the root partition is located on is | | | | mounted to /home. | +-------------------------------------+--------------------------------+--------------------------------------+ |3b8f8425-20e0-4f3b-907f-1a25a76f98e8 | Server Data Partition | The first server data partition on | | | | the disk the root partition is | | | | located on is mounted to /srv. | +-------------------------------------+--------------------------------+--------------------------------------+ |0657fd6d-a4ab-43c4-84e5-0933c84b4f4f | Swap | All swap partitions located on the | | | | disk the root partition is located | | | | on are enabled. | +-------------------------------------+--------------------------------+--------------------------------------+ |c12a7328-f81f-11d2-ba4b-00a0c93ec93b | EFI System Partition (ESP) | The first ESP located on the disk | | | | the root partition is located on is | | | | mounted to /boot or /efi, see below. | +-------------------------------------+--------------------------------+--------------------------------------+ The /home and /srv partitions may be encrypted in LUKS format. In this case, a device mapper device is set up under the names /dev/mapper/home and /dev/mapper/srv. Note that this might create conflicts if the same partition is listed in /etc/crypttab with a different device mapper device name. Mount and automount units for the EFI System Partition (ESP) are generated on EFI systems. The ESP is mounted to /boot, unless a mount point directory /efi exists, in which case it is mounted there. Since this generator creates an automount unit, the mount will only be activated on-demand, when accessed. On systems where /boot (or /efi if it exists) is an explicitly configured mount (for example, listed in fstab(5)) or where the /boot (or /efi) mount point is non-empty, no mount units are generated. When using this generator in conjunction with btrfs file systems, make sure to set the correct default subvolumes on them, using btrfs subvolume set-default. systemd-gpt-auto-generator implements systemd.generator(7). SEE ALSO
systemd(1), systemd.mount(5), systemd.swap(5), systemd-fstab-generator(8), systemd-cryptsetup@.service(8), cryptsetup(8), fstab(5), btrfs(8) NOTES
1. Discoverable Partitions Specification https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/ systemd 237 SYSTEMD-GPT-AUTO-GENERATOR(8)
All times are GMT -4. The time now is 07:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy