Sponsored Content
Full Discussion: Need to partition root
Operating Systems Solaris Need to partition root Post 302655033 by bhargav90 on Tuesday 12th of June 2012 03:51:13 PM
Old 06-12-2012
I have re-installed the OS and allocated 9 GB to the root and 2 GB other file system while installing but still i face the same problem.
By using the command format and partition i am getting the same error "out of range".
eg-
cylinder value for root ranges from [2 - 1031 root]
I am trying to create a partition from 1033 it gives me an error message "out of range"

Please suggest
 

10 More Discussions You Might Find Interesting

1. Solaris

Reinstall root partition

I had Solaris 8 installed on a Ultra 10 machine but during a shutdown the root partition got corrupted. I have 3 other partitions on the drive (var, swap, home). Is there a way to reinstall the root partition without effecting the other partitions? Also, when I run format from single user mode I... (4 Replies)
Discussion started by: jbestor
4 Replies

2. Shell Programming and Scripting

Disk space for root partition

Hello, I am trying to monitor disk space for each node on the machine. I am able to get all individual nodes but for the '/' node. For example: df -k: bash-2.05b# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/xxx 4127108 2415340 1502120 62% / /dev/yyy ... (3 Replies)
Discussion started by: chiru_h
3 Replies

3. Solaris

how to increase size of the root partition

Hi we have a sunfire v880 server . we have a problem with root partion it showing 90% full. so anyone can help me how to increase the size of that partion. NOTE: It is not in veritas & SVM control. Regards prakash (6 Replies)
Discussion started by: pshelke
6 Replies

4. Solaris

Can't metattach root partition

I'm mirroring up a T2000. Able to metainit and metattach all partitions with the exception of root. Getting the following error: metattach: <hostname>; c1t1d0s0; is mounted on / I'm stumped. By the way, target 1 is the boot disk. (7 Replies)
Discussion started by: Probos
7 Replies

5. Solaris

how to expand root partition size?

Dear All For installing an application that will seat under /opt , I need to increase my root partition size (/c0t0d0s0) . Can you please let me know how can I increase this partition size? Thank you (10 Replies)
Discussion started by: hadimotamedi
10 Replies

6. Solaris

increasing root / partition

Dear all, I have a root partition which is 20 G in size. I have var and /tmp as seperate file systems. But this 20 G of root is not sufficeint. I want to increase the size of the / partition. Is there any way to increase with out down time. my df -k output is Filesystem ... (4 Replies)
Discussion started by: jegaraman
4 Replies

7. Red Hat

increase root partition

i am using redhat 5.4 and my root size shows 98 %, how can i increase root size # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 77G 16G 75G 98% / /dev/sda1 2.4G 82M 2.2G 4% /boot tmpfs 3.8G 0 3.8G 0%... (8 Replies)
Discussion started by: reply.ravi
8 Replies

8. Solaris

Root partition filling up

I have a T1000 Sparc server that has a relatively small root partition which is 24Gb and a larger partition dedicated to /export/home that is approximately 100 Gb. We have a lot of data going to /var/audit and to /var/core/corefiles. Is there any non-destructive way to redirect files from... (4 Replies)
Discussion started by: goose25
4 Replies

9. SCO

Resize root partition

I have SCO Openserver 5.0.5 Root partition is 96% full and I would like to make it bigger. How can this be done? 1) Can I use 'dd' to backup 'root' and then backup '/u' to a third hard disk, then divvy the primary hard disk to have a larger 'root' filesystem (i.e. previous root + u) 2) ... (5 Replies)
Discussion started by: grips03
5 Replies

10. Ubuntu

Regarding OS partition and root user

Dear Concern, I am new in ubuntu. Is root user disable in ubuntu? Also, is os partition default in ubuntu? I don't find any feature to create customize mount point to install OS. Below is my current OS partition. amirislam@blnidapp03:~$ df -h Filesystem Size Used... (1 Reply)
Discussion started by: makauser
1 Replies
SYSTEMD-VERITYSETUP-GENERATOR(8)			   systemd-veritysetup-generator			  SYSTEMD-VERITYSETUP-GENERATOR(8)

NAME
systemd-veritysetup-generator - Unit generator for integrity protected block devices SYNOPSIS
/lib/systemd/system-generators/systemd-veritysetup-generator DESCRIPTION
systemd-veritysetup-generator is a generator that translates kernel command line options configuring integrity protected block devices (verity) into native systemd units early at boot and when configuration of the system manager is reloaded. This will create systemd- veritysetup@.service(8) units as necessary. Currently, only a single verity device may be se up with this generator, backing the root file system of the OS. systemd-veritysetup-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-veritysetup-generator understands the following kernel command line parameters: systemd.verity=, rd.systemd.verity= Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.systemd.verity= is honored only by the initial RAM disk (initrd) while systemd.verity= is honored by both the host system and the initrd. roothash= Takes a root hash value for the root file system. Expects a hash value formatted in hexadecimal characters, of the appropriate length (i.e. most likely 256 bit/64 characters, or longer). If not specified via systemd.verity_root_data= and systemd.verity_root_hash=, the hash and data devices to use are automatically derived from the specified hash value. Specifically, the data partition device is looked for under a GPT partition UUID derived from the first 128bit of the root hash, the hash partition device is looked for under a GPT partition UUID derived from the last 128bit of the root hash. Hence it is usually sufficient to specify the root hash to boot from an integrity protected root file system, as device paths are automatically determined from it -- as long as the partition table is properly set up. systemd.verity_root_data=, systemd.verity_root_hash= These two settings take block device paths as arguments, and may be use to explicitly configure the data partition and hash partition to use for setting up the integrity protection for the root file system. If not specified, these paths are automatically derived from the roothash= argument (see above). SEE ALSO
systemd(1), systemd-veritysetup@.service(8), veritysetup(8), systemd-fstab-generator(8) systemd 237 SYSTEMD-VERITYSETUP-GENERATOR(8)
All times are GMT -4. The time now is 09:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy