TRU64 - Cluster boot partition is FULL

 
Thread Tools Search this Thread
Top Forums UNIX for Beginners Questions & Answers TRU64 - Cluster boot partition is FULL
# 1  
Old 07-27-2016
TRU64 - Cluster boot partition is FULL

Good day,

Anybody, know how to clean/free up the Cluster_boot partition in TRU64


Thank you in advance
Miaka
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

PowerHA(HACMP) full vg loss - cluster hangs on release_vg_fs event

Hello, AIX 6.1 TL7 SP6 POwerHA 6.1 SP10 I was experimenting with new hacmp build. It's 3-node cluster build on AIX 6.1 lpars. It contains Ethernet and diskhb networks. Shared vg disk is SAN disk. Two nodes see disk using vscsi, third node sees disk using npiv. Application is db2 server. ... (4 Replies)
Discussion started by: vilius
4 Replies

2. HP-UX

/var partition full need help

My /var partition is almost utilized ... Here am not sure where to release space now OS/model : HP-UX B.11.11 U 9000/800 # bdf /var Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol9 6144000 6142176 1824 100% /var <root@pb>/var # du -sk * | sort -n |... (20 Replies)
Discussion started by: Shirishlnx
20 Replies

3. HP-UX

effect of full root partition on server

hi, I want to know that "What Happen if the root partition gets full on the server? I have HP-Unix 11.11 installed. (3 Replies)
Discussion started by: majidtahir
3 Replies

4. Filesystems, Disks and Memory

Tru64 Unix (HP) - copy file from 2nd HD to Boot HD

Hi, Here is some of the setup information on system: Tru64 UNIX OS and Two Hard Drives installed. One drive is boot drive and other is spare (Spare drive currently has some back up information on it). here is just a couple of the device/partition/mount points on boot drive. /dev/rz0a on... (4 Replies)
Discussion started by: willirb1
4 Replies

5. UNIX for Advanced & Expert Users

Supported but not advertised 1000baseT/Full only in one node of RH cluster

Hello all, I have two twins Proliant DL580 G3 with RHEL4U4 clustered with Oracle RAC with two nics working in each one. All nics have the same firmware, driver and type of physical cable connected (Cat 5E). All ports of the switch have the same configuration but only one of the nics of only... (9 Replies)
Discussion started by: RuBiCK
9 Replies

6. UNIX for Advanced & Expert Users

Hard-disk partition is Full problem?

HI, Currently I am working in One of the webhosting company and I found on one of my server "/home" partition is getting full say 105% usage... But when I actually check the partition size using "du -h", exact partition utilization is only 60-70%. So... (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies

7. UNIX for Dummies Questions & Answers

Full Partition?

Hi Everyone, I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
Discussion started by: Choppy
2 Replies

8. UNIX for Dummies Questions & Answers

Cannot boot Tru64

Hi, I just got an AlphaServer DS10 in my lap with a note 'Fix it !'. It's just that I'm not very good with unix. Anyways, it seems like the osf_boot file is missing from root. I can boot the server in singel user mode with the Tru64 5.1 cd and from there open a console window. When I checked... (0 Replies)
Discussion started by: magher
0 Replies

9. UNIX for Advanced & Expert Users

root partition full and problem start

We have SunOS 5.7 m/c. Following is the situation and problem what we are facing - - The root partition was full. - No login was possible on server (not from console also) - M/c was power swithced off - After this only console login is possible. FTP is possible. No telnet is possible. I... (1 Reply)
Discussion started by: rahul72
1 Replies

10. Filesystems, Disks and Memory

root partition was full and problem start

We have SunOS 5.7 m/c. Following is the situation and problem what we are facing - - The root partition was full. - No login was possible on server (not from console also) - M/c was power swithced off - After this only console login is possible. FTP is possible. No telnet is possible. I... (3 Replies)
Discussion started by: rahul72
3 Replies
Login or Register to Ask a Question
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD